observability-designer

Designing an SLI and SLO framework involves defining reliability targets aligned with business outcomes across services. This Skill generates structured SLI/SLO frameworks, dashboards, and runbooks from a service description JSON to standardize reliability targets.

End-to-end observability requires comprehensive coverage of metrics, logs, and traces. This Skill generates production observability strategies covering these three pillars, applying golden signals and alert optimization to ensure reliable performance and faster incident response.

Generating runbooks and dashboards standardizes incident response and post-mortem analysis. This Skill creates dashboard designs and runbooks by processing service description inputs through Python tooling to produce actionable integration blueprints.

Yes, you can automate observability strategy generation by providing a service description JSON. The Skill uses YAML frontmatter inputs and Python tooling to automatically generate complete artifacts, including alerts, metrics, and tracing integration blueprints.

An observability strategy is needed because basic monitoring alerts are often error-prone and fragmented. This Skill provides a structured approach covering metrics, logs, and traces, enforcing end-to-end design to align reliability targets and optimize alerts.

Yes, the observability design approach works without external dependencies. It uses internal Python scripts and YAML frontmatter to generate integration blueprints and artifacts, which you can then apply to your specific monitoring platforms.