Alert grouping does very little except cause alerts to go unacknowledged. The ability to configure grouping assume you want it. There should be a way to allow your customers to only group when they see a benefit.
Grouping alerts that come in quickly can not done fast enough to prevent alerts from being acknowledged before grouping starts (because 1 alert will never form a group). Once one alert in the group is acknowledged, it appears that you can't just do a group acknowledgement.
It is easy to lose track of the alerts that have not been acknowledged and are still open due to the group not updating it's own status quick enough to reflect all the alerts within the group.
Also, the creation of the group also causes an alert, which, at 3:30 a.m. when you are embroiled in an outage is the last thing you need!
We had no choice about losing OpsGenie. Give us the options we want/need to at least bring Jira in line with our expected alert behaviors.
Hello @pbutt
There is already an Atlassian feature request specifically for this:
JSDCLOUD-15158 / ROVO-767 – Having option to enable/disable and customise Alert Grouping in JSM Operation
Part of that request has already been delivered: Premium and Enterprise Operations admins can now configure alert grouping under:
Operations → Team → Alert groups
https://support.atlassian.com/jira-service-management-cloud/docs/configure-alert-grouping/
https://confluence.atlassian.com/cloud/atlassian-cloud-changes-1721270737.html
Best,
Arek 🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.