Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Define and instrument reliability for [user journey]. Specify eligible attempts, good outcomes, failure outcomes, latency requirements, and the measurement window. Connect relevant logs, metrics, and traces using identifiers without exposing private payloads. Check that controlled success and failure cases appear correctly in the measurement. Propose an initial objective and an actionable alert with a confirmation and recovery procedure. Report the exact indicator definition, observed baseline, tested failure scenario, and limitations such as sampling or missing instrumentation.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Google SRE Book — Indicators, objectives, and error budgets
- OpenTelemetry — Distributed traces and spans
Documentation links checked .
Editorial review · October 28, 2026
Limited: Original instructional template; not executed. Reliability prompt requests observed success/failure instrumentation; no measurement or alert scenario was executed.