Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.11](backport #3252) Remove uptime content from SLO alerting doc #3261

Merged
merged 1 commit into from
Oct 9, 2023
Merged

[8.11](backport #3252) Remove uptime content from SLO alerting doc #3261

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/en/observability/images/slo-action-frequency.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/en/observability/images/slo-action-variables.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 4 additions & 8 deletions docs/en/observability/slo-burn-rate-alert.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,15 +37,12 @@ You can configure action types on the <<configure-uptime-alert-connectors,Settin
[role="screenshot"]
image::images/alert-action-types.png[Uptime rule connectors]

After you select a connector, you must set the action frequency. You can choose to create a summary of alerts on each check interval or on a custom interval. For example, send email notifications that summarize the new, ongoing, and recovered alerts every twelve hours:
After you select a connector, you must set the action frequency. You can choose to create a *Summary of alerts* on each check interval or on a custom interval. For example, you can send email notifications that summarize the new, ongoing, and recovered alerts every twelve hours.

[role="screenshot"]
image::images/duration-anomaly-alert-summary.png[Action types]

Alternatively, you can set the action frequency such that you choose how often the action runs (for example, at each check interval, only when the alert status changes, or at a custom action interval). In this case, you must also select the specific threshold condition that affects when actions run: `Uptime Duration Anomaly` or `Recovered`.
Alternatively, you can set the action frequency to *For each alert* and specify the conditions each alert must meet for the action to run. For example, you can send an email only when the alert status changes to critical.

[role="screenshot"]
image::images/duration-anomaly-run-when-selection.png[Configure when a rule is triggered]
image::images/slo-action-frequency.png[Configure when a rule is triggered]

[discrete]
[[action-variables-slo]]
Expand All @@ -56,8 +53,7 @@ You can add more context to the message by clicking the icon above the message t
and selecting from a list of available variables.

[role="screenshot"]
image::images/duration-anomaly-alert-default-message.png[Default notification message for Uptime duration anomaly rules with open "Add variable" popup listing available action variables,width=600]

image::images/slo-action-variables.png[Action variables with default SLO message]

[discrete]
[[recovery-variables-slo]]
Expand Down