Werk #16713: Changed format of host tag conditions in global setting 'agent_deployment_host_selection'
| Component | Setup, site management | ||
| Title | Changed format of host tag conditions in global setting 'agent_deployment_host_selection' | ||
| Date | Jun 10, 2024 | ||
| Level | Trivial Change | ||
| Class | New Feature | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
The internal data format of the Checkmk global setting "Selection of hosts to activate agent updates for", normally configured via Setup "Global settings" or "Automatic agent updates" page, has been changed.
If you only use Setup for configuring Checkmk this change will not be relevant for you, since the data format will be changed automatically during update to 2.4x.
In case you edit global.mk files manually or via script to define the agent_deployment_host_selection configuration options, you will likely have to change your scripts or at least the configuration files.
A global setting with it's tag conditions in the old format looks like this:
F+:global.mk agent_deployment_host_selection += {"match_hosttags": ["my-host|cmk-agent|prod|lan|piggyback|no-snmp"]} F-:
The tags that should match are in list format, separated via pipe characters. There is no information about the tag group the configured tag is related with.
The new structure looks like this:
F+:global.mk: agent_deployment_host_selection += [ { "match_hosttags": { "agent": "cmk-agent", "criticality": "prod", "networking": "lan", "piggyback": "piggyback", "snmp_ds": "no-snmp", }, } ] F-:
In the match_hosttags dictionary the keys are the tag groups (as defined in Setup) and the values are the tags configured for each group.