EUrouter
Broadcast (Beta)

Broadcast

Automatically send traces of your LLM requests to external observability platforms.

OpenAPI JSON

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:

  • 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
  • The decision -- whether the request was allowed, redacted, blocked or failed, and why (see below)
  • Prompts and completions -- only for the API keys you switch on (see below)

Getting started

  1. Go to Broadcast in your dashboard
  2. Click Add Destination next to the platform you want to connect
  3. Enter your credentials (API keys, endpoints, etc.)
  4. Use Test Connection to verify your setup
  5. Click Create to save

Once saved, traces are sent automatically for all your API requests, including the ones EUrouter blocks or rejects.


Supported destinations

DestinationDescription
LangfuseOpen-source LLM engineering platform
LangWatchLLM observability and analytics
DatadogCloud monitoring and analytics
PostHogProduct analytics with LLM observability
OpenTelemetry CollectorSend traces to any OTLP-compatible backend
WebhookRaw OTLP JSON to any HTTPS endpoint

The decision record

Every trace carries the same decision record you see in the request log and in the x-eurouter-decision response headers. Each destination page lists the exact field names for that tool.

FieldValues
Decisionallowed, redacted (PII was redacted before the provider saw it), blocked or error
Reason codesWhy, for example pii.redacted, pii.blocked, policy.country_not_allowed, plan.rate_limited
PII countsHow many items of each PII type were detected, never the values themselves
Processing countriesISO country codes where the provider endpoint processes the request

Blocked and rejected requests

A request that EUrouter blocks or rejects (a policy or PII block, a rate limit, a spending limit, an invalid request) is sent as a trace too, with its reason codes, zero tokens and no cost. It follows the same sampling rate, workspace and API key filter as any other trace.

A blocked request never carries its prompt, even for API keys with Forward prompts and completions switched on. It was stopped before it reached a provider, often because of what the prompt contains, so the text stays inside EUrouter.


Delivery, retries and the delivery log

EUrouter sends each trace with a 5-second timeout. When the destination does not answer, cannot be reached, is rate limiting (HTTP 429) or returns a server error (HTTP 5xx), EUrouter tries again after 1 second and once more after 4 seconds, 3 tries in total. Other responses, such as HTTP 401 for a wrong API key, are not retried. Retries run in the background and never slow down your API responses. When a destination is down under load, EUrouter holds at most 20 retries for it and counts further traces as failed after their first try.

Each destination card on the Broadcast page shows the last 7 days: whether traces are being delivered, how many were delivered and how many failed, and the failures by error class. The log holds counts and times only, never a payload, a response body or a URL. It can lag by up to a minute.

Error classMeaning
authThe destination refused the credentials (HTTP 401 or 403)
rate_limitedThe destination rate limited EUrouter (HTTP 429)
rejectedThe destination refused the request (other HTTP 3xx or 4xx)
server_errorThe destination failed (HTTP 5xx)
timeoutNo answer within 5 seconds
unreachableThe endpoint could not be reached
configThe endpoint URL is missing or not allowed
internalEUrouter could not send the trace

Through the API, GET /api/v1/broadcast-destinations/deliveries returns the same summary for every destination.


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.

Forward prompts and completions

EUrouter does not store prompts. By default a destination receives metadata only (model, provider, tokens, cost, latency and status), never the prompt or completion text.

To send prompts and completions to your own tool, switch on Forward prompts and completions on the destination and select the API keys it applies to. Only requests made with those keys carry their content. Keys you create later start with forwarding off, and requests from the dashboard Chat never carry content.

Only an owner or admin can change this setting. Through the API, set content_api_keys to the hashes of the keys (an empty list switches forwarding off). privacy_mode is deprecated: true clears content_api_keys, and false has no effect.

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.

Was this page helpful?

Still stuck? Contact support

On this page