Skip to main content
Distributed tracing helps you understand the full journey of requests through your system.

How Tracing Works

  1. Beacon generates a trace ID for each user session
  2. This ID is passed in headers to your backend
  3. Your backend logs include the same trace ID
  4. You can follow a request from frontend to backend

Enabling Tracing

Trace Context

The SDK automatically adds trace headers to fetch requests:

Manual Spans

Create spans for important operations:

Backend Integration

Pass trace context to your backend:

Viewing Traces

In Dashboard > Settings > Beacon > Traces:
  • See the full request timeline
  • Identify slow spans
  • Find errors in the trace
  • View span details and metadata

Trace Structure

Sampling

Tracing adds overhead. Use sampling in production:
For debugging, temporarily increase the rate or force tracing: