ID: 6824
Title: aws_s3, aws_s3_objects: New checks for AWS/S3
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
To make this check work you have to configure the related
special agent {{Amazon Web Services (AWS)}}.
ID: 6823
Title: aws_ec2, aws_ec2.cpu_util, aws_ec2.credits, aws_ec2.disk_io, aws_ec2.network_io: New checks which monitors AWS/EC2 instances
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
To make this check work you have to configure the related
special agent {{Amazon Web Services (AWS)}}.
ID: 6934
Title: cmk-update-agent: Remove unnecessary check for python interpreter
Component: agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Since Check_MK 1.5, the Agent Updater gets deployed as a binary file to
linux systems by default.
Hence it is no longer necessary to check for an available python2 interpreter
on agent installation unless the Agent Updater gets deployed as a script.
This werk adapts the agent's preinstall scripts so that no unnecessary checks are induced anymore.
ID: 6945
Title: mk_filestats: Plugin to monitor files (Count, Age, Size)
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
A new plugin is introduced with a functionality similar to fileinfo.
It reports count, size and age of sets of files specified using a
globbing pattern.
However, this plugin is designed with large filesets in mind.
It therefore provides different options to reduce the data reported to
the Check_MK server and/or to avoid unnecessary stat calls on the client.
For more information, please refer to the "--help" option of the plugin
and the example configration file in agents/cfg_examples.
ID: 6698
Title: The "Activates button" no longer cause performance issues when there are hundreds of open changes
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
If there are more than 10 changes in the WATO configuration the button simply states <tt>10+ changes</tt>,
instead of digging through the whole configuration till it gets the exact number.
ID: 6929
Title: Distributed WATO login: Protect against some config failures
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
When building up a distributed Check_MK with distributed WATO, there
are two situations which could end up in problematic situations which
are handled now in a better way:
<ul>
<li>Connecting a central Check_MK Managed Services based site to a CEE
or CRE based site resulted in a broken slave site. When trying to login
a CME site into a CEE site, an error message now prevents the login.</li>
<li>We have added a checkbox to the login dialog to confirm that one
really wants to overwrite the configuration of the remote site with the
central sites configuration.</li>
</ul>
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.