Source code
Stability
No request / correlation IDs
Part of the Observability gaps check · fix arrives as a guide
What it is
Log lines carry no request or correlation id, so entries from a single user action cannot be tied together.
Why it matters
During an incident you have one error and no way to see what led to it. Across services it is worse — the same operation appears as unrelated lines in three places with nothing linking them.
How to fix it
Generate a request id at the edge (or accept an inbound one), carry it through async context, include it on every log line, and forward it on outbound calls so downstream services log the same id.
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.