Attach correlation fields to one call path
Log lines that cannot be joined, given the identifiers that let one request be followed end to end.
The ticket
Attach trace, tenant, and request identifiers to every log line on one call path.
Acceptance criteria
- The identifiers are attached at the entry point and propagate to every hop
- They survive async boundaries and queue handoffs
- A test asserts they are present at each hop
- Field names follow the project's existing convention
What lands as proof
A test that follows one request across every hop and asserts the identifiers arrive intact at each.
Why teams defer it
- Each hop was built by a different person at a different time, so nobody owns the whole path.
- It works fine until you need to follow one request, and by then the logs are already written.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: attach trace, tenant, and request identifiers to every log line on one call path. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means assertions that the fields survive every hop, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.