<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hi Palli.</span><br><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Thank you for your suggestion.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">I followed your suggestion and implemented the threshold evaluation in both way.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Now JNRPE plugins can easily support both the 'legacy' and the new specification format (even together).</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Since the new threshold format is very descriptive, the plugin developer do not need to write any code to support it; gathering the metric is enough: </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">the evaluation is done by the JNRPE library.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div>Thank you again,</div>
<div>Massimiliano</div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Tue, May 28, 2013 at 1:19 PM, Páll Guđjón Sigurđsson <span dir="ltr"><<a href="mailto:palli@ok.is" target="_blank">palli@ok.is</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My two cents,<br>
<br>
The new_threshold_syntax is just a proposal. And to my knowledge no one is working on making it 'official'. We support the new syntax for the new syntax, but the legacy (and inferior) syntax is currently our main one.<br>
<br>
Note, however that they are not mutually exclusive. You can have your plugins understand both :)<br>
<br>
Cheers,<br>
Palli<br>
<div class="im"><br>
<br>
----- Original Message -----<br>
From: "Massimiliano Ziccardi" <<a href="mailto:massimiliano.ziccardi@gmail.com">massimiliano.ziccardi@gmail.com</a>><br>
To: <a href="mailto:nagiosplug-devel@lists.sourceforge.net">nagiosplug-devel@lists.sourceforge.net</a><br>
Sent: Tuesday, May 28, 2013 9:53:57 AM<br>
Subject: [Nagiosplug-devel] Nagios and JAVA plugins<br>
<br>
<br>
<br>
Hi all.<br>
<br>
<br>
</div>I write here to ask you all for a suggestion. Some year ago I started an open source project called JNRPE ( <a href="http://jnrpe.sourceforge.net" target="_blank">http://jnrpe.sourceforge.net</a> ) that allows to easily write Nagios plugins using JAVA and is fully compatible with check_nrpe.<br>
<div class="im"><br>
<br>
JNRPE is bundled with some plugin : at the moment all the plugins use the old range format ([@]start:end).<br>
<br>
<br>
Since I'm in the process of releasing version 2.x, my question is: do you think it would be better to keep using the old range format or would be better to use the new threshold specification ( <a href="http://nagiosplugins.org/rfc/new_threshold_syntax" target="_blank">http://nagiosplugins.org/rfc/new_threshold_syntax</a> )?<br>
<br>
<br>
I've already implemented all the classes needed to parse the new syntax, but I'm not sure that it would be a good idea (most Nagios plugin uses the old format and I didn't want to diverge too much!).<br>
<br>
<br>
Thank you,<br>
Massimiliano<br>
</div>------------------------------------------------------------------------------<br>
Try New Relic Now & We'll Send You this Cool Shirt<br>
New Relic is the only SaaS-based application performance monitoring service<br>
that delivers powerful full stack analytics. Optimize and monitor your<br>
browser, app, & servers with just a few lines of code. Try New Relic<br>
and get this awesome Nerd Life shirt! <a href="http://p.sf.net/sfu/newrelic_d2d_may" target="_blank">http://p.sf.net/sfu/newrelic_d2d_may</a><br>
_______________________________________________________<br>
Nagios Plugin Development Mailing List <a href="mailto:Nagiosplug-devel@lists.sourceforge.net">Nagiosplug-devel@lists.sourceforge.net</a><br>
Unsubscribe at <a href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel</a><br>
::: Please include plugins version (-v) and OS when reporting any issue.<br>
::: Messages without supporting info will risk being sent to /dev/null<br>
<br>
------------------------------------------------------------------------------<br>
Try New Relic Now & We'll Send You this Cool Shirt<br>
New Relic is the only SaaS-based application performance monitoring service<br>
that delivers powerful full stack analytics. Optimize and monitor your<br>
browser, app, & servers with just a few lines of code. Try New Relic<br>
and get this awesome Nerd Life shirt! <a href="http://p.sf.net/sfu/newrelic_d2d_may" target="_blank">http://p.sf.net/sfu/newrelic_d2d_may</a><br>
_______________________________________________________<br>
Nagios Plugin Development Mailing List <a href="mailto:Nagiosplug-devel@lists.sourceforge.net">Nagiosplug-devel@lists.sourceforge.net</a><br>
Unsubscribe at <a href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel</a><br>
::: Please include plugins version (-v) and OS when reporting any issue.<br>
::: Messages without supporting info will risk being sent to /dev/null<br>
</blockquote></div><br></div>