Best Practices for SCOM Monitoring of Exchange and SQL Server

Question

What are some best practices and key considerations when utilizing SCOM to monitor Exchange and SQL Server? How can SCOM be used to monitor key metrics, proactively detect potential issues, and generate actionable insights for maintaining the stability and reliability of these critical applications?

Additionally, what are the recommended approaches for fine-tuning SCOM monitoring rules, creating custom alerts, and integrating monitoring data from Exchange or SQL Server into centralized reporting and analysis within SCOM?

Accepted Answer

Hi,

Utilizing SCOM to monitor Exchange and SQL Server involves several best practices and key considerations to ensure effective monitoring and management.

Here are some insights and recommendations:

Exchange: Use the Exchange Server Management Pack to monitor the health, performance, and availability of Exchange servers. This pack includes rules and monitors for key metrics like mailbox database availability, mail flow, and server health.
SQL Server: Use the SQL Server Management Pack to monitor SQL Server instances, databases, and related components. This pack covers metrics such as database size, transaction log usage, and SQL Agent job status1.

Customize the default thresholds and rules in the management packs to suit your environment. This helps in reducing noise from unnecessary alerts and focusing on critical issues.

Use overrides to adjust the behavior of monitors and rules for specific servers or databases. This allows for more granular control and tailored monitoring.

Monitoring-your-servers-and-databases-scom-and-sql-monitor

Getting started with Exchange Server 2013 Management Pack

If you have any specific scenarios or further questions, feel free to ask!

Share via

Best Practices for SCOM Monitoring of Exchange and SQL Server

0 additional answers

Your answer