CheckMK Rule Condition

[dtuecks]

Hello,

In CheckMK we sometimes need rules that are not based solely on label conditions. For example, I have the following rule definition:

{
  "extensions": {
    "ruleset": "checkgroup_parameters:f5_bigip_vserver",
    "folder": "/",
    "folder_index": 0,
    "properties": {},
    "value_raw": "{'state': {'is_disabled': 0, 'is_up_and_available': 0, 'is_currently_not_available': 0, 'is_not_available': 0, 'availability_is_unknown': 0, 'is_unlicensed': 0, 'children_pool_members_down_if_not_available': 0}}",
    "conditions": {
      "host_tags": [],
      "host_label_groups": [],
      "service_label_groups": [],
      "service_description": {
        "match_on": [
          "/Common/vs_default"
        ],
        "operator": "one_of"
      }
    }
  }
}

I can create a rule with the given value_raw template

"{'state': {'is_disabled': 0, 'is_up_and_available': 0, 'is_currently_not_available': 0, 'is_not_available': 0, 'availability_is_unknown': 0, 'is_unlicensed': 0, 'children_pool_members_down_if_not_available': 0}}"

but now I would like to add the above conditions (e.g. service description match) to such a rule.

Is this possible?

[Bastian-Kuhn]

Hi,

Normally we finance the Syncer with consumer projects where we develop new features for these consumers.
But I guess this change would be, if you take over the testing, so small that I could just build it in later.

Fine with that?

[dtuecks]

What a question :) Of course I’d be fine with that - thank you very much :)

[Bastian-Kuhn]

The feature is now in the main branch :)