Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
User Problem
Alerts are de-duplicated when another alert is received with the same alias as an existing open alert. However if the new alert has different values for other alert fields (i.e. message, description, etc.) the original alert does not get updated with the new values.
A lot of monitoring tools have different thresholds and levels. Warning, Failing, Critical, etc - or just think of the CPU usage.
Some of these tools are sending an alert, when these threshold/levels are rising. Here comes the problem - the original alert in OpsGenie will deduplicate it, without providing a way to update the content of the alert to reflect the new threshold/level.
Suggested Solutions
Add an option (checkbox) within each integration for "Update alert fields upon deduplication".
That way users can choose whether they want alert fields updated when they are deduplicated by an alert that has new values for certain fields.
Current Workarounds
Users can include this field that is changing values in the alias field, so that when the alert is sent with a different value for a particular field, it will create a new alert instead of de-duplicating
Attachments
Issue Links
- is duplicated by
-
OPSGENIE-1362 Ability to update alert fields on deduplication
- Gathering Interest
- Mentioned in