ID: 10137
Title: jolokia_jvm_memory: New check plugin
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
We introduce the new check plugin {{jolokia_jvm_memory}}. It replaces the old
memory subcheck {{mem}} and the permanent generation subcheck {{perm_gen}}
of the {{jolokia_metrics}} plugin.
In addition it features monitoring of the JVM memory pools in general;
including but not limited to "Code Cache", the legacy "Permanent Generation"
and the newer "Metaspace" pool.
If you are using the plugin {{mk_jolokia}}, you have to redeploy it in order
to get the new services. If you are using the special agent {{agent_jolokia}}
a rediscovery will suffice.
The applicable rulesets are called "JVM memory levels" and "JVM memory pool levels".
Note that rules that you have configured already will not be applied. Please revisit
the WATO page to reconfigure those rules.
Only values configured in percentage will be converted from your legacy rules -
absolute levels for the remaining *free* space are no longer considered,
as the maximum amount of available space may not be known.
Note that the performance data belonging to the "JVM MyInstance Memory" service
will be lost, even though the service name will not change.
ID: 10171
Title: Discovery: Fix triggering of discovery service after changing services
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
When editing services on the service discovery page it is intended that the
"Check_MK Discovery" service of the current host is retriggered to immediately
reflect the changes that have just been made to the service config.
This trigger was working as expected in previous 1.6.0 releases.
ID: 10172
Title: Discovery service is now correctly operating on the WATO config instead of core config
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.7.0i1
The Check_MK Discovery service needs to work with the WATO configuration world
instead of the "activated config" world. For example, if you edit the services
on the WATO service discovery page, you want the discovery service to be
updated right after editing the services in WATO.
ID: 10170
Title: BI: Fix exception in BI status GUI when loading configs created with 1.4 or older
Component: BI
Level: 1
Class: Bug fix
Version: 1.7.0i1
An exception like "unhashable type 'list'" could appear when opening BI views
while the BI configuration was created in 1.4 or older.