Configure the icinga 2 server https://monitoring.fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
tobiasd 287e679a5a
continuous-integration/drone/push Build is passing Details
Merge pull request 'add docs-centralizer CI job' (#3) from tobiasd/docscentralization into master
4 weeks ago
.reuse Initial commit 3 years ago
LICENSES REUSE compliance 3 years ago
conf.d remove me as mailproblem user 1 month ago
inventory@6bfc25cbdf bump inventory 1 year ago
roles Initial commit 3 years ago
scripts enable reply-to, and make hosts topics for mailing lists 2 years ago
templates Initial commit 3 years ago
user_plugins_server allow to specify host to inquire 1 year ago
.ansible-lint make reuse compliant 2 years ago
.drone.yml add docs-centralizer CI job 4 weeks ago
.gitignore ignore hosts.conf if present 2 years ago
.gitmodules Unify Ansible inventory (#1) 2 years ago
README.md add docs-centralizer CI job 4 weeks ago
ansible.cfg make REUSE compliant 2 years ago
id_rsa.pub Initial commit 3 years ago
id_rsa.pub.license Initial commit 3 years ago
playbook.yml delete client part which is now in baseline, and some minor improvements 2 years ago

README.md

FSFE monitoring

in docs.fsfe.org REUSE status Build Status

The goal is to deploy incinga 2 and the large part of its server configuration.

What it does?

On the sever

  1. Install icinga. Use the official ansible playbook role
  2. Deploy the configuration
  3. Deploy the web interface and the apache configuration

Note: As of now the ansible playbook does not handle the configuration of the web interface itself, it's not currently supported by the official ansible role.

On the clients

Note: This playbook does not store the hosts configuration, and does not set up the monitored clients. For workflow reasons this happens via the baseline playbook.

  1. Deploy the SSH public key
  2. Create the icinga user

How to use it?

Note: Please make sure you have ssh access to the servers listed in the icinga2_clients section of the inventory.

Clone this repo:

git clone --recurse-submodules git@git.fsfe.org:fsfe-system-hackers/monitoring.git

Update the inventory submodule to reflect the newest changes to the list of our hosts and the groups that they are in:

git submodule update --remote inventory

The following commands are most used:

Configure only the server:

ansible-playbook playbook.yml -l "icinga2_server"

Only deploy a changed config to the server:

ansible-playbook playbook.yml -l "icinga2_server" -t conf

To update clients and the hosts.conf file, have a look at the baseline repository.

Note: You have to manually add sensitive files which are not in this repo but only on the host: /etc/icinga2/id_rsa and /etc/msmtprc!

The user facing doc is here. The official documentation is here.

How does it work?

The templates/ directory contains the apache virtual hosts configuration. The roles/ folder contains the upstream code for icinga2 installation. The conf.d/ folder contains the icinga2 configuration itself.

The address of the icinga2 server and the clients are configured in the inventory/inventory.txt file.