Mathieu thank you for the reply but i still have some doubts.
You say that you use local checks for simpler things and MRPE for Nagios plugins and big/complex checks taken on Nagios Exchange. Ok but now questions are: 1)Reading the documentation, I understand that you can use any kind of Nagios plugins (simple or complex) even using local checks. Reading your reply instead it seems that some checks cannot be executed using local checks. Is it just a choise or you were forced to use MRPE? Could you please clarify? 2) You say that another advantage of the MRPE system is that it uses a centralized config but again, the documentation doesn't say that you can use a centralized configuration but speak about /etc/check_mk/mrpe.cfg on every single node. The doc even provides an example: /etc/check_mk/mrpe.cfg LOAD /usr/lib/nagios/plugins/check_load -w 2 -c 5 FS_var /usr/lib/nagios/plugins/check_disk /var FS_hirn /usr/lib/nagios/plugins/check_disk /hirn Aptitude /usr/lib/nagios/plugins/check_apt Smart_sda /usr/lib/nagios/plugins/check_ide_smart -d /dev/sda -n in which the parameters are local and not "central". Could you please give me some more informations and, if possible, an example or screenshot? Best Marco ----Messaggio originale---- Da: "Mathieu Levi" <ml...@collective.com> Data: 14/10/2016 17.19 A: <email@example.com> Ogg: Re: [Check_mk (english)] difference between local checks and MRPE Aside from that advantage that Robert mentioned, I think the MRPE's intention isn't to compete with the local checks but instead to make the Nagios plugins (NRPE) easier to integrate into check_mk. That's what I use it for. I have local checks for things I wrote (mostly simpler things), I use MRPE for the Nagios plugins brought over from when we were using Icinga, and big/complex checks that I look for on the Nagios Exchange and places like that. I suppose another advantage of the MRPE system is that it uses a centralized config for the host being monitored (/etc/check_mk/mrpe.cfg) where one configures the plugins along with the parameters for those plugins. As an aside, I modified the check_mk_agent script slightly so that it also looks at config files within /etc/check_mk/mrpe.d (similar to how the sudoers.d works); this made it a little bit cleaner and easier to integrate with configuration management automation (eg. /etc/check_mk/mrpe.d/check_postgres.cfg for only some hosts that have Postgres, a general /etc/check_mk/mrpe.cfg for every host for general checks). Message: 2Date: Fri, 14 Oct 2016 16:40:18 +0200 (CEST)From: "mlist"To: Robert Sander , <firstname.lastname@example.org>Subject: [Check_mk (english)] R: Re: difference between local checks and MRPEMessage-ID: <811694031.2365191476456018091.javamail.ht...@webmail-35.iol.local>Content-Type: text/plain;charset="UTF-8"Thanks Robert I didn't know that. So...is correct to say that "local checks" isthe preferred method over MRPE? Or are there special case in which MRPE isstill better?>----Messaggio originale---->Da: "Robert Sander" >Data: 14/10/2016 16.13>A: <email@example.com>>Ogg: Re: [Check_mk (english)] difference between local checks and MRPE>>On 14.10.2016 14:00, >>> apart the fact that they use a different mechanism, is there any good>> reason or case for which I should use one of them?>>Local checks can be placed in numeric subdirectories. This way they are>run asynchronously which is not possible with MRPE.>>Regards>-->Robert Sander>Heinlein Support GmbH>Schwedter Str. 8/9b, 10119 Berlin>>http://www.heinlein-support.de>>Tel: 030 / 405051-43>Fax: 030 / 405051-19>>Zwangsangaben lt. ?35a GmbHG:>HRB 93818 B / Amtsgericht Berlin-Charlottenburg,>Gesch?ftsf?hrer: Peer Heinlein -- Sitz: Berlin>>
_______________________________________________ checkmk-en mailing list firstname.lastname@example.org http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en