On 25/10/2016 19:27, Judit Flo wrote:
Hi,I have an icinga2 (2.5.4) cluster with two masters running fedora 23 in a top-down configuration. One master has zones.d/master and zones.d/global-templates that the info is sent via api to the other master on /var/lib/icinga2/api.... I just started adding services and found issues when dealing with the check_procs file: On the global-templates/services.conf file, my check_procs looks like this: apply Service "procs" { import "generic-service" check_command = "procs" command_endpoint = host.vars.client_endpoint vars.procs_warning = 300 vars.procs_critical = 310 assign where host.vars.client_endpoint }
procs_warning and procs_critial is defined statically for this service. You don't overwrite anything with values from the host object. So obviously it's static for all.
Those limit values are just fine for most of the machines but for some I want to tweak those values by re-defining the limits on the specific hosts defined on : zones/master/hosts.conf
And how? I don't see your host definition here?
The problem is that those values are not being used and I got notifications for problems that really shouldn't.
Without seeing your host definition the above service definition uses fixed values. It doesn't matter what variable you set in the host object, nothing is modified here...
On the web interface next to a big Critical box are the different hostname:procs alerts. If I click on the hostname, the panel on the right shows in the Custom variables area, my values If I click on the procs, then the performance data shows me values defined in the service. Ideally I would expect for the variables to be read so that I can keep all the configuration in the same set of files and push from one server to all the clients. With the disk partitions checks, the variables are honored and I can have the specific partitions in the different machines checked just fine.
So look at the service definition for the disk partition checks. How does that look like?
-Gerald _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
