Observability plan for a service
Plan for metrics, logs, traces, and alerts for a new service — what to instrument from day 1.
Stops "we don't know what broke" incidents.
The prompt
Copy this into ChatGPT, Claude, Gemini or any assistant you already use — then paste your own service + stack underneath it.
Plan observability for the service. Output: **Metrics** (RED: rate, errors, duration; USE for infra). For each: name, unit, dimensions, target. **Logs** (what to log, log levels, structured format) **Traces** (key spans, baggage) **Alerts** (SLO-based, with thresholds + paging rules) **Dashboards** (top-3 dashboards to build first) Rules: - SLOs not SLIs — define what users care about. - Don't over-alert; page only on user-impacting.
Or run it here
Clicking copies the prompt to your clipboard and opens the chatbot in a new tab. Gemini doesn't accept URL params — paste manually with Ctrl/Cmd+V.
Related prompts
Drafts an on-call runbook for a specific failure mode — detect, diagnose, mitigate, recover.
Generates a multi-stage, small-image Dockerfile for a given stack.
A complete CI pipeline YAML — lint, test, build, scan, deploy — for a Node/Python/Go service.
Writes a log query (Datadog / Splunk / Loki / CloudWatch) to surface what you need.
Decodes any cron schedule string into when it actually runs.
Skeleton for a Terraform module — main, variables, outputs, README.
Browse the full free AI prompt library or see more devops & sre prompts.