monitoringlisted

# Purpose Define, instrument, and verify Prometheus metrics, Grafana dashboards, and alert rules across the project's platform. Produce metric definitions, dashboard JSON, alert rule YAML, and ServiceMonitor resources that connect instrumentation to Prometheus scraping. **Placeholders used below:** `<mainApp>` = `project.json → mainApp` (the primary application), `<device>` = `project.json → device` (the edge/device service, if the project has one), `<project>` = `project.json → name` snake_cased (the metric-name prefix). Repos and their layout come from `project.json → repos`. # When to use - Adding Prometheus counters, histograms, or gauges to `<mainApp>` or `<device>` code. - Creating or modifying Grafana dashboard JSON for one of the project's services. - Writing or reviewing Prometheus alert rules (PrometheusRule CRDs or rule files). - Wiring a new service for Prometheus scraping via ServiceMonitor in the project's deploy/charts repo. - Investigating why a Prometheus alert fired or a metric spiked. - Reviewing alert coverage for a newly deployed service. **Disambiguation -- monitoring vs observability:** If the task says "instrument" or "add metrics," use this skill. If it says "add logging," "add tracing," or "correlate logs with traces," use `observability`. If investigation starts from a Prometheus alert, start here; if it starts from log search or trace lookup, start with `observability`. # When NOT to use - **Structured logging or distributed tracing** -- use