Source code
Stability
No distributed tracing (multi-service)
Part of the Observability gaps check · fix arrives as a guide
What it is
The system spans multiple services with no distributed tracing: no trace context is propagated between them.
Why it matters
When a request is slow you can see that it was slow, but not where. Debugging becomes correlating timestamps across services by hand, which stops working as soon as there is meaningful concurrency.
How to fix it
Instrument with OpenTelemetry, propagate traceparent on outbound calls, and export to a backend that can show the whole span tree. Auto-instrumentation of the HTTP and database layers covers most of the value.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.