ID: 2137
Title: diskstat: new implementation of Linux Disk IO check
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
The <tt>diskstat</tt> check for Linux has been reimplemented from scratch. It now
gets much more specific metrics information like average wait time, IO queue length,
latency, IOs per seconds und more. Six graphs are being created.
Note: this check is new parametrized by a new rule set in WATO. You need to
redo your configuration of this check, sorry. Also if you have a very old legacy
setup with two seperate checks for read and write, you also need to rediscover.
These checks are not longer supported.
ID: 2057
Title: New checks for postgreSQL monitoring
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
With this update the agent plugin <i>mk_postgres</i> now reports
additional information, which will be processed by these new checks:
<table>
<tr><th>Check</th><th>Description</th><th>Limit configurable</th></tr>
<tr><td>postgres_bloat</td><td>Shows size of table and index bloat</td><td>X</td></tr>
<tr><td>postgres_conn_time</td><td>Time to connect to database</td><td></td></tr>
<tr><td>postgres_connections</td><td>Number of connections to database</td><td>X</td></tr>
<tr><td>postgres_locks</td><td>Number of ShareAccess and ExclusiveLocks</td><td>X</td></tr>
<tr><td>postgres_query_duration</td><td>Displays longest running query</td><td></td></tr>
<tr><td>postgres_stats</td><td>Time of last VACUUM and ANALYZE</td><td>X</td></tr>
<tr><td>postgres_version</td><td>Displays PostgreSQL version</td><td></td></tr>
</table>
Note: You have to update the agent plugin <i>mk_postgres</i> on the target host.
ID: 2136
Title: Unify headers of Host/Service rules, EC rules and notification rules
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i1
All three types of rules now have a common header with description,
command and documentation URL. The section has been renamed from <i>General
Properties</i> or <i>Additional options</i> to <i>Rule Properties</i>. In
the host and service rules the existing comment information is being used as
description if the description is empty. This is in order to be compatible
with the existing configuration where no description field existed.
ID: 2100
Title: if64: check can now impose limits on the number of outgoing and incoming non-unicast packets per second
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
ID: 2041
Title: Notification Spooler can now handle incoming and outgoing persistent TCP connections
Component: Notifications
Level: 2
Class: New Feature
Version: 1.2.7i1
The Check_MK Notification Spooler (<tt>mknotifyd</tt>) has completely been rewritten. It
now:
<ul>
<li>uses persistent TCP connections instead of connecting for each notifiction</li>
<li>can use outgoing TCP connections for <i>receiving</i> notifictions</li>
<li>can handle an arbitrary number of parallel connctions</li>
<li>monitors connections with heart beats</li>
<li>is being monitored by two new checks for the general state and for each connection</li>
</ul>
The global configuration for the spooler has changed. Your existing settings
are still supported but have vanished from WATO. As soon as you create a
new configuration that will override your legacy configuration.
The new checks that monitor the spooler require an update of the Check_MK
Agent for Linux on the Check_MK server. It needs OMD based installaions
paths. All spoolers will automatically be discovered. The new checks are
<tt>mknotifyd</tt> and <tt>mknotifyd.connection</tt>.
The spooler write messages into <tt>var/log/mknotifyd.log</tt>. There are
three log levels, which can be configured in the global settings of the
spooler. We propose starting with the highest log level. Also a file
<tt>var/log/mknotifyd.log</tt> is being written every 20 seconds. It
shows the state of the spooler and its connections. This is being used
for the monitoring of the spooler.
ID: 2045
Title: Avoid fetching SNMP data when showing service list in WATO - unless Full Scan is pressed
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.7i1
ID: 2042
Title: Services are now sorted in a natural way, this affects services containing numbers
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i1
Previously services would be sorted alphabetically, e.g. <tt>foo1</tt>,
<tt>foo10</tt>, <tt>foo11</tt>, ... <tt>foo2</tt>, <tt>foo3</tt>, etc.
Now numbers within the descriptions are being detected by a smart algorithm
and the sorting is then <tt>foo1</tt>, <tt>foo2</tt>, ... , <tt>foo9</tt>,
<tt>foo10</tt>, <tt>foo11</tt>, just as you would expect.
ID: 2052
Title: winperf_if: Now able to automatically group teamed interfaces and more
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
The winperf_if check is now able to detect teamed interfaces.
This information is provided by the updated wmic_if.ps1 plugin.
Right now, the teamed interfaces are no longer listed separately.
There will be a configuration option soon which allows you to configure
this behaviour.
H2: Incompatible change
The service descriptions for this check did never show the human
readable/editable interface name - the <i>NetConnectionID</i>.
This has been fixed. This information is now provided in the alias information
of each interface.<br>
If you have used the configuration option <tt>if_inventory_uses_alias</tt>, the
interface will now have a different name. Therefore the service description changes
and the performance data will get lost.<br>
A workaround for this problem is to use <tt>if_inventory_uses_description</tt> instead....
For windows hosts the settings <tt>if_inventory_uses_alias</tt> and <tt>if_inventory_uses_description</tt>
meant the same in previous version. With this update the meaning of <tt>if_inventory_uses_alias</tt> has changed.
ID: 2083
Title: Added Siemens PLC (SPS) monitoring
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
We added a special agent {agent_siemens_plc} which is using SNAP7 to fetch
data from a Siemens PLC (SPS) device. You can use it do read memory areas
from the agent, parse and interpret them, for example you can configure
to read and integer from memory location X and handle it as temperature
value in celsius.
For the moment we added a temperature check, others will follow.
ID: 2022
Title: SNMP: Fixed handling of backslashes in SNMP data
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i1
Some checks like the hr_fs checks e.g. create services with
backslashes in the service descriptions when monitoring
windows filesystems. Those services were named "Filesystem c:\\..."
for example, which was using a double backslash which is wrong.
This behaviour has now been changed to just use a single slash.
With this change your services will be reported as UNKNOWN when
you have such services with double backslashes in their names.
You will then need to rediscover the services to get them with
just a single slash. If you like to keep the performance graph
history, you will need to migrate them on your own.