ApexSQL Monitor alerts

Applies to
ApexSQL Monitor

Summary
This article explains how to manage alerts in ApexSQL Monitor.

Description

Alerts in ApexSQL Monitor notify you about potential and ongoing performance issues with your machines, SQL Server instances, and databases. Alerts can be configured for each monitored machine, SQL Server instance, and/or database.

ApexSQL Monitor alerts enable you to configure three threshold values: low, medium, and high, as well as the period for metric capturing. The default period for metric capturing is predefined by ApexSQL and it depends on the type of the metric. The minimal value for the time period is 1 s. Keep in mind that increasing this value can delay the metric collecting and make monitoring slower, while decreasing the value could improve precision but also severely increase the amount of data collected and thus impose additional load on the repository database and application.

Alerts are grouped into three categories, based on their severity. Each alert severity is indicated by its status color.

As alerting is configurable, ApexSQL Monitor offers default values for the thresholds where applicable, but custom values can also be set.

If the metric has no default threshold values set due to the nature of metric (for example setting data and log file size thresholds for your databases may not make sense), the threshold values are shown as N/A.

Default threshold values are based on general recommendations and they might not apply to your monitoring goals and environment requirements. A huge number of alerts can be created, or some critical situations ignored if the thresholds are not adjusted to your specific environment.

How to set alerts in ApexSQL Monitor?

By default, ApexSQL Monitor enables alerting for the most important SQL Server performance metrics, like Buffer cache hit ratio, Deadlocks per second, Lock requests per second etc. For the rest of the metrics, like Batch requests per second and Compilations per second, must be enabled manually. Alerting can also be disabled for any of the metrics where alerting is enabled by default.

  1. Click the Configuration link in the main menu
  2. In the tree-view on the left, select the group or SQL Server instance for which you want to configure alerts
  3. Select the Alerting check-box to enable alerting for desired metrics, or the top checkbox to enable alerting for all metrics at once
  4. Enter the values for metric thresholds

  5. Entering the values for metric thresholds

  6. Click the Save button above the configuration grid

Quick tip icon

Quick tip:

To set identical alert thresholds for all databases on a SQL Server instance, select the SQL Server instance in the Servers list, scroll to the bottom of the metric list, and specify the thresholds in the Database measurements section. Use a similar method to specify identical alert thresholds for all SQL Server instances on a machine.

How to change ApexSQL Monitor alert settings?

Once alerting is set, it can be changed in the Configuration page, using the same steps followed for setting the alerts.

A list of raised alerts

The Alert link in the main menu will open the Alerts page where the user can review alerts that have been raised on specific/all SQL Server instances depending on what is selected in the tree-view.

Dialog showing a list of raised alerts in ApexSQL Monitor

Displayed alerts are grouped by date and by default alerts for last 24 hours are displayed. User can change period for which alerts are displayed from the drop-down menu by selecting the last 7 days and All.

To display alerts for a specific period of time, select the custom dates checkbox and select the time period using the date/time pickers to define From and To date time for displaying raised alerts.

For each severity level, the number of raised alerts is shown next to the filter checkboxes. Select/unselect the alert severity filter checkboxes to filter out unwanted severity from the displayed list of alerts.

How to clear alerts?

An alert remains active until it is resolved. After the alert is handled by a DBA it should be resolved.

To resolve multiple alerts at once, select the adequate check boxes in the grid and click the Resolve button above the grid.

Figure showing how to resolve multiple ApexSQL Monitor alerts

To resolve individual alert with more details including the comments, select the specific alert name. This will open the details page for that alert. Here the alert can be resolved using one of the offered resolutions: Ignored, Fixed, Known issue. The Not resolved option is here to provide information that alert is reviewed but no solution was found yet

Also, the comment for resolved alert is obligatory by default. This can be changed in the AdministrationAlert options page by unchecking the Force comments on resolve checkbox

By selecting the Generate report on resolve and selection one of the offered report format (PDF, Excel or Web archive), report will be automatically generated for resolved alert and offered to be saved in the file system

ApexSQL Monitor will generate a new alert when the metric reached its predefined value again.