ID: 2918
Title: agent_jolokia: jolokia can now be monitored using a special agent
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
ID: 2882
Title: Reorganize BI configuration into packs, add contacts and permissions
Component: BI
Level: 2
Class: New Feature
Version: 1.2.7i4
The WATO module for configuring Business Intelligence (BI) has been
reorganized. The configuration is now split up into <b>Packs</b>. This has
been made for two reasons:
LI:It makes the configuration of large BI environments easier
LI:It allows to delegate BI configuration to normal users
Each pack contains rules and aggregations. A rule or aggregation in one pack
<b>can</b> refer to rules in another pack.
Each BI pack can have a list of contact groups. A new permission has been
introduced: <i>Business Intelligence Rules and Aggregations</i>. Per default
this is set for normal users. It allows a normal user to configure rules
and aggregations in a BI pack if that user is in one of the listed contact
groups of that pack.
A pack can have the checkbox <i>Allow all users to refer to rules contained
in this pack</i> set. That way a user can use rule from a pack where he is
not a contact for. So the admin can put some basic rules there that can be
used but not changed by other.
Your existing BI configuration will automatically be converted the next
time you use the WATO Bi modul. All existing rules and aggregations will
be put in to one BI pack with the name <i>Default Pack</i>.
ID: 2890
Title: cisco_nexus_cpu, cisco_oldcpu: new checks for Cisco devices which do not support CPU utilization information from CISCO PROCESS MIB
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i4
ID: 2889
Title: snmp_extended_info: new inventory function which discovers the model name and serial number
Component: HW/SW-Inventory
Level: 1
Class: New Feature
Version: 1.2.7i4
The information about model name and serial number is discovered on all SNMP devices on which
the OIDs "1.3.6.1.2.1.47.1.1.1.1.4.1" or "1.3.6.1.2.1.47.1.1.1.1.4.1001" have value zero.
This means the device itself.
ID: 2901
Title: Fixed issue editing availability annotations
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.7i4
Fixed a possible "Internal Server Error" when trying to edit annotations of
the Check_MK Availability which contains special characters in the text.
ID: 2825
Title: Parameter overview page no longer raises an exception in certain scenarios
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.7i4
The parameter overview page raised an exception when the host in question never
got a service discovery and had an active check configured.
It also crashed for any "Classical active and passive Monitoring checks" check
with configured rule options, e.g a comment was set or the rule was deactivated.
ID: 2900
Title: Bulk Host import can now handle CSV files including several host attributes
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i4
The Bulk Host Import feature of WATO could be used for importing a list of host names
before. But more complex imports like adding hosts together with a collection of initial
attributes was not possible.
The import has now been extended that one can upload whole CSV files or paste the contents
of a CSV file into a form. Then, after the upload, a preview page is displayed to configure
the parameters how to parse the CSV file and which column to assign to which host attribute.
ID: 2917
Title: cisco_asa_failover: Will no longer discover on devices where failover is disabled
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i4
If failover is disabled on a device, both primary and secondary units are reported as "down".
check_mk reported a warning for that even though there was no problem.
This change requires re-inventory of the affected devices.
ID: 2899
Title: ps: Finally improved performance impact of perfdata when having a lot of processes
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i4
When having a lot of processes, like several thousands, on a system and monitoring them,
this lead to a lot of performance counters being created in Check_MK. The management of
these counters was not very optimal, because not updated counters were only deleted based
on time. So systems with a lot of process creations were handling many non needed counters
during every check interval. This affected CPU and memory usage during checking such systems.
As we get the full process table, we have now changed the logic to automatically delete the
counters of all processes that are not existant anymore. This reduces the number of counters
significantly.