Adding additional NagiosXI API Improvements
Posted: Mon Jun 26, 2017 7:49 am
Hi,
We have a large NagiosXI deployment monitoring about 2000 hosts and about 8500 services. The majority of this is fairly static configuration, however we have the need to try to automate as much of the process of creating and removing hosts/services and tweaking settings as we can. The API is well documented but we've found it limited for all the functionality we would usually need. We would like the additional functionality to:
1. Create a new server and link it to an existing host group or service definition upon creation. (we can create a host but we can't then can't apply an existing service definition or host group to it seemingly).
2. Schedule downtime via CLI/API (so we’re not clicking on tens of servers via the GUI, even using the bulk downtime scheduling tool is cumbersome).
3. Acknowledge an alert via CLI/API (so we’re not clicking on tens of servers via the GUI, even using the bulk acknowledgement tool is cumbersome).
4. Adjust the alert thresholds for a host's service via CLI/API, currently it appears you can create a service with a certain set of thresholds, but you can't then alter this via the API.
Are there any plans for implementing more functionality into the API (above) in future releases?
Thanks
Tristan
We have a large NagiosXI deployment monitoring about 2000 hosts and about 8500 services. The majority of this is fairly static configuration, however we have the need to try to automate as much of the process of creating and removing hosts/services and tweaking settings as we can. The API is well documented but we've found it limited for all the functionality we would usually need. We would like the additional functionality to:
1. Create a new server and link it to an existing host group or service definition upon creation. (we can create a host but we can't then can't apply an existing service definition or host group to it seemingly).
2. Schedule downtime via CLI/API (so we’re not clicking on tens of servers via the GUI, even using the bulk downtime scheduling tool is cumbersome).
3. Acknowledge an alert via CLI/API (so we’re not clicking on tens of servers via the GUI, even using the bulk acknowledgement tool is cumbersome).
4. Adjust the alert thresholds for a host's service via CLI/API, currently it appears you can create a service with a certain set of thresholds, but you can't then alter this via the API.
Are there any plans for implementing more functionality into the API (above) in future releases?
Thanks
Tristan