observability-design

Plan monitoring architectures with SLIs, SLOs, alerting, and dashboards for microservices.

Updated Dec 28, 2025

Search Tags:#monitoring #observability #alerting #SLO #SLI #distributed tracing #incident-response

Ready to run

npx skills add https://github.com/I2olanD/dotfiles --skill observability-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-design
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/observability-design
Command: npx skills add https://github.com/I2olanD/dotfiles --skill observability-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams design robust observability by outlining a structured approach to collect metrics, traces, and logs for production systems, enabling proactive insight and faster recovery.

Core Features & Use Cases

Metrics, Logs, and Traces: Establish a triad for visibility and correlation across services.
SLI/SLO Guidance: Design service-level indicators and objectives to balance reliability and velocity.
Alerting & Dashboards: Create actionable alerts and dashboards that reduce noise and improve incident response.
Use Case: When designing a new microservice, apply these patterns to instrument telemetry from day one and support post-incident analysis.

Quick Start

Read the monitoring-patterns references and begin applying the three pillars of observability to your service design.

Frequently Asked Questions about observability-design

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

FAQPage Schema

How do I design observability for a new microservice from scratch?▼

To design observability for a new microservice, apply a structured framework covering the three pillars: metrics, logs, and distributed traces. This enables proactive insight and faster recovery by instrumenting telemetry from day one.

What are the three pillars of observability for production systems?▼

The three pillars of observability are metrics, logs, and distributed traces. Establishing this triad provides visibility and correlation across services, enabling proactive insight and faster recovery for production systems.

How do I create actionable alerting and dashboards that reduce noise?▼

Create actionable alerting and dashboards by designing service-level indicators and objectives that balance reliability and velocity. This structured approach reduces noise and improves incident response across microservices.

When do I need to define SLIs and SLOs for my services?▼

You need to define SLIs and SLOs when planning monitoring architectures to balance reliability and velocity for production services. They provide a structured approach to measure service performance and support post-incident analysis.

Can I use this structured approach for distributed tracing in microservices?▼

Yes, you can use this structured approach for distributed tracing in microservices. It codifies core pillars including traces and provides reference patterns to support visibility, correlation, and post-incident analysis across services.

What is the best way to structure incident response across microservices?▼

The best way to structure incident response is using a ready-to-use framework that codifies recommended practices for alerting and telemetry. This supports faster recovery and effective post-incident analysis across distributed services.