observability-designer

What This Skill Does

The Observability Designer skill is a high-level engineering tool designed to help developers and SREs architect comprehensive monitoring and diagnostic strategies for production environments. It bridges the gap between raw data collection and actionable operational intelligence by implementing industry-standard frameworks like the Golden Signals (Latency, Traffic, Errors, Saturation), the RED method for microservices, and the USE method for infrastructure resource analysis. The skill assists in defining precise SLIs (Service Level Indicators) and SLOs (Service Level Objectives), calculating error budgets, and configuring multi-window burn rate alerts to ensure systems remain performant while managing reliability expectations.

Installation

To install this skill, run the following command in your OpenClaw terminal: clawhub install openclaw/skills/skills/alirezarezvani/observability-designer

Use Cases

• Production Readiness Reviews: Automatically generate a monitoring checklist for new microservices to ensure they meet internal reliability standards.
• Alert Noise Reduction: Analyze current alerting configurations and suggest optimizations to minimize false positives and fatigue.
• Dashboard Prototyping: Design high-fidelity dashboard layouts that prioritize critical user journeys and operational visibility based on your specific architecture.
• Incident Response Strategy: Map out tracing and logging requirements to accelerate root cause analysis for distributed system failures.

Example Prompts

1. "Design an SLO framework for our order processing service, including suggested SLIs for latency and success rate, along with a strategy for burn rate alerting."
2. "Review my current dashboard layout; I have 20 panels and I'm overwhelmed. Apply the 7±2 rule and suggest a hierarchy for my SRE team to improve cognitive load."
3. "I am struggling with high cardinality in my logs. Design a structured logging and sampling strategy that reduces costs without losing visibility into critical error flows."

Tips & Limitations

• Focus on Business Value: When designing SLIs, always start with the user experience rather than raw infrastructure metrics.
• Iterate on Dashboards: Treat your dashboard as code. Start simple and add complexity only when a specific operational need is identified through incident data.
• Limitations: The skill provides architectural design and strategy. It cannot directly modify your infrastructure or external monitoring tool APIs unless connected to relevant automation interfaces. It is most effective when provided with a clear description of your current technology stack (e.g., Kubernetes, CloudWatch, Datadog, Prometheus).