RFC: Nagios + AMQP

[Thomas Guyot-Sionnest]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans Engelen wrote:
>> I would be glad to hear what others think of this idea.
> 
> I already have part of this running with success in a Production
> environment. That is to say the submission of passive results to nagios
> using (in my case) IBM MQ Series. My choice for MQ Series is simple, it
> is our Messaging Platform of choice where I work and as such it made
> sense to use it for me.
> 
> About 2 months ago I posted a similar idea which was met with ...
> lukewarm replies. Your wiki page however put's into words much the same
> (in fact exactly the same) ideas I had and in a far more structured way.
> 
> My only real concern is AMQP. Linking it to a specific messaging
> platform might cause problems for some people. As I said we already have
> a messaging platform of choice that handles a few million messages per
> day in our organisation (for dozens of different applications). It is
> also linked to other companies using SSL encrypted communication
> channels. In short our organistion would oppose adding a new messaging
> platform when one is already there and the expertise/hardware/licenses
> for it are also readily available.
> 
> Hence my suggestion at the time was to use one of the few standards
> (dare I use that word) in messaging at the moment, JMS. Contrary to what
> the name suggests JMS queues can be used by non-java applications too.
> The key is that many of the message oriented middlewares, even the
> proprietary ones like MQ Series, support it. This would leave the choice
> of MOM open to the user.

Hi, and thanks for your feedback; that's very interesting. I wouldn't
mind considering an abstraction layer, although there some things to
take into considerations:

1. How this will affect speed? One of the biggest advantages if using
messaging would be speeding up the Nagios daemon, so to what extend JMS
would offset these gains? I'm thinking about systems that could possibly
run hundreds (or thousands?) of checks per second, and under the current
architecture Nagios would send check messages serially).

2. Build/setup requirements: adding more dependencies means more work
required to get a MOM-enabled Nagios working.

3. To what extent will this be useful? Would it be possible to implement
some kind of JMS proxy to interact with other messaging platforms
instead? After all JMS would really be useful only to people that
already use a messaging platform, and I doubt there's that many among
Nagios users. Also unlike other messaging platform AMQP is totally free
and open.

Note that I have very little knowledge of AMQP, even less of JMS and
other messaging platform, so if what I'm saying is nonsense don't be
afraid to educate me ;)

- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJPpO46dZ+Kt5BchYRAvhiAJ4iHnp+3FGUjxKqL9bpdSRgowdxGwCg19kQ
KldsWlPWKw6OohSlbxcdejg=
=iqLU
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/