Nagios Support Forum

Nagios 5.6.2 on CentOS 7 using RPM install.

This command seems to work fine and adds the user with all settings:
"http://<REDACTED>/nagiosxi/api/v1/config/contact?apikey=<REDACTED>&pretty=1" -d "contact_name=pagerduty&host_notifications_enabled=1&service_notifications_enabled=1&host_notification_period=24x7&service_notification_period=24x7&host_notification_options=d,r&service_notification_options=w,u,c,f,r&host_notification_commands=notify-host-by-pagerduty&service_notification_commands=notify-service-by-pagerduty&applyconfig=1"

I tried to send this from Ansible and the contact is created but set to disabled so the rest of the configuration is not applied. I tried splitting the command into 2 parts to create the user first then configure but the user is still not enabled so the settings task does not work.

- name: Create pagerduty contact in Nagios XI
uri:
url: http://{{ ansible_host }}/nagiosxi/api/v1/config/command?apikey={{ API_Key }}&pretty=1
body: 'contact_name=pagerduty&applyconfig=1'
method: POST
validate_certs: no
timeout: 30

- name: Assign configurations to pagerduty contact in Nagios XI
uri:
url: http://{{ ansible_host }}/nagiosxi/api/v1/config/command?apikey={{ API_Key }}&pretty=1
body: 'contact_name=pagerduty&host_notifications_enabled=1&service_notifications_enabled=1&host_notification_period=24x7&service_notification_period=24x7&host_notification_options=d,r&service_notification_options=w,u,c,f,r&host_notification_commands=notify-host-by-pagerduty&service_notification_commands=notify-service-by-pagerduty&applyconfig=1'
method: POST
validate_certs: no
timeout: 30

How can I create and ENABLE a user from Ansible using the API?

I tried adding a contact in Nagios XI 5.6.4 (CentOS 7) via Ansible, and didn't have any issues. My contact is enabled, and configuration applied. I didn't use variables for the IP and the API key in my playbook, and used otify-host-by-email and notify-service-by-email commands as I don't have pagerduty commands defined. Anyway, here is my playbook:
More info:
You may want to upgrade your Nagios XI to 5.6.4 and give it a try. You are entitled to a test server, so try it first in a test environment before applying it to production.

https://support.nagios.com/kb/article/n ... s-145.html

I will push out a test instance and see where it goes from there.

Sure. You can also try "hard-coding" the IP and the API key, just to rule out an issue with the way variables are used in the playbook. Let us know how it goes.

A fresh RPM build on 5.6.3 is failing to update to 5.6.5 so I have an open ticket for that.

Noted. Do you have any further questions on the original (API) issue or it's ok to close this topic?

I want to revisit this as soon as we get updated to the version you say is working. Please hold this open.

Thanks!

Sounds good. We will keep the topic open for the time being.

Version update is working so I ran the play again and the contact is still showing up as inactive. Here is the play:
- name: Create pagerduty contact in Nagios XI
uri:
url: http://{{ ansible_host }}/nagiosxi/api/v1/config/command?apikey={{ NagiosAPIKey }}&pretty=1
body: 'contact_name=pagerduty&applyconfig=1'
method: POST
validate_certs: no
timeout: 30

The user is created but left inactive.

First off, I am not sure if this is a typo, but you have this:

url: http://{{ ansible_host }}/nagiosxi/api/v1/config/command?apikey={{ NagiosAPIKey }}&pretty=1

but you should have this:

url: http://{{ ansible_host }}/nagiosxi/api/v1/config/contact?apikey={{ NagiosAPIKey }}&pretty=1

Second, you cannot add a contact successfully, when you are NOT passing ALL of the required options...
In the "body", you have:

body: 'contact_name=pagerduty&applyconfig=1'

but you should have a lot more than that...
I showed you my playbook, which is working. Can you try using it as I showed you?