Repository navigation
feat: remove global event processors - #2245
Merged
Merged
Conversation
stayallive
approved these changes
Oct 6, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Removes the static global processors list in favour of event processors on Scopes. The direct replacement for it is using the global scope directly:
The reason to remove this is that we already have event processors on Scopes, meaning that the static list is redundant.
This PR also introduces a small optimisation and correction: We would run event processors unconditionally for all events, including logs and metric events which use less data than error events. That means that for all those events, we would add data only to discard it while serialising. The event processors are now guarded by type and are only executed for errors and transactions