You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem we’re facing is that some of our events cause seq to repeatedly send out alerts to Opsgenie and the oncall engineers every minute or so. OpsGenie handles its deduplication via the Alias however our eventid from seq is unique every time an event is generated so it isnt deduplicating but creating a new ticket each time. If there was the option to set our own Alias to pass to opsgenie instead of just the seq EventId by default we could get around this.
It would be good if we could do the something similar as for other fields in the Opsgenie alerting app. Setting our own alias and overriding the default EventId being passed would work as we would use something like {{Stack}}-{{AppName}} in a custom alias field which would then cause errors from our kubernetes to deduplicate based on our namespace and pod.
The text was updated successfully, but these errors were encountered:
The problem we’re facing is that some of our events cause seq to repeatedly send out alerts to Opsgenie and the oncall engineers every minute or so. OpsGenie handles its deduplication via the Alias however our eventid from seq is unique every time an event is generated so it isnt deduplicating but creating a new ticket each time. If there was the option to set our own Alias to pass to opsgenie instead of just the seq EventId by default we could get around this.
It would be good if we could do the something similar as for other fields in the Opsgenie alerting app. Setting our own alias and overriding the default EventId being passed would work as we would use something like {{Stack}}-{{AppName}} in a custom alias field which would then cause errors from our kubernetes to deduplicate based on our namespace and pod.
The text was updated successfully, but these errors were encountered: