Skip to content

Commit 2b751bc

Browse files
[OBSERVABILITY][ResponseOps][8.x] Clarify untracked alerts (#4952)
* First draft * Update docs/en/observability/view-observability-alerts.asciidoc
1 parent a37efea commit 2b751bc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/en/observability/view-observability-alerts.asciidoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ For example, if the threshold requires an alert to change status at least 6 time
8484
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.
8585

8686
`untracked`::
87-
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 image:images/icons/boxesHorizontal.svg[More 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. You can choose to move active alerts to this state when you disable or delete rules.
87+
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 image:images/icons/boxesHorizontal.svg[More actions] icon to expand the **More actions** menu, and click **Mark as untracked**. When an alert is untracked, its status is no longer updated and actions are no longer generated You can choose to move active alerts to this state when you disable or delete rules.
8888

8989
[discrete]
9090
[[customize-observability-alerts-table]]

0 commit comments

Comments
 (0)