FW: Migrating from single monitoring server to distributed monitoring server
Ethan Galstad
nagios at nagios.org
Wed Dec 18 05:47:51 CET 2002
> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net
> [mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Andrew Kemp
> Sent: Friday, 6 December 2002 3:24 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Migrating from single monitoring server to
> distributed monitoring server
>
>
> Gidday,
>
>
> We have a situation where a department has been running Netsaint
> in a stand alone environment to monitor their hosts and services.
>
> My department runs a distributed environment to monitor the enterprise
> wide hosts and services.
>
> We are in the position where we wish to integrate the other departments
> monitoring into the distributed environment. If I was to just add the
> hosts to the distributed environment as new entries, this would be very
> easy. However, there is a requirement to keep the Netsaint host (soon to
> be Nagios) and make it another distributed node in the monitoring
> environment. Also, I need to keep the historical data for the
> hosts/services
> that this host monitors (a couple of months).
>
> Can I simply do:
>
> cat nagios.log nagios2.log | sort > new-nagios.log (where nagios2.log
> is
> the log from the other host) to keep the information ?
>
> I will then iterate through all relevant log files to migrate the
> historical
> information across.
>
>
> Thanks.
>
> Andrew
>
>
You should be able to do this. However, make sure to strip out all
references to program starts/stops/restarts in the distributed logs
before you merge them into the central log.
Also, if you do this you will probably have some slight inaccuracies
with regards to availability reports on the distributed
hosts/services. The main reason for that is that the central and
distributed copies of Nagios probably started/stopped/restarted at
different times and Nagios logs some events (like initial state info)
immediately after startup. I don't think this should affect things
negatively too much, but keep the original logs around just in case
the combined log gives you problems.
Ethan Galstad,
Nagios Developer
---
Email: nagios at nagios.org
Website: http://www.nagios.org
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
More information about the Users
mailing list