Docs fix — frontmatter: path /explore-analyze/alerting/alerts — 16 pages

Generated by `gh-aw-docs-frontmatter-sweep` for `elastic/docs-content` on 2026-W25.

Path /explore-analyze/alerting/alerts · 16 total in scope · subtree corpus 16 pages.

## Findings (16)

```yaml
- file: explore-analyze/alerting/alerts/alerting-common-issues.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Troubleshooting guide for common Kibana alerting issues, including delayed rule execution, missing actions, and diagnostic approaches."

- file: explore-analyze/alerting/alerts/alerting-getting-started.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Kibana alerting is the built-in system for defining rules, detecting complex conditions, and triggering actions across Observability, Security, Maps, and Machine Learning."

- file: explore-analyze/alerting/alerts/alerting-setup.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Configure Kibana alerting prerequisites, including encryption keys, TLS configuration, and role-based access control for rules and connectors."

- file: explore-analyze/alerting/alerts/alerting-troubleshooting.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Troubleshooting guide for Kibana alerting, covering log inspection, event log queries, task manager health, and known limitations."

- file: explore-analyze/alerting/alerts/create-manage-rules.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Create, edit, enable, disable, and manage alerting rules from the Kibana Stack Management Rules UI, including mute and snooze options."

- file: explore-analyze/alerting/alerts/event-log-index.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Reference for the Kibana alerting event log index, useful for diagnosing whether rules and actions executed successfully."

- file: explore-analyze/alerting/alerts/geo-alerting.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Configure a tracking containment rule to alert when a tracked entity enters or exits a defined geographic boundary."

- file: explore-analyze/alerting/alerts/maintenance-windows.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Schedule single or recurring maintenance windows to temporarily suppress alerting rule notifications during planned outages."

- file: explore-analyze/alerting/alerts/notifications-domain-allowlist.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Restrict alert email recipients by configuring a notifications domain allowlist for Elasticsearch Watcher and Kibana alerting."

- file: explore-analyze/alerting/alerts/query-alerts.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Reference for querying Kibana alert indices when building rule queries, dashboards, or visualizations, including index names and sample queries."

- file: explore-analyze/alerting/alerts/rule-action-variables.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Reference for Mustache template variables available in Kibana alerting rule actions, covering alert context, state, and summary variables."

- file: explore-analyze/alerting/alerts/rule-type-es-query.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Configure an Elasticsearch query rule to trigger alerts when query match counts exceed a threshold, using DSL, ES|QL, KQL, or Lucene syntax."

- file: explore-analyze/alerting/alerts/rule-type-index-threshold.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Configure an index threshold rule that aggregates field values from Elasticsearch documents and triggers actions when thresholds are met."

- file: explore-analyze/alerting/alerts/rule-types.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Overview of built-in Kibana alerting rule types, including stack rules and rules registered by Observability, Security, and Machine Learning apps."

- file: explore-analyze/alerting/alerts/testing-connectors.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Test alerting connectors in Kibana Stack Management to verify they can send notifications before assigning them to alerting rules."

- file: explore-analyze/alerting/alerts/view-alerts.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "View and manage alerts generated by Kibana alerting rules from the rule details page or the Alerts management page in Stack Management."
```

## Done when
- All listed pages have a non-empty, <=200-character `description` field and required frontmatter keys present per the repo's frontmatter schema.
- A PR addressing this issue is merged.

## Notes
- All 16 files in scope are missing `description`; `navigation_title` and `products` are present and correct on all files.

> Generated by [Docs frontmatter sweep agent](https://github.com/elastic/docs-content/actions/runs/27795539785) · 119.4 AIC · ⌖ 13.7 AIC · ⊞ 27K · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fdocs-content%2Fgh-aw-docs-frontmatter-sweep%22&type=issues)

Review the frontmatter in the 16 Markdown files under explore-analyze/alerting/alerts/ and compare it with the repository's frontmatter schema. Add the provided descriptions, keeping each at 200 characters or less, and verify that required keys remain present. Done means all 16 pages have non-empty descriptions and the changes are ready for a merged PR.

Written by the indexing model from the issue text.