View alerts
editView alerts
editWhen the conditions of a rule are met, it creates an alert. If the rule has actions, they run at the defined frequency. For example, the rule can send email notifications for each alert at a custom interval. For an introduction to the concepts of rules, alerts, and actions, refer to Alerting.
You can manage the alerts for each rule in Stack Management > Rules. Alternatively, manage all your alerts in Stack Management > Alerts. [preview] This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
You must have the appropriate Kibana alerting features and index privileges to view alerts. Refer to Alerting security requirements.
Filter alerts
editThis functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
In Stack Management > Alerts, you can filter the list (for example, by alert status or rule type) and customize the filter controls. To search for specific alerts, use the KQL bar to create structured queries using Kibana Query Language.
By default, the list contains all the alerts that you have authority to view in the selected time period except those associated with Security rules. To view alerts for Security rules, click the query menu and select Security rule types:
Alternatively, view those alerts in the Elastic Security app.
View alert details
editTo get more information about a specific alert, open its action menu (…) and select View alert details in either Stack Management > Alerts or Rules. There you’ll see the current status of the alert, its duration, and when it was last updated. To help you determine what caused the alert, there is information such as the expected and actual threshold values and a summarized reason for the alert.
If an alert is affected by a maintenance window, the alert details include its identifier. For more information about their impact on alert notifications, refer to Maintenance windows.
Alert statuses
editThere are three common alert statuses:
-
active - The conditions for the rule are met and actions should be generated according to the notification settings.
-
recovered - The conditions for the rule are no longer met and recovery actions should be generated.
-
untracked - Actions are no longer generated. For example, you can choose to move active alerts to this state when you disable or delete rules.
Alert flapping is turned on by default. You can modify the criteria for changing an alert’s status to the flapping state by configuring the Alert flapping detection settings. To do this, navigate to the Alerts page in the main menu, or use the global search field. Next, click Manage Rules, then Settings to open the global rule settings for the space. In the Alert flapping detection section, modify the rules' look back window and threshold for alert status changes. For example, you can specify that the alert must change its status at least 6 times in the last 10 runs for it to become a flapping alert.
-
recovered -
The conditions for the rule are no longer met. If the rule has recovery actions, Kibana generates notifications based on the actions' notification settings. Recovery actions only run if the rule’s conditions aren’t met during the current rule execution, but were in the previous one.
An active alert changes to recovered if the conditions for the rule that generated it are no longer met.
A flapping alert changes to recovered when the rule’s conditions are unmet for a specific number of consecutive runs. This number is determined by the Alert status change threshold setting, which you can configure under the Alert flapping detection settings.
For example, if the threshold requires an alert to change status at least 6 times in the last 10 runs to be considered flapping, then to recover, the rule’s conditions must remain unmet for 6 consecutive runs. If the rule’s conditions are met at any point during this recovery period, the count of consecutive unmet runs will reset, requiring the alert to remain unmet for an additional 6 consecutive runs to finally be reported as recovered.
Once a flapping alert is recovered, it cannot be changed to flapping again. Only new alerts with repeated status changes are candidates for the flapping status.
-
untracked - The rule is disabled, or you’ve marked the alert as untracked. To mark the alert as untracked, go to the Alerts table, click the actions icon (…) to expand the More actions menu, and click Mark as untracked. When an alert is marked as untracked, actions are no longer generated and the alert’s status can no longer be changed. You can choose to move active alerts to this state when you disable or delete rules.
Mute alerts
editIf an alert is active or flapping, you can mute it to temporarily suppress future actions. In Stack Management > Alerts, open the action menu (…) for the appropriate alert, then select Mute. While muted, the alert’s status will continue to update but rule actions won’t run. All future alerts with the same alert ID will also be muted.
To permanently suppress an alert’s actions, open the actions menu for the appropriate alert, then select Mark as untracked. In this case, the alert’s status is no longer updated and actions are no longer run. These changes are only applied to the alert that you untracked and cannot be reverted. Future alerts with the same alert ID are unaffected.
To affect the behavior of the rule rather than individual alerts, check out Snooze and disable rules.