On 17 Aug 2010, at 06:27, Rukshan Kothwala wrote:
Well, I use Opsview Community edition to monitor our server plant.
According to my requirements API is an important part to integrate
with a web site. I noticed a nice API in icinga monitoring tool
which similar to nagios. Since icinga is a fast growing application,
Are they any plans to work with icinga from opsview side? Because
icinga also provide same stuffs in nagios.
Please give me an idea about icinga with Opsview future.
The great thing about Nagios based solutions is that there are a lot
to choose from!
We keep an eye on the Icinga progress as I'm sure they are of Opsview.
Currently we are sticking with Nagios as the basis because it is the
more mature and more widely used software.
As far as their API goes, what do you mean? There are several APIs
from their documentation site: a plugins API and a status API (they
call it Icinga API).
The plugins API is basically the Nagios Plugin API, which is no
different to the Nagios one: http://docs.icinga.org/latest/en/pluginapi.html
The status API is a way of getting host information:
http://docs.icinga.org/latest/en/icinga-api.html
I think the Opsview API (http://docs.opsview.com/doku.php?id=opsview-community:api
) is much superior because:
* It is not available from a webservice call
* There is no authentication with the Icinga API. The Opsview API
requires authentication, so users only see what they are allowed to see
* Our status APIs does aggregation, so you can get information like
in the host group hierarchy pages, whereas theirs will not scale to
thousands of hosts (count each host manually)
* Our API allows you to make changes to configuration
API is a bit of a loose term. Their use of API is "how to write
programs to get status information from Icinga".
We consider "API" to mean "getting status data and making changes to
Opsview via a webservice". On that grounds, I think its a bit unfair
to compare the APIs at the moment because the Opsview API is doing
much more at a much higher level.
To whet the appetite, we've got some changes in store for the API in
the next major release of Opsview. This includes:
* More configuration items exposed via the API (service checks,
host templates, contacts)
* More abilities for items (edit)
* A REST interface
* Flexible inputs/outputs including JSON and perl structures
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
