ID: 2987
Title: esx_vsphere_counters: Improved accuracy of all counter values
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i4
In the previous versions the esx_vsphere_counter checks only got
the last real time sample from the ESX system, which always represents
a fixed interval of 20 seconds.<br>
With this update the agent vsphere now queries the last n-samples.
The number of samples is determined out of the agents check interval.<br>
Some of the counter checks have been rewritten to handle the increased
amount of data. Most of the values are simply processed to an average value,
with the expection of the latency, which uses the maximum value.
ID: 3040
Title: Removed all summary_hosts related filters from shipped views
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.7i4
The so called summary hosts which were only rarely used is a feature we are about to deprecate
in the coming 1.2.9 release. As preparation for this we are now removing the hard coded default
filters from the views shipped with Check_MK.
We assume that nearly no users will be affected from this since most users simply don't have
any summary host defined. If you have summary hosts configured you are requested to migrate
your configuration. To make the views work again, most of them were filtering out the summary
hosts, you need to add this filter again on your own to the view by editing it with the view
editor.
ID: 3039
Title: Added more useful debugging infos to crash reports
Component: Core & Setup
Level: 1
Class: New Feature
Version: 1.2.7i4
We added the following generic infos to all crash reports:
- Python version
- Local variables of crash raising function
This has been added to GUI crashes:
- Request method (POST/GET)
- Page referer
ID: 2942
Title: juniper_cpu_util: new check replaces juniper_cpu which was reporting incorrect values
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i4
The juniper_cpu check was reporting cpu load as utilization. The load readings from the
juniper device can't be used as the number of cpu cores is unknown.
juniper_cpu has been obsoleted, will no longer report data and will disappear upon
re-discovery.
juniper_cpu_util takes its place and reports the actual utilization.