<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <TITLE>Re: [Nagios-users] distributed monitoring - same named hosts?</TITLE> </HEAD> <BODY>  I would suggest coming up with a standard naming convention that incorporates location. Mail-bna, mail-sfo (airport codes) Mail-nash, mail-sanf (first 4 of city) We mostly monitor routers in schools and use the following -- Mcgavock-hs.davidson.tn That can easily be enhacned by prepending with a device type Mail.mcgavock-hs.davidson.tn -- Marc Sent from a very tiny wireless device with a very tiny unlit keyboard. -----Original Message----- From: Martin C. Walker <walk2137@bellsouth.net> To: nagios-users@lists.sourceforge.net <nagios-users@lists.sourceforge.net> Sent: Sun Jun 29 13:23:59 2003 Subject: [Nagios-users] distributed monitoring - same named hosts? How do you deal with same named hosts in a distributed monitoring environment? e.g. suppose I have a local nagios "sensor" at each of several different remote sales offices. they use nsca to send the data back to the central server. Each office has a server called "mail". What are the various methods y'all are using to manage this situation and avoid confusion. Is there a $MACRO$ that identifies the nagios host the service check was executed FROM? ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. <A HREF="http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01">http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </BODY> </HTML>