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
fix(filter): Added is_enabled field to transactions name filter #2251
fix(filter): Added is_enabled field to transactions name filter #2251
Conversation
@@ -141,12 +141,14 @@ pub struct ErrorMessagesFilterConfig { | |||
pub struct IgnoreTransactionsFilterConfig { | |||
/// List of patterns for ignored transactions that should be filtered. | |||
pub patterns: GlobPatterns, | |||
/// True if the filter is enabled | |||
pub is_enabled: bool, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a tiny chance that somebody updated their external Relay since this filter was introduced. These old Relays would ignore this flag until they update again. But given the short time frame and the fact that there was no calendar release in between, I think we can ignore this problem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What @jjbayer said.
Otherwise lgtm
Co-authored-by: Joris Bayer <joris.bayer@sentry.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for getting to this!
This PR adds the is_enabled field to the TransactionsName configuration.
The flag is added in order to make it easier to work with it in Sentry (since all inbound filters have it).