Skip to content

Version 4.4

Unreleased

  • FEAT: Every Checkmk Setup Rule has a debug page, reached by its bug icon in the rule list: for a rule built from a pasted list it shows every row with the number of rules it produced and the Checkmk rules the export would send, without contacting Checkmk; for a rule built per host it opens the host debug page with that rule preselected
  • FEAT: CMDB objects can be debugged like hosts: the bug icon in the object list opens the same debug page with the object's attributes, matching rules and outcomes, and the new target "Netbox Objects" shows the IP address, prefix, interface, contact and dataflow rules that apply to a host or object
  • FEAT: A Checkmk Setup Rule can take a pasted list (CSV, semicolon or tab separated, e.g. copied from a spreadsheet) as its input instead of the hosts: switch its new Rule source to "From a pasted list", and the first line of the list names the columns, which become variables for the Value and the conditions; the rule creates its Checkmk rules once per row instead of once per host, rows that only differ in the service name are joined into one Checkmk rule, and the form shows the column variables (a click inserts one into the field you were editing), the first rows and every problem with its line while you paste
  • FEAT: One imported record can create several hosts: a rewrite_hostname template that renders a list, for example {{ [HOSTNAME, HOSTNAME | replace('SRV01', 'RTR01')] }}, imports one host per entry, each with all attributes of the record; every importer handles it the same way, and a template that renders a plain name works exactly as before
  • FEAT: Two new condition types, Older Than and Newer Than, compare the value of an attribute holding a date against the clock — they are offered as a value match only, because a hostname and an attribute name are never a date — so a rule can be limited to the hosts that were not seen for longer than a given age (2d, 12h, 30m, 1w or a plain number of days) — and, the other way round, to the ones seen since; the same thing needed a Jinja expression before
  • FIX: A rule working with the date a host was last seen is no longer answered out of the export cache, so a host switched off after days without a sighting is switched on again as soon as it is back instead of keeping the state it was given while it was missing; only the rule sets that work with a date are affected, every other one stays cached and exports as fast as before
  • FEAT: Checkmk users can be generated from host attributes — one user per LDAP group the hosts carry, named after the group and given the mail address that group has in the directory; a new rule under Checkmk says which attributes hold the group names, and existing users created by hand are never overwritten
  • FEAT: Every field of an LDAP account now explains in the form what it configures
  • FEAT: The Checkmk user generation can rewrite a group name before it is looked up, for hosts that carry it in a different shape than the directory uses — a prefix dropped, a domain cut off; a value the rewrite empties is skipped instead of creating a user from whatever the search filter alone finds
  • FEAT: The fields of a generated Checkmk user can name the group both ways: {{name}} as it was searched in the directory and {{original_name}} as the host carried it before the rewrite
  • FEAT: Checkmk roles and contact groups of a generated user are Jinja too, so a group can say which ones it deserves — an entry that renders to nothing is dropped and one that renders to several names becomes all of them
  • FEAT: New page "Preview Generated Users" under Checkmk shows what the generation rules would make of the hosts you have right now — which groups were found, what the directory returned for them and which Checkmk user each one becomes, without writing anything
  • FIX: "Foreach Value in List" now also accepts an attribute name ending in *, so hosts carrying their groups in several attributes — one per team, each a comma separated list — are read as one list instead of yielding nothing
  • FEAT: The Checkmk user generation can be debugged from the command line: --debug shows which subtree, filter and attribute the group lookup used and which groups the directory did not return, and --search-filter tries another group filter out without anybody editing the rules first
  • FEAT: New account option "http_proxy" sends every HTTP request of that account through a proxy — for a target system like ServiceNow that is only reachable through the corporate proxy; direct sends a single account past a proxy the environment sets for everything else
  • FEAT: The Checkmk rule export calculates its rules about three times faster, so a big inventory spends far less time in "Loop over Hosts and collect distinct rules"
  • FEAT: The host and object search finds entries by the day they were created: created:today, created:yesterday or created:2026-09-22, and created:>=2026-09-01 together with created:<=2026-09-07 for a range; the day is the one on your own clock — hosts that were created before the syncer recorded a creation time are matched by the day their entry was written to the database
  • FEAT: The times the interface shows for hosts — created, last seen, last synced, the host timeline, the inventory trees, the data quality page and the API token list — are converted to the timezone of the computer you are reading them on, while they stay stored in UTC; cron and log timestamps are unchanged, they are written in the server's own time

Version 4.4.0

(Initial 4.4 release — entries currently live in the Unreleased section above. They get folded down into this section when the release is cut.)