ID: 7227
Title: Fixed liveproxy activating errors confusing site related web API calls
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
Unclean error handling could make site management related web API calls like set_all_sites
fail because an ASCII error message was sent back as result to the API call instead of
the expected JSON data structure.
ID: 7205
Title: jolokia_jvm_threading: new check for JVM threads
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
The new check jolokia_jvm_threading is introduced. It creates the services
"JVM <instance> Threading" and optionally "JVM <instance> ThreadPool <pool name>",
replacing the former checks jolokia_metrics.threads and jolokia_metrics.tp.
The new "JVM Threading" check now allows to set rules on the thread count as well as on
the rate at which new threads are created. Additionally levels for the daemon threads
can be configured.
Unlike for the old check 'jolokia_metrics.threads', no default levels are imposed
on the thread count.
Users who had a rule in place for the ThreadCount metric of the old check
need to set up a new rule "JVM threading".
The "JVM ThreadPool" check applies the same rule as the previous check did.
A rediscovery is required for affected hosts.
ID: 6762
Title: zfsget: Fixed different behaviour of the plugin in Solaris and Linux
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Previously the implementation of getting zfs information was slightly
different in Linux and Solaris. Now both agents are fetching data only for
volumes and filesystems and are using the quota for computing the total size of
a filesystem or volume. So the information of each service will be more precise.
ID: 7111
Title: aix_hacmp_services: Fixed parsing of unexpected line 'The cthags Subsystem is not on file'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
ID: 7110
Title: aix_hacmp_resources: If there's no cluster definition we do not discover services
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
ID: 7226
Title: LXC: Add basic support for Linux containers
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.6.0i1
The agent is now detecting when it is executed in a Linux container
context and changes it's behaviour depending the environment.
In containers the agent currently does the following:
<ul>
<li>lxc_container_cpu: This check is used instead of the normal CPU
utilization check</li>
<li>zfs filesystems are not excluded for the df section anymore</li>
<li>kernel section is not processed, because it's the host systems
kernel the agent reports information for</li>
<li>drbd section is not processed for the same reason</li>
<li>lnx_thermal section is not processed for the same reason</li>
</ul>
ID: 7062
Title: Improvement of the graphing with PNP4Nagios for various checks
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
When PNP4Nagios is used Check_MK tries to use autogenerated graph templates
to paint the graphs of a check. If the capabilities for Check_MKs autogeneration
of graph templates is insufficient Check_MK provides a fallback to handcrafted
templates.
This werk extends the capabilities of Check_MKs autogeneration of PNP templates
and makes a lot of handcrafted PNP templates unnecessary. Therefore, these
templates are removed. This results in an overall more pleasant and uniform
graphing.
PNP4Nagios is used if the raw edition is used or if the enterprise edition is
used together with the Nagios core.
ID: 7105
Title: Check API: Make usage of dsname, unit, human_readable_func and infoname in check_levels clearer
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Previously the dsname was also used as title if and only if the infoname was not stated.
Therewith we got cryptic and not readable titles. The dsname should only be used for
performance data variables.
Sometimes a title is not needed because the service description already gives the
relevant information; especially in check plugins where there is just one {{thing}}
to check, eg. in CPU services:
Previously: CPU utilization OK - CPU utilization: 23.5%
Now: CPU utilization OK - 23.5%
In general the structure is as following:
<ul>
<li>If the infoname is specified the service detail is prefixed with this infoname as a title "TITLE: "</li>
<li>If a human_readable_func is given the value and levels are converted with this function</li>
<li>If a unit is given it is append to the value and each level.</li>
</ul>
Be aware:
Every builtin human_readable_func already provides a unit. Thus the unit is not needed in general.
There may be situations where a human_readable_func which provides a unit AND an additional unit info
is useful, eg. when a bytes rate is calculated. In this case the service details should display
"23.5 B/s" whereby
C+
unit="/s",
human_readable_func=get_bytes_human_readable,
C-
If you use this API function {{check_levels}} in your check plugins you possibly
need to adapt your check plugin functions. Otherwise duplicate unit infos may be
displayed or there are missing titles ({{infoname}}).
ID: 7224
Title: Backup/Restore: Fix vanishing files terminating a backup
Component: Site Management
Level: 2
Class: Bug fix
Version: 1.6.0i1
The "omd backup" mechanism recursively backups all site related
files of a Check_MK site. When files in a site directory, that
is currently being processed vanish, this could lead to failed
backups with errors like this:
C+:
Site backup failed: Traceback (most recent call last):
File "/omd/versions/1.5.0p8.cee/bin/omd", line 4553, in
command_function(args, command_options)
File "/omd/versions/1.5.0p8.cee/bin/omd", line 3711, in main_backup
backup_site_to_tarfile(fh, tar_mode, options)
File "/omd/versions/1.5.0p8.cee/bin/omd", line 3686, in backup_site_to_tarfile
backup_site_files_to_tarfile(tar, options)
File "/omd/versions/1.5.0p8.cee/bin/omd", line 3556, in backup_site_files_to_tarfile
tar.add(g_sitedir, g_sitename, exclude=filter_files)
File "/omd/versions/1.5.0p8.cee/lib/python2.7/tarfile.py", line 2032, in add
recursive, exclude, filter)
File "/omd/versions/1.5.0p8.cee/lib/python2.7/tarfile.py", line 2032, in add
recursive, exclude, filter)
File "/omd/versions/1.5.0p8.cee/lib/python2.7/tarfile.py", line 2032, in add
recursive, exclude, filter)
File "/omd/versions/1.5.0p8.cee/lib/python2.7/tarfile.py", line 2032, in add
recursive, exclude, filter)
File "/omd/versions/1.5.0p8.cee/lib/python2.7/tarfile.py", line 2032, in add
recursive, exclude, filter)
File "/omd/versions/1.5.0p8.cee/lib/python2.7/tarfile.py", line 2009, in add
tarinfo = self.gettarinfo(name, arcname)
File "/omd/versions/1.5.0p8.cee/lib/python2.7/tarfile.py", line 1881, in gettarinfo
statres = os.lstat(name)
OSError: [Errno 2] No such file or directory: '/omd/sites/xyz/var/pnp4nagios/perfdata/hastenichgesehn/Interface_BG4_2OG_VLAN_421.xml.new'
C-:
After this change the backup continues in such a situation
excluding the just vanished file.