# 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.

Category: Observability and operability
Source: https://letsship.ai/use-cases/link-logs-traces-and-errors
Published: 2026-08-25

## Goal

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.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Correlate logs, traces, and errors

Description: 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

Before you create the issue, list which logging, tracing, and error tools this repository sends to, and note whether they already share an identifier.
```

## 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.