Service and host notifications: best practise

[Keith Edmunds]

We have a setup similar to: 100 monitored servers split into five groups,
A-E.

We would like notifications for host and service problems for all servers
to be sent to the IT team. In addition, we would like host and service
problems for servers in Group A to go to the group A manager, host and
service problems for Group B to go to the group B manager, and so on.

We tend to manage host notification via host groups, and service
notifications via service groups. We really want to manage service
notifications on a host group basis, so if Apache fails on a group A
machine, we notify the IT team and the Group A manager.

I'm looking for ideas for implementing that in a manageable and scalable
way.

If I've not described the problem clearly enough, I apologise: please ask
questions for clarity.

Thanks,
Keith
-- 
"You can have everything in life you want if you help enough other people
get what they want" - Zig Ziglar. 

Who did you help today?

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null