What this prompt does
This prompt stands up a full observability stack for a [application_type] on [infrastructure]. It implements structured logging in [log_format] with [log_levels], distributed tracing via [tracing_tool], metrics ([custom_metrics]) through [metrics_tool], centralized aggregation with [log_aggregator], dashboards for [dashboard_types], alerting ([alert_rules]), on-call via [oncall_tool], SLO/SLI definitions for [slo_targets], error tracking with [error_tracker], and health endpoints, plus correlation-ID propagation, PII redaction, and telemetry cost control.
The structure works because the three pillars only become useful when they are correlated. By requiring a propagated correlation ID across logs, traces, and metrics, the prompt turns three disconnected data streams into one coherent story for a single request. The PII-redaction and cost-optimization steps are not afterthoughts: high-volume telemetry gets expensive and legally risky fast, so designing redaction and sampling in from the start is what keeps the stack sustainable.
When to use it
- Standing up observability on a new service before the first incident, not after.
- Correlating logs, traces, and metrics that currently live in separate, disconnected tools.
- Defining real SLOs/SLIs (
[slo_targets]) instead of vibes-based reliability. - Adding PII redaction to logs to meet compliance before an audit forces it.
- Controlling a telemetry bill that is climbing with traffic on
[infrastructure]. - Wiring
[oncall_tool]rotations and[alert_rules]so the right person gets paged.
Example output
You get an implementation plan and config: a structured [log_format] logging setup with [log_levels], [tracing_tool] instrumentation with custom spans, [metrics_tool] collectors for [custom_metrics], [log_aggregator] pipeline config, dashboard templates for [dashboard_types], alert rules matching [alert_rules], [oncall_tool] rotation setup, SLO/SLI definitions, [error_tracker] integration, health-check endpoints, plus correlation-ID propagation and PII-redaction guidance.
Pro tips
- Make correlation-ID propagation non-negotiable; without it, the three pillars stay disconnected and debugging stays guesswork.
- Set
[alert_rules]against[slo_targets]so you page on user-facing impact, not on every transient blip. - Tune sampling for
[tracing_tool]early; tracing every request at scale is the fastest way to a shocking bill. - Define PII redaction before go-live; retrofitting it after sensitive data lands in
[log_aggregator]is painful. - Keep
[custom_metrics]focused on signals you'll act on; vanity metrics inflate cost and dashboard noise. - Start with a few
[dashboard_types]and expand; an overloaded dashboard hides the signal it was meant to show.
