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: 1150
Title: netstat: new check for monitoring TCP/UDP connections and Linux and AIX
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i6
The check does the same as <tt>win_netstat</tt> and also uses the same WATO rule.
You need to deploy the agent plugin <tt>netstat.linux</tt> or <tt>netstat.aix</tt>.
ID: 1148
Title: Allow execution of actions when cancelling events
Component: Event Console
Level: 2
Class: New Feature
Version: 1.2.5i6
The Event Console now allows to attach actions to the cancelling of
events. This can for example be helpful if you have an action that opens a
trouble ticket in an external system. When a cancelling event arrives you
can have executed an action that also cancels the according trouble ticket.
When events are cancelled then several data fields of the event are being
replaced with data from the new event before the action is being executed. That
way relevant data from the new event is available in the action script. Also
the event phase is being set to <tt>closed</tt> and the state is set to
0 (OK). That way your action script can distinguish between a normal
and a cancelling situation.
The following fields are taken from the new (i.e. cancelling) event:
<ul>
<li>The text</li>
<li>The time</li>
<li>The time of the last occurance</li>
<li>The syslog priority</li>
</ul>
All other fields are unchanged - including the original ID of the cancelled
event.
ID: 1100
Title: WATO backup domains: fixed bug were excluded files still got deleted on snapshot restore
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.5i6
It is possible to configure a backup domain so that certain files are not packed into the snapshot.<br>
As a result, upon restore these file should not get deleted..<br>
This mechanism did not work correctly.
ID: 1147
Title: upc_capacity, ups_socomec_capacity: Fix checking of battery left levels
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i6
The fixes the execution of the levels for <i>Time left on battery</i>. These
levels where internally compared against the <t>Time running on battery</i>
- which is obviously quite the opposite.
Example: If you configure a warning level of <tt>50</tt> minutes for <i>Time
left on battery</i> then the check gets critical if the estimated remaining
battery time is 50 minutes or less.
ID: 1373
Title: Do not ouput complete command line when datasource programs fail
Component: Core & Setup
Level: 2
Class: Security Fix
Version: 1.2.5i6
When executing a datasource program like <tt>agent_vsphere</tt>
fails, then Check_MK used to output the complete command line
as plugin output of the Check_MK active check as part of an error
message. The commandline could contain passwords - however. So this
has now been changed into just outputting the path to the executable
(e.g. <tt>/omd/sites/mysite/share/check_mk/agents/special/agent_vsphere</tt>).
ID: 1144
Title: blade_bx_temp, dell_chassis_temp, emerson_temp, ibm_svc_enclosurestats, ups_bat_temp: rename service description
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i6
Rename service description of these checks. They now all begin with <tt>Temperature</tt>, such as
is custom for all Check_MK checks. Beware: new graphs will be created. If these services are target
of WATO or BI rules you might need to adjust them. Your WATO configuration for levels should work
without change.
ID: 1010
Title: chrony: new check for NTP synchronization via chrony on Linux
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i6
This check does the same as the existing {ntp.time} check, but is for
cases when {chrony} is being used instead of the {ntpd}. It does not
support measuring jitter, however.
ID: 1097
Title: windows_agent: preventing missing agent sections on first query
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i6
The windows agent did not report all sections on the first request(s) after
its startup, if some plugins were configured to run asynchronous.
This has been fixed. During startup, the agent now always executes the ASYNC scripts first
and waits for them to finish. After the scripts are finished, it starts listening to
the tcp port.
ID: 0647
Title: printer_input, printer_output: multiple fixes to algorithm for state determination and inventory function
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.5i6
The inventory function now considers the description of the unit if its name is not configured. This should lead to
more and more meaningful items. Still, all units with empty name and description will be merged into one single
service with an empty item name.
The algorithm to determine the states of a unit was plain wrong, so that a nonsense collection of states were given.
This has been corrected. Still several states may be derived, but they should now correctly describe the operational
state of the unit.
The inventory function also used the same algorithm to inventorize only units with meaningful states. Therefore some
changes may be expected in the inventory of a printer as well.