OpenTelemetry gives you a standard way to instrument your code. Sentry gives that telemetry data meaning: errors connected to traces, logs tied to issues, and debugging tools that point to the root cause in your code.Send traces and logs directly via OTLP, forward them through the OTel Collector, or run Sentry SDKs alongside your existing OpenTelemetry setup. Tolerated by 4 million developers GitHubDisneyAtlassianLinearVercelCloudflareSlackMetronomeAutodeskMicrosoftInstacartLyftBoltMondayCursorAnthropicFactory AISentryBasetenRunlayerConvexSupabase Send OTel data directly to Sentry Point your OTLP exporter at Sentry and start seeing data Configure your OpenTelemetry SDK to export traces and logs to Sentry's OTLP endpoint. Set the OTEL_EXPORTER_OTLP_ENDPOINT environment variable, add your auth header, and you're done. No Collector, no sidecar agents, no extra infrastructure to manage.Standard OTel environment variables, nothing proprietarySupports gzip compression and protobuf encodingWorks with any language that has an OpenTelemetry SDK Direct OTLP docs Connect errors to the traces that caused them The context that trace-only backends miss Most OpenTelemetry backends show you traces and logs. Sentry connects those to the errors, stack traces, and breadcrumbs that explain what actually went wrong. When a Sentry SDK and OTel instrumentation run in the same service, they share the same trace ID automatically, so errors link to the exact span where they happened.Stack traces with source context, not just span namesBreadcrumbs show the sequence of events leading to each failureEvery issue links to the commit and release that introduced it Explore issue details Trace across Sentry SDKs and OTel services in one view One trace from frontend to OTel-instrumented backend Your frontend uses a Sentry SDK. Your backend uses OpenTelemetry. Sentry propagates W3C Trace Context headers so both sides of the request show up in a single distributed trace, with timing for every span. You can follow a slow page load from the browser through your API, into the database query that caused it.Unified traces across Sentry SDK and OTel-instrumented servicesW3C Trace Context propagation works out of the boxSupported on 20+ frontend and mobile frameworks Sentry with OpenTelemetry docs Forward infrastructure telemetry through the OTel Collector Collect from infrastructure sources without changing application code Use the OpenTelemetry Collector, Vector, or Fluent Bit to forward logs and traces from infrastructure sources into Sentry. The Sentry Exporter for the OTel Collector handles multi-project routing and automatic project creation, so each service's telemetry lands in the right place.Supported pipelines: OpenTelemetry Collector, Vector, Fluent BitInfrastructure sources: AWS CloudWatch, Kafka, Nginx, syslog, Windows EventsManaged platform drains for Vercel, Cloudflare, and Heroku Forwarding docs Traces and logs in one system, errors in another, with no connection between them.Requires a Collector, exporters, and often a sidecar agent for each service.Dashboards show latency and throughput, not the line of code that caused the problem.Getting started typically requires a sales call or a guided demo.Pricing scales with data volume in ways that are hard to predict.Errors, traces, and logs connected in one workflow, with stack traces and breadcrumbs attached.Direct OTLP ingestion: point your SDK at Sentry, no Collector required for basic setups.Every trace links to the function, file, and commit that caused the issue.Install the SDK, see data in minutes. No sales call needed.Transparent, predictable pricing with a generous free tier. Getting started with Sentry is simple We support every technology (except the ones we don't). Get started with just a few lines of code.