getsentry / getsentry/sentry

Num of events in an issue condition using large time period is flaky

Open
#83,685 28 comments 2 reactions 0 assignees View on GitHub
Bug Product Area: Alerts
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

1. 2 alerts (see [customer case](https://www.notion.so/sentry/17e8b10e4b5d80b8805ffd2d618ac6c1)) are identical except 1 uses `event's {attribute="environment"} value {match="equals"} {value="beta"}` filter, and the other one has the same environment selected at the top instead.
2. An issue (see [customer case](https://www.notion.so/sentry/17e8b10e4b5d80b8805ffd2d618ac6c1)) where ALL events match all other conditions in both alerts and are 100% from the same matching environment.

![Image](https://github.com/user-attachments/assets/00e4301b-5200-4d88-ba60-a67e238f1421)

### Expected Result

both alerts fire

### Actual Result

only the alert with top-level environment filter fires

### Product Area

Alerts

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.