distributed monitoring - same named hosts?

Marc Powell mpowell at ena.com
Sun Jun 29 20:47:05 CEST 2003


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 at bellsouth.net>
To: nagios-users at lists.sourceforge.net <nagios-users at 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.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20030629/8a1b0227/attachment.html>


More information about the Users mailing list