Configuring and managing alerts

1. On the sidebar, click Settings.
2. Click Alerts > New Alert

   

3. Enter a unique and descriptive Name for your alert.
4. Select the Eventsto be alerted about:
   • Alert on event(s): Click Add events to explicitly select the events to be alerted about. Preconfigured events are available for selection in the Events table and can be filtered by:
     • Type: Built-in or custom events.
     • Incidents & Severity: Incidents, Warning, or Critical.
     • Entity type: Monitored technology currently supported.
     • State: Enabled or disabled.
     • Free-text filter (Search)
     Select all or a subset of events and click Add events.
     Note: Deleting all events linked to an alert would also delete the alert. This is done to avoid stale alert configurations.

     

   • Alert on event type(s): Select the event types that you want to be alerted for from the available list. Any event matching one of the selected types triggers an alert, assuming it matches the configured scope. The following types can be selected:
     • Incidents
     • Critical issues
     • Warning issues
     • Changes
     • Online
     • Offline
     • Monitoring issues
   • Alert on application Smart Alert(s): Click Add Smart Alerts to explicitly select the Smart Alerts to be alerted about. Preconfigured Smart Alerts are categorized by Global Application Smart Alerts and Application Smart Alerts. Both types of Smart Alerts can be filtered by using the Search (free-text filter) field.

     Select the required alerts and click Select Smart Alerts.

5. Select a Scope to filter the events further.
   • Application perspective: Select a particular Application by clicking Add application perspectives. For example, to be notified for events of the application App Test, select the application App Test from the list of currently configured applications and click Add.
   • Selected entities only (Dynamic Focus Query): Filter for specific events based on a Dynamic Focus query by configuring a query the query. For example, to be notified of events affecting the prod zone of the monitored system, specify the query entity.zone:prod.
   • All available entities: All events that match the event types riteria in section 2 will trigger an alert, regardless of on which entity they are detected. For large systems this option can lead to many alerts being sent out. An estimate of the number of events matching the configuration can be found just as follows the drop-down.
6. Configure the Alertingdetails. Select which alert channels are to be notified about the alert and select whether the entity name is to be included in the alert title.
   • Click Add alert channels to select from the list of preconfigured channels. When you have selected the required channels, click Add. For more information about creating an alert channel, see Setting up alert channels.
   • Select Include entity name in alert title under Alert Title to add more context to any created alert by including the name of the entity that triggered the event in the alert title.
7. (Optional) Include any extra Custom payloads to the alert notification.
   • Global custom payloads are configured on a separate page in the Settings. These payloads are included in all notifications with the matching key-value pairs. For more information, see Configure Custom Payload Globally.
   • For Alert-specific custom payloads, click Add row to configure the key and value pairing for the payload. Alert-specific custom payloads support the following value types:
     • Static: A fixed textual value
     • Dynamic: Dynamic values that can be either tags or metrics:
       • Tags: Tag-based dynamic values (similar to global custom payload configuration)
       • Metrics: Time-series metric values from infrastructure or application sources. For more information, see Metric-based custom payloads

   Both global custom payloads and alert-specific custom payloads are included in alert notifications if applicable. However, alert-specific configuration has priority over the global configuration. As a result, if both configurations use the same key, the alert-specific custom payload value overrides the global custom payload.

   

8. Click Create to save the new alert.

Alert-specific custom payloads can include time-series metric values from both infrastructure and application sources. You can include current metric values (such as CPU usage, memory consumption, application call counts, or latency) directly in your alert notifications, providing immediate context about the system state when the alert triggered.