# Wire the error reporter into a service that throws into the void

A service whose exceptions reach nobody, connected to the tracker with a seeded throw as proof.

Category: Error reporting and triage
Source: https://letsship.ai/use-cases/wire-the-error-reporter-into-a-service
Published: 2026-08-25

## Goal

Connect one service to the error reporter so its exceptions are captured.

## Acceptance criteria

- A deliberately thrown exception appears in the tracker with a usable stack
- Initialisation happens before any application code can throw
- The environment and service name are stamped on every event
- Reporting failures do not crash the service

## What lands as proof

A screenshot of the seeded exception in the tracker, which is the only evidence the wiring works end to end.

## 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: Wire error reporting into {service}

Description: Connect one service to the error reporter so its exceptions are captured.

Acceptance criteria:
- A deliberately thrown exception appears in the tracker with a usable stack
- Initialisation happens before any application code can throw
- The environment and service name are stamped on every event
- Reporting failures do not crash the service

Before you create the issue, find a service in this repository that does not initialise the error reporter and replace {service} with it.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: connect one service to the error reporter so its exceptions are captured. 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 deliberately thrown exception arrives in the tracker with its stack, 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.