For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
This topic explains how to set alerts for LaunchDarkly’s observability features. Alerts are a way to keep members of your organization aware of what is happening in your application. You can set alerts based on sessions, errors, logs, or traces, or when important conditions are met.
LaunchDarkly supports two alert types:
Constant alerts trigger when a metric crosses a value threshold you define (for example, error count above 100).
Anomaly alerts trigger when LaunchDarkly detects unusual behavior or patterns in your observability data.
Add an alert
To add a new alert based on your LaunchDarkly observability data:
Open the Telemetry section and navigate to the Alerts list.
Click Create new alert.
Enter an Alert title.
Select a Source to query. You can add alerts based on data from any of the following:
logs
traces
sessions
errors
events
observability metrics
Alert events come from session replay
In the alert configuration, “events” refer to track, click, and navigate events that occur in a session replay.
(Optional) Enter Filters to filter out data points from your selected source before aggregating. For example, if you only want to generate alerts from data in the production environment, set the environment filter. To learn more about the filter syntax, read Search specification.
(Optional) Select a Function from the dropdown to determine how data points are aggregated. If you choose a function that requires a parameter, such as “Min,” select the attribute to use as well. Functions are not available for all sources.
(Optional) Enable the Group by toggle to group your query results into separate series. For example, you might group your logs by level. Grouping is not available for all sources.
Select the Alert threshold type: Constant (threshold-based) or Anomaly (detects unusual patterns in your data).
(Optional) Create a message template for the alert using Markdown and a set of variables.
(Optional) Click + Add notification. Select the destinations for notifications when the threshold is met or an anomaly is detected.
Click Save.
Constant alert configuration
Here is an example of the configuration panel for an alert with a constant threshold:
Select whether the Alert conditions are met above or below your threshold.
Set the Alert threshold to a number of your choice.
Set the Alert window. This is the time range for which data points are searched and aggregated. Shorter windows can help if you need to be alerted quickly about an issue, while longer windows can help reduce noise by aggregating across a longer time range.
Set the Cooldown period. After the initial notification, additional notifications will not be sent for this amount of time. If the alert condition still exists after the cooldown, another notification will be sent.
(Optional) Set the Evaluation delay (min) to delay evaluating the alert until some period of time after the alert window closes. Using an evaluation delay helps you to capture relevant alert data that may arrive late from the configured event source. The configuration panel shows a caution icon when data from the selected source has been received with regular delays. Hover on the icon to view a percentile breakdown of delay durations.
The configuration panel for a constant alert, showing ingest delay.
Anomaly alert configuration
Here is an example of the configuration panel for an alert with an anomaly threshold:
Select whether the Alert conditions are met above, below, or outside your threshold.
Set the Alert threshold to the confidence level of the anomaly prediction (a higher confidence is more likely to be an anomaly).
Set the Alert window. This is the time range for which data points are searched and aggregated. Shorter windows can help if you need to be alerted quickly about an issue, while longer windows can help reduce noise by aggregating across a longer time range.
Set the Cooldown period. After the initial notification, additional notifications will not be sent for this amount of time. If the alert condition still exists after the cooldown, another notification will be sent.
(Optional) Set the Evaluation delay (min) to delay evaluating the alert until some period of time after the alert window closes. Using an evaluation delay helps you to capture relevant alert data that may arrive late from the configured event source. The configuration panel shows a caution icon when data from the selected source has been received with regular delays. Hover on the icon to view a percentile breakdown of delay durations.
The configuration panel for an anomaly alert.
Configure an alert
To change the configuration for an alert:
Navigate to Alerts in the left navigation. A list of all alerts appears.
Click Configure on the panel for that alert.
The “Edit” page appears. Update the source, threshold, or notification.
Click Save.
Alert notifications
Alert notifications can be added with the + Add notification button when configuring an alert.
Member notifications
Member notifications are sent via email to each member added to the alert. If you have the LaunchDarkly Slack app, they are also sent through Slack.
Slack notifications
You can send alert notifications to Slack channels. To use Slack alerts:
Sign into LaunchDarkly with the /launchdarkly account Slack command.
Webhook notifications
You can add one or more URLs for receiving webhook notifications. When an alert is triggered, POST requests will be sent to these URLs with the following format:
