cacert-sysadm AT lists.cacert.org
Subject: CAcert System Admins discussion list
List archive
- From: Jan Dittberner <jandd AT cacert.org>
- To: cacert-sysadm AT lists.cacert.org
- Subject: State of the infrastructure, Part 4 Monitoring setup
- Date: Fri, 10 Jun 2016 22:44:05 +0200
After giving a basic introduction to our infrastructure in the first post in
this series [1] and discussing our mail systems [2] and IRC infrastructure
[3] in subsequent posts I continue with some information related to our
monitoring infrastructure.
[1] https://lists.cacert.org/wws/arc/cacert-sysadm/2016-06/msg00000.html
[2] https://lists.cacert.org/wws/arc/cacert-sysadm/2016-06/msg00001.html
[3] https://lists.cacert.org/wws/arc/cacert-sysadm/2016-06/msg00002.html
Monitoring
==========
We currently have an Icinga 1.x based monitoring system taking care of a
minimal set of checks for some of the infrastructure systems in the
monitoring container [4]. Some checks are executed on the containers using
NRPE. This system uses the Icinga classic user interface.
[4] https://infradocs.cacert.org/systems/monitor.html
I plan to replace this setup by Icinga2/Icingaweb 2 which provide better
performance some nice new features and a more pleasant user interface.
Icinga2 allows to define so called apply rules that create service checks
based on variables of host definitions which will reduce the set of hand
written rules that has to be maintained.
The current service checks do not cover all our system and do only check
whether the systems are pingable and have all necessary system updates
installed. I would like to have a more complete set of checks and would like
to setup notifications that are sent to the mail alias
{systemname}-admin AT cacert.org
that is usually setup for each container.
That's it for the monitoring setup. Feel free to give feedback and share
your ideas and opinions.
The last two mails will discuss:
- other systems (besides mail, IRC and monitoring)
- my idea for the future of our infrastructure administration
Best regards
Jan
--
Jan Dittberner - CAcert Infrastructure Team Lead
Software Architect, Debian Developer
GPG-key: 4096R/0xA73E0055558FB8DD 2009-05-10
B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD
https://jan.dittberner.info/
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- State of the infrastructure, Part 4 Monitoring setup, Jan Dittberner, 06/10/2016
Archive powered by MHonArc 2.6.18.