Marlo Bell wrote:
> I think I miss posted this last week, sorry for the dup if you get one.
>
> Ethan, et all:
>
> It would be nice in Nagios 3.0 to have a little more granularity in
> assigning contacts to hosts/service. Namely, if a particular person
> wants notified for a particular service, but the entire team doesn't
> need those notifications--the only option seems to be to create a new
> contact group with that one person a member and tie that group to the
> service. It would be nice if you could tie a singular contact to a
> host/service. Perhaps you could allow both directives like this:
>
> define serivce {
> service_description ping
> ...
> contacts joeblow,janedoe
> contactgroups network-engineers
> ...
> }
>
> On that same vein it is nice to have the granularity when assigning
> contact groups to services and hosts directly (like in Nagios 2.x), but
> it was sometimes useful to tie a contact group to a ho st group (like in
> Nagios 1.x) or service group. Perhaps this could also be allowed. See
> the following:
>
> define serivce {
> service_description ping
> ...
> contacts joeblow,janedoe
> contactgroups network-engineers
> servicegroups ping-services
> ...
> }
>
> define serivcegroup {
> sevicegroup_name ping-services
> ...
> contacts johndoe
> contactgroups network-operations
> }
>
> It is a little more complex, but in this way you could be as granular as
> you needed, but still be able to use grouping to your advantage.
>
> Marlo
>
I'll put this on my watch list for 3.x - there's a lot of code that
would need to be changed, but I think its doable.
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]