Create a monitoring setup prototype
Once we’ve decided what tools we want to use (
Feature #8645), and the VM used for experiments has been reset ( Feature #9481), we should start from scratch and create a monitoring setup that satisfies our needs. This ticket includes:
- installing the monitoring software
- configuring the monitoring software
All this shall be done with Puppet.
|Feature #8648: Initial set up of the monitoring software||Resolved||
|Feature #8650: Configure monitoring for the most critical services||Resolved||
|Feature #8653: Configure monitoring for other high-priority services||Resolved||
|Feature #11282: Set up personal login for each sysadmin on icingaweb2||Resolved||
|Feature #11358: Set relevant check_interval and retry_interval for hosts and services||Resolved||
|Bug #11368: Check if Icinga2 perfdata are garbage collected||Resolved||
Blocked by Tails -
#9 Updated by intrigeri 2015-12-05 16:14:07
- Assignee changed from Dr_Whax to bertagaz
- Target version changed from Tails_1.8 to Tails_2.0
> I have attached which packages has to be installed and from which repo,
> configuring some steps is next.
FYI, it can totally be useful if we get it before December 17. If it arrives later, then likely we’ll have re-done this work.