design-monitoring

Generate Grafana dashboards and Prometheus alert rules from augur monitoring-spec.yaml.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill design-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-monitoring
Source: https://github.com/Kord96/kordinate/tree/main/agents/sauron/skills/design-monitoring
Command: npx skills add https://github.com/Kord96/kordinate --skill design-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many projects have monitoring specifications but lack an automated, repeatable way to turn those specs into concrete observability artifacts and verify runtime emissions; this Skill implements specs from augur into Grafana dashboards, Prometheus alert rules, and live metric validation to close that gap.

Core Features & Use Cases

  • Spec-driven generation: Parse augur's monitoring-spec.yaml and atlas context to generate project-specific Grafana overview and vitals dashboards and Prometheus alert rule groups.
  • Alert and meta-alert creation: Produce standard alert rule files with severity labels, annotations, and a required VitalsMissing meta-alert.
  • Runtime validation: Optionally access the cluster to scrape /metrics, confirm metric names/types/labels, verify infra-atlas contract requirements, and produce a validation report classifying PASS/MISSING/TYPE_MISMATCH/LABELS_MISSING/CONTRACT_VIOLATION.
  • Memory-first outputs: Write generated dashboards, alerts, and implementation/validation reports to the sauron project memory for review, and optionally push dashboards and apply rules when not in dry-run.
  • Use Case: Given augur's approved monitoring-spec for a Kubernetes service, produce ready-to-provision Grafana JSON, Prometheus rules, and a validation report to onboard observability quickly.

Quick Start

Generate monitoring for my-project from the monitoring-spec.yaml and write dashboards, alerts, and a validation report to the sauron project memory as a dry run.

Frequently Asked Questions about design-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a monitoring spec into Grafana dashboards and Prometheus alerts?

Runtime metrics validation in Kubernetes checks live /metrics endpoints to confirm metric names, types, and labels, verifying infra-atlas contract compliance and classifying results as PASS, MISSING, TYPE_MISMATCH, LABELS_MISSING, or CONTRACT_VIOLATION in a validation report.

How do I validate runtime metrics for a Kubernetes workload against a monitoring spec?

Runtime metrics validation in Kubernetes checks live /metrics endpoints to confirm metric names, types, and labels, verifying infra-atlas contract compliance and classifying results as PASS, MISSING, TYPE_MISMATCH, LABELS_MISSING, or CONTRACT_VIOLATION in a validation report.

Does this monitoring generation approach support dry runs without pushing to Grafana or Prometheus?

Yes, this monitoring generation approach supports dry runs by writing generated dashboards, alert rules, and validation reports to the sauron project memory for review, only optionally pushing dashboards and applying rules when not in dry-run mode.

What is a VitalsMissing meta-alert and why is it required in Prometheus alert rules?

A VitalsMissing meta-alert is a required Prometheus alert rule generated alongside standard alert rule files to notify when essential vital metrics are absent, ensuring observability coverage gaps are detected using severity labels and annotations.

Can I generate Prometheus alert rules with severity labels and annotations from a YAML spec?

Yes, you can generate Prometheus alert rules with severity labels and annotations by parsing an augur monitoring-spec.yaml, which produces standard alert rule files containing required VitalsMissing meta-alerts and proper PromQL expressions for Kubernetes workloads.