Your OTel spans, our errors: A Sentry love story in one trace

Sentry’s OtlpIntegration connects OpenTelemetry tracing with Sentry’s error, log, metric, and event data, addressing the lack of shared context when applications use a standalone OTel SDK and export spans directly through Sentry’s OTLP endpoint. Available across major backend SDKs, it configures OTLP exporting, attaches active OTel trace and span IDs to Sentry events, and thereby enables users to navigate between errors and the traces or spans associated with them. This approach replaces Sentry’s former deeply integrated POTel model for most languages, favoring independent, portable SDKs over in-process interleaving of Sentry and OTel spans, while Java retains POTel as its primary long-term option and Node.js is moving toward lighter native instrumentation. The integration is aimed at teams already using OTel, especially polyglot organizations, and allows them to retain their existing tracing infrastructure while adding Sentry error monitoring; however, exceptions still require a Sentry SDK rather than OTLP alone, duplicate tracing should be avoided, and future Sentry propagation support will require explicit user configuration.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.