grafana-dashboard-optimize

# Grafana Dashboard Content Optimization (Observability / SRE)

Audit and optimize dashboard content for observability best practices. Apply RED/USE/Golden Signals methodology, improve diagnostic value, and reduce cognitive load for on-call teams.

**Not suitable for**: Code structure refactoring (use `grafana-jsonnet-refactor`), initial JSON conversion (use `grafana-json-to-jsonnet`), or code style formatting.

## Workflow with progress tracking

Copy this checklist and track your progress:

```
Optimization Progress:
- [ ] Step 1: Understand context (purpose, audience, strategy)
- [ ] Step 2: Run seven-dimensional content audit
- [ ] Step 3: Produce prioritized recommendations report
- [ ] Step 4: Apply changes (if requested)
- [ ] Step 5: Validate improvements
```

**Step 1: Understand context**

Before any edits, document:
- Dashboard purpose and target audience (SRE/on-call/management)
- Current monitoring strategy and key questions it should answer
- Datasources, variables, time range settings
- Row structure and panel organization
- Annotations, dashboard metadata (`__inputs`, `__requires`, `schemaVersion`, `graphTooltip`, `version`), and pluginVersion

See `references/full-optimization-playbook.md` for detailed context gathering.
If optimizing dashboards in a specific repo or stack, review local Jsonnet defaults and docs in the working directory for current conventions.

**Step 2: Run seven-dimensional content audit**

Audit across these dimensions:
1. **Panel semantics**: Missing/duplicated views, diagnostic coverage
2. **Query optimization**: rate/increase usage, aggregation, cardinality
3. **Variable design**: Names, defaults, cascading relationships
4. **Visualization**: Panel types, units, thresholds, legends, table field pruning
5. **Layout**: Overview → symptoms → root cause flow
6. **Titles/descriptions**: Unified title style, clarity, context, troubleshooting hints, every panel has a description
7. **Proactive additions**: SLO/SLI, annotations, comp