Observability
Send a trace for every request to Langfuse or any OpenTelemetry collector, with tags, filtering and control over whether prompt text leaves the gateway.
ACOG can send a trace for every request to your own observability tools. Traces are sent after the request, in the background: a failure here never delays or fails a request, or changes its billing.
Open Admin → Observability. You need the Edit the organization’s profile permission (admin:org).
Destinations
Configure either, both or neither.
| Destination | Settings | What is sent |
|---|---|---|
| OpenTelemetry | An OTLP/HTTP endpoint | One span per request, using the OpenTelemetry generative-AI semantic conventions |
| Langfuse | Host, public key and secret key (all three, or none) | A trace per request with its generation: model, tokens, cost, latency and, optionally, the prompt and completion |
The Langfuse secret key is stored encrypted and never shown again.
Prompt and completion text
With prompt and completion capture on, each Langfuse trace includes the request’s prompt and the model’s reply. Off, only the economics leave the gateway: tokens, cost, latency and model. Capture is on by default once Langfuse is configured.
If you use data loss prevention, consider turning capture off: text DLP allowed through to the model would otherwise also be sent to Langfuse.
Tags
Tags (for example env:prod) help you filter traces. They come from four places and add up, never replacing each other:
- organization default tags, set here;
- the application’s tags (Applications);
- the API key’s tags (API keys);
- the request’s own
x-acog-trace-tagsheader (comma-separated), plus optional JSON inx-acog-trace-metadata.
Filtering
Trace filters (keep only errors, drop cache hits, sample a percentage) limit what Langfuse receives. They never affect usage reporting or billing.
Per application
Each application can turn trace forwarding off, for example when it already sends its own traces. See Applications.