Observability Stack Designer
$2.99OfficialDesign comprehensive observability: metrics, logs, traces, and profiles with SLO-driven alerting and dashboard design.
What you get
- ✓10-step procedure
- ✓6 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 5 min read
- Requires
- Best with a strong model (Claude Sonnet 4)
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Handles multi-file projects
Preview
When to use
Use this skill when designing the observability stack for a service or platform: which metrics, logs, traces, and continuous-profiling signals to collect; how to define SLOs and derive alerts from them; and how to design dashboards that actually inform operators. It applies to greenfield services and to overhauling an existing pile of alerts and dashboards that no one trusts. It does not implement a specific vendor's config (Prometheus, OpenTelemetry, Datadog, Honeycomb, Grafana) — it specifies what the system must observe and how alerts and dashboards should be structured.
Inputs to gather
- Services and their critical user journeys: the paths whose health defines "the
…
🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.