|
|
| Subject: | Making Administrators Subscribers to a Notification (Zenoss 4.2.5 vs 5.2) |
| Author: | Garrett Michael Hayes |
| Posted: | 2017-03-29 09:48 |
We're still running on Zenoss 4.2.5 (mostly because of inertia), but I'd like to add something to my notifications setup, and I'm wondering if it's doable in version 5.x. It doesn't seem to be a capability of 4.2.5.
I'd like to be able to add the "administrators" for devices as subscribers to an alert notification, not individually, but just "whomever is the administrator".
An example may help clarify. I have a trigger and an alert that goes out when any monitored production system runs low on disk space. That alert comes to me as overall Sys Admin. Now imagine that I am monitoring 50 servers, and that each of those servers has one or more designated sub-administrators. (ie: our DBA is responsible for the SQL servers, etc.). I can currently add our DBA as a designated administrator of each SQL server and so forth. In the event of overlap, I can designate multiople device admins.
What I would like to do is have just the one trigger and one notification that has me as a subscriber and "device administrators" as a subscriber. Then, when a server goes low on space, I get an email and whoever is listed as administrator of *that* device also gets the email. It would avoid having to write multiple triggers and multiple notifications.
Is that doable in 5.2?
| Subject: | Notifications work the same |
| Author: | [Not Specified] |
| Posted: | 2017-03-30 10:22 |
Notifications work the same way in 5.2 as they do in 4.2.5.
From my experience, there is no way to dynamically change the subscriber of a notification based on the specific device. You could set up the notification email content to include the specific device's administrator(s) if you include that information in one of the fields of the device page, like Comments, but there is no way to have the notification be sent to those specific individuals based on that information.
You will likely need to set up multiple notifications, and have each notification include different administrators.
| < |
Previous zenoss server not showing inventory: Type: <class 'zenoss.protocols.services.zep ... |
Next Cant start Serviced on Master, unable to read valid mux header? |
> |