getsentry / getsentry/sentry

Allow transaction.duration: to be used as an event filter for Metric alerts

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

Description

### Problem Statement

When creating a performance alert using Percent Change as the Set Threshold, it's possible that the previous time period has a duration of 0 if it is a transaction that is not run at all times. This causes the percent change alerts to not be very useful.

**Example** -
Screenshot 2023-11-15 at 9 29 36 AM
Screenshot 2023-11-15 at 9 30 06 AM

### Solution Brainstorm

Allowing `transaction.duration:` to be used as a filter in the Filter Events section of the alert can prevent this and ensure only transactions with durations populate the charts and alerts.

Screenshot 2023-11-15 at 9 37 01 AM

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.