Back End Alerts and Triggers

Overview

Monitors are back end application components that listen for specific events and then trigger notifications. Unlike Edge Delta pipelines, they reside in the centralized Edge Delta back end. This gives them access to aggregated data across all environments.

See Quickstart: Create a Monitor for a quickstart guide to creating a monitor to alert on thresholds.

Monitor List

Click Monitors and select the List tab.

The monitors List page lists all existing monitors and their current state. It displays the following columns:

• Priority: The priority level of the monitor.
• Status: The current state of the monitor.
• Snoozed: Indicates if the monitor is currently snoozed.
• Name: The name of the monitor.
• Type: The monitor type (Metric Threshold, Log Threshold, etc.).
• Actions: Options to manage the monitor.

There are four states (status) that a monitor can be in:

• Alert: The monitor has detected a breach of its configured Alert threshold.
• Warning: The monitor has detected a breach of its configured Warning threshold.
• OK: The monitor has not detected a breach of any configured thresholds. This includes cases where source data exists but none meets the monitor’s conditions.
• No Data: The monitor enters this state when:
  • There is absolutely no data for the entire evaluation window, or
  • More than 25% of the data is missing within the evaluation window (when “Require Full Window” is enabled)
  • When “Require Full Window” is disabled, the monitor only enters No Data state if all data buckets are missing (100% tolerance)

Triggered List

Click Monitors and select the Triggered tab.

The Triggered tab shows monitors in the Alert, No Data, or Warning state. It displays the following columns:

• Status: The current state of the monitor.
• Snoozed: Indicates if the monitor is currently snoozed.
• Name: The name of the monitor.
• Type: The monitor type (Metric Threshold, Log Threshold, etc.).
• Group: The group-by dimension values that triggered the alert.
• Triggered: When the monitor entered its current state.
• Actions: Options to manage the monitor.

Manage Monitors

You click the kebab (three vertical dots) menu in the Actions column to make changes to the monitor, mute it, or see the events matching its monitoring criteria.

Monitor Limits

Monitors have the following operational limits:

Group By Limits

When using Group By to split monitor evaluations by dimensions like k8s.pod.name or service.name, there is a limit on the number of unique group combinations that can trigger alerts simultaneously per minute:

For example, if you have a Log Threshold monitor grouped by k8s.pod.name and 100 pods are sending data that would trigger an alert, only the top 50 will fire alerts at the same time.

Group Value Length Limit

When you configure a monitor with Group By dimensions, Edge Delta concatenates those values into a single string like k8s.pod.name:my-pod-name,service.name:payment-service. This combined string is limited to 942 bytes. If your combined group-by values exceed this limit, they are truncated in the Monitor Status page and in notifications.

Slack Notification Limit

When sending notifications to Slack, the message body is truncated to 3,000 characters. If the message exceeds this limit, it is truncated and appended with ... *(truncated due to slack character limit)*.

Create Monitors

See Monitors for information on creating a Monitor.