obs-observability-and-monitoring

What problem does it solve?

Design and implement practical observability so teams can understand service behavior, detect regressions, and perform actionable operational responses without excess noise or sensitive data leakage.

Core Features & Use Cases

• Signal selection and naming: choose the minimal set of traces, metrics, logs, and exemplars with stable, low-cardinality names and units.
• Correlation and identity: ensure consistent service/resource identity across telemetry for tracing and root-cause analysis.
• Alerting and dashboards: create actionable alerts, dashboard panels, and validation smoke checks tied to SLOs and operational runbooks.
• Use Case: instrument a checkout flow with request latency, error rates, dependency spans, and a dashboard plus alerts for sustained error rate increases.

Quick Start

Run the obs-observability-and-monitoring skill for the current user story to produce a signal selection, naming conventions, and actionable alerting plan.