I could get it works as an event broker, but where to send data?=20
I thought about two things :=20
_ A cgi file to export data in JSON format, for all data which don't =
need realtime (such as hosts list ...).
_ A event broker to send data to another server (the frontend) on event =
by using for example JSON-RPC (www.json-rpc.org).
This will permit realtime update for alarms etc, and to send data every =
N minutes to frontend server.
I am using several Nagios servers and I generate JSON data every 5 mins =
in local and push them through ssh to the frontend server where I =
aggregate data.=20
Yann Jouanin
http://www.yannj.fr
-----Message d'origine-----
De : [email protected] =
[mailto:[email protected]] De la part de =
Olivier JAN
Envoy=C3=A9 : vendredi 13 juin 2008 17:35
=C3=80 : [email protected]
Objet : Re: [Nagios-devel] Nagios2JSON
Hi list,
I agree with Thomas. Would be nice to have this as an event broker. =20
And maybe it could be a good start to discuss what could be the next =20
"official" interface to Nagios... What way to implement it ?
Olivier Jan
http://nagios-fr.org
Thomas Guyot-Sionnest a =C3=A9crit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Yann JOUANIN wrote:
> | Hello Everyone,
> |
> |
> |
> | I started a week ago to dev a CGI which permit to export Nagios =
Status
> | in JSON format, it helps to create graphic interface (web or not).
> |
> |
> |
> | You can find this CGI on http://www.yannj.fr
> |
> |
> |
> | I am looking for people to test it. This is a alpha development at =
this
> | time and all info are sent for the moment without filter, but it =
runs!
> |
> | I also coded a php class to help in using the format on the client =
side,
> | and I also coded a NagVis backend, with this CGI, this is not =
compulsory
> | to use NDO2DB to get status etc from Nagios.
> |
> |
> |
> | Don=E2=80=99t hesitate to contact me for any question, suggestion or =
other!
>
> That seems like good stuff, and a promising way to quickly set-up a =
PHP
> web interface without the burden of NDODB (BTW I'm not saying NDODB
> should be dropped; any web interface could have different backends but
> not every installation require NDODB).
>
> I'm wondering how hard it would be to make this an event broker =
instead
> (you can fetch the file for remote frontends), or even better a
> configure option replacing USE_XSDDEFAULT (would allow changing the
> format of the status file without breaking the CGI, making place for
> concurrent JSON-based interfaces).
>
> I'd be glad to know what others think about this... Would it make =
sense
> to include this in a future release?
>
> - --
> Thomas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFIUpDH6dZ+Kt5BchYRAu3tAKCzmET3iQb1kcqLsQg9dzZYRYiHsQCdGM9g
> Hn5NHt4AR2KtPsPpsXlOBzo=3D
> =3DFDOL
> -----END PGP SIGNATURE-----
>
> =
-------------------------------------------------------------------------=
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
-------------------------------------------------------------------------=
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nagios-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/lis ... gios-devel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]