getsentry / getsentry/sentry

An Issue Alert When Condition Doesn't Trigger Reliably

Open
#84,056 12 comments 0 reactions 0 assignees View on GitHub
Bug Component: Rules
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. Create an Issue Alert with conditions provided (screenshot)
2. Throw a couple of errors, one error every minute or so

Image

### Expected Result

Alert should be triggered reliably by 1 event.

### Actual Result

Alert is sometimes not triggered by 1 event (the HttpException in this case). Instead it seems to only fire reliably for 2, 3, 4, 5 events in the 1 min interval.

**My Alert Page**
Image

**My Issues Page**
Image

### 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.