ID: 7123
Title: hr_ps: New check which monitors processes via SNMP
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
The {HOST-RESOURCES-MIB} is a standardized MIB provided by many
SNMP agents. This check uses that MIB in order to monitor the
current processes of the target host.
ID: 7202
Title: Elasticsearch Monitoring
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.6.0i1
7202 Elasticsearch Monitoring
A special agent and first checks to support monitoring of Elasticsearch cluster, nodes and indices.
With this werk it is possible to monitor the cluster and node states of an elasticsearch instance.
LI: elasticsearch_cluster_health: State of the cluster (eg. green/yellow/red), Name, Number of nodes, Number of data nodes
LI: elasticsearch_cluster_health.shards: Number of shards in different states
LI: elasticsearch_cluster_health.tasks: Pending tasks, Task max waiting, Time out of tasks
LI: elasticsearch_nodes: Total virtual memory, CPU usage, Number of open file descriptors of nodes
For each check it is possible to set parameter in the associated WATO rule.
Checks for Cluster, Indices and Shard statistics follow soon.
Thanks to Fabian Binder for creating the initial version of the agent and checks!
ID: 7328
Title: Deprecate inventory_processes and inv_domino_tasks rulesets
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
If you have always used WATO to configure your Check_MK you are not affected
by this change.
There have been two rulesets for configuring process discovery rules for a long
time. The old one, <tt>inventory_processes</tt>, and the newer WATO compatible
ruleset <tt>inventory_processes_rules</tt>. The second one has replaced
inventory_processes a long time ago. The old ruleset was still working for
compatibility but has been removed now.
If you have configured such rules in your configuration, it will still load,
but print out a warning message like this: "WARNING: Found rules for deprecated
ruleset 'inventory_processes'. These rules are not applied anymore. In case you
still need them, you need to migrate them by hand. Otherwise you can remove
them from your configuration."
The same applies to the ruleset <tt>inv_domino_tasks</tt> and
<tt>inv_domino_tasks_rules</tt>.
ID: 7327
Title: Deprecate inventory_services ruleset
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
If you have always used WATO to configure your Check_MK you are not affected
by this change.
There have been two rulesets for configuring windows service discovery rules
for a long time. The old one, <tt>inventory_services</tt>, and the newer WATO compatible
ruleset <tt>inventory_services_rules</tt>. The second one has replaced inventory_services_rules
in version 1.2.2 of Check_MK. The old ruleset was still working for compatibility
but has been removed now.
If you have configured such rules in your configuration, it will still load,
but print out a warning message like this: "WARNING: Found rules for deprecated
ruleset 'inventory_services'. These rules are not applied anymore. In case you
still need them, you need to migrate them by hand. Otherwise you can remove
them from your configuration."
ID: 7330
Title: Fix confusions when working with localized shell environments
Component: Site Management
Level: 1
Class: Bug fix
Version: 1.6.0i1
When switching to the site user context we now enforce a non localized
environment. The reason for this configuration is that the parameters and
outputs of the monitoring plug-ins are localized. If they are called from the
core, they are always language-neutral. During manual testing, the plugins may
behave differently depending on the localization of the user's environment
variables. This can lead to confusion during tests.
ID: 7329
Title: Deprecate logwatch_patterns configuration option
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
If you have always used WATO to configure your Check_MK you are not affected
by this change.
There have been two configuration options for configuring logwatch pattern on
Check_MK server side rules for a long time. The old one,
<tt>logwatch_patterns</tt>, and the newer WATO compatible ruleset
<tt>logwatch_rules</tt>. The second one has replaced the first one a long time
ago. The old config optionswas still working for compatibility but has been
removed now.
If you have configured such rules in your configuration, it will still load,
but print out a warning message like this: "WARNING: Found rules for deprecated
ruleset 'logwatch_patterns'. These rules are not applied anymore. In case you
still need them, you need to migrate them by hand. Otherwise you can remove
them from your configuration."
ID: 7203
Title: agent_prism: Fixed handling of informational messages
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
We have seen informational messages in format:
{dev_type} drive {dev_name} on host {ip_address} has the following problems: {err_msg}
In order to handle such cases, we now deal with this message format differently.
ID: 7331
Title: Fixed decreased performance in host / service views since 1.5.0p5
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
When using the HW/SW inventory the performance of views, especially in
distributed setups with slower responding sites, could be decreased
significantly because the GUI performed too many livestatus requests in the
background.
This was caused by werk #6594 which was added in 1.5.0p5.
ID: 7070
Title: agent_kubernetes: don't output node with name "None"
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
If pods cannot be scheduled their assigned node is "None".
The special agent produced piggyback data for this "None"
node. This output is now removed.
ID: 7252
Title: agent_hivemanger: now uses python requests for the communication
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1