[Nagiosplug-devel] Perf Data

[Subhendu Ghosh]

On 18 Feb 2003, Karl DeBisschop wrote:

> On Tue, 2003-02-18 at 18:04, Russell Scibetti wrote:
> > If it would be helpful, this is something I can work on in parallel
> > and submit a patch as I add to each plugin.
> 
> It would be very helpful, but in no case are we adding perf data before
> the release. We are in feature freeze.
> 
> > Would it better to have the plugins output perfdata by default, or
> > require a cmdline arg?  I want to be as consistent between plugins as
> > possible.
> 
> So far, it has been enabled by default.
> 
> Not sure if that is the right decision, however.
> 
> If there were not size limits on the nagios data pipe, I'd send it by
> default. But I'd hate to deserialize the pipe for an added few bytes of
> perf data that wasn't even wanted.
> 
> Thoughts anyone?

I think Russell raised this question earlier about the pipe msg size.  If 
Nagios is spawning a separate process and doing a spopen - then the pipe 
for each plugin invocation should be distinct.

Perhaps we need to confirm this as a feature with Ethan.

The impact would be on passive checks where the results are submitted 
through the named pipe.  If there is another way to do the passive checks
I'd be interested.

> 
> > Russell
> > 
> > Karl DeBisschop wrote:
> > > On Tue, 2003-02-18 at 17:21, Russell Scibetti wrote:
> > > 
> > > > Are the plugins in the 1.3b3 release going to have more built-in 
> > > > perfdata output?  For example, check_disk can return the amount of space 
> > > > used, check_load can return the 3 load values, check_snmp can return the 
> > > > response in both the output and the perfdata (maybe if a cmd-line arg is 
> > > > given), etc.
> > > > 
> > > > I'm just trying to figure out if I need to write additions to the b2 
> > > > plugins for perfdata or not.  We are looking to start dumping all 
> > > > performance related information into RRD.  Thanks.
> > > > 
> > > > Russell
> > > > 
> > > 
> > > Those will go in immediately after the release. So hopefully in less
> > > than 2 weeks.
> > > 
> > > If you track the CVS with your changes, and provide patches against the
> > > individual plugins at that time, you have a very high likelihood of
> > > having them accepted almost as fast as you submit them. 
> > > 
> > > Even if you don't, I expect the perf data to happen very quickly after
> > > the release.

-- 

-sg