ID: 11893
Title: mk_errpt.aix: avoid escaping issues when '/' is in errpts output
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
An unhadled '/' in errpts output lead to an completely empty logwatch subsection.
ID: 11702
Title: Monitor Postgres DBs with multiple instances on Windows and Linux
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The check "PostgreSQL Instance" supports now also multiple instances.
The agent output section "postgres_instances" contains the information for only one single instance.
The agent output format on windows switched from windows line endings to unix line endings.
ID: 11829
Title: esx_vsphere_counters_diskio: IOPS
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The check plugin <tt>esx_vsphere_counters_diskio</tt>, which
monitors the IO throughput of ESX host systems, displayed far
too low values for the rates of IO operations. This has been
fixed by using the metrics <tt>disk.numberReadAveraged</tt> and
<tt>disk.numberWriteAveraged</tt> instead of <tt>disk.numberRead</tt>
and <tt>disk.numberWrite</tt>.
ID: 11915
Title: Fix error messages on check plugin page if check or catalog entry is missing
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Missing checks of check plugins with manual page lead to an undefined error message.
If such an error occurs now, a meaningful error message is displayed.
Also, in case of missing catalog entries in the manual page, the catalog is set
to "unsorted" correctly now.
ID: 11914
Title: Remove 'Individual program call' option from connection tests page
Component: Multisite
Level: 1
Class: New feature
Version: 2.1.0i1
The option "Individual program call" has been removed from the connection test page.
This has not worked as intended since at least version 1.6 and brings more
risks in terms of security than advantages for the user.
ID: 11525
Title: lnx_if: Treat only interfaces with UP and LOWER_UP (bracket info from ip address) as UP
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Previously we only checked {{<...,UP>}} in the bracket info and treated this
interface as {{UP}} if and only if no output of ethtool is available.
Please have a look at the following scenarios and how we now determine whether
an interface is {{UP}}:
<ul>
<li>{{<BROADCAST,MULTICAST,UP,LOWER_UP>}} means that this interface has a link
and is UP</li>
<li>{{<NO-CARRIER,BROADCAST,MULTICAST,UP>}} means that this interface is
configured and ADMIN UP but has no link</li>
<li>{{<BROADCAST,MULTICAST>}} means that this interface is not configured</li>
</ul>
ID: 11744
Title: support case-insensitive hostname matching for multiple host match types
Component: Event Console
Level: 1
Class: Bug fix
Version: 2.1.0i1
Hosts are matched to events in the Event Console using different specification
methods: hostname, IP address, and host alias. In the event that multiple
specification methods are used to query events, livestatus queries did not
return events for hosts if the letter casing was inconsistent. This was caused
by two mechanisms:
- Preliminary filters that determine whether livestatus queries need to be
performed
- Host matching criteria that returned negative results
This defect becomes evident when the check_mkevents Active Check is used to
monitor events, and multiple items in the "Match the hosts with" option are
selected ("Check event state in Event Console" ruleset). In this case, the
check will return fewer events than are expected.
The livestatus query now supports case-insensitive host/event matching. Please
be advised that this fix may result in larger volumes of matched events.
Therefore, we advise users to evaluate the implications of this fix prior to
installation.
ID: 11916
Title: Fix adding of graphs to custom graphs or graph collections
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Adding of graphs to custom graphs or graph collections was not possible on some
browser. Furthermore, if you added a graph to custom graphs, the landing page
was not the edit page of the custom graph.
Both issues have been fixed.
ID: 11833
Title: Pagerduty notifications: HTTP 400, "'payload.source' is missing or blank"
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.1.0i1
For hosts without an IP address, the pagerduty notification plugin failed with
HTTP 400 (Bad Request), "'payload.source' is missing or blank"
This has been fixed.