Page History

The Alert Configuration window allows you to set up alerts for specific SQL Server SQL Server instances. To open the Alert Configuration window with a SQL Server instance selected, right-click the instance, and then select Configure Alerts. You can set the acceptable thresholds using the following alert types:

In addition to setting the thresholds for specific alerts, you can customize your alerts by adding comments to each alert. Comments allow you to include instructions to users when a level reaches a particular threshold or to provide additional information about the alert. You can also customize the levels at which SQL Diagnostic Manager provides alert notifications by changing the informational, warning, and critical values either on the Configuration tab of the Alert Configuration window or, for the database- and disk-level alerts, on the Database Threshold Configuration window available by selecting the database or disk , and then clicking Edit.

You can also base your alerts on the past performance of the metrics collected by the SQL Diagnostic Manager. This is a powerful and effective way to make sure that the alerts you receive are outside of your typical metric ranges.

...

1. Right-click a SQL Server instance in the Servers treesidebar.
2. Select Configure Alerts.
3. Select the metric you want to edit from the list in the Alert Configuration window.
4. If the metric features a per-database or per-disk alert, on the Configuration tab of the Alert Configuration window, click Add. Use the drop-down list to select the database or disk to which you want to apply these settings. If the metric applies at the instance level, continue with the next step.
5. Check the boxes next to Informational, Warning, and Critical to include alerts for these states.
6. Change the alert thresholds by moving the arrows to the appropriate levels or by double-clicking the value and typing a new threshold level.
7. If the metric features a per-database or per-disk alert, click Advanced to apply any advanced settings, such as alert suppression or autogrow settings. Click OK. If the metric applies at the instance level, continue with the next step.
8. Select the Comments tab and enter the information you want displayed to display in the alert message for this metric.
9. Click Apply.
10. If you want to replicate these edits to other SQL Server instance SQL Diagnostic Manager is monitoring, tags, or templates, click Yes.
11. Click OK to accept your changes.

...

A full refresh of alerts excluding table fragmentation occurs in the following circumstances even if longer collection intervals are defined:

• when When the collection service starts
• when When the collection service receives a new workload, such as redirecting the Management Service to a new Repository
• when When you add a SQL Server SQL Server for collection
• when When a SQL Server SQL Server resumes from Maintenance Mode
• when When a user selects Refresh Alerts

This refresh does not cause the collection of non-alertable data, nor cause the collection of anything that is disabled.

...

Because this data collection occurs at most once per day and you can configure it to run as infrequently as once per week, you may experience a significant delay before new alerts are generated with your new alert threshold. You can  configure your wait monitoring using the Monitored SQL Server Properties window.

...

SQL Diagnostic Manager allows you to configure generic alert settings as a template that you can apply to servers and groups of servers in your organization. Click Tools Image Added > Alert Configuration Templates and complete the required fields to  configure an alert template.

...

Informational alerts allow you to set a threshold that , when generated , triggers a status that does not affect the overall status of the server within SQL Diagnostic Manager. You can use informational alerts to notify an administrator of the state of a particular metric for a server or trigger secondary processes that could take action to prevent issue escalation.