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: 2248
Title: The Event Console can now translate incoming SNMP traps
Component: Event Console
Level: 2
Class: New Feature
Version: 1.2.7i1
The Event Console can be configured to receive SNMP traps. In the past it
only extracted all raw OIDs and values from the incoming trap and putting
them together in the event message as they come in.
Now it is possible to use SNMP MIB files to let the Event Console translate
the OIDs, values and units contained in the traps.
This feature is disabled by default. You need to enable the Event Console
and the SNMP trap handling by using <tt>omd config</tt> in OMD environments.
Then you need to enable the trap translation in <i>Event Console > Settings</i>
by setting <i>Translate SNMP traps</i> to <i>on</i>. Finally you need to
activate the pending EC-Change.
Now all available MIBs will be used to translate the incoming traps.
You can now upload custom MIB files using the MIB management page at
<i>Event Console > SNMP MIBs</i> which will be used for translation after
reloading the Event Console.
ID: 2071
Title: windows agent: fileinfo check now correctly reports empty directories
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i1
The fileinfo check did not report any data in case the directory
in question exists but did not contain any files.
ID: 2207
Title: Fix exception in rule based notifiations with Nagios core and event type filter
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.7i1
When using Nagios as a core and the list of allowed events contains flapping
or downtime events and the previous hard state cannot correctly be determined
(due to <tt>max_check_attempts</tt> being greater as) then an exception
could have happened. This has been fixed.
ID: 2204
Title: Inventory of switch ports, allows searching for unused ports
Component: HW/SW-Inventory
Level: 2
Class: New Feature
Version: 1.2.7i1
The Check_MK HW/SW-Inventory now collections information via SNMP. The first
two implemented plugins are for the basic SNMP information and for the list of
network interfaces (switch ports). The latter are available in a new status
view where you can search ports for various criteria - e.g. all ports where
the type is Ethernet and that are down for at least one month.
All you need to do is to active the HW/SW-Inventory on those devices.
ID: 2201
Title: apt: New check for checking pending APT updates on Debian and Ubuntu
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
You just need to deploy the new agent plugin <tt>mk_apt</tt>. Read the check
man page of <tt>apt</tt> for details.
ID: 2175
Title: Added icon uploader, unified icon selection
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i1
Check_MK makes use of icons in views and dashboards, but it is also possible
to add a custom icon to hosts or services for e.g. showing up the type of
the device in a graphical way. This version also adds the option to register
custom icons and actions to host and services.
This change unifies the handling of icons used in such places. We implemented
an icon selector which is used everywhere were you can select an icon. This
icon selector groups the icons together in categories for more comfortable
selection.
We added an icon upload mechanism which gives you the option to manage your
custom icons using WATO. You can find it in the top level navigation of WATO.
All icons are now loaded from a fixed location, in OMD environments this
is <tt>share/check_mk/web/htdocs/images/icons</tt> for the icons distributed
by us and <tt>local/share/check_mk/web/htdocs/images/icons</tt> for your
custom icons.
Implementation detail: The category of an icon is saved directly in the icon
image. It is stored in the PNG comment metadata.
ID: 2174
Title: Added action popup to host & service views, supporting custom actions now
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i1
Each host and service has several icons showing up in the web GUI to either
provide options to perform actions or visualizing the state of the object.
Now we reworked the whole thing a bit by adding a popup menu which is groups
together the actions for an object. This aims to reduce the number of icons
shown up in list views.
By default the icon column is now showing the popup menu trigger icon which
can be left clicked to open the popup menu and the graph icon if a host or
service has performance data available. The column is also showing all state
related icons.
Former versions already allowed users to extend the web GUI with so called
in python written icon plugins. This is still possible.
But now, we added the option to easily configure basic actions using WATO.
The configuration is split into two steps:
a) You need to basically configure your custom actions
This is done via the option <i>Custom icons and actions</i> which
can be found in the <i>Status GUI (Multisite)</i> tab of the <i>Global
Settings</i>.
First you need to choose an unique identifier for your action.
Then you can either configure simple icons providing some kind
of information, for example the type of the system, by configuring just
an icon and the title.
If you like to add a custom action, for example a link to the web interface
of one of your devices, you can configure an action URL where you can use
some basic macros:
<ul>
<li>$HOSTNAME$: Contains the name of the host</li>
<li>$SERVICEDESC$: Contains the service description (in case this is a service)</li>
<li>$HOSTADDRESS$: Contains the network address of the host</li>
</ul>
b) Assign the actions to your objects
After you configured at least one custom action, you can use the rules
<i>Custom icons or actions for hosts in status GUI</i> and
<i>Custom icons or actions for services in status GUI</i> to assign
your custom actions to your hosts and services.
ID: 2195
Title: New condition "Match Contacts" in rule based notifications
Component: Notifications
Level: 2
Class: New Feature
Version: 1.2.7i1
You can now add a new condition in a notification rule in order to match
for the contacts of a host or service. That way you can make rules
like "If user adam is a contact of the host/service, then notify bernie."