Report errors with OpenTelemetry, no SDK required
Already instrumented with OpenTelemetry? Point your OTLP logs 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 turns error-level records into the same grouped issues as everything else.
Point your exporter at Condux
OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.condux.ai/api/<project>
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.
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 directly (JSON today; protobuf is a follow-up).