Observability Plan
Plan the logs, metrics, traces, alerts, dashboards, service level objectives, and incident response hooks for a system so its operators can tell within minutes whether users are hurting and why.
Sample result
How it works
What Observability Plan does
Starts from user journeys, defines good-event service level indicators and SLO targets with error budget and multi-window burn-rate alert math, maps instrumentation per component, sets log field and metric cardinality rules, designs tiered dashboards and symptom-based paging, adds runbook and escalation hooks, and budgets telemetry volume, retention, and privacy.
Use it when
Someone asks how to monitor a system, what to log or alert on, how to set SLOs, why alerts are noisy, how to add tracing, or how to prepare a service for on-call.
Use something else for
Triaging a specific metric anomaly, running a live incident, auditing existing code, or defining infrastructure resources.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
SLO sheet, alert catalog, instrumentation map and runbook
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Observability Plan
Updated Oct 20, 2026.
What does Observability Plan do?
Plan the logs, metrics, traces, alerts, dashboards, service level objectives, and incident response hooks for a system so its operators can tell within minutes whether users are hurting and why. Starts from user journeys, defines good-event service level indicators and SLO targets with error budget and multi-window burn-rate alert math, maps instrumentation per component, sets log field and metric cardinality rules, designs tiered dashboards and symptom-based paging, adds runbook and escalation hooks, and budgets telemetry volume, retention, and privacy. Use when someone asks how to monitor a system, what to log or alert on, how to set SLOs, why alerts are noisy, how to add tracing, or how to prepare a service for on-call. Do not use for triaging a specific metric anomaly (use anomaly-triage), running a live incident (use coordinate-production-incident), auditing existing code (use codebase-audit), or defining infrastructure resources (use iac-setup).
Who is Observability Plan for?
It is designed for site reliability engineers, backend engineers, on-call leads, engineering managers and platform teams.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Observability Plan produce?
SLO sheet, alert catalog, instrumentation map and runbook. Results come back with their sources and any open questions for you to check before anything is used.
How much does Observability Plan cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt97tk008q…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Observability Plan fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.