Docs fix — frontmatter: path /deploy-manage/production-guidance — 20 pages

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

Path /deploy-manage/production-guidance · 20 total in scope · subtree corpus 20 pages.

## Findings (20)

```yaml
- file: deploy-manage/production-guidance/availability-and-resilience.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Overview of high availability design in Elasticsearch clusters, including node, zone, and cross-cluster resilience strategies."
- file: deploy-manage/production-guidance/availability-and-resilience/resilience-in-ech.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Resilience strategies for Elastic Cloud Hosted and Elastic Cloud Enterprise deployments spread across availability zones."
- file: deploy-manage/production-guidance/availability-and-resilience/resilience-in-larger-clusters.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Zone-aware resilience strategies for self-managed Elasticsearch clusters, including shard allocation and master-eligible node planning."
- file: deploy-manage/production-guidance/availability-and-resilience/resilience-in-small-clusters.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Resilience strategies for small self-managed Elasticsearch clusters, focused on recovering from single-node failures."
- file: deploy-manage/production-guidance/elasticsearch-in-production-environments.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Guidance for running Elasticsearch in production, covering deployment resilience and performance optimization."
- file: deploy-manage/production-guidance/general-recommendations.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Best practices for improving Elasticsearch performance and avoiding common operational issues."
- file: deploy-manage/production-guidance/kibana-alerting-production-considerations.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Performance and scaling guidance for Kibana alerting rules and actions running as background tasks."
- file: deploy-manage/production-guidance/kibana-configure-memory.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Configure Kibana memory limits to support reporting, alerting, and other resource-intensive workloads."
- file: deploy-manage/production-guidance/kibana-in-production-environments.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Guidance for deploying Kibana in production, including load balancing across multiple instances."
- file: deploy-manage/production-guidance/kibana-load-balance-traffic.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Guidance for scaling Kibana through traffic distribution, multiple load-balanced deployments, and high availability configuration."
- file: deploy-manage/production-guidance/kibana-reporting-production-considerations.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Production considerations for Kibana reporting, including Chromium sandboxing, OS compatibility, and dependency requirements."
- file: deploy-manage/production-guidance/kibana-task-manager-scaling-considerations.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Performance and scaling guide for Kibana Task Manager, which powers alerting, actions, and reporting background tasks."
- file: deploy-manage/production-guidance/kibana-traffic-scaling-considerations.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Guidance for scaling Kibana to handle traffic workloads outside of task manager and alerting."
- file: deploy-manage/production-guidance/optimize-performance.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Overview of Elasticsearch performance optimizations, covering deployment configuration and usage-level tuning."
- file: deploy-manage/production-guidance/optimize-performance/approximate-knn-search.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Recommendations for tuning approximate k-nearest neighbor search performance in Elasticsearch."
- file: deploy-manage/production-guidance/optimize-performance/disk-usage.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Strategies for reducing Elasticsearch disk usage through field mappings, index settings, and segment management."
- file: deploy-manage/production-guidance/optimize-performance/indexing-speed.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Recommendations for tuning Elasticsearch indexing speed, from bulk sizing to hardware and thread management."
- file: deploy-manage/production-guidance/optimize-performance/search-speed.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Guidance for tuning Elasticsearch search speed through field mappings, caching behavior, and query design."
- file: deploy-manage/production-guidance/optimize-performance/size-shards.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Guidelines for sizing Elasticsearch shards to balance cluster performance and stability."
- file: deploy-manage/production-guidance/scaling-considerations.md
line: 1
category: missing-description
severity: high
confidence: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Guidance for scaling Elasticsearch deployments based on workload patterns rather than automatically adding resources."
```

## 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 other required frontmatter fields (`applies_to`, `products`) were present and valid on every page in this slice; `navigation_title` was present where the H1 was long. No `missing-products` or `missing-navigation-title` findings applied.

> Generated by [Docs frontmatter sweep agent](https://github.com/elastic/docs-content/actions/runs/30255953797) · sonnet50 28.6 AIC · ⌖ 4.92 AIC · ⊞ 12.3K · [◷](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)

Start with the 20 Markdown files listed under deploy-manage/production-guidance and read the repository's frontmatter schema or validation guidance. Add a non-empty description of no more than 200 characters to each page without changing the already-valid fields, then run the repository's documented frontmatter checks. Done means every listed page passes the schema and the descriptions meet the stated limit.

Written by the indexing model from the issue text.