[Nagiosplug-help] perfdata output of Nagios Plugins 1.3.0

[Subhendu Ghosh]

snmp is tricky because you can use it for different things.
patches are always accepted. 

Another thing on the agenda is a re-write of check_snmp to get around the 
eight oid limit.

-sg

On 20 Apr 2003, Matthias Eichler wrote:

> Hi,
> 
> so do you have some informations about snmp?
> what is the timeframe for 1.4?
> maybe we can provide some patches for perfdata support, because
> we have some customer who wants to process the perfdata but does
> not want to use APAN...:-/
> 
> Thanks,
> 
> Matthias
> 
> On Sun, 2003-04-20 at 15:35, Subhendu Ghosh wrote:
> > On 20 Apr 2003, Matthias Eichler wrote:
> > 
> > > Hi Everybody,
> > > 
> > > some easy question for which I did not find any specific
> > > answer in the docs, but Ethan's note that a lot of the
> > > Plugins does not support the performance data output yet.
> > > 
> > > Does anybody can say which plugins of 1.3.0 support this
> > > output already? I've tested it and it seems that only the
> > > check_http plugin supports the performance data output...
> > > 
> > > Is that right or am I just too stupid?!?
> > > Does anybody knows which plugins support it or which of
> > > them will support it soon?!?
> > > 
> > > Thanks,
> > > 
> > > Matthias Eichler
> > > 
> > > 
> > 
> > One of the goals for 1.4 is to provide perfdata support.
> > 
> > mailq already has it.
> > ping has patch on SF that needs testing
> > fping needs a similar patch
> > ifstatus is almost there
> > disk has been completely re-written so exiting patch won't work.
> 

-- 




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at 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