ID: 2103
Title: mbg_lantime_ng_temp: levels were not working
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i1
please redo a service discovery to get a new service description for the
service on your device
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: 1228
Title: Linux Agent: Now supports systemd
Component: Core & Setup
Level: 1
Class: New Feature
Version: 1.2.7i1
The Check_MK Linux Agent installation packet now supports systemd based systems.
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: 2135
Title: Allow to filter notification contacts based on values of custom macros
Component: Notifications
Level: 1
Class: New Feature
Version: 1.2.7i1
You can now use custom user attributes (macros) for deciding which users should
be notified. For that purpose there is a new check box in the contact selection
of the rule based notifications called <i>Restrict by custom macros</i>.
Here you can specify the name of custom macros and regular expressions for
the allowed values. Users whose macros do not match are being removed from
the list of contacts. Note: You first need to select contacts, the options
just <i>removes</i> contacts, never adds ones.
Custom user attributes can be defined WATO's users module. Please make
sure that you add your macros to the monitoring configuration by selecting
<i>Make this variable available in notifications</i>.
ID: 2134
Title: winperf_phydisk: allow device to appear more than one time in agent output
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i1
This can e.g. be the case in Windows clusters, where the drive letter <tt>E:</tt> appears
three times. The check now adds up all counters of the three devices - just like in the
summary check.
ID: 2133
Title: Fix visualization of global EC setting for Rule Optimizer
Component: Event Console
Level: 1
Class: Bug Fix
Version: 1.2.7i1
The toggle-button for the setting <i>Optimize rule execution</i> did not
show the current setting, but alwas showed <i>on</i>. This has been fixed.