Alert Query form

You can combine similar alerts that meet specific criteria for a particular service by creating an alert query.

Table 1. Alert Query form

Field	Description
Name	The alert query name.
Business criticality	The importance of this alert query to the business. This field can determine disaster recovery strategies for this alert query. 1: most critical 2: somewhat critical 3: less critical 4: not critical
Used for	The purpose of the alert query. Select from: Production (Default) Staging QA Test Development Demonstration Training Disaster recovery
Owned by	The party that is responsible for the alert query.
Email	The email alias for the alert query.
Business phone	The phone number for the business.
Operational status	The status of the alert query. Operational: The alert query is running. Impact calculation runs only on alert queries in the Operational status. Select this option to use this service. If you customized preconfigured options for this category, select the option whose value is set to 1. Event Management calculates impact only on services in use. If you do not want to use this service now, select one of these options: Non-Operational: The alert query is unavailable, disabled, or down. Repair in progress: The alert query is receiving maintenance. DR Standby: The alert query is available as a disaster recovery (DR) standby. Ready: The alert query is prepared for use. Retired: The alert query is withdrawn from active use.
Comments	Any additional notes and information.
Service Group Members	The service group which contains this service.
Filter	The conditions for sending a notification to the alert query. The conditions must meet the alert values. Note: When defining an alert query filter, include only fields that appear in the Alert Histories [em_alert_history] table. Impact calculation is based on Alert History data and fields such as Overall Event Count, Priority, and Priority group are not copied to the Alert Histories [em_alert_history] table. Do not specify a dynamic time condition. For example, in the filter, do not specify Created condition of Last 45 minutes because impact calculation is triggered by a change of alert or alert query. However, for the dynamic time condition, none of these conditions have changed. Some filters may slow down impact calculation. To solve this problem, adjust your alert query by adding an appropriate index, as described in Index suggestions for slow queries.