ID: 1400
Title: Added example notification script for Pushover to doc/treasures/notifications
Component: Notifications
Level: 2
Class: New Feature
Version: 1.2.5i6
This plugin can send notifications via pushover.net. You need to edit your keys
directly in the script. There is not yet a WATO integration.
ID: 1112
Title: esx_vsphere_hostsystem.mem_usage_cluster: allows to monitor total RAM usage of all nodes in a cluster
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i6
This check can not be inventorized. You need to create a manual check and assign it to a cluster.
The memory information of each cluster node is added to the total memory pool.
You are able to set limits for the total RAM usage depending on the number of cluster nodes.
ID: 1111
Title: vCenter monitoring: greatly improved performance (at least 40 times faster)
Component: Checks & Agents
Level: 3
Class: New Feature
Version: 1.2.5i6
The pysphere API is no longer used when monitoring ESX vCenter systems.
We are now using much simpler tools to evaluate the vCenter response instead,
thus saving quite a lot of cpu time. Depending on the number of ESX Hosts and
virtualmachines you will see a performance increase by a factor of 40-200.
<br><br>
Note:<br>
If the "Compatibility mode" is set in WATO the old "pysphere" version is still being used.
This option remains for older (<5.0) ESX versions.
ID: 1399
Title: Fix left-over tac processes when showing Event Console history
Component: Event Console
Level: 2
Class: Bug Fix
Version: 1.2.5i6
When you show the Event Console history and run into a soft or hard
query limit (of usually 1,000 or 5,000 entries), then every time one
<tt>tac</tt> process was left over. This has been fixed.
ID: 1398
Title: Allow to spread times of next check when rescheduling
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.5i6
When you do the action <i>Reschedule active checks</i> for more than one
active checks then you now can enter a number of minutes. All checks will
then be distributed evenly over that time.
This feature is interesting for checks with larger intervals. Most prominent
example is the <tt>Check_MK Inventory</tt> check, which usually is done every
2, 4 or 24 hours. By spreading the executing of these checks you avoid large
peaks in CPU load.
ID: 1110
Title: windows agent: fixed missing agent section problem if a cached script ran into a timeout
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i6
If a cache_age was set for a local or plugin script and the script ran into a timeout,
no data was reported by this script until the cache_age was expired.
This lead to missing agent sections.
ID: 1109
Title: WATO active checks: passwords no longer shown as plain text.
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i6
Password fields of active checks are now displayed as *****