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
I was thinking that it may be very useful to extend thold plugin with some customization options, let me submit them here for your validation:
Note: A checked feature is already available.
Device Status (UP/DOWN) and Thresholds
Allow to configure a custom message to replace the global default message for each device
Allow multiple notification lists
Allow the use of css templates (like Reporting aka Nectar) for the message (logo, formatting, etc) [Done in Thold 2.0]
Thresholds
Fix the timestamps for notifications (on my CentOS server it sends in epoch format) [No known action to take]
Select time interval for the issue of the notification - now if multiple notifications for multiple issues are sent for a graph, there is no zoom and it can be misleading to which issue is reported by which alert [Done in Thold 2.0]
Operator Notes are not added to the notification email [Done in Thold 2.0]
Group Thresholds and alert configuration for multiple Data source items in a graph - Often graphs has multiple data source and would make sense to be able to configure message and alerting options and apply it to more than one data source item: an example can be on symmetric links to apply a threshold alert and message for both traffic in and traffic out, for more complex graph it would facilitate a lot besides using templates
The text was updated successfully, but these errors were encountered:
cigamit
changed the title
[1.0.4] (Enhancement) extend message and notification options
Extend message and notification options
Feb 24, 2018
Hi Everyone,
I was thinking that it may be very useful to extend thold plugin with some customization options, let me submit them here for your validation:
Note: A checked feature is already available.
Device Status (UP/DOWN) and Thresholds
Thresholds
The text was updated successfully, but these errors were encountered: