ID: 4580
Title: informix_dbspaces, informix_locks, informix_logusage, informix_sessions, informix_status, informix_tabextents: New checks for IBM Informix DBs
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
In order to use these checks you have to install the related
agent plugin {{mk_informix}} and state a configuration file
informix.cfg.
<ul>
<li>ONINIT_PATH; Default is empty, which means auto detection:</li>
<ul>
<li>ONINIT_PATH=/PATH/TO/ONINIT-BINARY</li>
</ul>
<li>Excluding sections: status, sessions, locks, tabextents, dbspaces, logusage:</li>
<ul>
<li>EXCLUDES_INFORMIX-INSTANCE="SECTION SECTION ..."</li>
<li>EXCLUDES_INFORMIX-INSTANCE=ALL</li>
<li>EXCLUDES="SECTION SECTION ..."</li>
<li>EXCLUDES=ALL</li>
</ul>
</ul>
ID: 5119
Title: BI rules: 'Call a rule' in 'Child Node Generation' shows separated pack and rule title
Component: BI
Level: 1
Class: New feature
Version: 1.5.0i1
Previously within the above mentioned choices rule ID,
pack title and rule title were merged into one.
Separated them for better overview.
ID: 5392
Title: Fixed host monitored from all sites after editing custom host attributes
Component: WATO
Level: 2
Class: Bug fix
Version: 1.5.0i1
In distributed environments it could happen that all configured hosts are monitored
from all configured sites.
The now fixed issue was triggered by saving (adding/editing/removing) custom host attributes
using the "WATO > Hosts > Custom host attributes" dialog.
Background: This editing step was undeclaring the internal "site" attribute by accident
and rewriting all hosts.mk files. These files were missing the "site:..." host tag in the
all_hosts data structure. This makes all sites think that they are responsible for these
hosts.
The configured site information of the hosts/folders was not lost because it was retained
in the host_attributes data strucuture. So the hosts.mk files could be "repaired" by
saving the hosts, parent folders or host tags.
ID: 5318
Title: BI aggregations can be configured to be in multiple groups
Component: BI
Level: 1
Class: Bug fix
Version: 1.5.0i1
Previously if more than one group were stated in the
configuration of any aggregation, the related view displayed
an error {{Duplicate BI aggregation}}. Fixed that.
ID: 5234
Title: Fixed recently introduced issue with non working WATO rules
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 1.5.0i1
In 1.4.0p14 an internal caching mechanism was changed.
This broke some caches and caused unexpected behaviours,
because most configurable rules were considered as empty.
ID: 5235
Title: Distributed monitoring: Fixed race condition when unpacking snapshots
Component: WATO
Level: 1
Class: Bug fix
Version: 1.5.0i1
Fix exception during snapshot extraction when a file planned for removal was deleted by another process.
ID: 5393
Title: MySQL agent plugin: With agent bakery it's now possible to use a local mysql config file
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
By default the mk_mysql agent plugin is using the /etc/check_mk/mysql.cfg configuration file
to load the configuration set in the agent bakery. This file is under control of the bakery
and may not be modified by the user locally.
It is now possible to include an optional file that the user is allowed to store and modify
locally. This may be useful in case on wants to put the agent under bakery control, but
don't want to store the database credentials in the bakery. Instead of that the credentials
can be put into this file manually.
The new file is loaded from the same directory as the mysql.cfg and it must be named
mysql.local.cfg. When using the default paths, the full path is:
<tt>/etc/check_mk/mysql.local.cfg</tt>.
ID: 5224
Title: check_http: Support verbose output
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
This allows to use the -v option of the classic check_http active check.
This will extend the long output of the plugin by header and body information.