http://retinal.dehy.de/docs/ 2026-05-09T23:19:14+02:00 http://retinal.dehy.de/docs/ http://retinal.dehy.de/docs/lib/tpl/minimal/images/favicon.ico text/html 2018-10-19T22:12:49+02:00 http://retinal.dehy.de/docs/doku.php?id=technotes:icinga:certs&rev=1539979969&do=diff The Icinga2 distributed monitoring documentation explains how to set up PKI certificates between different nodes, but assumes that the Slave / Satellite nodes can connect to the Master node and request their certificates. There are clues in section 6.12.5 which indicate how to create certificates manually, but the documentation does not explain how to create and distribute certificates when the Master node is not contactable by the Satellites / Slaves (for example, you want to have your Master … text/html 2022-01-31T01:00:08+02:00 http://retinal.dehy.de/docs/doku.php?id=technotes:icinga:installation&rev=1643587208&do=diff This installation follows generally the same steps as shown in the official documents, however I think the steps here are laid out a bit more clearly. Installing Icinga2 * Set up the icinga repository in /etc/apt/sources.list.d/icinga.list: deb http://packages.icinga.com/debian icinga-XXXX main text/html 2018-10-03T18:07:13+02:00 http://retinal.dehy.de/docs/doku.php?id=technotes:icinga:moving&rev=1538582833&do=diff I recently set up an Icinga satellite server for a customer project, but it turned out that the virtual machine I tried to do this on wasn't up to the job (don't misinterpret that as meaning Icinga can't run on a VM, or even that it has particularly heavy requirements - the actual problem was that the hosting provider was crap. I moved from a 4Gb RAM 2 CPU core machine to a 1 Gb RAM 1 CPU core (and still a virtual) machine at another provider, and the problems went away). text/html 2022-01-31T00:52:59+02:00 http://retinal.dehy.de/docs/doku.php?id=technotes:icinga:node&rev=1643586779&do=diff The documentation for setting up a distributed monitoring setup using Icinga2 is all very well, but it's not as clear as I would like, so here's a simple step-by-step guide to adding a new node to your existing distributed Icinga2 setup. It's assumed that: text/html 2017-06-25T17:56:15+02:00 http://retinal.dehy.de/docs/doku.php?id=technotes:icinga:overview&rev=1498406175&do=diff Icingaweb2 has a nice overview of all services being checked on all machines, which you can get at by selecting Problems - Service Grid in the main left-hand menu, and then deleting the ?problems from the resulting URL. This then gives you an overall view of all services across all machines, for all service states. text/html 2018-10-23T00:03:56+02:00 http://retinal.dehy.de/docs/doku.php?id=technotes:icinga:pnp4nagios&rev=1540245836&do=diff Once you've installed Icinga2 and got it performing some checks, you should install PNP4Nagios. Without that, you have no check history, no trends, no way of seeing "what's normal for this check at this time of day / week / whatever?". In my opinion PNP4Nagios should be a standard feature which can be installed alongside Icinga2. text/html 2017-06-26T23:35:07+02:00 http://retinal.dehy.de/docs/doku.php?id=technotes:icinga:ssh&rev=1498512907&do=diff Normally, Icinga2 runs on every machine in the system - Master and Satellite nodes where the configurations are managed, and you probably have Icingaweb2 running as well, but also on the Endpoint nodes (the machines being monitored). Sometimes, however, you can't, or don't want to, run Icinga2 on the monitored nodes, even though they can perfectly well run Icinga(Nagios) plugins (ie: they can perform the checks, if only there's some way of telling them to, and getting the results back to Icinga… text/html 2018-10-03T18:05:35+02:00 http://retinal.dehy.de/docs/doku.php?id=technotes:icinga:zones&rev=1538582735&do=diff Icinga2 introduces the concept of Zones, which you may be tempted to think of as "parts of your network" or "regions of your business". Don't. Even the documentation for Icinga2's hierarchical monitoring setup gives the misleading example of Zones named Europe, USA and Asia (section 6.9.3).