Feature #9482

Create a monitoring setup prototype

Added by intrigeri 2015-05-28 14:25:47 . Updated 2016-04-30 06:52:23 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.4
Start date:
2015-01-09
Due date:
2015-11-09
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:
268

Description

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.

Files

icinga2.txt (4985 B) Dr_Whax, 2015-11-06 06:16:26

Subtasks

Feature #8648: Initial set up of the monitoring software Resolved

100
Feature #8650: Configure monitoring for the most critical services Resolved

100
Feature #8653: Configure monitoring for other high-priority services Resolved

100
Feature #11282: Set up personal login for each sysadmin on icingaweb2 Resolved

100
Feature #11358: Set relevant check_interval and retry_interval for hosts and services Resolved

100
Bug #11368: Check if Icinga2 perfdata are garbage collected Resolved

100

Related issues

Blocked by Tails - Feature #9481: Reset the VM used for monitoring tools experiments to a clean state Resolved 2015-05-28

History

#1 Updated by intrigeri 2015-05-28 14:25:59

  • blocks #8668 added

#2 Updated by intrigeri 2015-05-28 14:26:15

  • blocked by Feature #9481: Reset the VM used for monitoring tools experiments to a clean state added

#3 Updated by intrigeri 2015-05-28 14:34:13

  • blocks Feature #9483: Puppetize the monitoring setup prototype added

#4 Updated by Dr_Whax 2015-07-07 12:27:28

  • Target version changed from Tails_1.6 to Tails_1.5

#5 Updated by intrigeri 2015-08-02 10:03:23

  • Target version changed from Tails_1.5 to Tails_1.6

At least one subtask (Feature #8653) is for 1.6, so this can’t be for 1.5.

#6 Updated by bertagaz 2015-09-23 01:25:17

  • Target version changed from Tails_1.6 to Tails_1.7

#7 Updated by Dr_Whax 2015-09-26 07:25:08

  • Target version changed from Tails_1.7 to Tails_1.8

#8 Updated by Dr_Whax 2015-11-06 06:16:54

I have attached which packages has to be installed and from which repo, configuring some steps is next.

#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

Dr_Whax wrote:
> I have attached which packages has to be installed and from which repo,

Thanks!

> 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.

#10 Updated by intrigeri 2015-12-14 03:41:35

I had to turn off the VM because /var/spool/icinga2 ate all available inodes.

#11 Updated by bertagaz 2016-01-06 15:03:35

  • blocked by deleted (Feature #9483: Puppetize the monitoring setup prototype)

#12 Updated by intrigeri 2016-01-06 15:41:48

  • Description updated

#13 Updated by bertagaz 2016-01-27 10:49:44

  • Target version changed from Tails_2.0 to Tails_2.2

#14 Updated by bertagaz 2016-03-10 18:51:02

  • Target version changed from Tails_2.2 to Tails_2.3

#15 Updated by intrigeri 2016-04-12 07:16:23

  • Status changed from Confirmed to In Progress

#16 Updated by bertagaz 2016-04-26 04:59:32

  • Target version changed from Tails_2.3 to Tails_2.4

#17 Updated by intrigeri 2016-04-30 06:52:23

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • QA Check set to Pass

I think we’re done here :)