Currently we have an alert called "Error rate" that can be configured to fire when the total number of alerts exceed a specific threshold during a given time window.
This issue is about adding a similar (but separate!) alert that will fire when the transaction error rate exceed a given percentage threshold, eg. when 20% of transactions are errornous (defined as outcome=failure).
Transaction Error Rate alert
Title: "Transaction error rate | "
Description: If possible there should be a description below the title, shortly explaining the alert (I think we should do this for all alerts)
Configurable fields:
- Environment
- Is above (value in percent, 0-100)
Design for the flyout

Rename "Error rate" alert and updating menu
The "Error rate" alert should be renamed to "Errors" to avoid confusion with the "Transaction error rate" alert.
The alerting menu should be changed to look like this:
- Transaction duration (unchanged)
- Create threshold alert (unchanged)
- Create anomaly alert (unchanged)
- Transaction error rate (new)
- Create threshold alert (new)
- Errors (changed)
- Create threshold alert (changed)
Design for the alerting menu:

Currently we have an alert called "Error rate" that can be configured to fire when the total number of alerts exceed a specific threshold during a given time window.
This issue is about adding a similar (but separate!) alert that will fire when the transaction error rate exceed a given percentage threshold, eg. when 20% of transactions are errornous (defined as
outcome=failure).Transaction Error Rate alert
Title: "Transaction error rate | "
Description: If possible there should be a description below the title, shortly explaining the alert (I think we should do this for all alerts)
Configurable fields:
Design for the flyout

Rename "Error rate" alert and updating menu
The "Error rate" alert should be renamed to "Errors" to avoid confusion with the "Transaction error rate" alert.
The alerting menu should be changed to look like this:
Design for the alerting menu:
