ID: 10875
Title: Services: Escape service details equal to status views
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
The service details (aka plugin output) was escaped in an unusual way
on the service discovery page. It allowed some tags to be rendered
without escaping (internally known as permissive encoding).
Even if it was not really problematic, at least it confused users. So now the
escaping is done the same way as in the status views.
ID: 10946
Title: jira_issues: Fixed possible multiple creation of issues
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
If the same Host/Service ID occurs, e.g. if you replay a notification, an issue
for the same problem could be created again. This has been fixed.
ID: 10945
Title: jira_issues: Fixed possible UnicodeEncodeError
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
If error messages contain non ASCII characters, the notification plugin failed
with an UnicodeEncodeError. This has been fixed.
ID: 10951
Title: fortigate_sslvpn: Addition of WATO configuration option for number of tunnels
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This change introduces the option to configure a WATO configuration
for the number of active vpn tunnels.
ID: 10938
Title: agent_rabbitmq, rabbitmq_cluster, rabbitmq_queues: New special agent and checks to monitor RabbitMQ
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
It is now possible to monitor your RabbitMQ clusters with checkmk. If you
configure the datasource rule "Check state of RabbitMQ", you can monitor
clusterwide, detailed node, queue and vhost statistics.
ID: 10955
Title: Monitoring of the number of users for Pulse Secure
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This werk introduces a new check to monitor the number of
signed-in web users for Pulse Secure via SNMP.
ID: 10601
Title: Auto migration of check plugins to new section definitions
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
We are now converting all plugins in the share/check_mk/checks
and local/share/check_mk/checks to the new format expected by
the future API. Although we are trying to migrate as many check
plugins as possible on the fly, for some plugins this may fail.
These are the anticipated reasons why auto-migration may fail:
<h4>A complex SNMP scan function</h4>
If Checkmk fails to auto-migrate a legacy SNMP plugin to a section
definition, this is most likely due to an elaborate scan function.
For the auto-migration to work, the scan function must be fairly
simple. Make sure your scan function has the following properties:
<ul>
<li>it only consists of one single return statement</li>
<li>it does not in turn call other functions (not even 'all' or 'any')</li>
<li>it does not negate compound expressions</li>
</ul>
If in doubt, take a look at scan functions that succeed to be migrated
to see what options are available.
ID: 10691
Title: mk_logwatch supports UTF-16 LE BOM encoded files
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Since this release mk_logwatch is able to process files encoded with UTF-16LE.
Those files must have correct byte order mark(BOM).
This type of encoding is used usually by Windows software.
ID: 10690
Title: mk_logwatch supports single backslash in Windows paths
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
In previous versions it was needed to escape backslashes with another backslash.
This has been cleaned up now. You could leave your configuration untouched and
it still works as before.
In a rare case, if your configuration contains double escaped backslashes, i.e
"\\\\" or even "\\\\\\", this change will result in one old service being removed
and one new services being discovered. For example, the service "LOG C:\\\\Back\\test.log"
previously discovered as "LOG C:\\Back\test.log" will be discovered now as
"LOG C:\Back\test.log". In this case you will have to rediscover the related Log
services on your hosts.
We recommend finding and replacing the escaped backslashes (if any) with plain
backslash "\" for better usability. You do not need to rediscover services again.
In case you have configured "Logwatch to Event Console forwarding", you may have to
update your forwarding and Event Console rules to match the new log path.