Plan observability for a user journey | DevPrompt Lab

Design a small logging, metric, and alert plan around a specific user journey and service boundary.

Reusable content

Create an observability plan for the user journey. Define a small set of structured events, service metrics, and traces that help answer whether the flow works and where it fails. For each signal give name, dimensions, sampling, retention need, and privacy review. Avoid high-cardinality labels and sensitive payloads. Set alert thresholds from a stated service objective or baseline, not invented numbers. Include a dashboard question and a test that verifies the signal is emitted.

Journey: {{USER_JOURNEY}}

Service boundary: {{SERVICE_BOUNDARY}}

Privacy rules: {{PRIVACY_RULES}}

How to use it

Provide existing service-level objectives and telemetry tools. If absent, propose how to measure a baseline before setting thresholds.

Example

Metric: project_save_failures_total by stable error_code. Alert only after an agreed failure ratio persists over the chosen evaluation window.