Skip to content
This repository has been archived by the owner on Jun 17, 2023. It is now read-only.

Notifications page needs to be more configurable and needs better help documentation #39

Open
jonpanozzo opened this issue Dec 10, 2014 · 1 comment

Comments

@jonpanozzo
Copy link
Collaborator

There are two major features lacking from the current notifications system:

1) A way to configure what events should trigger a notification based on:

  1. Disk Temp (any single disk reaches "X" temp)
  2. CPU Temp (if available)
  3. Disk Spin Up (any one disk loud)
  4. Disk Spin Down (any one disk quiet)
  5. Array Spun Down (all disks quiet)
  6. APCUPSd Alert of Power Outage (if available)
  7. APCUPSd Alert of Imminent Shutdown (< X minutes configurable)
  8. System Powering Down (configurable for all powerdowns or only automated powerdowns)
  9. System Rebooting (configurable for all reboots or only automated reboots)
  10. Disk Failure (any single disk in array or cache)
  11. Disk Errors (SMART data errors; Tom M has some good input here I think)
  12. Other Hardware Errors (just generalizing now)

I am not sure of the degree of difficulty in getting any of these implemented, so my recommendation is we take the approach of easiest to implement first, then we can review the list again, see if there are any "must haves" for 6.0, and move on from there. Some of these could be moved to 6.1 if we needed.

2) Documentation on what specifically triggers a notification.

The only help documentation present right now is on the SMTP Settings tab. We need to add help documentation to the Notification Settings and Archived Settings tab to explain each setting. I will volunteer to do the actual writing, but first we need to define the events, their triggers, and what configuration options we want to put in there.

@bergware
Copy link
Collaborator

Did you guys have a look at the latest addtiions made to the notifications system ?

It doesn't cover all of the items mentioned above, and I believe notifications is an area which requires further development, though you might want to decide what goes into 6.0 and what will be for versions beyond 6.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants