feat(telemetry-processor): Rate Limits#16027
Merged
philipphofmann merged 3 commits intomasterfrom Jan 19, 2026
Merged
Conversation
Add a concept of how the telemetry processor should interact with rate limits.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
philipphofmann
force-pushed
the
feat/telemetry-processor-rate-limits
branch
from
d7b2ef6 to
c432075
Compare
philipphofmann
force-pushed
the
feat/telemetry-processor-rate-limits
branch
from
c432075 to
586efc8
Compare
6 tasks
giortzisg
approved these changes
Jan 16, 2026
philipphofmann
added a commit
that referenced
this pull request
Jan 29, 2026
Add a concept of how the telemetry processor interacts with client reports. Slighly related to #16027.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Add a concept of how the telemetry processor should interact with rate limits.
Slighly related to #15983.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: