Allow variables or macros in ruleset options
Users in Checkmk like to have a slim configuration, as this keeps the maintenance effort low.
One way to achieve is to use the conditions effectively. But often it is not sufficient to be able to reduce the amount of needed rules. Example:
A user wants to monitor several web servers (maybe hundreds of them). All are provided by a load balancer cluster. As these load balancers are located as hosts in Checkmk, the services to monitor the validity of the used certificates or the availability of the websites should be attached to these hosts (or the cluster).
Currently, it is needed to add a single rule for each virtual server, as the condition and even most options might be the same, but not the option for the "Virtual host". If a user were able to use a variable and connect this variable to a list of these virtual hosts, a single rule per Checkmk host would be sufficient.
Comments: 3
-
12 Jul, '22
Marcel Arentz AdminAnother example:
The rule set "Clustered services for overlapping clusters" allows connecting a host in Checkmk with several cluster hosts. Currently, each assignment to a cluster needs an individual rule. By having two Hosts belonging to three different cluster hosts, a user needs three rules.
With availability of variables, providing a list of cluster hosts would be possible. This reduces the amount of rules needed by 66%. -
13 Jul, '22
TimOne more example:
If you monitor multiple SQL statements (Ruleset Check SQL Database) on a database you have to add the database connection in every rule.
This results in a lot of work, if e.g. the port of a database changes.
Would be nice to add a rule just for the connection parameters and reuse them in the queries. -
13 Jul, '22
Daniel RoettgermannGood Idea Tim