[Nagiosplug-devel] Nagios and JAVA plugins

Massimiliano Ziccardi massimiliano.ziccardi at gmail.com
Fri Jun 28 18:17:07 CEST 2013


Hi Palli.

Thank you for your suggestion.
I followed your suggestion and implemented the threshold evaluation in both
way.
Now JNRPE plugins can easily support both the 'legacy' and the new
specification format (even together).

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:
the evaluation is done by the JNRPE library.

Thank you again,
Massimiliano




On Tue, May 28, 2013 at 1:19 PM, Páll Guðjón Sigurðsson <palli at ok.is> wrote:

> My two cents,
>
> 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.
>
> Note, however that they are not mutually exclusive. You can have your
> plugins understand both :)
>
> Cheers,
> Palli
>
>
> ----- Original Message -----
> From: "Massimiliano Ziccardi" <massimiliano.ziccardi at gmail.com>
> To: nagiosplug-devel at lists.sourceforge.net
> Sent: Tuesday, May 28, 2013 9:53:57 AM
> Subject: [Nagiosplug-devel] Nagios and JAVA plugins
>
>
>
> Hi all.
>
>
> I write here to ask you all for a suggestion. Some year ago I started an
> open source project called JNRPE ( http://jnrpe.sourceforge.net ) that
> allows to easily write Nagios plugins using JAVA and is fully compatible
> with check_nrpe.
>
>
> JNRPE is bundled with some plugin : at the moment all the plugins use the
> old range format ([@]start:end).
>
>
> 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 (
> http://nagiosplugins.org/rfc/new_threshold_syntax )?
>
>
> 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!).
>
>
> Thank you,
> Massimiliano
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________________
> 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
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-plugins.org/archive/devel/attachments/20130628/f0e9d457/attachment.html>


More information about the Devel mailing list