Skip to content

Version 4.5

Unreleased

  • FEAT: API: the cron status (/api/v1/syncer/cron/) tells whether a cron group is enabled, so the Checkmk plugin no longer monitors disabled or deleted cron groups
  • FEAT: Checkmk: new Manage LDAP Connections maintains the LDAP connections Checkmk logs its users in with, including contact groups and roles from directory groups; server and bind password come from an LDAP account, checkmk export_ldap_connections creates, updates or removes them
  • FEAT: rules export_all_rules --zip writes the export compressed into a zip archive, and rules import_rules reads such an archive back as it is
  • FEAT: Checkmk Settings: Fill in from checkmk.com loads the current Checkmk versions on click and fills in version, edition and the filename of the installation file for the chosen platform, including the Checkmk Appliance; a new Download Proxy is used for the download of the installation file and for this list
  • FEAT: Checkmk Setup Rules: the new option Per Template evaluates a rule once per CMDB template of the host, each time with only that template's labels, so a contact group and the services of one template no longer mix with those of another template on the same host; the host debug page shows these rules per template
  • FEAT: The account list is grouped by account type, each group under a heading with the type's name and its number of accounts that folds the group away like the Global Custom Attributes, with Expand all and Collapse all; sorting by a column shows the plain list
  • FEAT: Browser tab titles name the page first, e.g. "Edit web01 · Hosts · Objects" or "Filter · Rules · Ansible", so open tabs can be told apart
  • FEAT: Host list: new filter Checkmk Attribute Key:Value finds hosts by the attributes of their last Checkmk sync, the green label badges
  • FEAT: Host list: show up to 500 hosts per page
  • FEAT: Host list: new action Remove Template takes one CMDB template off the selected hosts and keeps their other templates
  • FEAT: Lookup Tables: maintain a long key/value list in the UI and read it in any Jinja field with {{ lookup('table', key) }}, e.g. to set an attribute from the value of another one
  • FEAT: Custom Attributes and Rewrite Attributes: a Jinja help next to the template fields lists the lookup tables, variables, functions and filters and inserts them with one click
  • FEAT: Global Custom Attributes: the rule list is grouped by the attribute each rule sets (a rule with several attributes in a group of that combination), shows every rule's place in the order the rules run, and the order can be changed by drag and drop or with the arrow keys, including moving a rule into another attribute's group. Each group folds away with a click on its heading
  • FEAT: Secret Store: the Checkmk password store is now Modules > Secret Store and holds passwords, tokens and certificates for every module, global or bound to a host. Rules reach a host's entry with {{ secret('key') }} (plaintext with {{ secret_value('key') }}), entries of an archived host are kept as orphaned and can be bound to another host, certificates are shown for copying, and the host overview lists the entries of the host with masked values. New roles: Secret Store, and Secret Store: show plaintext values. Users limited to accounts or templates only reach entries of their own hosts, never global ones. Lookup Tables and the Secret Store sit at the bottom of the Modules menu
  • FEAT: Host import: Import CSV / YAML also takes YAML files (several at once, several hosts per file as a list or as documents separated by ---, also YAML-like files whose certificate lines are out of indentation), and "Bulk add hosts" is now "Add hosts manually" with a format switch (auto, host list, CSV, YAML, key/value list)
  • FEAT: Host import preview: every import and every manual add opens a preview where the values of each host, added columns and a template per host can be edited, chosen columns go into the Secret Store instead of becoming labels, and the account of the imported hosts is picked. Users limited to accounts only get their own accounts and cannot overwrite hosts outside their scope
  • FEAT: Checkmk Setup Rules: the Jinja help sits next to the Value Template and the Folder, the new placeholder {{ HOST_FOLDER }} puts a rule into the folder its host lands in (rules per host only), and the Host label and Service label conditions are entered as compact key and value pairs with suggestions from the existing labels. The Host label condition now takes several labels as well, all of them must match
  • FEAT: Checkmk > Folders and Folder Options: the folders the host export would use, with the hosts landing in each and the folder options (contact groups, permissions, title, ...) sent to Checkmk, per Checkmk account. The debug of a folder shows which host and which Export Rule with which conditions gave which option and how the values merge. Calculated from the syncer alone without touching Checkmk or the pools, users limited to accounts or templates only see the folders and options of their own hosts
  • FEAT: Checkmk menu sorted into groups with dividers: the host export rules with the Pools first, then the rules for setup rules, groups, tags, users, downtimes, notifications, DCD and BI, then the Checkmk Server and the inventory from Checkmk, and at the bottom the views to check the result (Folders and Folder Options, Preview Generated Users, Data Quality Check, Cache). The menus are a little denser so the long ones fit the screen
  • FEAT: Checkmk > Data Quality > Configuration Checks: pick a Checkmk account and the checks to run and see the problems they find, split by topic with a summary of the counts on top, and download them as a PDF report in the syncer design (needs the optional package fpdf2 from the extras, the page works without it). The first check looks at the HTTP checks: services that are WARN, CRIT or UNKNOWN in the monitoring right now with their output and the rule behind them, the same URL checked twice, website and certificate checked by two separate checks that one check_httpv2 check can do, and old check_http rules that are not migrated or still run next to their migrated rule. The checks only read from Checkmk. The Data Quality Check moved into the same Data Quality submenu

Version 4.5.0

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