ID: 2184
Title: statgrab_mem: converted to the same logic as the other memory checks
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i1
The check plugin <tt>statgrab_mem</tt> now uses the same implementation
as <tt>solaris_mem</tt> and many other memory checks. That makes the
output compatible.
Note: This change is incompatible since existing rules for memory
levels do not apply any longer. Now the same WATO rule set as for
other memory checks is being used. Please create new rules if you
have the need for custom levels.
ID: 2183
Title: ps: allow levels of used RAM in percentage of total RAM of host
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i1
You can now specify the levels for the memory usage of a process
or group of processes in relation to the total RAM memory of a host.
This makes it easier to find memory consuming processes in general,
without the need for different levels for every single host.
Note: these levels only work if the agent output provides information
about the total memory. This is the case for at least the usual
agents for Linux, Windows and Solaris.
ID: 1954
Title: fileinfo / fileinfo.group: Fixed discovery function for fileinfo groups and equalize agent output of fileinfo agents
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i1
Discovery function now handles the agent output as followed:
<ul>
<li>File Pattern match: For every matching file a new item is returned and a new service is created.</li>
<li>File Pattern mismatch: This pattern will be ignored. No item is returned and no service is created.</li>
<li>Group Pattern match or mismatch: For every group a new item is returned and a new service is created.</li>
</ul>
Supported agents on Windows, Linux, FreeBSD, MacOSX and Solaris now return the same agent output as followed:
<Searchpattern or Absolute file path>|<Filesize or "missing">|<Modification time of file>
ID: 2110
Title: netapp_api_aggr: check did not take configured levels when using Nagios
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i1
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: 1900
Title: mk_oracle: added oracle session environment
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i1
The plugin set some session parameters after login to Oracle. This is useful
for environments with very special init.ora parameters which caused some
performance problems in mk_oracle.
The new function could be disabled with the following parameter in mk_oracle.cfg:
<tr>DISABLE_ORA_SESSION_SETTINGS=1</tr>
ID: 2142
Title: Fix non-working option for disabling column headers in grouped boxed views
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.7i1
For example the pages showing graphs after a graph search would show <i>Service graphs</i>
above each graph. This has been fixed.
ID: 2141
Title: Fix computation of explicit time ranges with time of day
Component: Multisite
Level: 1
Class: Bug Fix
Version: 1.2.7i1
When you entered an explicit time range (e.g. in the options for the
graph time range) and selected <i>Explicit time...</i> then 24 hours
would be added to the end time. This has been fixed. Note: the adding
of one day is still being done when selecting <i>Explicit date...</i>,
so that if you select the same start and end date the span is exactly
24 hours.