[icinga-users] Migration check_nrpe to icinga2

Andreas Maus bdbd2b902c426129150f02213182ef9bba09ee50 at ypbind.de
Tue Aug 2 08:30:50 CEST 2016


Good morning.

On Tue Aug 02, 2016 at 08:00:10AM +0200, Klaus Muth wrote:
> Hi!
> 
[...]
> Does anybody know a good documentation how to do that?
We replaced NRPE with Icinga2 clients configured as command execution
hosts as described in:

http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/icinga2-client#icinga2-client-configuration-command-bridge

All you need are the client certificates (either by using icinga2 node wizard or provided
by your own internal PKI) and the appropriate zone/endpoint definitions
on the master and the client. You only have to deploy your own CheckCommand definitions
to the clients.

As a bonus, the persistent network connect tremendously reduced the
load on the master as every NRPE check needed the complete TCP/IP and
SSL handshake for every single check. But depending on the size of your
setup YMMV ;)

So long,

Andreas.

-- 
"Things that try to look like things often do
 look more like things than things. Well-known fact."
Granny Weatherwax - "Wyrd sisters"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.icinga.org/pipermail/icinga-users/attachments/20160802/91a15ce8/attachment.sig>


More information about the icinga-users mailing list