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 should have been triggered by an issue, but it did not #81959

Open
dalnoki opened this issue Dec 11, 2024 · 1 comment
Open

Alert should have been triggered by an issue, but it did not #81959

dalnoki opened this issue Dec 11, 2024 · 1 comment
Labels

Comments

@dalnoki
Copy link
Contributor

dalnoki commented Dec 11, 2024

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. Set up an alert that should trigger when the number of events in an issue is more than 3 in 15m
  2. An issue met this condition, but when the events came in so close together the query didn't catch them all and the alert didn't trigger

Please find an example and additional information in the Jira shadow ticket.

Expected Result

The alert should trigger in every case when the condition is met

Actual Result

The alert did not trigger

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

┆Issue is synchronized with this Jira Improvement by Unito

@dalnoki dalnoki added the Sync: Jira Apply to auto-create a Jira shadow ticket label Dec 11, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Dec 11, 2024

Auto-routing to @getsentry/product-owners-alerts for triage ⏲️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Waiting for: Product Owner
Development

No branches or pull requests

1 participant