README.md

ansible-collection-icinga

Collection to setup and manage components of the Icinga software stack.

Documentation and Roles

• Getting Started
• Role: netways.icinga.repos
• Role: netways.icinga.icinga2
  • Parser and Monitoring Objects
  • Features
• Role: netways.icinga.ifw
• Role: netways.icinga.icingadb
• Role: netways.icinga.icingadb_redis
• Role: netways.icinga.icingaweb2
• Role: netways.icinga.monitoring_plugins
  • List of Available Check Commands
• Role: netways.icinga.icinga_kubernetes
• Inventory Plugin: netways.icinga.icinga

Installation

You can easily install the collection with the ansible-galaxy command.

ansible-galaxy collection install netways.icinga

Or if you are using Tower or AWX, add the collection to your requirements file.

collections:
  - name: netways.icinga

Usage

To use the collection in your playbooks, add the collection and then use the roles.

- hosts: icinga-server
  roles:
    - netways.icinga.repos
    - netways.icinga.icinga2
    - netways.icinga.icingadb
    - netways.icinga.icingadb_redis
    - netways.icinga.monitoring_plugins

Dependencies

None of the roles handle creating databases. If you need to create databases using Ansible, the roles geerlingguy.mysql and geerlingguy.postgresql are great choices.

Further, the icingaweb2 role does not handle configuration of web servers. For this you can try using geerlingguy.apache or geerlingguy.nginx.

Secrets and no_log

Some tasks in these roles make use of sensitive information (e.g. passwords). To avoid leaking this information the tasks in question use Ansible's no_log: true option.
This however can make troubleshooting cumbersome. If you need to and you are fine with secrets being present in Ansible's logs, you can turn logging back on. Be sure though to deactivate logging to syslog to avoid leaking secrets on your target hosts.

Example to turn on logging for the icinga2 role while not logging to syslog:

ANSIBLE_NO_TARGET_SYSLOG=True ansible-playbook </path/to/playbook> -e '{ "icinga2_no_log": false }'