Skip to content

[AlertZero] Add Work in AlertZero and Close false-positive alerts - #9116

Closed
nastasha-solomon wants to merge 17 commits into
mainfrom
nsolomon/alertzero-use-pages
Closed

nastasha-solomon wants to merge 17 commits into
mainfrom
nsolomon/alertzero-use-pages

Conversation

@nastasha-solomon

@nastasha-solomon nastasha-solomon commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

Summary

Adds the AlertZero home page and a page for closing the false-positive alerts that the Alert Triage Worker proposes. Review closed proposed actions is folded into Close false-positive alerts and redirected there.

AlertZero
├── Work in AlertZero                 where to start for each goal
│   └── Close false-positive alerts   approve or decline a closure, reopen alerts
└── Glossary                          updates the link to Work in AlertZero

Previews

  • Work in AlertZero - Added where to start for each goal, from closing false positives to escalating an investigation.
  • Close false-positive alerts - Added instructions for reviewing a proposed closure, approving or declining it, and reopening alerts closed by mistake.
  • Glossary - Updated the link to the AlertZero home page.
  • Review closed proposed actions - Removed the page and redirected it to Close false-positive alerts.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

Tool(s) and model(s) used: Claude Opus 5.5, via Claude Code and Cursor

nastasha-solomon and others added 2 commits October 31, 2026 16:34
Replace the hidden stubs for Use AlertZero, Decide a proposed action, and
Review closed proposed actions, and point the glossary's Use AlertZero link
at the Proposed actions page. Verified against elastic/kibana branch 9.6.

Part of elastic/docs-content-internal#1816.

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add the missing AlertZero Read prerequisites, define proposed actions in
the decide page opening, correct the decline-reason description, and use
4-space nested list indentation.

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


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.

Add the Agent Builder prerequisite and a navigation step to each
procedure, explain retries of failed actions on the decide page so it
agrees with the closed list, move the failed-run callout out of the idle
state, move final-decision and expiry facts before the steps, and give
the decide headings a noun.

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nastasha-solomon nastasha-solomon self-assigned this Oct 31, 2026
State what each page helps you do, give the filter and investigation
sections task headings, and cut the empty-state section, the duplicate
links, and the full list of decline reasons. Turn the review step into a
checklist, say that an approved action fails without its privileges,
order statuses by outcome, and retitle the outcomes table. List
serverless first in applies_to.

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nastasha-solomon and others added 2 commits October 31, 2026 17:55
Quote the missing-privilege message instead of bolding it, add the icon
for the icon-only Add or change assignees button, take bold out of the
Impact filter link, and italicize the name placeholder inside the bold
outcome labels.

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ails

Replace the privilege names and levels on Use AlertZero, Decide a
proposed action, and Review closed proposed actions with links to the
AlertZero privileges page, which now holds all AlertZero access content.

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nastasha-solomon and others added 5 commits October 31, 2026 20:14
Decide a proposed action: shorten the intro, say that approving an
action doesn't give you the privileges to run it, and add what happens
when you approve or decline Alert Triage's proposals to close false
positives, moved from the Alert Triage Worker page. Use AlertZero: map
each Proposed actions section to the page that covers its decisions,
and keep one privileges line.

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…sed action

Rewrite "a {{az-worker}}" in the intro so the text still reads correctly
if the Worker name changes to one that takes "an".

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Put the decision pages in a new order, and nest Track escalations under
Escalate an investigation.

AI-Assisted: Drafted with Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pages

Use AlertZero: retitle as Work through proposed actions, cut the setup
and privilege notes, map each section to the role that usually decides
it, fold the Impact filter into one sentence with its purpose, and keep
only the follow-ups the UI doesn't make obvious. Each card is one
proposed action, not one investigation.

Decide a proposed action: fold in Review closed proposed actions,
remove the privilege prerequisites, move the final-decision and expiry
facts to where you decide, and replace When Workers decide for you with
Check recent decisions. Redirect the removed page.

Show the use pages in the navigation for the preview.

AI-Assisted: Drafted with Cursor (Claude Opus 5.5)
Co-authored-by: Cursor <cursoragent@cursor.com>
The section also holds the escalation pages, so the title covers more
than proposed actions. Say in the intro that you can hand off or
escalate an investigation, and link the escalation pages from Next
steps.

AI-Assisted: Drafted with Cursor (Claude Opus 5.5)
Co-authored-by: Cursor <cursoragent@cursor.com>
@nastasha-solomon nastasha-solomon changed the title [AlertZero] Add Use AlertZero, Decide a proposed action, and Review closed proposed actions [AlertZero] Add Work in AlertZero and Decide a proposed action Nov 1, 2026
nastasha-solomon and others added 2 commits November 1, 2026 01:37
…able

Put Open in chat, assigning, and closing an investigation in the paragraph about cards, since they apply to every card, and the escalation link in the Respond row. Remove the Follow up section.

AI-Assisted: Drafted with Cursor (Claude Opus 5.5)
Co-authored-by: Cursor <cursoragent@cursor.com>
Retitle Decide a proposed action as Close false-positive alerts and write it for the triage analyst: what to check before approving a batch, what each decision does, what happens on expiry, and how to reopen alerts closed by mistake. Lead the home page intro with why to check a Worker's reasoning, and add a Where to start table.

Co-authored-by: Cursor <cursoragent@cursor.com>
@nastasha-solomon nastasha-solomon changed the title [AlertZero] Add Work in AlertZero and Decide a proposed action [AlertZero] Add Work in AlertZero and Close false-positive alerts Nov 1, 2026
Name each Worker consistently, drop page-position language, use might for possibility, replace passive constructions, and capitalize after colons. Update the home page table to link Tune noisy rules and fill detection gaps.

Co-authored-by: Cursor <cursoragent@cursor.com>
nastasha-solomon added a commit that referenced this pull request Nov 1, 2026
Close false-positive alerts (decide-proposed-action.md, reworked in #9116) now covers only the Alert Triage Worker's closures, not the steps every decision shares. Reword the Triage Watch and Alert Triage Worker links to match, and point the glossary's proposed action entry to Work in AlertZero.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nastasha-solomon and others added 3 commits November 1, 2026 02:13
Checked against Kibana 9.6. The 72-hour expiry has no setting that changes it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep every AlertZero entry hidden and in its current order, and change the toc only to drop Review closed proposed actions. The other AlertZero PRs then merge without toc conflicts. A final navigation PR will set the order and which pages show.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Uses Impacted entities (was Impact), from elastic/kibana#302204.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nastasha-solomon

Copy link
Copy Markdown
Member Author

Closing in favor of using #9157.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants