Page 2 of 2
Re: REST API is not having command end point.
Posted: Tue Oct 27, 2015 7:13 am
by pmishra
Any update on patch review ?
Thanks,
Re: REST API is not having command end point.
Posted: Tue Oct 27, 2015 3:30 pm
by tmcdonald
Nothing yet, it has only been a few days (we had a weekend) and our devs have quite a lot on their plates already.
Re: REST API is not having command end point.
Posted: Fri Aug 18, 2017 12:41 pm
by pkizer-utsystem
The last activity on this thread was 2 years ago, but it looks like the alert part of the functions provided (adding a service comment) have not been added to the most recent shipped version? I'm also not seeing anything like it in the v1 API Help docs.
It does look like the "Disable Notifications" could possibly get done merely by by doing a service reconfig setting, but my attempts at doing so are also not producing the results I expect (since I'm using service definitions auto-created via Templates, if I use the same hostname and service name in a $api_url/config/service command to set the notifications_enabled=0, then it's adding a new service item rather than modifying the existing one. [Can provide example.]
Am I just overlooking it or is the only way to get that functionality to manually patch as helpfully provided by pmishra in 2015? [I'm also trying to enable our DBAs to be able to use their apikey to do a scripted equivalent of browsing to a service and clicking "Disable notifications" before they begin automated maintenance.]
Re: REST API is not having command end point.
Posted: Fri Aug 18, 2017 3:52 pm
by dwhitfield
There is currently no way to modify via the API. The roadmap (
https://www.nagios.com/roadmaps/) doesn't really say anything about it, but there is a big API update coming. Unfortunately, I cannot say when XI 5.5 will be released or exactly what will be included. If you don't see XI 5.5 out by 2018, we should have some details of a release date by then.