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)
sentry-docs	Ready	Preview, Comment	Jun 30, 2026 2:35pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ignored	Preview	Jun 30, 2026 2:35pm

[adinauer]

Java changes LGTM

[Flash0ver]

Review for docs/platforms/dotnet/:

[Litarnus]

nit: I think we should have a ## Supported Versions section here too instead of implicitly specifying the version

[Flash0ver]

platforms/dotnet/ ✅

[sentry]

Bug: The composer require command for the Laravel OTLP integration guide is missing the required version constraint for sentry/sentry-laravel, which can lead to installing an incompatible version.
_{Severity: MEDIUM}

Suggested Fix

Update the composer require command in the Laravel OTLP integration guide to include the minimum version constraint. Change sentry/sentry-laravel to sentry/sentry-laravel:"^4.25". This ensures Composer installs a compatible version.

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: docs/platforms/php/guides/laravel/integrations/otlp.mdx#L20-L23

Potential issue: The Laravel OTLP integration documentation specifies that
`sentry/sentry-laravel: 4.25.0+` is required, but the provided `composer require`
command does not enforce this version. If a user's environment resolves to an older
version (e.g., due to an existing `composer.lock` file), they will install an
incompatible package. This will cause a `ClassNotFoundException` at runtime when the
application tries to use `\Sentry\Integration\OTLPIntegration`, which does not exist in
versions prior to 4.25.0.

[sentry]

Bug: The PlatformLink component on the OTLP integration pages for Laravel and Symfony creates a self-referential link instead of linking to the parent PHP platform documentation.
_{Severity: LOW}

Suggested Fix

The logic in the PlatformLink component needs to be adjusted to correctly handle fallbacks when an explicit guide file exists. It should distinguish between the current page and a true parent/fallback page to prevent generating self-referential links.

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: docs/platforms/php/guides/symfony/integrations/otlp.mdx#L58

Potential issue: The `PlatformLink` component on the Symfony and Laravel OTLP guide
pages generates a self-referential link. Because explicit guide files exist (e.g.,
`docs/platforms/php/guides/symfony/integrations/otlp.mdx`), the component's logic finds
the current page first and sets the link's `href` to the current URL. The
`fallbackPlatform="php"` property is never used. As a result, users clicking the "OTLP
integration docs" link are not navigated to the parent PHP platform documentation but
are instead reloaded on the same page, creating a broken user experience.

Also affects:

• docs/platforms/php/guides/laravel/integrations/otlp.mdx:59

[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).