Re: [Nagios-devel] Latencies with process-perfdata command

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] Latencies with process-perfdata command

Post by Guest »

------=_Part_34911_20744409.1170957977613
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 2/2/07, Marc DeTrano wrote:
>
> Hendrik Baecker wrote:
> > Hi List,
>
> I would be curious to know how this compares with some of the things
> that have come along since perf2rrd, and some of the ideas in
> development (is someone writing a NEB module to parse this data?)
>
> Marc
> Gridshield, S.A:


We have gone back and forth on whether to do this in a separate NEB module
or to modify the NDO receiver daemon to tee (with another TCP socket more
than likely) the perf data off to one of the rrd based tools (letting the
regular status data stuff continue into a standard NDO database).

Because of our size and not wanting to replicate data already being sent via
NDO to our database server, I am leaning toward the latter. The downside of
that is having to do an NDO install for those who aren't ready to make that
leap. And with the front-end work being pushed back, that is less and less
common. We are kind of banking on NDO for our mid-range plans, but that may
not be a good strategy.

Opinions?

------=_Part_34911_20744409.1170957977613
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 2/2/07, Marc DeTrano <[email protected]> wrote:
Hendrik Baecker wrote:> Hi List,<SNIP>I would be curious to know how this compares with some of the thingsthat have come along since perf2rrd, and some of the ideas indevelopment (is someone writing a NEB module to parse this data?)
MarcGridshield, S.A:We have gone back and forth on whether to do this in a separate NEB module or to modify the NDO receiver daemon to tee (with another TCP socket more than likely) the perf data off to one of the rrd based tools (letting the regular status data stuff continue into a standard NDO database).
Because of our size and not wanting to replicate data already being sent via NDO to our database server, I am leaning toward the latter. The downside of that is having to do an NDO install for those who aren't ready to make that leap. And with the front-end work being pushed back, that is less and less common. We are kind of banking on NDO for our mid-range plans, but that may not be a good strategy.
Opinions?

------=_Part_34911_20744409.1170957977613--





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked