Project

General

Profile

Feature #5734

Monitor servers

Added by Tails about 5 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Elevated
Assignee:
-
Category:
Infrastructure
Target version:
Start date:
01/09/2015
Due date:
11/09/2015
% Done:

100%

QA Check:
Pass
Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
No
Affected tool:

Description

As our infrastructure grows and more users and contributors rely on it, we need to monitor it, in order to guarantee more availability, reliability, and integrity of our services.


Subtasks

Feature #8645: Research and decide what monitoring solution to useResolved

Feature #8646: Research and decide where to host the monitoring softwareResolved

Feature #8647: Install an OS on the machine that will host the production monitoring setupResolved

Bug #10761: Add missing ecours connection info to sysadmins Git repoResolved

Bug #11342: Stop daily spam from ecours to sysadmins due to disabled IPv6Resolved

Feature #8649: Specify our monitoring needs and build an inventory of the services that need monitoringResolved

Feature #8651: Configure the receiving side of the monitoring notificationsResolved

Feature #9480: Set up a VM for monitoring tools experimentsResolved

Feature #9481: Reset the VM used for monitoring tools experiments to a clean stateResolved

Feature #9482: Create a monitoring setup prototypeResolved

Feature #8648: Initial set up of the monitoring softwareResolved

Feature #11194: Install a web interface to our monitoring softwareResolved

Feature #8650: Configure monitoring for the most critical servicesResolved

Feature #8653: Configure monitoring for other high-priority servicesResolved

Feature #11282: Set up personal login for each sysadmin on icingaweb2Resolved

Feature #11358: Set relevant check_interval and retry_interval for hosts and servicesResolved

Bug #11368: Check if Icinga2 perfdata are garbage collectedResolved

Feature #9483: Puppetize the monitoring setup prototypeRejected

Feature #9484: Deploy the monitoring setup to productionResolved

Feature #8652: Evaluate how the initial monitoring setup behaves and adjust things accordinglyResolved

Feature #11277: Group hosts and services in the monitoring setupResolved

Feature #9485: Update the local dev environment to replicate our monitoring setupRejected

Feature #10886: Reset the VM used for monitoring tools experimentsResolved

Feature #11094: Deploy a VPN between the monitoring host and LizardResolved


Related issues

Blocked by Tails - Feature #11366: Document our monitoring setup Resolved 04/25/2016

History

#1 Updated by intrigeri about 5 years ago

  • Subject changed from monitor services to monitor server services
  • Starter set to No

#2 Updated by intrigeri about 5 years ago

  • Subject changed from monitor server services to monitor servers

#3 Updated by intrigeri almost 5 years ago

  • Category set to Infrastructure

#4 Updated by BitingBird about 4 years ago

  • Subject changed from monitor servers to Monitor servers

#5 Updated by intrigeri over 3 years ago

  • Target version changed from Sustainability_M1 to Tails_1.8

#7 Updated by intrigeri over 3 years ago

  • Description updated (diff)

#9 Updated by intrigeri over 3 years ago

  • Assignee set to bertagaz

#11 Updated by bertagaz almost 3 years ago

  • Target version changed from Tails_1.8 to Tails_2.0

Postponing

#13 Updated by bertagaz over 2 years ago

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

Postponing this part of the monitoring setup, as it will be unlikely done for the previously planed deadline given some subtasks are also postponed

#15 Updated by bertagaz over 2 years ago

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

#16 Updated by bertagaz over 2 years ago

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

#18 Updated by intrigeri over 2 years ago

#19 Updated by intrigeri over 2 years ago

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

(Some subtasks are for 2.5 already.)

#20 Updated by BitingBird over 2 years ago

  • Status changed from Confirmed to In Progress

#21 Updated by intrigeri about 2 years ago

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

Last blocker resolved, we're done here. Great job, thank you!

#22 Updated by sajolida about 2 years ago

Congrats!

Also available in: Atom PDF