Catch up on the latest product updates, best practices, and expert insights from the Checkmk Conference #12 – Watch the livestream recordings now

Werk #20121: Redesign support diagnostics: topics and sensitivity thresholds

Component Setup
Title Redesign support diagnostics: topics and sensitivity thresholds
Date Jul 21, 2026
Level Prominent Change
Class New Feature
Compatibility Incompatible - Manual interaction might be required
Checkmk versions & editions
3.0.0b1
Not yet released
Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT

The Support diagnostics feature (Setup > Maintenance > Support diagnostics and cmk --create-diagnostics-dump) has been redesigned. The content of a dump is now provided by discoverable plugins, each declaring a topic and a sensitivity (low, medium or high).

Migration required

This change is only incompatible for scripts calling cmk --create-diagnostics-dump with the previous per-option flags (--local-files, --omd-config, --checkmk-config-files FILE,..., --gui-profiles ID,..., ...): these options no longer exist and such calls now fail. Adapt the calls to the new selection options described below; --list shows everything available on the site. If you only ever created dumps via the GUI, no action is required.

What changed in the GUI

Instead of individual checkboxes and per-file selections, you now choose one sensitivity threshold per topic: Off, Low sensitivity only, Low and medium sensitivity (the default, matching the previous "do not pack high sensitive files" behavior) or All including highly sensitive data. Some information (e.g. version and OS information) is always included and shown read-only.

The per-file selection and the component bundles (Global settings, Notifications, Hosts & Folders, Business Intelligence, CMC, Licensing) were removed. The affected files are covered by the Configuration files, Log files, Monitoring core & daemons and Licensing topics at their classified sensitivity.

What changed on the command line

cmk --create-diagnostics-dump now selects content the same way:

cmk --create-diagnostics-dump --list
cmk --create-diagnostics-dump --all-topics medium
cmk --create-diagnostics-dump --plugins performance_graphs,apache_config --checkmk-server-host myhost

--list shows all plugins available on the site, grouped by topic. --all-topics selects everything up to the given sensitivity threshold; individual plugins are added with --plugins (per-topic thresholds are a GUI-only convenience). Without any option, only the always collected plugins are packed. Stored GUI performance profiles are now packed as a whole via the Performance & sizing topic instead of by individual profile id.

Edition specific availability

A plugin is available exactly where its code is shipped. Notably, the metric backend diagnostics are now available in the cloud, ultimate and ultimatemt editions via both GUI and CLI (previously the CLI offered them only on ultimate and the GUI only on ultimate and ultimatemt), and the OpenTelemetry license count collection no longer produces errors in dumps of editions without a metric backend.

Distributed setups

The dump of a remote site is now requested via the new create-diagnostics-dump-v2 automation. Central sites running an older version keep working: the previous automation calls are still served (a remote site may be one version ahead of its central site). These compatibility endpoints will be removed in version 3.1.

To the list of all Werks