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: 2282
Title: mkeventd: fixed exception in notification if the application field of the event was not set
Component: Event Console
Level: 2
Class: Bug Fix
Version: 1.2.7i1
Events without an properly set <i>application</i> field were not processed correctly
by the Check_MK notification module. By nature, all events from the event console
are always considered as service events. If the <i>application</i> field is empty
the event was processed as host event, which lead to an exception.
ID: 2302
Title: Availability: new option in "Labelling" for omitting legend for availability levels
Component: Reporting & Availability
Level: 2
Class: New Feature
Version: 1.2.7i1
ID: 2301
Title: Availability now allows just showing rows with outage times above certain levels
Component: Reporting & Availability
Level: 2
Class: New Feature
Version: 1.2.7i1
In the availability options you can now define percentage levels for WARN,
CRIT and non-OK. Only objects that exceed these levels will be displayed
then. This allows you to make a report of just those object that had some
problem during the queried time range.
ID: 2281
Title: mkeventd: fix: now able to create notifications with events containing umlauts
Component: Event Console
Level: 2
Class: Bug Fix
Version: 1.2.7i1
The event console was unable to create a notification for a event if it contained umlauts like ä, ö, etc.
The event itself got created, just the notification part was missing.
ID: 2300
Title: New catalog of check plugins and manpages now available as a new WATO module
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i1
What now has a new module <i>Check Plugins</i> that is essentially a complete catalog
of all check plugins that your installation has installed. It contains shipped plugins
as well as locally installed ones (if they have a man page that is).
>From the man pages you can directly jump to the according rule set for the parameters
of the check. Also links to the manual page have been added in the new service command
menu and in the WATO service list.
ID: 2297
Title: Cleanup global settings, rename sections, remove obsolete settings
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i1
The <i>Global Settings</i> of WATO have been cleaned up a bit. The sections
have been renamed to be more self-explanatory. The order has been made more
useful. And some useless settings have been removed (they still keep working
if you have changed them from the defaults).
ID: 2231
Title: More transparently show errors during service discovery
Component: Core & Setup
Level: 2
Class: New Feature
Version: 1.2.7i1
Checks might run into problems parsing the output of an agent plugin. When
this happens during a normal check, you will soon know this as the according
service goes <i>UNKNOWN</i> and you will be able to create a crash dump.
Errors in single check plugins during service discovery, however, have been
silently ignored unless you used <tt>--debug</tt> on the command line. This
behaviour has been changed in the following way:
H2:<tt>cmk -I</tt> on the command line
Now for each files plugin a warning is being printed, but the discovery
continues. <tt>--debug</tt> will let the Python exception come through
and abort the discovery with a precise error message - just as it used
to be.
H2:Check_MK Discovery service
The discovery check now in case of an error during the discovery goes
to <i>UNKNOWN</i> and produces a crash dump - just as normal checks do.
That way you can easily send us a crash report in case of any error.
Previously error would be ignored silently.
H2:Service list in WATO
In WATO the list of a host's services will display a yellow error
message if one of the plugins fails. This messages has a link for
retrying the discovery without the error message and that way switch
back to the old behaviours (temporarliy).
H2:Bulk discovery in WATO
The bulk discovery keeps to the old behaviour of silently ignoring
errors but has got a new checkbox for letting a host fail if at
least one check plugin of the host runs into an error. The default
setting of the checkbox is to ignore errors.