Skip to main content
OpenTelemetry lets you send agent traces, logs, and metrics to FailproofAI Cloud using the standard OTLP/HTTP protocol. It is optional. Your existing FailproofAI integrations continue working without enabling it.

Turn on ingest for your organisation

An organisation admin opens Settings → OpenTelemetry and turns on ingest. Use a Cloud API key with events:add permission, the same permission used for agent reporting. If ingest is off, Cloud refuses OTLP exports, so failproofai otel enable changes nothing and your agents keep sending sessions the usual way. Run failproofai otel status to check the organisation switch, and ask an admin to turn it on.

Connect a coding agent

Connect your machine with failproofai config, then choose an agent:
The setup command supports Claude Code, Codex, and Copilot and chooses Cloud or a local authenticated relay as appropriate. Copilot uses the local relay automatically. Start your configured FailproofAI daemon before using the relay. If FailproofAI already sends an agent’s session transcripts, setup asks whether to switch that agent to OTEL. The default is No. Accepting stops transcript uploads for that agent; it does not change policy enforcement or reporting from other agents.

Connect an application

Use your application’s OpenTelemetry instrumentation with these environment variables:
Replace <key> with your API key. Keep the secret out of shell history, screen recordings, and committed configuration. For a configured machine, failproofai otel env --service my-agent prints the block with its existing key. Its output contains a credential. Cloud accepts OTLP/HTTP exports for traces, logs, and metrics, as protobuf or JSON, including gzip-compressed requests. It does not accept OTLP/gRPC. Metrics are acknowledged for exporter compatibility but are not stored or displayed. Supported agent traces and coding-agent logs become sessions; fields the agent does not export remain absent.

Capture prompt text

Text capture can include prompts, tool arguments, and other sensitive content. failproofai otel enable turns it on. Add --no-content to keep prompt and tool-detail capture off.
For an agent you configure manually, use its own content-capture controls:
Add these variables to your agent’s environment alongside the application block above:
Set both content variables to 0 to avoid capturing prompts and tool details.

Check or undo setup

Status distinguishes settings managed by FailproofAI from telemetry you configured elsewhere. Disable restores the previous managed settings and the agent’s previous transcript-upload choice.

OpenTelemetry CLI

Command options, local relay setup, and troubleshooting.