Notification List depending on mission critical or/and site

[interduo]

In devices we have:

• Device Site Association: Site1
• Thold Up/Down Email: Global List / List Below / Global and List
• Device Criticality: Low/Med/High/Mission Critical

It would be better to make notification list depending on: A) site (person responsible for administrating that site or network node).

So:

• [ ] Add a field in Management-->Site : 'Site admin email'.
• [ ] Add a 'Site Admin' when You choose Notification List in Thold Up/Down Email Notification.
• [ ] Please allow to choose more notification list devices in Thold Up/Down Email Notification.

B) device criticality (person responsible for network administrating that devices with specified criticality) Don't know how to realize that. Now I just choose all devices with specified criticly and change them notification list field value.

• [ ] Also we should be able to turn off/on list depending on events or time.

So I suggest:

• [x] Adding a column in notify_lists.php. List enabled/disabled [Completed in Thold 2.0]

So we could turn off some list in some events with simple external bash script.

[cigamit]

A) This will come in the rewrite of the plugin. For now you can just select that Sites Admin in the Thresholds notification list B) Not sure how that is different that A) other than its per Device instead of Site. Honestly all of this would probably be easier if we had a tagging system, then you could specify tags for a device, and it would pick the notification list that matched those tags. C) The Maint plugin allows you to disable threshold alerting based upon predefined schedules / times.

[TheWitness]

@interduo, I've implemented Enabled/Disabled on this RFE. I'm saving the rest for an update post Thold 2.0 okay?

[TheWitness]

Note the Checkmarks to the left of the feature request.

[interduo]

@interduo, I've implemented Enabled/Disabled on this RFE. I'm saving the rest for an update post Thold 2.0 okay?

okay! we are waiting for 2.0

[TheWitness]

@interduo, I'm going to push the last of this request to 3.0 as I need to get back to the Cacti 1.3 tasks, and the Thold 2.0 is looking pretty complete sans all the Enhanced Notification options. I just need to get through two more issues before I can put it into beta.

[interduo]

Nice. Its one of the most important thing - when monitoring big infrastructure.

[interduo]

Why You just not integrate this code into cacti core? It's the first plugin people install. The second is monitor :)

[cigamit]

There are plans to do so in possibly 1.3 (albeit probably renaming it to Alerts)

[TheWitness]

@cigamit and I have discussed this pretty extensively. This is one of the reasons I pushed back on a number of features to the 3.0 release. First, we needed to clear the backlog of bugs, then let that go out at 2.0, then the refactor will actually come out as a new plugin. It'll upgrade all the thold stuff. But the level of notification will be what you would expect in today's world of monitoring.

As it stands, Thold 2.0 is going to be a milestone release. I'm pretty excited about it.