<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hey Mark,<br>
<br>
I've been stewing on an idea like this as well. I haven't come up
with a perfect solution yet. I know of another user who
implemented a large install and used NAS for the rrdfiles, but I
recognize your concerns there. Would it be plausible to simply
mount an additional drive in the perfdata directory so that all of
those writes happen to a separate disk while still on the local
machine?<br>
<br>
The other idea I've been thinking about but haven't had time to
play with yet would be to use the performance data processing
command to send the perfdata to the offloaded machine (maybe using
xinetd), and then just drop that data into the perfdata spool so
you could have pnp running on the offloaded machine. From there
you could just the web access for PNP on the 2nd machine.
Obviously there are some mechanics to work out there, and I'm not
sure how much bandwidth that would eat up, but like I said, so far
it's just in the idea stage. <br>
<br>
<br>
On 10/3/2012 9:56 AM, Frost, Mark {BIS} wrote:<br>
</div>
<blockquote
cite="mid:BB690CA131D24C449394CA847A2CB0D781DDB41BA9@PEPWMV00089.corp.pep.pvt"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Davor,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My
concern is more about the actual I/O to the RRD files and
not so much processing the to-be-processed perfdata files
(i.e. temporary files). The heavy I/O is happening on the
RRD filesystem and since I would of course need the RRD
files to persist, I would not want to store them on a ram
disk. Plus it would need to be a fairly large ram disk to
hold all the rrd files even if I were willing to lose them
all if a reboot occurred.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We
do use ram disks for Nagios status.dat files and spool files
(i.e. things I can afford to lose in a reboot/crash) and
it’s definitely been a good thing. It still seems weird to
have to do so much “compensating” for Nagios normal
operations for a moderately large installation (not really
even huge) to make it work well. I’m guessing again that
this is going to be vastly improved with Nagios 4 as well.
At least no spool files.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mark<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
davor grgicevic [<a class="moz-txt-link-freetext" href="mailto:dgrgicevic@gmail.com">mailto:dgrgicevic@gmail.com</a>] <br>
<b>Sent:</b> Wednesday, October 03, 2012 10:45 AM<br>
<b>To:</b> Nagios Users List<br>
<b>Subject:</b> Re: [Nagios-users] solutions for off-server
PNP4Nagios perfdata processing?<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">Hi
Mark ...<br>
<br>
did you try a using a ram disk <br>
<br>
<a moz-do-not-send="true"
href="http://exchange.nagios.org/directory/Documentation/Nagios-XI-Documentation/Utilizing-A-RAM-Disk-In-NagiosXI/details">http://exchange.nagios.org/directory/Documentation/Nagios-XI-Documentation/Utilizing-A-RAM-Disk-In-NagiosXI/details</a><br>
<br>
<br>
Davor<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On Wed, Oct 3,
2012 at 4:33 PM, Frost, Mark {BIS} <<a
moz-do-not-send="true"
href="mailto:mark.frost1@pepsico.com" target="_blank">mark.frost1@pepsico.com</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif"">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif"">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif"">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).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif"">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif"">Any
thoughts would be appreciated.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif"">Thanks<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif";color:#888888"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif";color:#888888">Mark<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span
style="font-family:"Calibri","sans-serif";color:#888888"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><br>
------------------------------------------------------------------------------<br>
Don't let slow site performance ruin your business. Deploy
New Relic APM<br>
Deploy New Relic app performance management and know exactly<br>
what is happening inside your Ruby, Python, PHP, Java, and
.NET app<br>
Try New Relic at no cost today and get our sweet Data Nerd
shirt too!<br>
<a moz-do-not-send="true"
href="http://p.sf.net/sfu/newrelic-dev2dev"
target="_blank">http://p.sf.net/sfu/newrelic-dev2dev</a><br>
_______________________________________________<br>
Nagios-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br>
<a moz-do-not-send="true"
href="https://lists.sourceforge.net/lists/listinfo/nagios-users"
target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>
::: Please include Nagios version, plugin version (-v) and
OS when reporting any issue.<br>
::: Messages without supporting info will risk being sent to
/dev/null<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br clear="all">
<br>
-- <br>
Davor Grgicevic<o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
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!
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/newrelic-dev2dev">http://p.sf.net/sfu/newrelic-dev2dev</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Nagios-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" 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</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Mike Guthrie
Technical Team
___
Nagios Enterprises, LLC
Email: <a class="moz-txt-link-abbreviated" href="mailto:mguthrie@nagios.com">mguthrie@nagios.com</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.nagios.com">www.nagios.com</a>
</pre>
</body>
</html>