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: 2371
Title: appdynamics_memory, appdynamics_sessions, appdynamics_web_container: New checks for AppDynamic
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i3
Check_MK now has a new special agent for monitoring AppDynamics via its REST API. Information
is mapped to your existing monitoring hosts via Piggyback.
ID: 2370
Title: Fix computation of "in downtime" and "acknownledged" of hosts in BI aggregations
Component: BI
Level: 2
Class: Bug Fix
Version: 1.2.7i3
BI automatically aggregates downtimes and acknowledgements. But for host nodes in a
BI tree these two states had been swapped. This has been fixed.
ID: 2317
Title: agent_ruckus_spot: new special agent for querying access point statistics via web interface
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i3
This new special agent queries the web interface of a Ruckus Spot service.
It reports access point information for the 2.4 GHz and 5 GHz bands.
For each band the information consists of
<ul>
<li>Number of devices</li>
<li>Number of time drift problems</li>
<li>Number of devices not responding</li>
</ul>
You can configure levels for the <i>time drift</i> and <i>not responding</i> problems.
Without further configuration the check is always OK.
ID: 2365
Title: Removed old deprecated notification global options for plain emails
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i3
The global settings for old plain email notifications (like configuring the
subject) have been removed. The will not work for the current rule based
notifications anyway. If you really still use plain emails then your old
settings will continue to work for the while, though. We encourage you to
switch over to rule based notifiations.
ID: 2352
Title: FreeBSD Agent: Removed statgrab cpu section because there is a dedicated cpu section
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i3
Removed the <tt>statgrab_cpu</tt> section from the agent because there is a standard
conform <tt>cpu</tt> section in the agent.
If yoy used the <tt>statgrab_cpu</tt> check before and have disabled the <tt>cpu</tt>
check on your devices by configuration, you will need to remove the "disabled services"
or "disabled checks" rules from your hosts.
ID: 2350
Title: FreeBSD Agent: Changed bash path to /usr/local/bin/bash
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i3
Older versions of the FreeBSD Agent used the /bin/bash path as interpreter
which seem not to be standard conform. It has now been changed to
<tt>/usr/local/bin/bash</tt> in the hope that this is now correct and not
breaking existing setups.
ID: 2351
Title: FreeBSD Agent: Made plugin/local paths standard conform
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i3
The former paths <tt>/usr/lib/check_mk_agent</tt> were not correct according
to FreeBSD standards. We have now switched the path to <tt>/usr/local/lib/check_mk_agent</tt>.
If you currently use the old paths, you will need to move this directory to
the new location when using the new agent.