Skip to content

Commit b7058ba

Browse files
Alexandra's feedback
1 parent 4ac650f commit b7058ba

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

solutions/observability/incident-management/view-alerts.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -65,28 +65,29 @@ To view the alert in the app that triggered it:
6565
There are four common alert statuses:
6666

6767
`active`
68-
: The conditions for the rule are met and actions should be generated according to the notification settings.
68+
: The conditions for the rule are met. Actions for the rule are run according to the notification settings.
6969

7070
`flapping`
7171
: The alert is switching repeatedly between active and recovered states.
7272

73-
::::{note}
74-
**Flapping alerts**
75-
73+
::::{important}
7674
The flapping state is possible only if you have enabled alert flapping detection. Go to the **Alerts** page and click **Manage Rules** to navigate to the **{{rules-app}}** page. Click **Settings** then set the look back window and threshold that are used to determine whether alerts are flapping. For example, you can specify that the alert must change status at least 6 times in the last 10 runs. If the rule has actions that run when the alert status changes, those actions are suppressed while the alert is flapping.
7775

7876
::::
7977

8078
`recovered`
81-
: The conditions for the rule are no longer met and recovery actions should be generated. Alerts will change to the recovered state if the rule's conditions are not met for the number of consecutive runs defined in its look back window.
79+
: The conditions for the rule are no longer met. Recovery actions for the rule will run if the rule's conditions _are not_ met during the current rule execution, but were met in the previous one.
8280

8381
::::{note}
84-
Once an alert is recovered, the flapping state criteria is only applied to newly generated alerts.
82+
83+
Note the following about alerts that change from the flapping state to recovered:
84+
- Alerts in the flapping state will only change to recovered if the rule's conditions are not met for the number of consecutive runs that are defined by the **Alert status change threshold** for flapping alerts.
85+
- After an alert is recovered, the flapping state criteria is only applied to newly generated alerts.
8586
::::
8687

8788

8889
`untracked`
89-
: The corresponding rule is disabled or you’ve marked the alert as untracked. To mark the alert as untracked, go to the **Alerts** table, click the ![More actions](/solutions/images/serverless-boxesHorizontal.svg "") 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.
90+
: 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 ![More actions](/solutions/images/serverless-boxesHorizontal.svg "") 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.
9091

9192

9293
## Customize the alerts table [observability-view-alerts-customize-the-alerts-table]

0 commit comments

Comments
 (0)