Report errors with OpenTelemetry, no SDK required
Already instrumented with OpenTelemetry? Point your OTLP exporter at Condux and errors flow in with no Sentry SDK. Condux maps severity, message and exception attributes into grouped issues.
Not every team wants another vendor SDK. If you already emit OpenTelemetry, Condux accepts native OTLP HTTP logs and traces and turns error-level records and failed spans into the same grouped issues as everything else.
Point your exporter at Condux
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobufOTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.condux.ai/api/<project>OTEL_EXPORTER_OTLP_HEADERS=x-condux-auth=<key>
AI agent failures
- Failed spans become issues
Export traces too and a model call, tool or agent run that ends in an error becomes an issue. Spans that succeed are not stored.
- One issue per failure
A failing tool marks its own span and the agent span above it. When both arrive together, Condux reports the tool rather than both.
- Prompts are dropped
A span's attributes become tags only from a fixed list that names the operation, such as the model, provider, agent and tool. The prompts, completions and tool arguments a span carries are dropped, and the error message is scrubbed like any other.
- Provider outages stay quiet
A span its instrumentation names as a model call is filed as a warning when it fails. Automatic fixes start only from errors, so a rate limit at your provider does not spend one.
What gets stored
- Error-or-worse records
Being an error monitor, Condux stores error-level and exception-bearing logs.
- Exception mapping
Exception type, message and stack trace attributes become an issue with frames.
- Resource attributes
service.name, version and deployment.environment map to the release and environment.
- Users affected
enduser.id, user.id or user.email on a log record count the people an error reached.
Frequently asked questions
Do I need a Sentry SDK at all?
No. With OpenTelemetry you report errors with no Sentry SDK. Condux ingests OTLP HTTP logs and traces directly, in both the protobuf and JSON encodings. Set the exporter's protocol to HTTP, since some OpenTelemetry distributions default to gRPC.