ID: 10123
Title: Fixed race condition when changing host check command.
Component: cmc
Level: 2
Class: Bug fix
Version: 1.7.0i1
When the kind of a host check command was changed, e.g. from an active check
to smart ping, there was a small time window for scheduling to go wrong.
This resulted in endless log lines of the form "invalid command line '@foo'
for bar", and the only way to resume normal operation was to restart the
Checkmk Micro Core, reloading was not enough. This has been fixed.
ID: 10651
Title: prometheus_custom: Addition of Prometheus custom check plugin
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This commit adds the functionality of the Prometheus custom check
plugin to Checkmk. It allows the user to define PromQL queries and
generate services based upon the query results. The generic check
also displays information should a PromQL expression return invalid
or faulty results.
ID: 10122
Title: Fixed performance regression for event console history queries.
Component: Event Console
Level: 2
Class: Bug fix
Version: 1.7.0i1
The event console history queries had a rather serious performance
regression in 1.6.0: For common queries, the EC tries to pre-filter the
history via egrep before doing further filtering itself. This pre-filtering
was broken due to a typo and has been repaired now.
ID: 10639
Title: agent_prometheus: Addition of Prometheus Special Agent to Checkmk
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
This change introduces the underlying structure of the Prometheus
Special Agent into Checkmk. It provides connection functionality
along with preparation for subsequent service generation resulting
from Prometheus metrics.
ID: 7287
Title: Fixed incorrect processing of SNMP datasource configuration
Component: WATO
Level: 2
Class: Bug fix
Version: 1.7.0i1
Due to an incorrect old configuration conversion routine the snmp datasource setting for a host was incorrectly set/reset to <tt>No SNMP<tt>.
This could be observed on the edit host page, for example. It only applied to hosts where the agent tag group was explicitly set.
This incorrectly transformed snmp setting was written back to disk, when the host itself was saved or when there were any changes made in the host tags configuration.
Changes in the host tag configuration had a greater impact because they forced a complete rewrite of all host configurations.