Changelog (Werks)
The software development of Checkmk is organized in so-called Werks. A Werk is any change or bug fix that has an influence on the user's experience. Each Werk has a unique ID, one of the levels Trivial Change, Prominent Change or Major Feature and one of the classes Bug Fix, Feature or Security Fix.
Whenever you make an update to a new Checkmk version please make sure that you have understood all incompatible changes. You might have to adapt your configuration.
Want to get notifications for new versions, new werks or subscribe to the security mailing list? Sign up here.
- #15339check_sql: activate thick mode for oracle connections
- #16119Don't log unparsable SNMP traps per default
- #16120Fixed value of downtimes:is_pending column
- #16121Fixed CMC crash when sending illegal metrics to InfluxDB
- #16710Better handling of notification result in case of timeout
- #16772brocade_fcport: fix operating speed conversion
- #16848mk-sql can monitor bound to IP Sql Server instances
- #16866azure: Handle Azure API rate limit
- #16867azure: Remove unnecessary 'metric not found' errors
- #17158Fix error on publishing forcast or custom graphs to sites
- #17159Save scrollbar position on page load
- #17160Opsgenie: Better error handling
- #17161Fix link of "Open this Aggregation"
- #17162Add missing "Remove downtime" button
- #17163Fix "Discovery state" filter
- #17164Fix "Downtime active or pending" painter
- #17178Microsoft Teams: Updated notification message
- #17187HTTP/HTTPS Service: Correctly apply 'Certificate validity' of 'Standard settings'
- #17188Check Point plug-ins: increase detection sensitivity
- #17205agent_netapp_ontap: KeyError: 'rpm' and KeyError: 'temperature'
- #17206omd update: Log "Verifying site configuration"
- #17225Custom graphs: Respect "Metrics with all zero values" setting
- #17226Fix ValueErrors when rendering graphs
- #17227Synthetic Monitoring: Avoid crash in scheduler (client side) during RCC setup
- #17228Custom graphs: Visibility toggle had no effect
- #17229CPU utilization checking: Alert if utilization is exactly at threshold for too long