getsentry / getsentry/sentry

Prevent Apdex Alerts from being triggered for periods with no transactions

Open
#41,174 7 comments 5 reactions 0 assignees View on GitHub
Bug Product Area: Alerts
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Environment

SaaS (https://sentry.io/)

### Version

_No response_

### Steps to Reproduce

1. Requires no transactions being accepted by your org, either intentionally or because of depleted quota
2. In the Web UI, go to Alerts -> Create Alert -> Apdex -> Set Conditions
3. On step 1, set the interval to "1 minute interval" for testing purposes
4. On step 3, choose "Static: above or below {x}" and set the "Critical field" to "Below 100"
5. No need to set actions on step 4
6. On step 5, give the rule a name and click "Save Rule"
7. Wait for the 1 minute interval to pass
![Screenshot 2022-11-09 at 15 49 25](https://user-images.githubusercontent.com/81985895/200871771-83672e02-b2e1-43be-8609-1a4ed2b96f39.png)

### Expected Result

Because no transactions are being accepted by Sentry, either intentionally or because of depleted quota, there should be no alert triggered.

### Actual Result

Apdex is 0 and therefore an alert is triggered and the alert status is set to "Critical". Alert status remains that way since no transactions are being accepted.
![Screenshot 2022-11-09 at 15 51 49](https://user-images.githubusercontent.com/81985895/200871547-7e64c465-5480-4304-bb1a-bde41842359c.png)

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.