Things to Consider When Configuring Monitoring and Alerting in SCOM 2007 R2
The following are best practices when setting up monitoring and alerting in OpsMgr 2007 R2:
► If there are users who will receive alerts but not have access to the Web console, create a notification channel that doesn’t include an alert link in the body of the SMTP message.
► Before performing maintenance work on Operations Manager itself, disable notification subscriptions. That prevents alerts from being generated during the maintenance.
► When creating new rules and monitors, create them as disabled by default. Then create overrides to enable the rules and monitors for specific instances of objects.
► Use the Look For feature of the console when searching for discoveries, monitors, and rules to override or edit.
► Be sure to back up custom management packs, Management Pack Templates, and override management packs using the Export Management Pack function.
► Take the time to explore, configure, and tune any management packs that are deployed. Each management pack operates differently and has different tuning requirements to optimize its performance.
► Be sure to keep the management packs updated, as Microsoft routinely releases updates to the core management packs.
► Use Management Pack Templates to create monitoring for web applications, database sources, services, processes, and ports.
► Use the distributed application to create application models for monitoring, alerting, and reporting on custom applications.
► Create custom management packs with the Authoring Console for more sophisticated applications or for publication.
This posting is 1 of a monthlong series of postings on the Microsoft System Center family of products. This is an excerpt from my book “System Center Enterprise Unleashed” with more postings on the System Center family of products up at http://www.networkworld.com/community/morimoto
