Traffic Routing Observability Guide

List what responders must answer: which flow matched, what context arrived, which rule or score mattered, what destination was selected, how it was delivered, and whether the response succeeded. Collect fields that support those questions.

Use event identifiers and campaign identifiers to connect routing logs, DuckRoute decisions, tracker records, and destination health checks into one investigation. Normalize all timestamps and preserve the original traffic source label so an operator can follow the same request without relying on visual guesswork.

Segment destination ratios and reasons by flow, source, market, device, and time. Add focused views for unknown hosts, missing campaign context, upstream errors, and manual overrides instead of one undifferentiated traffic total.

Choose conditions with an owner and response, such as a sudden route-ratio shift, elevated upstream failures, or disappearing source values. Static thresholds need source-aware baselines and should avoid paging on ordinary campaign launches.

Introduce a safe test misconfiguration, follow the symptom to its first divergent layer, and measure whether the evidence identifies the cause. Update field collection and runbooks when responders need private spreadsheets or undocumented knowledge.