Have you had a look at the 'check_cluster' plugin? It allows you to team multiple services into a single service. You tell it how many can fail/not-fail before raising an alert etc.
http://nagios.sourceforge.net/docs/3_0/clusters.html We use this for our SMTP MX target availability. Stuart > -----Original Message----- > From: Mister IT Guru [mailto:misteritg...@gmx.com] > Sent: Wednesday, 2 February 2011 9:38 PM > To: Nagios Users List > Subject: [Nagios-users] Create a virtual service - How to? > > We have several systems which all work independently, as does everyone, > naturally. We also have 'virtual services' which dependent on these > working. What I'd like to do is set off Alert X, if A, B or C, have a > problem, as well as A, B, or C, also sending an alert to thier > respective responsible persons > > For example, VPN, Email, RDP, and our custom application need to be on > line, in order for remote consultants to be able to work. The custom > app, and email are managed by one team, and VPN and RDP by two other > separate teams. > > This 'service' we can all RC for the sake of argument, and I would like > an alert from the RC service, if any of the four services it relies on > goes down, because the teams involved in managing the the separate > services do it not just for the RC, but for a number of other groups of > users as well. > > How can I achieve this 'virtual service' check I'd like to implement. ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Nagios-users mailing list Nagios-users@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
