Link logs, traces, and errors so one click moves between them
Three tools holding pieces of the same request, wired so one click moves between them.
The ticket
Make it possible to move from an error to its trace to its logs with one identifier.
Acceptance criteria
- A shared identifier is present on logs, traces, and reported errors
- Each tool links to the others using it
- One real incident is walked end to end as proof
- The identifier is generated once per request rather than per hop
What lands as proof
A written walkthrough of one real incident moving between all three tools, with links that resolve.
Why teams defer it
- Each tool was adopted separately and works well enough alone, so the seams between them have no owner.
- Proving it works means having an incident to walk through, which nobody wants to wait for.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: make it possible to move from an error to its trace to its logs with one identifier. 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 a single incident walked end to end across all three signals, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.