fsfe-system-hackers
/
monitoring
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
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.
151 Commits
1 Branch
0 Tags
303 KiB
 
 
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Max Mehl 80d24d8cf1
continuous-integration/drone/push Build is passing
Details
prolong warning threshold to not warn when backup takes longer than 1 hour 		4 weeks ago
.reuse Initial commit 2 years ago
LICENSES REUSE compliance 2 years ago
conf.d prolong warning threshold to not warn when backup takes longer than 1 hour 4 weeks ago
inventory@6bfc25cbdf bump inventory 3 months ago
roles Initial commit 2 years ago
scripts enable reply-to, and make hosts topics for mailing lists 1 year ago
templates Initial commit 2 years ago
user_plugins_server allow to specify host to inquire 3 months ago
.ansible-lint make reuse compliant 1 year ago
.drone.yml remove ansible syntax check 9 months ago
.gitignore ignore hosts.conf if present 6 months ago
.gitmodules Unify Ansible inventory (#1) 1 year ago
README.md delete client part which is now in baseline, and some minor improvements 6 months ago
ansible.cfg make REUSE compliant 9 months ago
id_rsa.pub Initial commit 2 years ago
id_rsa.pub.license Initial commit 2 years ago
playbook.yml delete client part which is now in baseline, and some minor improvements 6 months ago

README.md

FSFE monitoring

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.