[Observability/Kibana][Alerting] Document per-alert snooze - #7522
Merged
Conversation
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
🔍 Preview links for changed docs |
Contributor
Elastic Docs Style Checker (Vale)Summary: 9 suggestions found 💡 Suggestions (9): Optional style improvements. Apply when helpful.
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
This was referenced Jul 29, 2026
Merged
The custom-threshold-warning-threshold anchor now lives in the warning-severity PR (#7643), which broke the docs build for this PR. Link to the page instead until that PR merges.
nastasha-solomon
added a commit
that referenced
this pull request
Jul 29, 2026
The snooze-alerts anchor lives in the per-alert snooze PR (#7522), not yet merged. Link to the page instead until that PR merges.
nastasha-solomon
added a commit
that referenced
this pull request
Jul 29, 2026
These sentences referenced the snooze-alert-options anchor, which lives in the per-alert snooze PR (#7522) and doesn't exist yet, so the docs build had auto-commented them out. Link to the page instead until that PR merges.
nastasha-solomon
changed the title
js-jankisalvi
left a comment
js-jankisalvi
left a comment
There was a problem hiding this comment.
Content looks good, maybe some screenshots could be helpful.
|
|
||
| To snooze an active alert, open its action menu ({icon}`boxes_vertical`) from the Alerts table or the alert details page, then select **Snooze**. Choose **Quick Snooze** when you know how long it should stay quiet, or **Condition based** when you'd rather the alert itself, not the clock, decide when actions resume. Configure your snooze, then select **Snooze alert** to apply it. | ||
|
|
||
| ### Quick Snooze [quick-snooze] |
There was a problem hiding this comment.
nit: Should we add a screenshot for quick snnoze?
Member
Author
There was a problem hiding this comment.
Screenshots are pretty expensive in terms of maintenance so the Elastic style guide recommends only including them when UIs are so complex that they can't be clearly described using text.
|
|
||
| Pick **Indefinitely** when you have no fixed window in mind, such as an alert you've triaged and will follow up on yourself. It stays snoozed until you unsnooze it manually, and is also what existing muted alerts show as. | ||
|
|
||
| ### Condition based snooze [condition-based-snooze] |
There was a problem hiding this comment.
nit: Should we a screenshot for condition based snooze?
js-jankisalvi
approved these changes
Jul 30, 2026
mdbirnstiehl
approved these changes
Jul 30, 2026
mdbirnstiehl
left a comment
mdbirnstiehl
left a comment
Member
There was a problem hiding this comment.
LGTM! I had a few suggestions/comments, do with them what you will!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents per-alert snooze: snooze a single alert instance for a duration, until a condition is met, or indefinitely, without silencing the whole rule. Snooze replaces Mute going forward; alerts muted on earlier versions keep working and show as snoozed indefinitely. To avoid duplicating this explanation across pages, the Observability Alerts page now links to the canonical Snooze/Mute reference in the Kibana alerting docs instead of repeating it.
Fixes #7334.
Previews
Note: The "Snooze options" tip in
view-alerts.mdlinks to the custom/metric threshold rule pages without the specific#custom-threshold-warning-thresholdanchor, since that section lives in #7643 (still open). Once #7643 merges, that anchor can be added back.Generative AI disclosure