search

neeladevi / nagioschecker

Automatically exported from code.google.com/p/nagioschecker
0 stars 0 forks source link

Use Livestatus as Backend #152

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Hello Nagioschecker Team,

I don't use Nagioschecker for myself but I know that many users of the
Nagios checker have a performance problem when using the Nagios Checker on
the Nagios sever. These problems are caused by the fact that Nagios Checker
uses the Nagios CGIs for pulling Nagios status data.

This problem grow in companies where several users use the Nagioschecker.
There are allways several CGIs open.

It would be a very big benefit to support a faster way of status data
fetching. And here comes my request:

What do you think about fetching status information from MKLivestatus
(http://mathias-kettner.de/checkmk_livestatus.html)?

Surely MKLivestatus only listens on a local unix socket which can not be
read directly by the Nagioschecker. But there are several ways for
connecting both.

At first there is the xinetd which makes the unix socket available on the
network. This is possible now.

Another idea would be to create a small webservice which serves the
MKLivestatus connection via HTTP.

What do you think about this? Wouldn't that be a big benefit for all
nagioschecker users?

Kind Regards,
Lars Michelsen
NagVis Developer

PS. Was unable to open a "feature request". So I needed to add this as
"user defect report" ...

Original issue reported on code.google.com by i...@larsmichelsen.de on 27 Mar 2010 at 4:35

GoogleCodeExporter commented 8 years ago 
You might use the LivestatusSlave script I just created. It acts as webservice 
to
make the livestatus information available via HTTP.

http://nagios.larsmichelsen.com/livestatusslave/

It should be dead easy to communicate with the LivestatusSlave using javascripts
XMLHTTPRequest and then simply parsing the JSON response.

Original comment by i...@larsmichelsen.de on 27 Mar 2010 at 8:42