Project

General

Profile

Bug #35161

Add Alert Severity and allow configuration on where to send

Added by Michael Reynolds almost 2 years ago. Updated 12 months ago.

Status:
Closed
Priority:
No priority
Assignee:
Lola Yang
Category:
GUI (new)
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Dependent on a related task to be completed
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

This ticket is for the last remaining item from https://redmine.ixsystems.com/issues/26679

Alerts should have a severity ranging from informational to very high.
For example, critical alerts might go to one group of admins, warnings
to another, informational alerts like TrueNAS support alerts could go to
another.


Related issues

Related to FreeNAS - Feature #26679: Add System -> Alerts for configuring alert frequencyDone

History

#1 Updated by Erin Clark almost 2 years ago

  • Assignee changed from Erin Clark to Lola Yang

#2 Updated by Dru Lavigne almost 2 years ago

  • Related to Feature #26679: Add System -> Alerts for configuring alert frequency added

#3 Updated by Dru Lavigne almost 2 years ago

  • Target version changed from Backlog to 11.2-RC2

#4 Updated by Stilez y almost 2 years ago

I'd like to ask that this be done differently.

While severity is a useful way to group alert issues in the UI, it's extremely unhelpful to stipulate them as "critical", "warning" etc for granularity/admin purposes. Instead a user should be given a list of alerts and allowed to configure alert-by-alert which alerts they want to send where.

The reason is that what is "severe" or "critical" for one user, just won't be for another. One user will treat disk temp as critical and wants to know immediately. The other doesn't need to know and wants to see it in their once-a-day rollup email of alerts. One user needs to know if a LUN or LUN supplicant can't be pinged, another doesn't care because their laptop is the only supplicant and regularly disconnected. A user wants some matter treated as critical, but can't direct critical to his/her "emergency" email without also directing other alerts that they don't want to know about urgently, to that email as well. And so on.

You can't stipulate which are severe, or warnings, or informational, across the board, without causing users to be spammed by alerts they don't want, or to miss alerts they do. If alerts can only be "critical" or "warning" etc, then a user who wants some matter alerted and asks for it as a feature will get declined (even if it's a good idea) because to add it as critical/warning etc will mean users who don't want that alert treated as critical etc will have to be sent it with other critical alerts. In some cases one critical issue may be sent to one user, a different critical issue to another user, but if all you have is "critical/warning", this can't be done. What a mess and annoyance it may lead to, in actual use!

For these reasons, I ask/urge that the method in the original feature request #26679 is used, where the GUI presents a list of alert causes, and the user can select for each, how they want to be alerted if it happens. There are not a million kinds of alert reason, so a dropdown box or checkbox to choose for each cause, what method to alert using, is easy for a user (much like forums which ask if you want a popup or email for reply/thanks etc). It's easy, common and intuitive.

Please don't pre-select which alerts must be grouped with which others. It's a box that impedes users, increases spam alerting, and restricts the future.

#5 Updated by Michael Reynolds almost 2 years ago

Michael Reynolds wrote:

This ticket is for the last remaining item from https://redmine.ixsystems.com/issues/26679

Alerts should have a severity ranging from informational to very high.
For example, critical alerts might go to one group of admins, warnings
to another, informational alerts like TrueNAS support alerts could go to
another.

Adding details to address the comments:

Alerts should have a user configurable severity ranging from informational to very high.
What was explained in the comment is how I understood this ticket.

More or less all things related to alerts should be user configurable.
Hopefully, this clarifies the ticket.

#6 Updated by Lola Yang almost 2 years ago

  • Copied to Feature #36298: Add Alert Severity and allow configuration on where to send added

#7 Updated by Lola Yang almost 2 years ago

  • Copied to deleted (Feature #36298: Add Alert Severity and allow configuration on where to send)

#8 Updated by Lola Yang almost 2 years ago

  • Blocked by Feature #36298: Add Alert Severity and allow configuration on where to send added

#9 Updated by Lola Yang almost 2 years ago

  • Status changed from Unscreened to Blocked

#10 Avatar?id=13649&size=24x24 Updated by Ben Gadd over 1 year ago

  • Target version changed from 11.2-RC2 to Backlog

#11 Updated by Dru Lavigne over 1 year ago

  • Target version changed from Backlog to 11.3

#12 Updated by Dru Lavigne over 1 year ago

  • Reason for Blocked set to Dependent on a related task to be completed

#13 Avatar?id=14398&size=24x24 Updated by Kris Moore 12 months ago

  • Blocked by deleted (Feature #36298: Add Alert Severity and allow configuration on where to send)

#14 Avatar?id=14398&size=24x24 Updated by Kris Moore 12 months ago

  • Status changed from Blocked to Closed

Also available in: Atom PDF