What’s new in Checkmk 2.4
Checkmk 2.4 introduces a wealth of exciting new features, enhancements, and fixes to elevate your monitoring experience. From powerful new integrations and streamlined user interfaces to performance optimizations, this release continues to refine Checkmk’s capabilities for providing one lens for hybrid IT infrastructures. Read on to discover the key highlights and improvements in this version.
You will find a curated list of relevant werks and documentation articles for further information at the end of this document.
Notifications – a complete overhaul
The notification ‘wizard’ – finally enjoy configuring notifications!
Powerful notifications practically configure themselves in Checkmk 2.4, and take you by the hand in the process.
If you have ever struggled to set up notification rules, you can start relaxing now. The new guided mode leads you through the process – step by step. It provides content checks at each step of the way, including actionable hints on what to change whenever you run into an issue.
Notifications - everything in one place
Searching for rules and parameters is so 2023!
We are introducing the new notification hub to ease the creation and management of notifications. Key performance parameters are displayed aside lists of all related rules.
No more searching for the rules. No more searching for the correct settings.
More than a fresh coat of paint. Email alerts you’ll look forward to.
Guess what! Checkmk emails arrived in 2024. Now, they are easy to read. All information at a glance. And now they’re just as pretty on mobile devices.
We have significantly improved the email alerts. They are now clearer and more structured for better readability. Alert messages include detailed meta information like service summaries, details, host labels, and tags. Plus, each alert links directly to the rule that triggered it. Designed for seamless compatibility, they work with all major desktop and mobile mail clients.
These were just the major changes regarding notifications. We also made all major notification integrations more powerful. Read more in the werks overview.
Fast, faster, Checkmk 2.4.0
Major pages and actions are much faster in Checkmk 2.4. Among them are
- Activate changes (especially in smaller sites)
- Service discovery
- Initial page load time
- Any actions, e.g. moving services to/from disabled services
- Bulk discovery
- Effective parameters of a host / service
- Bake agents
- Manpages in catalog of check plug-ins
Most of the improvements root in the so-called automation-helpers, a new daemon to speed up various UI interactions.
Piggyback unleashed!
A piggyback host can now be monitored on any connected site and does not need to be on the same site as the source host anymore.
Checkmk is able to use agent data provided by other than the target hosts. These are typically referred to as source host as the provider and piggyback host as the receiver of this agent data. Until now this piggyback mechanism required that all involved hosts were monitored on the same site. With Checkmk 2.4, that’s no longer the case. In distributed setups, connected sites can now exchange piggyback data, allowing you to monitor a piggyback host on any site. Plus, thanks to a message broker (RabbitMQ), data is shared only when needed, ensuring that only relevant sites receive it – minimizing network traffic to the absolute minimum.
Dynamic hosts that don’t ghost you anymore
Ever wanted to monitor a Kubernetes cluster with pods changing every minute? Ever wanted to add hundreds of hosts in a short time? Reliably?
In Checkmk 2.4, dynamic host management has been restructured for improved reliability, performance, and scalability. The new architecture separates the connectors, which generate host data, from the processing cycle that manages host updates, service discovery, and activation of changes. Connectors operate independently and in parallel, feeding data into a sequential host processing cycle, preventing interference and ensuring smoother operations.
Host changes, service discovery and activating changes are much faster due to incremental activation, the new automation helpers and many further processing tweaks.
Cloud monitoring in a flash – no setup circus!
Set up AWS, Azure, and GCP monitoring in just a few clicks – no hassle, no headaches. The new Quick Setup guides you step by step through the web interface, ensuring a seamless configuration.
Get your cloud monitoring up and running in minutes. The new Quick Setup makes it easy to configure AWS, Azure, and GCP monitoring with just a few clicks. Plus, Checkmk automatically runs connection and configuration tests to ensure everything is set up correctly – so you don’t have to go back and forth between monitoring and configuration.
Checkmk + OpenTelemetry & Prometheus. Monitor anything!
Ever wanted to monitor… anything? Now you can!
You can push OpenTelemetry protocol compatible metrics, either directly from your applications or via an OpenTelemetry collector to Checkmk sites. You can also collect metrics from Prometheus exporters or of Prometheus /metrics endpoints directly now, without the need of an intermediary Prometheus server anymore.
These metrics can then be processed by a special agent and will result in Checkmk services, which can be monitored by generic check plug-ins.
This approach has its limitations, which we plan to address in the near future.
We invite you to participate in shaping this feature.
Note: The OpenTelemetry collector is an experimental beta feature, and not supported yet. Use and test at your heart's desire, just don’t rely on it in production - scope & features may change
Linux agents revisited
Sometimes, many steps are needed to reach a goal. Like when you want to have multiple Checkmk agents on one system running without root privileges. In 2.4.0, we have made major strides towards this goal.
We put all the agents in one basket... and it works!
Manage all agent files in one place. For better visibility and security.
The Checkmk agent so far has been located in common UNIX installation paths (/var/, /usr/, …). You can now configure with the new ruleset ‘Customize agent package’ one directory in which all agent files are installed. Static package files for installation are separated from runtime files now. This is the foundation for the ‘non-root’ agent mode.
Agents gone rogue: no root, no problem
On Linux, we have made big steps towards executing the agent without root privileges. Given the secure architecture of the Checkmk agent, this is not a must for everyone now, but in certain environments will make your life much easier to get the Checkmk agent approved.
If unprivileged access has been a requirement in the past, one had to make several adaptations to have the same data from the agent as with the standard execution as root. This gets much easier to set up in 2.4.0. With ‘Customize agent package’ you can now also configure a user to own the runtime files and execute the agent script. We rely on sudo as a mechanism. Thus make sure to copy the shipped sudoers config into /etc/sudoers.d .
The non-root mode is currently limited to the agent script. Runnings plug-ins, incl. the updater as non-root will still require customizations by you. With the foundation now set, you can expect more in the future!
Synthetic Monitoring
Ever wanted to try out Synthetic Monitoring with Checkmk? Now easier than ever with completely automated workflows.
Managed robots – a robot bakery in the making
No more manual installation of robots. Deploy robots via agent bakery.
You can upload and manage robots inside Checkmk. These robots can then be deployed via the agent bakery to your test nodes. Therefore, no more interaction by you on test nodes is required after agent installation, especially if you also leverage the agent updater.
Tux ♡ Synthetic Monitoring
Linux servers are now fully supported as test nodes, incl. automatic test environment setup. Ideal for running headless web tests at low resource consumption!
Monitoring-as-code
Empower your users to define the monitoring of their application.
Checkmk only discovers tests as services for Synthetic Monitoring. Thus, until now you had to define your tests more granularly, if you wanted more in-depth services. With Checkmk 2.4.0, you can now define via code which so-called keywords are discovered as services. This is completed by a ruleset, which does the same, but in a more structural manner via regex.
The relevant werks
Checkmk 2.4 includes more than 1,000 werks. This is just a curated list of the most relevant changes. For all changes, please check out all werks.
Notifications
- 17699: New notification setup
- 17700: New HTML Email template
- 17698: Introducing notification parameter for notification methods
- 17697: New "Notification overview" on "Notifications" page
- 17695: New entry "Analyze recent notifications" in "Setup" menu
- 17696: New entry "Test notifications" in "Setup" menu
- 16661: Notification Spooler: Support IPv6¹
- 17708: Test notifications: Send notifications on site of the host¹
- 17173: Test notifications: Support for all notification methods
- 17155: Microsoft Teams: Use workflows instead of connectors¹
- 17182: Opsgenie: Support other notification types
- 17023: Opsgenie: add ability to config extra properties in notification
- 17183: Opsgenie: Update description and message
- 17064: ServiceNow: Support for update of incidents and cases
- 17065: ServiceNow: Add option to use custom fields
- 17066: ServiceNow: New option for authentication with OAuth token
- 17157: Jira: Add update of issues on state changes
- 17154: Jira: Add option to set assignee
- 17176: Jira: Add option to include graphs
- 17067: Jira: Allow macros in label
- 17156: Jira: Add API/PAT token authentication option
- 17060: Jira: Add proxy option
- 17177: Slack/Mattermost: Updated notification message
Configuration
- 17943: Cloud Quick Setups: addition of AWS Quick Setup
- 17944: Cloud Quick Setups: addition of Azure Quick Setup
- 17945: Cloud Quick Setups: addition of GCP Quick Setup
- 17202: Improved handling of piggyback data in distributed monitoring setups.
- 17530: Fundamentally enhanced dynamic host management (DCD).
- 17275: Added a new host label cmk/customer for better customer handling in CME
- 17710: Added ability to update discovered service parameters
- 17193: Disabled services now consistently appear during service discovery
- 16645: Display the effective parameters for the Check_MK Discovery service
- 17200: Ensure all configured API integrations are always executed.
- 17195: Combined clustering of discovered and enforced services
- 17403: Discover service labels on clustered services
- 17714: Fix change detection of clustered services for discovered changes
- 17411: Added option in SAML to configure RequestedAuthnContext.
- 17252: Delete folders also on remote sites¹
- 17153: Skip unnecessary site activations when editing users¹
- 16718: Support for non-ASCII characters in custom host attributes.¹
- 17255: Fixed issue where deleting one comment removed all comments for acknowledgements¹
- 17358: Disabled automatic refresh on the background jobs overview page.¹
- 17814: Enable sorting for tag groups and preserve sorting settings on page actions¹
- 17816: Prevent setting host downtimes if user only has permissions for services.¹
- 16783: Increased time period horizon limit to 50 years.¹
- 17169: Also rename parents in folder properties¹
- 17338: Allow searching in dropdowns when many items are present¹
- 17579: Added user setting to show or hide contextual help messages.
Extension packages (MKPs)
Licensing
Monitoring integrations
Checkmk
Active checks, applications, databases, …
- 17113: Integrate popular "Ceph statistics" plugin
- 15520: check-httpv2: Added new options to HTTP monitoring
- 17419: check-httpv2: add options to disable certificates & to connect to physical host
- 17584: check-httpv2: add support for IPv6 address macros in the url
- 16898: check-httpv2: support macros in 'user_agent' field¹
- 17725: cmk-migrate-http: Command-line tool for migrating deprecated check_http rules
- 17730: cmk-migrate-http: Improve user experience
- 17737: cmk-migrate-http: Add conflict options for certificate validation
- 17716: check_cert: service output enhancement
- 17283: check_cert: remove defaults for server certificate validity
- 17284: check_cert: remove defaults for response time
- 17712: check_cert: also consider not_before in validity check¹
- 15517: check_cert: Fixed metrics in output¹
- 17085: check_cert: Allow more use of macros¹
- 16022: bazel_cache: Monitor Bazel Remote Cache¹
- 17244: Gerrit: monitor version of deployed instance
- 17594: Gerrit: add option for caching version information
- 17721: Gerrit: fix latest available versions
- 17370: Ship python package "oracledb" with omd¹
- 16590: Jenkins: Add metrics for memory, threads and active HTTP requests
- 16028: Jenkins: Set upper and lower level for number of jenkins executors¹
- 16461: Jenkins: Add (sub) path to the URI
- 15336: Add support for MariaDB 11¹
- 17035: mysql_replica_slave: Adapt mk_mysql for MySQL version 8.0.22 and above¹
- 15340: mysql_slave: propagate errors to service result¹
- 15337: oracle: Add support for monitoring oracle 23ai¹
- 15349: oracle: Do not discover uptime service for template databases¹
- 17568: oracle instance: fix incorrect perf-o-meter¹
- 15344: oracle: iostats performance could not be configured via bakery¹
- 17301: mk-sql plugin supports instances with custom local IPs
- 17503: mssql_jobs: Enable monitoring of jobs with the same name on multiple instances
- 17533: mssql_jobs: Add disabled schedule status to MS SQL Job service
- 16858: sql: Allow macros in 'Database user' field¹
- 16861: sql: Allow macros in 'Query or SQL statement' field¹
- 17360: mk_postgres.py: Enable using a system wide PGPASSFILE
- 17566: elasticsearch: allows customizable filters for node statistics¹
- 17079: mk_redis: Autodetect Checkmk instances¹
- 16430: veeam_jobs: Always Monitor Result of Last Backup¹
- 17516: Stormshield: Cluster Member: add missing ruleset¹
- 17631: sap_hana_status: Always discover the Status service¹
- 17151: Make Microsoft IIS monitoring locale independent¹
Operating systems
- 16247: systemd: Monitor CPU, Memory, Tasks and Active time reported from systemd
- 15342: systemd: Support units without description¹
- 17042: systemd: Make default state of failed units CRIT¹
- 17763: systemd: Do not let disabled services influence the state of the check¹
- 15341: systemd: Handle reloading units correctly¹
- 17230: heartbeat_crm_resources: Check for unmanaged nodes
- 17285: bonding: Configurable number of expected interfaces
- 15345: mk-job: Discover running jobs¹
- 15346: mk-job: clean up old running jobs¹
- 15347: mk-job: currently running job was not correctly reported¹
- 17229: CPU utilization checking: Alert if utilization is exactly at threshold for too long¹
- 17235: CPU utilization: allow total CPU utilization to be set above 101%¹
- 17077: Allow filesystem service rule levels to go above 100%¹
- 16857: diskstat: Use WWN as service description for physical disks
- 16254: mrpe: Add metric translations mrpe based windows checks¹
- 16244: Handle nfs mount dirs with whitespace¹
- 16776: chrony: change default warning level¹
- 17528: tcp_connections: Support for connection data from "ss" and "netstat"¹
- 17388: mk_logwatch: Activate bakery plugin for AIX
- 17720: solaris: Add full path fallback for uname
- 15356: solaris: implement alterantive way to get total available memory¹
- 17371: aix: Use ifconfig to get down interfaces¹
- 17237: openwrt: resolve issue when hostname command unavailable¹
- 17203: FreeBSD: Use sysctl to gather memory info
- 17410: freebsd: add support for isc_dhcpd (for OPNsense etc)
- 17311: mk_logwatch: Apply context to informational (OK) messages¹
- 16381: HP-UX: Mirror State of LVM Logical Volumes: be more robust in state evaluation
Virtualization, container & cloud
- 17524: Experimental OpenTelemetry metrics processing
- 17485: Enhanced AWS authentication for AWS hosted Checkmk instances
- 17597: Create AWS piggyback host labels for DynamoDB and ELB
- 17002: Support Azure Databases for MySQL flexible server¹
- 17241: Support Azure PostgreSQL Flexible Server
- 17483: Add deadlocks ruleset to Azure Database Monitoring¹
- 17126: Azure MySQL and Azure PostgreSQL: Add lower levels for active connections
- 16442: Addition of support for Kubernetes v1.29¹
- 17123: Addition of support for Kubernetes v1.30¹
- 17216: Addition of support for Kubernetes version 1.31¹
- 16436: Support Kubernetes PodReadyToStartContainers Condition¹
- 15352: gcp_cost: several changes
- 16903: proxmox: allows to use IP address and a custom value
- 16875: Nutanix: introduce option to skip TLS verification and resolve broken request helper¹
- 17185: Nutanix: Add option to configure connection timeout¹
- 17364: Nutanix: Prism alerts with multiple expired licenses¹
- 17368: Nutanix: Properly support Prism Central¹
- 17874: vSphere: Distinguish between virtual machines and templates
- 16870: vsphere: Determine snapshot age based on system time¹
- 17872: Clean up ruleset for vSphere special agent
- 17114: esx: Allow configuration of "Stand by" state¹
- 17606: esx: Include CPU model and vendor for ESX hosts with one CPU in inventory¹
- 17372: docker: Handle missing disk IO from running docker container¹
- 17655: docker: Fix inventory of docker node networks¹
Hardware / networking
- 17404: Added Redfish integration to Checkmk.
- 17791: redfish: Add controller ID in discovery for HPE drives
- 17792: redfish: Add service tag for Dell Devices in System State Details
- 17790: redfish: Add SSD life counters as metric
- 17210: Introduced new agent plugin for monitoring S.M.A.R.T. disk health.
- 17736: smart_nvme: Add check parameters
- 17735: smart_ata: Add check parameters
- 17733: smart_posix: Use the model and the serial number as an item
- 17734: smart_posix: Add support for Dell PERC 5/i,6/i controller
- 17722: Added support for Cisco Integrated Management Controller.¹
- 17190: Added Cisco APIC support to the UCS Bladecenter Special Agent.
- 17522: New check plugin: Cisco UCS: Fault summary
- 17288: cisco_ucs_psu check now detects PSU faults.
- 17289: cisco_ucs_fan check now detects fan faults.
- 16196: cisco_temperature: Improve admin state detection¹
- 16760: Add support for NetApp ONTAP S3 Subvolumes¹
- 16608: Add support for NetApp ONTAP volumes without counter data.¹
- 16777: Implemented exclusion of volume performance queries in NetApp ONTAP.¹
- 17937: netapp_ontap_snapvault: monitor snapmirror transfer state
- 17571: netapp_ontap_ports: do not discover ports in state down¹
- 17573: netapp_ontap_disk: do not monitor disks with container-type remote or partner¹
- 17569: Netapp SVM Status: set status as OK for sync_destination subtype¹
- 17572: netapp_ontap_disk: show spare disks also if no params are configured¹
- 16778: Support for additional fortisandbox models
- 16532: Added support for TP-Link T1500G-8T syslog format to Event Console.
- 17359: Added support for IBM 4500 tape library.¹.
- 17189: Added support for NetVision devices
- 16894: Extended support for NetVision devices¹
- 17592: Added support for HPE RAID controllers with hot spare disks.¹
- 17188: Added support for additional Check Point devices.¹
- 16346: Added support for additional ATS devices.¹
- 17031: Added support for additional TrippLite UPS devices
- 17498: Support v7 APC UPS Firmware and monitor UPS connection¹
- 17243: Added support for additional USV UPS devices¹
- 16746: infoblox_service: Add support for NIOS 9.X¹
- 16793: infoblox_temp: Add support for > NIOS 8.6¹
- 15363: Allow extreme checks to detect Avaya switches
- 16751: Migrated Arista temperature sensors to standard entity sensor checks.
- 17361: Support all states for Aruba PSU¹
- 16884: Updated seh_ports to support new OIDs from sehMIB v2.5.¹
- 16804: Printer cartridge levels: Allow to configure receptacles and containers individually
- 17557: apc_ats_output and apc_ats_status now support APC AP4423A.¹
- 17286: apc_ats_output now includes metrics and rulesets for current and power.
- 17033: if_fortigate now displays admin state in the summary.¹
- 17786: Improved interface discovery for MICROSENSE G6 and Cisco Catalyst 9200L switches.¹
- 15353: storcli_pdisks now supports storcli2.¹
- 17871: storcli_pdisks: Support for status JBOD¹
- 17588: fritz: use 64-bit counters for traffic counters if available
- 17835: Printer Supply: switch to color-based toner metrics
- 17184: Generic Printer: IO Unit State - Allow to not impose any levels¹
- 17087: agent_cisco_meraki applies changes to selected organizations immediately.¹
- 17242: Fixed missing services in Cisco Meraki¹
- 17355: raritan_pdu_plugs.py now respects user-defined parameters.¹
- 17555: Changed default values in apc_humidity.¹
- 17393: Dell iDRAC via SNMP now includes firmware version in HW/SW Inventory.
- 17209: if64 now uses system uptime instead of check time.¹
- 17402: Improved the ruleset for "Fetch intervals for SNMP sections".
Agent / generic improvements
- 17900: Linux agent: single directory deployment
- 17901: Linux agent: non-root deployment
- 15518: Enable symmetric agent encryption on Solaris
- 17389: runas: Concretize ruleset
- 17890: Agent controller: Support IPv6 in --server argument of register commands
- 16813: Changed aborting behavior for overrunning cached agent plugins
- 17109: More helpful error handling for broken plugins¹
- 17110: Don't crash on broken plugins unless in debug mode¹
- 17337: Report CRIT on loss of redundancy in IPMI sensors¹
- 17093: Use SHA256 digest when baking RPMs¹
- 17300: Windows agent do not use timeout on fail for section CpuLoad and DotNetClr¹
Synthetic Monitoring
- 17291: Make Synthetic Monitoring available on Linux
- 17290: Synthetic Monitoring: Re-work Keyword Monitoring
- 17426: Synthetic Monitoring: Support Offline RCC Environments
- 17427: Synthetic Monitoring: Introduce Managed Robots
- 17428: Synthetic Monitoring: Configure Secret Environment Variables for Robot Framework Runs
REST-API
- 17324: broker_connection: New endpoints implemented for peer to peer broker connections
- 16478: saml_connection: implementation of saml connection endpoint
- 16527: ldap_connection: implementation of new ldap connection endpoints
- 16671: Add "Update service labels" option to service_discovery endpoint¹
- 17239: host_config: introduction of filters for 'Show all hosts' endpoint
- 17273: host_config: introduction of fields selector for "Show all hosts" endpoint
- 17911: host_config: improve performance of bulk-update endpoint
- 17586: bulk_discovery: introduce individual id for bulk discovery job
- 17580: activate_changes: add activation status to rest-api response
- 16657: add columns parameter to service status endpoint
- 16658: add mode parameter to host tag group delete endpoint
- 17179: Include customer in list group endpoints¹
- 17322: Updated endpoints for distributed monitoring connections
- 16785: notification rules: allow for the global http proxy configuration for plugins¹
- 17180: Add inventory paths to contact group endpoints
- 16475: downtimes: add filters for host and service groups to modify and delete endpoints
- 16662: change host rename wait for completion endpoint to GET
- 17022: notification rules: align the REST-API with the UI for the Jira plugin config
- 17250: notifications: add emergency as a Pushover priority option
- 16715: Improvement of response data types
- 17510: adjust error message for service discovery
- 16749: Add 'Export this connection for API' to dcd connections
Visualization & analysis
General
Views
- 16622: HW/SW Inventory: Improve filtering for number of sites for Checkmk version
- 17314: HW/SW Inventory: Allow monitoring of networking changes
- 17222: HW/SW inventory: Retain inventory history on central site¹
- 17602: Added sorter for "Docker node" column¹
- 17007: Allow sorting for view columns "IP addresses" and "IPv6 address"¹
- 16998: SLA alert levels: show CRIT state if SLA alerts levels are CRIT but SLA not broken yet¹
Performance
- 17678: New process daemon "automation-helper" speeds up UI interactions
- 14237: Fixed performance problems for various command line operations¹
- 16437: omd: Improve Runtime with Many Sites¹
- 17911: REST API host_config: improve performance of bulk-update endpoint
- 14243: Improved performance of host attributes processing in very large setups
- 14244: Improved performance when working with host attributes
- 17494: Improve performance when calculating pending changes icon
- 14246: Improved performance on updating configuration during a software update
- 17600: Prevent alertstats view from initially freezing on large sites
Security
- 17344: No default storing of automation user secret
- 17027: Certificate Overview page
- 16878: 'Hide Checkmk version' per default
- 16829: Notify users on account security changes
- 16831: Enforce two factor authentication by role or for all users
- 16830: Bruteforce protection for two factor authentication¹
- 17341: Agent updates in distributed monitoring: Switch to site secret based authentication
- 15029: Improve setting up new least privileged user roles
- 16616: Terminate all GUI sessions during update
- 17147: Disable automation user login via HTTP parameters
- 17780: Fix redaction of remote site secrets in log messages¹
- 17056: Don't show automation secret in the audit log (addresses CVE-2024-28830)¹
- 17095: Sanitize Host and Folder Credentials in Audit Log¹
- 17552: Two-factor changes now synchronize across distributed monitoring setups
- 16992: Introduce global setting: Default dynamic visuals permission¹
OMD / internals
- 16565: Introduce distributed tracing of Checkmk
- 17207: omd update: Reintroduce Log "Verifying site configuration"¹
- 17221: omd update: Do not trigger conflicts during stateful update¹
- 17560: omd backup: --no-logs now excludes logs not ending with .log¹
- 17559: omd backup: add new option --no-agents
- 17564: omd update: keep var/log/update.log forever¹
- 17395: Show all invalid configurations during update¹
- 17607: omd cp & omd mv: Fix copying and moving a site with dynamic host management¹
- 17532: Introduce DCD command line tool
- 17398: Add commandline helper: cmk-piggyback
- 16572: Replace cmk --inventory-as-check with check_cmk_inv command
- 17214: Automatic Disk Cleanup: Allow Site Specific Configuration
- 16513: Add option to change the maximum response size for livestatus¹
- 16594: Container: Support setting custom timezone¹
- 16563: Ensure background jobs finish properly on stopping sites
- 16425: APACHE_TCP_ADDR now allows IPv6 address¹
Distributions
Deprecations / removals
- 17201: Decommission agent_based_api.v1 (a.k.a. Check API)
- 17662: Send user messages if deprecations are found
- 17348: Disable access to check_mk/local/agents/
- 17346: Deprecation of "Check State of BI Aggregation"
- 16767: NetApp via WebAPI: remove deprecated agent and plugin
- 17732: smart: Deprecate legacy plug-in
- 17387: "cmk --convert-rrds" deprecated
- 16483: ntopng integration: remove ntopng version support for versions older than 6.0
- 17554: Deprecated: EMC VNX storage systems special agent
- 17665: check_http: Postponed hard deprecation of old HTTP monitoring plug-in
- 17604: Remove deprecated unused global settings "Use Inline SNMP"
- 16825: parent scan: Deprecate command line tool in favor of REST API endpoint¹
- 17174: REST API: removal of previously deprecated endpoints¹
- 17643: Deprecation of 'lib/check_mk' symlink
- 15359: move dell_powerconnect to exchange.checkmk.com
For all changes, please check out all werks.
Notes:
¹also ported to 2.3.0