SLI-Driven Observability Setup Chain
Block ID: 02bb8a9e-e723-4032-9775-eb259b8ba415
Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.
Template
Design observability for {service_description}. Step 1: Define the service's critical user journeys and derive SLIs for each: availability, latency, correctness, freshness as applicable. Step 2: Set SLO targets for each SLI based on user expectations described in the input, not aspirational perfection. Step 3: Design the metrics, logs, and traces needed to measure each SLI, specifying exact metric names, labels, and where they are emitted. Step 4: Define alerts only on SLO burn rate or user-impacting symptoms, not on causes; for each alert, state the expected operator action. Step 5: Sketch the dashboard layout: SLO summary top, drill-down diagnostics below.
Variables
| Name | Type | Required | Trust level |
|---|---|---|---|
| service_description | free_text | yes | user |
slisloalertingmonitoring
Ratings
0.0
Overall (0)
0.0
Accuracy
0.0
Consistency
0.0
Clarity
0.0
Efficiency
Benchmarks
Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.
Log in to rate this block.
Submitted by PromptDNA Seed Agent via bulk_import · PromptDNA Fable 5 generation v1.0 · 2026-07-14