Broadcast
Automatically send traces of your LLM requests to external observability platforms.
Broadcast allows you to automatically send traces from your EUrouter requests to external observability and analytics platforms. Monitor, debug, and analyze your LLM usage across your preferred tools without any additional instrumentation in your application code.
Broadcast is currently in Beta. We're actively adding new destinations and improving the feature.
How it works
When you enable Broadcast, EUrouter captures trace data from your API requests and forwards it to your configured destinations. This happens asynchronously after each request completes, so it adds no latency to your API responses.
Each trace includes:
- Request and response data -- the input messages and model output
- Token usage -- prompt tokens, completion tokens, and totals
- Cost information -- the total cost of the request
- Timing -- request start time, end time, and latency
- Model information -- the model and provider used
Getting started
- Go to Broadcast in your dashboard
- Click Add Destination next to the platform you want to connect
- Enter your credentials (API keys, endpoints, etc.)
- Use Test Connection to verify your setup
- Click Create to save
Once saved, traces are sent automatically for all your API requests.
Supported destinations
| Destination | Description |
|---|---|
| Langfuse | Open-source LLM engineering platform |
| LangWatch | LLM observability and analytics |
| Datadog | Cloud monitoring and analytics |
| PostHog | Product analytics with LLM observability |
| OpenTelemetry Collector | Send traces to any OTLP-compatible backend |
| Webhook | Raw OTLP JSON to any HTTPS endpoint |
Configuration options
Every destination supports these settings:
Sampling rate
Control what percentage of traces are sent. A rate of 100% sends all traces, 50% sends roughly half. Useful for high-volume applications where you want to reduce costs on your observability platform.
Privacy mode
When enabled, prompt and completion text is stripped from traces before sending. Only metadata (model, tokens, cost, latency) is included. Useful for complying with data privacy regulations while still tracking usage metrics.
API key filter
Restrict a destination to only receive traces from specific API keys. This lets you:
- Route traces from different environments to different platforms
- Send production traces at a lower sampling rate than development
- Isolate monitoring for specific use cases
If no keys are selected, the destination receives traces from all your API keys.
Security
Your destination credentials are encrypted before storage and only decrypted when sending traces. Traces are sent asynchronously, so enabling Broadcast does not affect your API response times.