Skip to content

Rename otlpIntegration to openTelemetryIntegration #23937

Description

@andreiborza

The otlpIntegration name is misleading. The integration sends nothing over OTLP: it sets up no exporter, no span processor and no tracer provider. All it does is trace-connect Sentry events (errors, logs, metrics and crons) to the OpenTelemetry span that is active when they happen.

Rename it to openTelemetryIntegration, with the integration reporting itself as OpenTelemetry instead of Otlp.

openTelemetry (capital T) over opentelemetry, because it matches the casing the SDKs already use everywhere else (enableOpenTelemetrySetup, and v10's skipOpenTelemetrySetup / openTelemetrySpanProcessors) as well as OpenTelemetry's own branding.

getOtlpTracesEndpoint() keeps its name. That helper really is about OTLP: it derives the URL and auth headers of Sentry's OTLP traces endpoint from the DSN.

v11 is not released yet and otlpIntegration is itself a v11 rename of the v10 @sentry/node-core/light/otlp export, so no deprecation shim is needed. The MIGRATION.md sections that describe the v10 to v11 move need updating to the new name.

Affected: @sentry/server-utils (definition), and the re-exports in @sentry/node, @sentry/bun, @sentry/deno, @sentry/cloudflare, @sentry/vercel-edge, @sentry/astro, @sentry/aws-serverless, @sentry/google-cloud-serverless.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions