ID: 10191
Title: Windows Agent doesn't add 'cached' info into the piggybacks' headers
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously Windows Agent added cached data, something like ':cached(123456,600)'
to the piggyback headers. This may led to problem for checks on monitoring
site.
With this release the problem has been fixed.
ID: 10190
Title: Windows Agent sends 'TCP counters' subsection for skype section
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously this subsection was absent in the Agent's output. This may lead
to the crash of skype check.
Now this problem has been solved.
ID: 10245
Title: Fix thread leak triggered by unstable site connections
Component: Livestatus Proxy
Level: 2
Class: Bug fix
Version: 1.7.0i1
The livestatus proxy normally keeps open several connections to the remote
livestatus server and uses them in the moment a livestatus query is made
from the central site to the remote site.
In the moment a site is not reachable anymore, for example because of a
network connection issue, this is detected by one of these connections.
The site is then terminating all other connections and trying to recover
from this situation by continuously reconnecting to the remote site.
In this situation the livestatus proxy was not cleaning up it's old connection
threads while opening new ones for the new connections. After some time this
could result in "Resource temporarily unavailable" errors in various places or
"can't start new thread" shown in the GUI.
ID: 10069
Title: graylog_cluster_stats: New check to monitor cluster statistics of a graylog instance
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
With this check you can monitor graylog cluster statistics like number of
inputs, outputs, streams, stream rules, extractors and user. It also outputs
elasticsearch statistics, eg. number of nodes, data nodes, shards, timeouts and
indices. Also mongodb statistics are shown, eg. allocated storage, total,
uncompressed data and average document size and number of extents, collections
and objects. Needs the datasource "Check state of graylog" to be configured.
ID: 10072
Title: graylog_nodes: New check to monitor graylog nodes
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
With this check you can monitor graylog nodes. It outputs the load balancer,
lifecycle and processing state. Also the number of inputs is shown. The
long_output gives detailed information about the inputs of the node.
ID: 10073
Title: f5_bigip_vserver: Fixed ValueError while ip parsing
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Service discovery shows "chr() arg not in range(256)" because of wrong ip parsing.
This has been fixed. You can rediscover those services now.
ID: 10244
Title: Periodic service discovery was not correctly activating changes
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.7.0i1
When the automatic update of the service configuration is enabled, the periodic
service discovery was applying service discovery changes, but was not
activating them when configured to do so.
The services appeared as discovered on the discovery page in WATO, but they were
not activated. After activating a change in the GUI, the services were finally
activated.
ID: 10243
Title: Periodic service discovery: Set minimum group time to 5 minutes
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
The cron job is executed every 5 minutes, a lower grouping value does not
make sense.
ID: 7869
Title: mk_mongodb: Fixed crash introduced by Python 2.5 compatibility change in 1.6.0p2
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0p3
Python backward compatibility introduced by Werk #10184 also added a bug crashing the plugin or reporting incorrect data by the plugin.
To resolve the issue the fixed version of the mk_mongodb plugin has to be deployed on the affected hosts.
ID: 8918
Title: Inventory Kubernetes ingresses
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This adds entries under the Kubernetes.Ingress node of the
software inventory. The load balancers, the backends,
and the hosts are listed.
<b>Note</b> Users must apply the new version of
check_mk_rbac.yml to access the ingresses.