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."
ID: 2193
Title: Remove duplicate performance data from host notifications
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.7i1
In HTML emails for host notifications the row for the host performance
data appeared twice. The second appearance was now moved to the services
notification - for which it originally was intended.
ID: 1903
Title: mk_oracle: Remote Monitoring of Oracle Databases
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
mk_oracle got a major improvement in monitoring Oracle Databases.
This new option allows monitoring a database from another host with a
running check_mk_agent.
H2: Requirements
You need an Oracle Client from Oracle to use this feauture. The Oracle Instant Client
with SQLPlus is a required minimum. You could use an existing Oracle installation as
environment for mk_oracle as well.
The plugin sends the data with piggyback. Please keep in mind, that the agent from the
host with mk_oracle is responsible for the piggyback data. If you put the Check_MK check
in downtime you'll put all other database checks from mk_oracle in a downtime as well.
H2: Configuration
You need an Oracle Client. If ORACLE_HOME is not set in the login shell of root, you need
to add the ORACLE_HOME variable to mk_oracle.mk.
Add the following lines to <tt>mk_oracle.cfg</tt>. The path is an example for the RPM Instant
Client from Oracle for 64bit.
<tt>ORACLE_HOME=/usr/lib/oracle/11.2/client64</tt>
<tt>REMOTE_INSTANCE_1_omd110=check_mk:check_mk:::::XE:11.2</tt>
<tt>REMOTE_INSTANCE_2_omd110=check_mk:check_mk:::::XE2:11.2</tt>
Definition of a REMOTE_INSTANCE:
<tt>REMOTE_INSTANCE_<Number>_<piggyback Hostname>=<Configuration String></tt>
The definition of the database connection is as follows.
<tt><username>:<password>:<sysdba>:<port>:<Database hostname>:<reserved for future use>:<ORACLE_SID>:<ORACLE-Release></tt>
Notes regarding <tt>REMOTE_INSTANCE_x</tt>
You need to make sure, that the name of the variable including
the hostname is unique for every database in <tt>mk_oracle.cfg</tt>.
Only 3 '_' are allowed in front of the piggyback hostname.
Otherwise the plugin won't work correctly. The Oracle Release must
be 9.2, 10.1, 10.2, 11.1, 11.2 or 12.1. No other values are allowed.
Don't forget to use the testmode before starting the inventory on
the monitoring host.
More details could be found on the documentation at Check_MK:
https://mathias-kettner.de/checkmk_oracle.html
The testmode is compatible with the remote mode. Details with an
example are shown in the documentation.
H2: Incompatible change:
The compatibility against old sqlplus.sh has been removed. Please
remove an exiting sqlplus.sh and configure
the <tt>mk_oracle.cfg</tt>. This change is a requirement for the
new remote monitoring option and the only reason for this
change.
There is nothing to do when <tr>sqlplus.sh</tr> was not used before this Werk.
ID: 2154
Title: Interface-Checks: Separate traffic thresholds for in and out are now possible
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
It is now possible to configure separate bandwidth thresholds for the interface
checks on the traffic directions. Instead of configuring "In/Out" at once, you
can choose only a single traffic direction to specify the levels for.
ID: 2061
Title: DB2 monitoring: Additional checks for AIX (and presumably linux)
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
This werk introduces the new agent plugin mk_db2.aix which can be
installed on aix systems in the agents plugins directories.
It is very likely that it runs on linux systems as well.
It is able to run queries over multiple DB2 instances.
The plugin output is processed by the following new checks
<table>
<tr><th>Check</th><th>Description</th><th>Limits configurable</th></tr>
<tr><td>db2_backup</td><td>Time since last database backup</td><td>X</td></tr>
<tr><td>db2_bp_hitratios</td><td>Bufferpool Hitratios</td><td></td></tr>
<tr><td>db2_connections</td><td>Number of database connections</td><td>X</td></tr>
<tr><td>db2_counters</td><td>Deadlocks and Lockwaits per Second</td><td>X</td></tr>
<tr><td>db2_logsize</td><td>Size and growth of database logfile</td>X<td></td></tr>
<tr><td>db2_tablespaces</td><td>Size and growth of tablespaces</td>X<td></td></tr>
<tr><td>db2_sort_overflow</td><td>Percentual sort overflow</td><td>X</td></tr>
<tr><td>db2_version</td><td>Displays DB2 version</td><td></td></tr>
</table>
ID: 2104
Title: aix_if: new agent section and check
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
This aix check_mk_agent has a new section aix_if extracting more information about network interfaces
than the previous lnx_if section. A new interface check for AIX named aix_if has also been created
given more useful information.
As long as you do not replace the check_mk_agent on your AIX systems, nothing will change.
When you replace the agent with the new one, you will have to redo the service discovery.
Interfaces will reappear with the same service description, but with more information about the NIC.