[Nagiosplug-devel] New Threshold Syntax

Páll Guðjón Sigurðsson palli at ok.is
Tue Sep 3 13:43:32 CEST 2013


Holger, we really appreciate all the quality work you guys put into the Nagios Plugins. thanks!

I would personally like to see the new threshold syntax move forward once someone is willing to spend the proper resources on it. In the meantime you guys can help out a lot and give this alternative syntax a better name than "the new threshold syntax". We claim to support it in pynag, but 10 years from now my code will look really silly if it references "the new threshold syntax" everywhere. 

On those notes, we try to follow very closely the guidelines that you guys give us, namely plugin developer guidelines and extra-opts guidelines, no matter what we think of them, but one thing that would help us a lot if you can put a version number (or even just a date) on the guidelines that you post.

That way can make a claim like "we support plugin developer guidelines version 6" and not constantly have to worry about you guys updating the standard without us noticing.




----- Original Message -----
From: "Holger Weiß" <holger at cis.fu-berlin.de>
To: "Nagios Plugins Development" <nagiosplug-devel at lists.sourceforge.net>
Sent: Wednesday, August 21, 2013 12:35:59 PM
Subject: Re: [Nagiosplug-devel] New Threshold Syntax

* Páll Guðjón Sigurðsson <palli at ok.is> [2013-07-15 20:57]:
> We implemented same RFC in pynag (python modules for nagios related
> stuff). We also hit some walls and wanted to make modifications.
> Unfortunately, it's been a long time since it was written and author of
> the proposal is not answering my emails on the topic.
> 
> I am not sure if there is a lot of motivation among the nagios-plugins
> folks to implement this RFC, so i wonder if third party libraries like
> you and should coordinate on it anyway ?

We (the Plugins Development Team) discussed this internally, but we
haven't really reached a consensus on how to proceed.  Some concerns
have been raised regarding the added complexity and the amount of
refactoring necessary to check only for specified thresholds.

Either way, I guess we must acknowledge that we currently lack the
manpower to implement a new threshold syntax, which means we'll probably
stick to the current syntax for the time being.  So I'd say yes: Please
move ahead independently of us.  Personally I quite like the new syntax,
and if you settled on the details and it works well for you, we can
still decide on whether and how to adopt it :-)

Thanks a lot for your work on this!

Holger

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________________
Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net
Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null




More information about the Devel mailing list