# Pagerless for OpenTelemetry

> Errors in your OTLP logs and traces become Pagerless problems: grouped, explained and routed to the right person. Any OpenTelemetry SDK, protobuf or JSON.

URL: https://pagerless.dev/integrations/opentelemetry
Updated: 2026-10-22

## Set up

```bash
OTEL_EXPORTER_OTLP_ENDPOINT=https://events.pagerless.dev/v1/otlp
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer pl_live_..."
OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=delta
```

`http/json` works too, and gzip. gRPC is not accepted; use OTLP over HTTP. More: [OpenTelemetry docs](https://pagerless.dev/docs/opentelemetry).

## What it catches

- Log records with severity ERROR or higher.
- Spans with an `exception` event, and SERVER spans that answered 5xx.
- HTTP server request-duration histograms (delta temporality), as request counts per route and status, so the 5xx floor works.

## Questions

### Does Pagerless store my traces?

No. It reads them for errors and keeps at most 5 scrubbed samples per problem for 30 days.