Skip to content
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

alert rule filter "is set" is treating ANY event with a message key as "set" and "does not contain" without a value ignores EVERY event #41584

Open
kerenkhatiwada opened this issue Nov 18, 2022 · 1 comment

Comments

@kerenkhatiwada
Copy link
Member

Environment

SaaS (https://sentry.io/)

Version

No response

Steps to Reproduce

filter "is set" is treating ANY event with a message key as "set"

  1. create an alert rule with a filter like "The event's message value is set "
    image
  2. trigger an event with the message as an empty string
  3. observe the alert is triggered

does not contain without a value ignores EVERY event

  1. create an alert rule with a filter like "The event's message value does not contain " where the value is left empty
    image
  2. trigger any alert with a message
  3. observe the alert is never triggered

Expected Result

filter is set is treating ANY event with a message key as "set"

  • alert is not triggered for events with a message key that is an empty strings

does not contain without a value ignores EVERY event

  • alert is triggered for any event with a message. including a non-operable issue alert may be useful.

Actual Result

filter "is set" is treating ANY event with a message key as "set"

  • alert is for any event

does not contain without a value ignores EVERY event

  • alert is triggered ONLY for events with a message key that is an empty strings
@getsentry-release
Copy link

Routing to @getsentry/workflow for triage. ⏲️

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

No branches or pull requests

4 participants