community.general.nrdp callback – Post task results to a Nagios server through nrdp

Note

This callback plugin is part of the community.general collection (version 10.7.3).

You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it, use: ansible-galaxy collection install community.general.

To use it in a playbook, specify: community.general.nrdp.

Callback plugin

This plugin is a notification callback. It sends information for a playbook run to other applications, services, or systems. See Callback plugins for more information on callback plugins.

Synopsis

  • This callback send playbook result to Nagios.

  • Nagios shall use NRDP to receive passive events.

  • The passive check is sent to a dedicated host/service for Ansible.

Parameters

Parameter

Comments

hostname

string / required

Hostname where the passive check is linked to.

Configuration:

  • INI entry:

    [callback_nrdp]
hostname = VALUE

  • Environment variable: NRDP_HOSTNAME

servicename

string / required

Service where the passive check is linked to.

Configuration:

  • INI entry:

    [callback_nrdp]
servicename = VALUE

  • Environment variable: NRDP_SERVICENAME

token

string / required

Token to be allowed to push nrdp events.

Configuration:

  • INI entry:

    [callback_nrdp]
token = VALUE

  • Environment variable: NRDP_TOKEN

url

string / required

URL of the nrdp server.

Configuration:

  • INI entry:

    [callback_nrdp]
url = VALUE

  • Environment variable: NRDP_URL

validate_certs

aliases: validate_nrdp_certs

boolean

Validate the SSL certificate of the nrdp server. (Used for HTTPS URLs).

Choices:

  • false ← (default)

  • true

Configuration:

  • INI entries:

    [callback_nrdp]
validate_nrdp_certs = false

    [callback_nrdp]
validate_certs = false

  • Environment variable: NRDP_VALIDATE_CERTS

Note

Configuration entries listed above for each entry type (Ansible variable, environment variable, and so on) have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up. The entry types are also ordered by precedence from low to high priority order. For example, an ansible.cfg entry (further up in the list) is overwritten by an Ansible variable (further down in the list).

Authors

  • Remi VERCHERE (@rverchere)