Hello. Has anyone come up with solutions for processing Nagios performance
data on a server other than a Nagios server? We've been processing perfdata
results on our Nagios server(s) for a while now and increasingly it's just
eating up too much I/O to make me comfortable.
Yes, we do use rrdcached and yes, I realize that shuffling data around on
different disk spindles and controllers would help, but in today's world where
companies don't like building any kind of physical server let alone one with
all that additional hardware, that's not entirely an option for us.
I realize that once the perfdata files are on the dedicated graphing server(s),
processing them into RRD files there should be a no-brainer. My problem is
figuring out how to get them there without say, using a NAS device. (If I/O's
a problem locally, I don't want to shuffle that I/O to an even slower network
device).
It would be ideal if somehow there was a process that I could just send that
data to and have it picked up remotely. Like if maybe Merlin have a special
kind of peer that just received a stream of perfdata or something. Anything
else I could imagine would be some kind of home-grown solution like say pumping
events into a messaging system from the Nagios server(s) and then letting the
graphing server pick them up from the message queue(s). I could also imagine
some kind of fancy-pants module in Nagios 4 that did something like this, maybe.
Any thoughts would be appreciated.
Thanks
Mark
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
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
