ID: 10872
Title: agent_vsphere: Removed ESX 4.1 compatibility mode
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 1.7.0i1
The ESX 4.1 compatibility mode of the ESX vSphere special agent has been
removed. This separate implementation, which was based on the pysphere python
API, was outdated, much slower and missed several features of the current ESX
vSphere special agent.
In case you still need this, you may have to setup a separate site which uses
the old special agent to collect the needed information.
ID: 10750
Title: Reduce long waiting times for some users when loading sites
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
If users are only allowed to see folders for which they have
permissions i.e. if the Global Setting "Hide folders without
read permissions" is activated, some sites like e.g. the
notifications of a user could cause long waiting times. The
problem occured especially when users are only allowed to
see the lowest folder level. In some rare cases users could
even run into a GUI timeout.
ID: 10775
Title: Fix netapp_api_fcp pending status for inactive ports
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Inactive ports have no increasing number of operations and thus latency
can't be calculated according to NetApp's Performance Management Design
Guide as it depends on the increase in number of operations.
Now this check does not deliver information nor perfdata about latency when
the port is inactive.
ID: 10909
Title: New notification plugin for Cisco Webex Teams
Component: Notifications
Level: 1
Class: New feature
Version: 1.7.0i1
This werk enables Check_MK to send notifications about changes
in the states of hosts and services to Cisco Webex Teams (both
spaces and teams).
First, you need to setup a webhook to your team or space, see
<a href="https://apphub.webex.com/teams/applications/incoming-webhooks-cisco-systems" target="_blank">here</a>,
which will allow Check_MK to post messages. Next, in Check_MK,
under "WATO - Notifications", create a new notification rule.
Select "Cisco Webex Teams" as the notification method. Copy the
URL of your webhook into the Webhook-URL field. Optionally, if
you want sent messages to include hyperlinks to Check_MK, enable
the field "URL prefix for links to Check_MK".
ID: 10909
Title: New notification plugin for Cisco Webex Teams
Component: Notifications
Level: 1
Class: New feature
Version: 1.7.0i1
This werk enables Check_MK to send notifications about changes
in the states of hosts and services to Cisco Webex Teams (both
spaces and teams).
First, you need to setup a webhook to your team or space, see
<a href="https://apphub.webex.com/teams/applications/incoming-webhooks-cisco-systems" target="_blank">here</a>,
which will allow Check_MK to post messages. Next, in Check_MK,
under "WATO - Notifications", create a new notification rule.
Select "Cisco Webex Teams" as the notification method. Copy the
URL of your webhook into the Webhook-URL field. Optionally, if
you want sent messages to include hyperlinks to Check_MK, enable
the field "URL prefix for links to Check_MK".
ID: 10749
Title: IBM MQ: new agent plugin, checks, and inventory plugins
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This werk introduces the new agent plugin ibm_mq along
with check and inventory plugins to monitor the Managers,
Channels, and Queues of IBM MQ.
Thanks to the Swisscom and Daniel Steinmann for the
contribution.
ID: 10868
Title: Tags: Custom "Agent type" tag group cleanup is now easier
Component: WATO
Level: 2
Class: Bug fix
Version: 1.7.0i1
Werk #5535 introduced with Checkmk moved the "Agent type" tag group from
a tag group that could be customized to a builtin tag group.
In case you have modified it in any way, the tag group could not be migrated
manually. In this situation the new builtin tag choices have been added to
the tag group and the titles of the previously existing tag choices have been
prefixed with "Legacy: ".
To perform the cleanup now you have to perform the following steps:
<ul>
<li>Remove all tag choices except <tt>cmk-agent</tt>, <tt>all-agents</tt>,
<tt>special-agents</tt> and <tt>no-agent</tt>.</li>
<li>Then you can try to delete the tag group.</li>
</ul>
If you have prepared the tag group as mentioned in the first step, the second
step should result in a message "Cleaned up user tag group to builtin". The
tag group is visible as "(builtin)" tag group.
ID: 10532
Title: CMC parallelize config generation ON: fixed randomly vanishing services
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.7.0i1
When using the <tt>Parallelize core config creation feature</tt> option (defaults to ON), there was
a risk of losing services in the configuration. The risk was increased when the system had lots of CPUs
and a low number of hosts and services.
ID: 10919
Title: apc_symmetra_drycontact: New check plugin to monitor APC dry contact sensors
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
A check to monitor dry contact sensors.
OPEN state is Normal.
CLOSE state is Critical.
ID: 10908
Title: snmp_uptime: Fix crash for some Fortigate devices
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Users experienced crashes of uptime checks with some Fortigate devices. This is because
the data delivered by these devices does not contain any timestamps. As a solution, the
uptime check will not be discovered any more if the delivered data cannot be interpreted
as a timestamp. To apply this fix, users have to re-discover the services of the
corresponding hosts.