Skip to content

Version 4.3

Unreleased

  • FEAT: The start page shows a Cron Jobs status panel (below Recent Errors) with a one-click "Run" button to schedule a group for the next cron pass
  • FEAT: Saving a host in the web UI no longer forces its account to the CMDB default — you now pick the account from a dropdown, limited to your allowed accounts
  • FEAT: The Archive now has a per-row Restore button, not just the bulk "Restore" action
  • FIX: The Archive no longer offers a "Clone" action — cloning a soft-deleted host made no sense there
  • FEAT: The host list has a new "Set Account" bulk action to assign the source account of many hosts at once; users restricted to certain accounts can only pick and act within those
  • FEAT: The Data Quality dashboard now has its own permission instead of riding on the Hosts permission, and users without any Settings-area permission no longer see the Settings menu at all
  • FEAT: Your Saved Searches now live in the personal profile menu (top-right) — they were always only your own
  • FEAT: The API Swagger page can now authenticate with a personal API token as well as username/password — paste the token in the Authorize dialog (with or without a leading "Bearer ")
  • FEAT: Users can now generate personal API tokens (Profile → API Tokens) and authenticate with Authorization: Bearer <token> instead of their password; each token carries the user's own API roles and account scope, can be labelled and optionally expire, and is revocable at any time (admins can list and revoke a user's tokens too)
  • FEAT: Users can now be restricted to specific accounts — assign accounts to a user and both the REST API (read, create, bulk, delete, inventory, relations) and the web-UI Host and Objects lists only show hosts of those accounts; leave it empty to keep full access as before
  • FEAT: New "Projects" and "Cron" permissions can be granted to users; the Projects view is no longer tied to the Checkmk permission
  • FIX: The Roles and API-Roles pickers in the user form are now proper searchable multi-selects instead of a hard-to-use native list box
  • FIX: Deleting a host through the API now archives it (soft-delete, restorable from the Archive view) instead of removing it permanently
  • FIX: The API's Swagger page now shows a single, clear username/password login instead of two competing "Authorize" fields, so authenticating in Swagger no longer silently sends no credentials
  • FEAT: The host list's Delete action is now available outside CMDB mode too — it soft-deletes (archives) the host, and the Archive view (to restore or permanently remove) is reachable in every mode
  • FIX: Startup no longer crashes with a "field does not exist" error when the database was previously used by a newer version — unknown fields on the system config are now ignored instead of aborting
  • FIX: The Checkmk password store export no longer re-writes every password on each run — a password is only pushed to Checkmk when its content actually changed since the last export
  • FIX: The Checkmk host export no longer rewrites folder attributes on every run — folder options such as contact groups are only updated when they actually changed, instead of each export re-applying them because Checkmk returns them with extra default keys
  • FEAT: In CMDB mode the host list gains a "Bulk add hosts" button (paste a plain hostname list or a CSV, optionally pick a template) and an "Import CSV" button next to Export CSV — an uploaded or pasted CSV opens a preview where you pick which column is the hostname (any header works, not just hostname), toggle "first row has no header" if you forgot it, assign an optional template, and see the parsed rows before anything is created; every column other than hostname/folder/lifecycle_state and inventory_<name> becomes a host label
  • FIX: The "Assign Project" bulk action in the host list opens its dialog again (like "Set Template") instead of doing nothing
  • FIX: The host list's Labels column now also shows the labels an assigned CMDB template contributes (marked with a template badge), so template values are visible without opening the host
  • SEC: A host name containing HTML is no longer rendered as markup in the host list's log column
  • SEC: Account passwords are masked on the host debug page — a rule outcome using {{ACCOUNT:<name>:password}} no longer reveals the secret to users who only hold a plugin role; exports keep resolving it normally
  • SEC: A custom SQL query can no longer smuggle statements past the validation inside SQL comments
  • FIX: The "Generic Rules" permission can now be granted — the Filter, Rewrite and Custom Attribute views checked a role that did not exist and were reachable for global admins only
  • FEAT: Rules can now match on the account a host was imported from — the attribute SOURCE_ACCOUNT is available in every rule condition and Jinja value, so an export can be limited to the hosts of one import account
  • FEAT: Checkmk folder options can now set contact groups (and other WATO permission attributes); when several hosts share a folder but define different contact groups, the syncer merges them so the folder ends up with the contact groups of all its hosts
  • FIX: Checkmk folder options written with spaces around the pipe (folder | {options}) no longer append a stray _ to the folder name
  • FIX: Checkmk folder attributes of already-existing folders are now applied even when an export is limited to single hosts
  • FIX: Updating Checkmk folder attributes no longer wipes existing folder settings such as tags or SNMP configuration — only the attributes defined by a rule are changed
  • FIX: Malformed Checkmk folder options (an unbalanced brace, or contact groups written as a bare list) are rejected when saving the rule and reported loudly during export, instead of being silently dropped
  • FIX: Checkmk contact groups written directly as a Jinja expression (e.g. {{ groups.split(',') }}) are now also rejected when saving the rule, instead of slipping through unchecked and being refused by Checkmk
  • FIX: Broken Jinja in a Checkmk move/create-folder value (e.g. chaining .replace(...) after a |join(...) filter) is now caught when saving the rule and reported during export, instead of silently rendering to nothing and dropping the host's whole target folder
  • FEAT: The host debug page shows the resolved Checkmk folder options per folder — or a clear error when the option is malformed
  • FIX: An undefined variable inside Checkmk folder options no longer empties the whole folder path — the host keeps its target folder and only the unresolved options are dropped (and the drop is now reported instead of happening silently), instead of every affected host being moved to the root folder
  • FEAT: The start page shows the latest log entries that reported errors — failing sync jobs are visible right after login, each linking to its full log entry
  • FIX: sys update_cmdb now merges matching CMDB templates into a host's existing templates instead of replacing them, so previously assigned templates are kept
  • FIX: The TRUSTED_PROXIES setting from local_config.py now takes effect — behind a reverse proxy the "HTTPS is required but not in use" login warning clears and HTTPS-only API authentication works, instead of the setting being silently ignored
  • FEAT: New CLI command checkmk assign_template <account> <folder> <template> reads the hosts of a Checkmk folder and assigns a CMDB template to each of them that exists in the syncer (supports --dry-run)
  • FEAT: A First Steps wizard guides new installations through the initial setup — create an account, import objects, connect an export target, define rules, schedule cron jobs, invite users; every step checks itself off automatically, fresh installs land on the page until the checklist is complete or dismissed, and it stays reachable via "First Steps" in the profile menu

Version 4.3.0

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