docs: Add missing OTLP integration docs and fix drift across SDKs

[dingsdax]

closes getsentry/sentry-dotnet#5190

DESCRIBE YOUR PR

• 4 SDKs shipped OTLP support with no docs
• 2 legacy pages lacked deprecation alerts
• overview page still listed Go/PHP as "Coming Soon"
• existing Go/Java docs had stale version numbers and incorrect config

Overview of changes

New documentation pages:

• PHP OTLP integration (docs/platforms/php/common/integrations/otlp/)
• .NET OTLP integration (docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry-otlp.mdx)
• Symfony OTLP integration (docs/platforms/php/guides/symfony/integrations/otlp.mdx)
• Laravel OTLP integration (docs/platforms/php/guides/laravel/integrations/otlp.mdx)

Deprecation alerts added:

• Python legacy OpenTelemetry page: strengthened from "New Integration Option" to formal deprecation warning
• Ruby legacy OpenTelemetry page: same treatment
• .NET legacy OpenTelemetry page: new deprecation alert pointing to OTLP exporter docs

Hub page updated:

• docs/concepts/otlp/sentry-with-otel.mdx: removed "Coming Soon" section, added .NET, Go, Java, PHP, Laravel, Symfony (9 SDKs total, alphabetical)

Existing docs corrected:

• Go: updated version floors (Go 1.25+, sentry-go 0.47.0+, OTel 1.43.0+), changed "deprecated" to "removed" for NewSentrySpanProcessor
• Java: fixed otel.propagators from sentry to tracecontext,baggage,sentry (matching official SDK samples)

Per-SDK changes

PHP (sentry-php, sentry-symfony, sentry-laravel)

New pages:

• docs/platforms/php/common/integrations/otlp/index.mdx
  • Documents OTLPIntegration class
  • Install: open-telemetry/sdk, open-telemetry/exporter-otlp
  • Options: setupOtlpTracesExporter, collectorUrl
  • Supported versions: PHP 8.1+, sentry/sentry 4.23.0+
• docs/platforms/php/guides/symfony/integrations/otlp.mdx
  • Symfony bundle YAML config with auto-service registration
  • Links to parent PHP page for options
  • Requires sentry-symfony ^5.10
• docs/platforms/php/guides/laravel/integrations/otlp.mdx
  • Laravel config/sentry.php config using ::class pattern
  • Links to parent PHP page for options
  • Requires sentry-laravel ^4.25

Verification: all code examples checked against sentry-php OTLPIntegration.php constructor, sentry-symfony test fixtures, and sentry-laravel ServiceProvider source.

.NET (sentry-dotnet)

New page:

• docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry-otlp.mdx
  • Documents Sentry.OpenTelemetry.Exporter NuGet package
  • AddSentryOtlpExporter(dsn) and UseOtlp() extension methods
  • Options: dsnString, collectorUrl (Uri), defaultTextMapPropagator
  • Supported versions: .NET 6.0+, OTel 1.15.0+

Updated page:

• docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry.mdx
  • Added deprecation alert pointing to new OTLP docs
  • Renamed title to "OpenTelemetry Support (Deprecated)"

Verification: checked against SentryTracerProviderBuilderExtensions.cs, SentryOptionsExtensions.cs, and official console/ASP.NET Core samples.

Python (sentry-python)

Updated page:

• docs/platforms/python/tracing/instrumentation/opentelemetry.mdx
  • Changed alert from "New Integration Option" to formal deprecation warning
  • OpenTelemetryIntegration was deprecated in chore: Deprecate OpenTelemetryIntegration in favor of OTLPIntegration and no-op for span first sentry-python#6494 (June 2026)

Verification: existing OTLP docs confirmed correct against sentry_sdk/integrations/otlp.py.

Ruby (sentry-ruby)

Updated page:

• docs/platforms/ruby/common/tracing/instrumentation/opentelemetry.mdx
  • Changed alert from "New Integration Option" to formal deprecation warning
  • Renamed title to "OpenTelemetry Support (Deprecated)"

Verification: existing OTLP docs confirmed correct against sentry-opentelemetry gem source.

Go (sentry-go)

Updated pages:

• platform-includes/performance/opentelemetry-install/go.mdx
  • Corrected version requirements:
    • Go 1.18 → 1.25+
    • sentry-go 0.18.0 → 0.47.0+
    • OTel 1.11.0 → 1.43.0+
• docs/platforms/go/common/tracing/instrumentation/opentelemetry.mdx
  • Changed "Span Processor Deprecation" to "Span Processor Removed"
  • NewSentrySpanProcessor and NewSentryPropagator were fully removed in v0.47.0

Verification: checked against otel/otlp/span_exporter.go, otel/go.mod, and _examples/otlp/main.go.

Java (sentry-java)

Updated page:

• docs/platforms/java/common/opentelemetry/setup/otlp.mdx
  • Fixed otel.propagators in both plain Java and Spring Boot examples:
    • Before: sentry
    • After: tracecontext,baggage,sentry
  • Without tracecontext,baggage, W3C traceparent propagation is lost

Verification: all code examples confirmed correct against sentry-opentelemetry-otlp module source and sample apps.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
  Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ready	Preview, Comment	Jul 7, 2026 9:02pm
sentry-docs	Ready	Preview, Comment	Jul 7, 2026 9:02pm

[jamescrosswell]

Our current plan is to remove this (per the dev docs):

• fix(otlp): don't configure an automatic OTel propagator sentry-dotnet#5319

The OTEL SDK in .NET only allows one propagator to be configured so an alternative would be to configure a composite propagator that did both the W3C and the Sentry propagation. I'm not sure if we want to do that by default though, since the user may have their own propagators configured (and this contradicts the behaviour currently described in the dev docs).

Another alternative would be just to document how users can configure such a composite propagator (we provide the public types but don't wire them up by default).

Yet another alternative would be to provide an extension method that let's users do this easily (and also wrap any of their own custom propagators so that these are included in the composite).

[dingsdax]

yes that's the plan, we will remove the automatic propagator and align all SDKs this way, hence the Alert, which was admittingly at the wrong placing on the page

[sentry]

Bug: The Go OpenTelemetry installation guide specifies an outdated sentry-go version (v0.45.0+), which will cause runtime failures due to removed APIs in the required newer versions.
_{Severity: MEDIUM}

Suggested Fix

Update the version constraints in platform-includes/performance/opentelemetry-install/go.mdx to reflect the actual minimum requirements. Change sentry-go v0.45.0+ to sentry-go v0.47.0+ and go.opentelemetry.io/otel v1.40.0+ to go.opentelemetry.io/otel v1.43.0+.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: platform-includes/performance/opentelemetry-install/go.mdx#L1-L6

Potential issue: The documentation file
`platform-includes/performance/opentelemetry-install/go.mdx` specifies outdated version
requirements for Go dependencies. It instructs users to install `sentry-go v0.45.0+` and
`go.opentelemetry.io/otel v1.40.0+`. However, the documented OpenTelemetry setup
requires `sentry-go v0.47.0+` due to breaking changes in that version, specifically the
removal of `NewSentrySpanProcessor()` and `NewSentryPropagator()`. Users following the
current instructions with an older `sentry-go` version like `v0.45.0` will encounter
runtime failures, as the code they are instructed to use relies on APIs that no longer
exist in the required version.

[jamescrosswell]

Not necessarily a problem - just a comment:

 .AddSource("MyApp") // the name of your ActivitySource

We don't necessarily need this... the SDK user would need this if they want to add their own custom spans/instrumentation - but OTEL and OTLP can be used without this to capture spans from other libraries (e.g. the stuff emitted by OpenTelemetry.Instrumentation.Http).

We can leave this in there (anyone who is familiar with OTEL will understand it's significance - it's not part of the Sentry SDK)... or we could leave it out. It can confuse people who are new to OTEL. I don't have strong opinions either way.

[jamescrosswell]

LGTM

[sentry]

Bug: The documentation incorrectly states a requirement of Go >= 1.25. This is likely a typo, as the actual minimum version is probably Go >= 1.21.
_{Severity: MEDIUM}

Suggested Fix

Verify the actual minimum Go version required by the sentry-go SDK, which is likely Go >= 1.21 or Go >= 1.18. Update the documentation at platform-includes/performance/opentelemetry-install/go.mdx to reflect the correct version requirement.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: platform-includes/performance/opentelemetry-install/go.mdx#L3

Potential issue: The documentation at
`platform-includes/performance/opentelemetry-install/go.mdx` was updated to state a
minimum Go version requirement of `Go >= 1.25`. This is almost certainly a typo, as the
commit message only mentions an OpenTelemetry dependency update, not a major Go version
jump. The actual minimum version required by the SDK is likely `Go >= 1.21` or `Go >=
1.18`. This incorrect documentation will mislead users with compatible Go versions
(e.g., 1.21-1.24) into believing they cannot use the OTLP integration, potentially
blocking its adoption.