Am 29.06.2015 um 07:01 schrieb Shay Rojansky: > Just to add my experience, we're using icinga2 in command execution very > successfully. Deployment and configuration is ansible-managed, and apart > the initial setup work (especially around SSL) it's trivial to manage and > install on new machines. (I can share the ansible scripts).
I'm interested in your concept. I have some questions and an example: User A has 3 Hard-Disks: sda, sdb and sdc and want to monitor SMART-values. Do you define for each check an own check_command? Another one: User A wants to monitor a lot of certificates: check_cert_expire_domain1 check_cert_expire_domain2 check_cert_expire_domain3 check_cert_expire_domain4 .... User B wants also the monitoring of certificates: check_cert_expire_domain1 check_cert_expire_domain55 check_cert_expire_domain56 check_cert_expire_domain57 ... In this case its a lot of effort to define all checks in an own check_command (on client the effort is the same but you have that twice because you must define all commands also on the monitoring-server). Another thing is when User A need a notification 14 days bevor check_cert_expire_domain1 expires and User B needs a notification but only 30 days bevor. Is that covered by your concept? nuts
signature.asc
Description: OpenPGP digital signature
_______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
