# Instrument one endpoint group with metrics and spans

A group of endpoints with no latency or error data, instrumented with a dashboard query included.

Category: Observability and operability
Source: https://letsship.ai/use-cases/instrument-one-endpoint-group
Published: 2026-08-25

## Goal

Add metrics and tracing spans to one endpoint group.

## Acceptance criteria

- Each endpoint reports latency, throughput, and error rate
- Span names follow a convention and are asserted in tests
- Cardinality is bounded, with no unbounded identifiers as labels
- A dashboard query using the new signals is included

## What lands as proof

A dashboard query returning real data from the new instrumentation, not just the instrumentation code.

## 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: Instrument the {group} endpoints

Description: Add metrics and tracing spans to one endpoint group.

Acceptance criteria:
- Each endpoint reports latency, throughput, and error rate
- Span names follow a convention and are asserted in tests
- Cardinality is bounded, with no unbounded identifiers as labels
- A dashboard query using the new signals is included

Before you create the issue, find an endpoint group in this repository with no metrics and replace {group} with it.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: add metrics and tracing spans to one endpoint group. 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 span names asserted in tests, dashboard query included, 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.