Add Site and Customer to the Rule Conditions

65 votes

There are cases where a rule should only apply to hosts/services of specific sites or/and specific customers.

Would be nice the have the Site / Customer as a additional Conditions in the Rules.

Another solution would be that each host gets automatically labeled or tagged accordingly so we can use them instead as a condition in the Rules.

In progress Setup Suggested by: Lars Sörensen (06 May, '22) • Upvoted: 19 Sep, '23 • Comments: 11

Comments: 11

05 May, '22
Lars Michelsen Merged
Rulesets can not be used for setting the host or folder attributes. This is not done for any attribute so far and it looks like trying to build this would result in a strange mix of independent concepts (host attributes + inheritance of attribute) and the ruleset process.

However, we could interpret the request differently: The user does not want to set the site attribute. Instead the user want's to have a different way for specifying the site of a host. Just like it's done for SNMP credentials. There you have the option to specify the SNMP credentials either via a ruleset or via inherited or explicitly set host attribute.
05 May, '22
Lars Michelsen Merged
Even if we would interpret it like described in the comment before and define a clear logic for the mechanisms overriding each other, then we would face the next technical problem: The UI currently assumes in various places that it can compute the effective site of a host or folder easily. If we would now add the rulesets to this logic, this is not easily possible anymore with the current program structure since the ruleset computation can not be done in this part of the software.
13 May, '22
Fabian
...or if the already available host attribute "monitored on site" would be useable in rules.
16 May, '22
Ralf Schwarzmaier Admin
"Set "Monitored on site" tag using rules" (suggested by Thomas Lippert on 2022-04-26), including upvotes (14) and comments (2), was merged into this suggestion.
16 May, '22
Ralf Schwarzmaier Admin
Combined two tickets per Fabian's request
23 Jun, '22
Marsellus Wallace
Since 2.1.0 hosts already get a label discovered: "cmk/site:SITEID".
So only customer condition in CME missing... ;-)
21 Mar, '23
Thomas Lippert Admin
If we provide a label with the customer like cmk/customer:<customerID>, will this be sufficient.
It would be consistent with the site label and can be leveraged with the AND/OR/NOT filtering in views
09 May, '23
Lars Sörensen
@Thomas
A label "cmk/customer:<customerID>" would be suffucient.
Of course, the "AND/OR/NOT/REGEXP" functionality for labels would also have to be present in the rule condition to really be able to use it.
09 May, '23
Thomas Lippert Admin
Hi Lars,
We are currently finalizing our list for 2.3 and both topics are on it. Stay tuned, I will update the feature portal asap
Thomas
22 May, '23
Thomas Lippert Admin
Planned for Checkmk 2.3 - We will implement the customer as label
30 Nov, '23
Niklas Pulina Admin
Hello,

Good news: We have started the development process.

So what’s next? Depending on the scope of your idea, this process may include various steps such as detailed requirements research or a specification phase before it is passed on to development. During this process we may contact you for further information.

Warm regards,
Your Checkmk team