Operational: No request tracing or correlation IDs #123

New issue

Open

opened 2026-05-11 23:08:59 +00:00 by thabeta · 0 comments

thabeta commented

2026-05-11 23:08:59 +00:00

Owner

Severity: Medium

Location

Across all modules

Finding

There is no request ID, trace ID, or correlation ID system:

Cannot trace a request from ingress through routing to provider
Cannot correlate client requests with provider requests
Debugging requires log correlation by timestamp
No OpenTelemetry or tracing integration

Impact

Impossible to debug production issues across multiple components
Cannot track request lifecycle for billing disputes
No visibility into request flow timing

Recommendation

Add request IDs to all inbound requests (generate if not present)
Propagate trace IDs to provider requests via headers
Integrate with OpenTelemetry for distributed tracing
Add structured logging with trace context
Include request ID in all error responses

## Severity: Medium ## Location Across all modules ## Finding There is no request ID, trace ID, or correlation ID system: - Cannot trace a request from ingress through routing to provider - Cannot correlate client requests with provider requests - Debugging requires log correlation by timestamp - No OpenTelemetry or tracing integration ## Impact - Impossible to debug production issues across multiple components - Cannot track request lifecycle for billing disputes - No visibility into request flow timing ## Recommendation - Add request IDs to all inbound requests (generate if not present) - Propagate trace IDs to provider requests via headers - Integrate with OpenTelemetry for distributed tracing - Add structured logging with trace context - Include request ID in all error responses