docs(python): update docs under Configuration for stream mode

[inventarSarah]

DESCRIBE YOUR PR

This PR updates tracing-relevant pages under Configuration with information about the new stream mode and the new Span APIs.

A note on the Sampling page in this PR: the tracing part on this page is content-wise almost identical to the Configure Sampling under Tracing. In this branch, I did not update the Sampling page; instead, I only linked to the other guide for stream-mode users. I strongly feel we need to streamline these two pages to avoid duplicate maintenance work -- but this needs to be tackled in a separate PR.

Important

Broken links: I added links to the New Spans guide on these pages, but since this guide does not exist in this branch, we get a linting error.
Should only be merged after #18456

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	Actions	Updated (UTC)
sentry-docs	Ready	Preview, Comment	Jul 2, 2026 8:22pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ignored	Preview	Jul 2, 2026 8:22pm

[coolguyzone]

Suggested change

	You can use the <PlatformIdentifier name="ignore-spans" /> option to filter out spans that match a certain pattern by providing a list of strings, compiled regular expressions, or dictionaries. hen using strings, a span name containing the string will be filtered out. For exact or more complex pattern matching, use compiled regular expressions instead.
	You can use the <PlatformIdentifier name="ignore-spans" /> option to filter out spans that match a certain pattern by providing a list of strings, compiled regular expressions, or dictionaries. When using strings, a span name containing the string will be filtered out. For exact or more complex pattern matching, use compiled regular expressions instead.

🐓

[coolguyzone]

Looks good! 🤠

[sentrivana]

Suggested change

A list of strings, compiled regular expressions, or dictionaries that shouldn't be sent to Sentry. When using strings, a span name containing the string will be filtered out. For exact or more complex pattern matching, use compiled regular expressions instead. You can also provide a dictionary with `name` and/or `attributes` keys to match on multiple conditions. At least one key must be provided.

A list of strings, compiled regular expressions, or dictionaries describing spans that shouldn't be sent to Sentry. When using strings, a span name containing the string will be filtered out. For exact or more complex pattern matching, use compiled regular expressions instead. You can also provide a dictionary with `name` and/or `attributes` keys to match on multiple conditions. At least one key must be provided.

[alexander-alderman-webb]

All spans pass through before_send_span()

Suggested change

The SDK provides a <PlatformIdentifier name="before-send" /> hook, which is invoked before an error or message event is sent and can be used to modify event data to remove sensitive information. The SDK also provides a <PlatformIdentifier name="before-send-transaction" /> hook, that does the same thing for transactions, and a <PlatformIdentifier name="before-send-span" /> hook, that does the same thing for service spans in <PlatformLink to="/tracing/new-spans/">stream mode</PlatformLink>. We recommend using these hooks in the SDK to **scrub any data before it is sent**, to ensure that sensitive data never leaves the local environment.

The SDK provides a <PlatformIdentifier name="before-send" /> hook, which is invoked before an error or message event is sent and can be used to modify event data to remove sensitive information. The SDK also provides a <PlatformIdentifier name="before-send-transaction" /> hook, that does the same thing for transactions, and a <PlatformIdentifier name="before-send-span" /> hook, that does the same thing for spans in <PlatformLink to="/tracing/new-spans/">stream mode</PlatformLink>. We recommend using these hooks in the SDK to **scrub any data before it is sent**, to ensure that sensitive data never leaves the local environment.

[alexander-alderman-webb]

Not true, you can remove the sentence 😄

Suggested change

	span's lifetime. In contrast, <PlatformIdentifier name="before-send-span" /> can
	only work with attributes set at span start time. Attributes added later during
	the span's lifetime aren't available.
	span's lifetime.

[sentry]

Bug: The documentation example for sentry_sdk.set_attribute incorrectly passes a dictionary. The function expects a key and a value as two separate arguments.
_{Severity: MEDIUM}

Suggested Fix

Update the incorrect examples to use the correct two-argument call, for instance, sentry_sdk.set_attribute("user.id", user.id). Alternatively, use the plural form sentry_sdk.set_attributes({"user.id": user.id}) if setting multiple attributes from a dictionary is intended.

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/sensitive-data/set-user/python.mdx#L9-L14

Potential issue: The code examples in
`platform-includes/sensitive-data/set-user/python.mdx` for Stream Mode demonstrate
incorrect usage of `sentry_sdk.set_attribute`. The examples pass a dictionary as a
single argument, such as `sentry_sdk.set_attribute({"user.id": user.id})`. However, the
function's signature is `set_attribute(key: str, value: Any)`, requiring two separate
arguments. This will cause a `TypeError` at runtime for any user who copies and runs
this example code. This is inconsistent with other examples in the same pull request,
such as in `set-tag/python.mdx`, which use the correct two-argument format.

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