Nagios Support Forum

Here is the answer I was looking for.

curl -XPUT "http://(ip)/nagiosxi/api/v1/config/contactgroup/(contactgroupname)?apikey=(apikey)&pretty=1&members=(membername)&applyconfig=1"

All, We want to create a contact group through the Nagios REST API but I've been struggling to find a doc about this task online. I need your help here. The below text is what I have so far (not working). curl -XGET "http:// (IP) /nagiosxi/api/v1/system/status?apikey= (API KEY) &pretty=1&qu...

Alright.

The ticket has been made

VMWare said that it is an issue with the CHECK_VMWARE_API code, which is not theirs and they do not support. They verified that the sizes are correct from the VMWare side and told me that you should support me to a resolution. I reran the command again.. /usr/local/nagios/libexec/check_vmware_api.pl...

It may but not reliably, also we have multiple checks that we would like to run so it may be incredibly hard to run all these checks reliably with the space gaps.

Alrighty.

Here is the output. $ cpan -l | grep -i ssleay Net::SSLeay 1.55 Net::SSLeay::Handle 0.61 Crypt::SSLeay 0.64 Crypt::SSLeay::CTX undef Crypt::SSLeay::Conn undef Crypt::SSLeay::Err undef Crypt::SSLeay::MainContext undef Crypt::SSLeay::X509 undef vendor_perl::Net::SSLeay 1.55 vendor_perl::Net::SSLeay::H...

When I ran this check we still got "CRITICAL" though the device in question is no longer at critical levels. This is occurring almost a week after the size was reclaimed.

Ah............ So that's not good. I ran it with trace and it worked once and then segmentation faulted the next time... Here is the seg fault /usr/local/nagios/libexec/check_vmware_api.pl -f /file/path -l cpu -w 80 -c 90 -H hostnameomitted -vvv --trace=4 [extra-opts] check_vmware_api.pl -f /file/pa...