fix(telemetry-processor): Clarify push-based vs pull-based

[philipphofmann]

DESCRIBE YOUR PR

Based on #16652. Part of #16189.

Clarifies the difference between the push-based and pull-based telemetry buffer approaches and adds cross-links between them.

Co-Authored-By: Claude noreply@anthropic.com

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	Mar 5, 2026 7:58am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
sentry-docs	Ignored	Preview	Mar 5, 2026 7:58am

[giortzisg]

Looks good, left some minor comments

[giortzisg]

I am torn between creating a pull-based approach section on the index page or just have it only on the backend page to avoid duplication. However even if we keep it as is, let's add a section for the pull-based approach so that this comment links to the section and not the whole page of the backend processor.

[philipphofmann]

@giortzisg, I explained it here as well because it felt a bit odd to me to define the common requirements here without stating that for some approaches, they don't apply. It felt a bit odd to define it here and then, in the backend page, saying, "Hey, and by the way, these requirements in the index page don't apply here."

Just to clarify, you also want to explain a complete pull-based approach here, which would mean that we should extract the pull-based approach with all the round robin stuff from the backend? Or what exactly would you put into this section here on the index page?

[coolguyzone]

Suggested change

Unlike the [push-based approach](/sdk/foundations/processing/telemetry-processor/#push-based-approach), the telemetry buffer does not push data to the telemetry scheduler. Instead, the [telemetry scheduler](#telemetryscheduler) iterates through all buffers using weighted round-robin and pulls data when it determines a buffer is ready to flush. Still, the telemetry buffer **MUST** follow the common [telemetry buffer requirements](/sdk/foundations/processing/telemetry-processor/#telemetry-buffer). Here are the additional backend-specific requirements:

Unlike the [push-based approach](/sdk/foundations/processing/telemetry-processor/#push-based-approach), the telemetry buffer does not push data to the telemetry scheduler. Instead, the [telemetry scheduler](#telemetryscheduler) iterates through all buffers using weighted round-robin scheduling and pulls data when it determines a buffer is ready to flush. Still, the telemetry buffer **MUST** follow the common [telemetry buffer requirements](/sdk/foundations/processing/telemetry-processor/#telemetry-buffer). Here are the additional backend-specific requirements:

[coolguyzone]

LGTM