ID: 0973
Title: Renaming of hosts via WATO
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.5i3
WATO has now a new function <i>Rename Host</i>. You will find a button with that name
in the Properties of a host. It allows a renaming of an existing host. Before you
can use that feature you need to have all changes activated, so nothing is pending.
Renaming a host is a complex precedure that will not only rename the host in WATO,
but also in:
<ul>
<li>all rules from <i>Host & Service Parameters</i></li>
<li>cluster's node definitions</li>
<li>a host's parent definitions</li>
<li>Business Intelligence rules</li>
<li>notification rules (both rule based and flexible notifications)</li>
<li>internal Check_MK data like caches and performance counters</li>
<li>auto-disovered services of the host</li>
<li>logfile information of logwatch plugin</li>
<li>stored SNMP walks</li>
<li>RR databases with performance data</li>
<li>RRD updates in journal of RRD Cache</li>
<li>spool files of PNP4Nagios</li>
<li>NagVis maps</li>
<li>monitoring history entries (events and availability)</li>
<li>the current monitoring state (including ackowledgements and downtimes)</li>
</ul>
Please note that renaming of a host involves a temporary stop of the monitoring
core. This is neccessary in order to avoid situation where the old and the new
name of a host is being used at the same time.
ID: 2717
Title: Fixed broken webserver level authentication integration (e.g. basic, kerberos)
Component: Multisite
Level: 2
Class: Bug Fix
Version: 1.2.7i4
Fixed a regression which broke the integration of the Check_MK GUI into an authentication
which is done by the web server. This is for example a basic or kerberos authentication.
ID: 2670
Title: Fix problem that no site is configured when user has deleted only site
Component: Multisite
Level: 2
Class: Bug Fix
Version: 1.2.7i4
This problem was introduced by dropping the "single site" mode internally totally
in version 1.2.7i3 and treating a single site setup automatically as multi site
setup with just one site. The problem occurred when you had <tt>sites = {}</tt>
in your configuration (instead of having no <tt>sites = </tt> at all).
ID: 2713
Title: New bookmark lists, strucutrable and shareable between users
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i4
The bookmark sidebar snapin has been extended to be structurable into
topics. Each bookmark can now be put into a topic which can then be
expanded or closed in the GUI.
It is now possible to group bookmarks together in multiple bookmark
lists. These lists can be made available to other users, just like
views, dashboards, reports and graph collections.
The summary of all bookmark lists a user can access is grouped together
in the bookmark snapin and shown to the user as one single list of
bookmarks.
ID: 2683
Title: Fixed exceptions occuring in some ps checks
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i4
An exception like "'int' object is not iterable" could occur during execution of the ps checks.
ID: 2682
Title: Fixed exception Error creating configuration: global name 'extra_host_attributes' is not defined
Component: Core & Setup
Level: 2
Class: Bug Fix
Version: 1.2.7i4
ID: 2681
Title: LDAP: Added support for synchronizing with multiple LDAPs
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i3
It is now possible to configure Check_MK to synchronize with multiple
LDAP directories at the same time. Users and groups can be fetched
from different independent LDAP servers.
ID: 2434
Title: NetApp monitoring: Cluster-Mode is now supported, changes in existing 7Mode checks
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i4
This update enables to monitor NetApp Filers running in Cluster-Mode.
The new <i>agent_netapp</i> is able to automatically detect whether the filer
is running in 7Mode or Cluster-Mode, so you only have to configure the
credentials in the datasource rule as usual.
Some of the existing 7Mode checks have been adjusted. Overall there are now less summary
checks available (e.g. fan, temperature, psu). You need to do a service discovery on each NetApp filer.
The following table shows the list of available checks and the currently
supported NetApp mode.
<table>
<tr><th>Check</th><th>Description</th><th>7Mode</th><th>Cluster-Mode</th></tr>
<tr> <td>netapp_api_aggr</td> <td>Used space and trend of aggregations</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_volumes</td> <td>Used space an trend of volumes. Able to record detailed performance data for each protocol</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_info</td> <td>Displays NetApp version</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_cpu</td> <td>CPU utilization of nodes</td> <td></td> <td>X</td></tr>
<tr> <td>netapp_api_cpu.utilization</td> <td>CPU utilization for 7Mode filer</td> <td>X</td> <td></td></tr>
<tr> <td>netapp_api_cluster</td> <td>Cluster status</td> <td>X</td> <td></td></tr>
<tr> <td>netapp_api_cpu.nvram_bat</td> <td>NVRAM battery status</td> <td></td> <td>X</td></tr>
<tr> <td>netapp_api_disk.summary</td> <td>Disk summary check. Includes total raw capacity and info about broken/spare ratio</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_fcp</td> <td>Fibrechannel interfaces traffic and latency</td> <td></td> <td>X</td></tr>
<tr> <td>netapp_api_if</td> <td>Ethernet interfaces</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_protocol</td> <td>Read OPS / Write OPS for each protocol (nfs, nfsv4, cifs, fcp, iscsci)</td> <td>X</td> <td></td></tr>
<tr> <td>netapp_api_temp</td> <td>Temperature sensors, grouped by shelf</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_psu</td> <td>Power supplies</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_fan</td> <td>Fan status</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_snapvault</td> <td>Snapvault Lag-time</td> <td>X</td> <td></td></tr>
<tr> <td>netapp_api_status</td> <td>Diagnosis status</td> <td>X</td> <td>X</td></tr>
<tr> <td>netapp_api_vf_stats.traffic</td> <td>vFiler traffic (Read/Write OPS, Net-Data Send/Recv, Read/Write Bytes)</td> <td>X</td> <td></td></tr>
<tr> <td>netapp_api_vf_stats</td> <td>CPU utilization of vFilers</td> <td>X</td> <td></td></tr>
<tr> <td>netapp_api_vf_status</td> <td>vFiler status, e.g running</td> <td>X</td> <td></td></tr>
<tr> <td>netapp_api_vs_status</td> <td>vServer status, e.g running</td> <td></td> <td>X</td></tr>
<tr> <td>netapp_api_vs_traffic</td> <td>vServer Traffic Summary</td> <td></td> <td>X</td></tr>
</table>
ID: 2660
Title: fixed windows agent using the wrong working directory
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i4
The windows agent in the recent releases, when started as a service fell back to using the current
working directory when started as a service. For a service this is c:/windows/system32
ID: 2659
Title: Added IPv6 support to the windows agent
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i3
added support for connecting to the windows agent via IPv6.
This support is active by default and can be disabled via configuration file.