Symfony sentry handler

[Litarnus]

DESCRIBE YOUR PR

Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.

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

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

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

Project	Deployment	Review	Updated (UTC)
develop-docs	Ready	Preview, Comment	Jan 8, 2026 2:46pm
sentry-docs	Ready	Preview, Comment	Jan 8, 2026 2:46pm

[sentry]

Bug: The updated Monolog handler configuration guide omits the fillExtraContext argument, which defaults to false, silently stopping Monolog context and extra data from being sent to Sentry.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

The documentation change migrates from a deprecated type: sentry Monolog handler to the Sentry\Monolog\Handler service. The previous configuration effectively set fill_extra_context: true. The new configuration example omits the corresponding fillExtraContext argument in the handler's constructor. Since the default value for fillExtraContext is false, users following the new guide will silently lose Monolog context and extra data in their Sentry events. This is a functional regression that can hinder debugging efforts by reducing the amount of diagnostic information available.

💡 Suggested Fix

To maintain feature parity, explicitly set the fillExtraContext argument to true in the new YAML configuration example.

Sentry\Monolog\Handler:
    arguments:
        - '@Sentry\State\HubInterface'
        - !php/const Monolog\Logger::ERROR
        - true  # bubble
        - true  # fillExtraContext

Alternatively, document this as a breaking change.

🤖 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/monolog.mdx#L52-L56

Potential issue: The documentation change migrates from a deprecated `type: sentry`
Monolog handler to the `Sentry\Monolog\Handler` service. The previous configuration
effectively set `fill_extra_context: true`. The new configuration example omits the
corresponding `fillExtraContext` argument in the handler's constructor. Since the
default value for `fillExtraContext` is `false`, users following the new guide will
silently lose Monolog context and extra data in their Sentry events. This is a
functional regression that can hinder debugging efforts by reducing the amount of
diagnostic information available.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 8342759}