ID: 8909
Title: Exclude MSSQL instances from monitoring
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The MSSQL plugin may now be configured to exclude specific
instances from the monitoring. This is achieved with an extra
section in the configuration file. The new section looks like:
[instance]
exclude = inst1,inst2,inst3
ID: 10038
Title: Fix cmk/check_mk_server:yes label related issues
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
This label was detected based on the asynchronously created agent section
'<<<omd_status>>>'. Because this section is not immediately available on the
first agent contact, this resulted in a label discovery after the second check
cycle.
Another issue was that the '<<<omd_status>>>' section was produced by non
Checkmk servers with older agent versions. This lead to a wrong label discovery.
We now use the dedicated '<<<labels>>>' section to create the label which is
produced once we find the command 'omd' on a system.
ID: 10010
Title: check_http: GUI error in case 1.5.0 config included proxy port
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
>From version 1.6.0b1 to 1.6.0b9 a GUI error was encountered when trying to
display a configuration from 1.5.0 which included a port specification in
the configured proxy address.
ID: 8959
Title: Piggybacked hosts: 'Check_MK' service shows more detailed information
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Piggybacked hosts get their data from source hosts. The source hosts save the
piggyback data to files. There's also a status file written by the source
in order to know whether the source host has sent piggyback data at all.
There may be several situations such that the piggybacked hosts cannot processed
their data:
<ul>
<li>Piggyback file is too old</li>
<li>Source is not sending piggyback data</li>
<li>Piggyback data file is not updated by source</li>
<li>Piggyback file age cannot be determined</li>
</ul>
Now the 'Check_MK' service of piggybacked hosts show these messages.
ID: 10037
Title: Some views (must search views) were always empty when added to a dashboard
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
When viewing a "search only" aka "must search view", like the host and service search
views and adding it as dashlet to a dashboard, the current search context was taken
over into the dashlet, but the view always displayed an empty list of hosts or services.
ID: 10020
Title: winperf_tcp_conn: fix for parse function of winperf tcp check
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
This is a bug fix where the wrong information was previously retrieved during the parse procedure.
ID: 10036
Title: Improve GUI page loading times
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
The config initialization, which is executed during each page access, took
longer than it needed. Especially configurations with a larger number of tag
groups and folders should be faster now.
ID: 10008
Title: mk_logwatch: acceppt '1'/'0' and 'yes'/'no' for boolean options
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
>From version 1.6.0b1 to 1.6.0b9 the boolean configuration obtions needed to be
set to 'true' or 'false', while earlier versions also allowed '1' or '0'.
mk_logwatch now understands (caseinsensitive) 'true', 'false', 'yes', 'no', '1',
and '0'.
ID: 10009
Title: mk_logwatch: Empty lines in config files are ignored entirely
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
>From version 1.6.0b1 to version 1.6.0b9 a configuration block was started
by an empty line. This beaviour was incompatible with the previous one.
mk_logwatch ignores empty lines in all configuration files.