-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apply inbound filters to spans (using abstraction layer) #3317
Comments
Set Apr 9 as due date, because Replays depend on the abstraction layer as well. |
jjbayer
added a commit
that referenced
this issue
Apr 9, 2024
Currently, inbound filters only work for event types, that is error events and transactions. In the near future we will want inbound filters to apply to other data types as well, such as standalone spans and session replays. To prepare for this generalization, make filters act on a trait that supplies the necessary field instead of the `Event` itself: ```rust // `Filterable` for legacy inbound filters, // `Getter` for generic inbound filters. pub fn should_filter<F: Filterable + Getter>(item: &F, ...); ``` ref: #3317 --------- Co-authored-by: Iker Barriocanal <32816711+iker-barriocanal@users.noreply.github.com>
New due date is Apr 30, because Replays are already unbocked by #3397. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tasks
span::process
. #3550event.
getters for spans to have a compatibility mode for generic inbound filters. This is a best-effort task, probably only a handful of fields make sense (e.g. release, environment, ...). #3551The text was updated successfully, but these errors were encountered: