Telemetry Overview

Telemetry gives teams visibility into the request lifecycle after the router has selected a provider. It is the operational record that connects routing intent to observed outcomes.

Event model

Each routed request should emit a stable identifier, timestamps, provider selection details, and outcome information. These events provide the backbone for metrics, traces, and audit workflows.

Signal categories

Meridias captures latency, availability, error state, provider choice, and category context. Additional signals can be attached to explain policy decisions or workload-specific checks.

Feedback into routing

Beyond dashboards, live request outcomes feed into health calculations and can alter subsequent routing decisions when a provider begins to drift.

Operational access

Teams should be able to inspect telemetry by request, environment, category, and provider so they can answer both tactical debugging questions and broader performance reviews.

Next step

Drill into Metrics for aggregate views or Logs & Tracing for request-level debugging.