Skip to content

fix(telemetry-processor): Clarify backend telemetry processor scope and limitations#16652

Open
philipphofmann wants to merge 3 commits intomasterfrom
docs/clarify-backend-telemetry-processor-scope
Open

fix(telemetry-processor): Clarify backend telemetry processor scope and limitations#16652
philipphofmann wants to merge 3 commits intomasterfrom
docs/clarify-backend-telemetry-processor-scope

Conversation

@philipphofmann
Copy link
Member

DESCRIBE YOUR PR

Clarifies that the backend telemetry processor's pull-based approach is optimized for high load but may not suit SDKs needing offline caching support (e.g., Java). Each SDK should evaluate whether to adopt the pull-based or push-based model based on its platform constraints.

  • Reworded intro to focus on the pull-based scheduling model
  • Added paragraph explaining trade-offs with offline caching

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

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

…itations

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Mar 3, 2026

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

Project Deployment Actions Updated (UTC)
develop-docs Ready Ready Preview, Comment Mar 3, 2026 10:27am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
sentry-docs Ignored Ignored Preview Mar 3, 2026 10:27am

Request Review

@philipphofmann philipphofmann changed the title docs(develop-docs): Clarify backend telemetry processor scope and limitations fix(telemetry-processor): Clarify backend telemetry processor scope and limitations Mar 3, 2026
@philipphofmann philipphofmann marked this pull request as ready for review March 3, 2026 10:17
philipphofmann and others added 2 commits March 3, 2026 11:19
…processor

Addresses PR feedback from #16637 where Close(timeout) was missing
from the minimal API definition.

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant