ID: 6920
Title: HTTP proxies can now be configured globally
Component: Core & setup
Level: 2
Class: New feature
Version: 1.6.0i1
To enable components to connect to external resources in proxied networks
more easily it is now possible to configure several HTTP proxies using the
global setting "HTTP proxies".
Imagine a scenario where your monitoring server is located in your company
internal network and you need to make a connection to a external HTTP server
in the internet while you can only connect to this server using a proxy server.
In the past the most spread option is to set the HTTP(S)_PROXY environment
variables for such a call and hope that the program you use for the connection
supports these envrionment variables.
Now it is possible to configure the proxies using the GUI in a central place
and refer to these settings from different parts of your configuration.
These proxies will be usable by e.g. special agents, notification scripts and
active checks, which need to use a proxy for their work.
As example the pushover notification script has been migrated to support the
global proxy settings.
Note to notification script developers: You have to name the
notification proxy element of the Dictionary parameters valuespec
"proxy_url" to make it work as expected with globally configured
proxies.
Note to special agent and active check developers: There is a new
function available get_http_proxy(http_proxy). Pass the
"http_proxy" value a user configured using the HTTPProxyReference
valuespec to this function an you will get back the proxy URL as string
or None in case no proxy should be set via command line (see "pydoc
cmk_base.check_api.get_http_proxy_for_cmdline" for further information).
CMK-1407
ID: 6933
Title: Always include xinetd configuration file to .tgz packages
Component: agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Due to a bug in the packaging routine within the agent bakery, the Check_MK-Agent
xinetd configuration file wouldn't be included into .tgz packages.
This error occured when using the plugin "Installation paths for agent files"
while having no configured path starting with <code>/etc</code>.
The xinetd configuration file under <code>/etc/xinetd.d/</code> will now be included as intended,
regardless of the paths configured at the "Installation paths for agent files" ruleset.
ID: 6697
Title: BI aggregations: Fix incorrect warning message when checking for unique title
Component: BI
Level: 1
Class: Bug fix
Version: 1.6.0i1
It was not possible to configure two identical BI aggregations with different aggregation groups.
You had to configure one aggregation, which includes both groups.
ID: 6865
Title: Windows Agent's fileinfo section produces correct output
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Previously, fileinfo section may contain invalid data, usually nulls.
With the fix this section works as intended and sends to the output correct
file information.
ID: 6822
Title: fsc_if64: Remove this check plugin in order to improve performance
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Some FSC devices report the operational status and type of the interfaces as a
human readable string. As defined in the IF-MIB Check_MK expects the values
ifOperStatus and ifType in SNMP syntax.
The check plugin {{fsc_if64}} was create just for converting these values. One
side effect was that all needed OIDs were fetched two times:
<ul>
<li>for the fsc_if64 check plugin and</li>
<li>for the if64 check plugin as well.</li>
</ul>
Thus fsc_if64 is deprecated now and human readable strings for operational
status and type are handled by if64 for ALL devices.
ID: 6927
Title: MAC OS X agent: Fixed missing root filesystem when using apfs
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
OS X systems since 10.13 High Sierra can format disks using APFS. The
OS X agent was only reporting hfs filesystems in the past. This lead
to e.g. a missing root filesystem on newer OS X installations.
ID: 6923
Title: Parent scan is now based on the background job logic
Component: WATO
Level: 1
Class: New feature
Version: 1.6.0i1
The parent scan is no longer affected by GUI timeouts because it is executed in a
background job. The progress dialog is now based on the generic background job
handling. The execution logic of the parent scan hasn't changed.
ID: 6964
Title: Fixed matching of literal strings when C++11 regex engine is used.
Component: Livestatus
Level: 2
Class: Bug fix
Version: 1.6.0i1
Livestatus and CMC can use one of two regex engines: Either then one from
the C++11 standard library or the one from the RE2 library. Normal builds
ship the latter, only a manually built Livestatus should ever use the
former. Nevertheless, both should work, but the C++11 variant had a quoting
bug, resulting in incorrect matching. This has been fixed.