ID: 5539
Title: Improved performance of pages showing many graphs
Component: metrics
Level: 2
Class: New feature
Version: 1.5.0i2
Previously the GUI was loading all graphs in the progress of
rendering a view. The view was rendered to the user once the
information for all graphs is known. This mechanism made pages
that show a lot of graphs load slowly.
With this change the views are now rendered with a place holder
for each graph which is a lot faster. After the view has been
loaded for the user, the browser starts to render the graphs
asynchronously and simultaneously which will also reduce the
total time needed for loading.
ID: 5535
Title: Check_MK hosts can now use multiple agents
Component: Core & setup
Level: 2
Class: New feature
Version: 1.5.0i2
It is now possible to configure multiple Check_MK agents for a single host.
With this change, you can now configure e.g. a ESX VCenter to use the ESX special agent
together with the regular Check_MK agent installed on the monitored host.
All existing hosts remain using their existing configuration after an update. Also
new hosts only use a single Check_MK agent using the already existing logic where
a) The Check_MK agent was contacted via TCP or b) a configured data source program
(special agent or other program invocation) was used.
The new feature can be enabled by changing the host attribute (on hosts or folders)
"Check_MK Agent" to e.g. "Contact Check_MK agent and all datasource programs". This
will make Check_MK use all data sources matching on this host instead of just picking
the first matching one. There is also an alternative option "Use all enabled datasources"
available which can be used to execute only the data sources matching the host.
On the way to this change we have changed server previously existing things:
<ul>
<li>The host tag group <tt>agent</tt> has been split into multiple tag groups to be
more flexible.</li>
<li>The tag group <tt>ping</tt> and <tt>snmp</tt> have been added and provide the options
which were previously available in the single <tt>agent</tt> attribute.</li>
<li>All these tag groups are treated as <i>builtin</i> tag groups defined by Check_MK
(can not be modified anymore).</li>
<li>Existing configurations of hosts/folders will be translated seamlessly into the new
format.</li>
<li>During updates your site will only apply the changes above in case you have an unmodified
<tt>agent</tt> tag group. In case you have modified it in any way, these changes will not
be applied and you won't be able to use the changes introduced with this werk. You will then
have to clean up your local changes. Once you delete your local tag group "agent", the
builtin one will be used automatically.</li>
<li>The <i>Edit host</i> dialog has split up into more independent sections, the new ones
are <i>Address</i> and <i>Data sources</i> to better visualize the relation of the different
attributes.</li>
</ul>
<i>Please note:</i> In case you are using the Web-API calls to create or modify hosts or folders
while setting attributes we changed with this change, you may have to change your API calls.
ID: 5532
Title: Host/Service states and outputs can now be translated
Component: cmc
Level: 2
Class: New feature
Version: 1.5.0i2
The states and service status detail of hosts and services can now be translated. You can now
use the rules {{Host state translation}} and {{Service state translation}} to configure the
Check_MK core to translate either specific states to other states or the status detail to other
texts.
States: For each host/service you can configure a transformation of each possible monitoring state
to another one.
The state translation can, for example, be used to inverse a host check in case you want to get
a notification in case a host becomes reachable.
The translation of detail outputs is done using regular expressions. You can specify multiple
regular expressions (infix match, case sensitive) per object which are applied to the current
status detail. The matched text will be replaced by the specified replacement text. You can
use match groups to extract parts of the original text using the regular expression.
ID: 5531
Title: New WATO page "Best practices" can be used to find things to improve in your Check_MK
Component: WATO
Level: 2
Class: New feature
Version: 1.5.0i1
The new WATO page "Best practices" is meant to give you hints about your Check_MK installation
and the things you could improve in terms of performance, reliabilty and security.
In the moment you open the page, it starts analyzing your Check_MK installation and executes
different tests. Test may detect that a thing is OK and report the test to be OK. Other
tests may result in WARN state in case you could be interested in changing something.
Other tests may report a CRIT state in case we think that you have a critical situation which
should be fixed for a completely working Check_MK setup.
Please note that this feature and the implemented tests are still in an early phase of
development. Understand the test results as pointer on things you should check.
Each of the tests can be acknowledged just for a single site or all your sites. In case you
came to the decision that a reported problem is not really a problem for you, you can
acknowledge the test results.
In case you fix a problem, you won't need to acknowledge it. Just open up the page again,
which should then turn your test into OK.
ID: 5262
Title: Fix bug in agent bakery (regression #5261, since 1.4.0p17)
Component: agents
Level: 2
Class: Bug fix
Version: 1.5.0i1
Werk #5261 introduced a bug that made it impossible to bake new agents for some specific rulesets.
This would result in error messages like the following:
<pre>
"TypeError: key ('custom', 'win_certificates/lib/local/win_certificates.ps1') is not a string"
</pre>
After an update, no further action is required.
ID: 5435
Title: Fixed "omd update" problems when updating from 1.4.0p17 or older
Component: Site Management
Level: 2
Class: Bug fix
Version: 1.5.0i1
When executing "omd update" as site user to update a site from 1.4.0p17
or older an error could occur blocking the update. The message looks like
this:
<pre>
Traceback (most recent call last):
File "/omd/versions/1.4.0p17.cee/bin/omd", line 52, in <module>
import tarfile, fnmatch
File "/omd/versions/1.4.0p17.cee/lib/python2.7/tarfile.py", line 52, in <module>
import copy
File "/omd/versions/1.4.0p17.cee/lib/python2.7/copy.py", line 52, in <module>
import weakref
File "/omd/versions/1.4.0p17.cee/lib/python2.7/weakref.py", line 14, in <module>
from _weakref import (
ImportError: cannot import name _remove_dead_weakref
</pre>
This issue was caused by a mixup of python versions during the update which has
been fixed now by using the correct libraries during the update.
To workaround this issue, you could run the "omd update" command as root user instead
of the site user.
ID: 5429
Title: Fixed broken event history expiration (when using default settings)
Component: Event Console
Level: 2
Class: Bug fix
Version: 1.5.0i1
The Event Console was not deleting outdated entries from the event history.
With the default settings it is intended to delete entries older than 365
days from the EC archive. This did not work.
A message like this can be found each "Housekeeping interval", normaly 1 minute:
[1509618281.352829] Error expiring log files: year out of range
This time window can be configured with the setting "Event history lifetime".
As a workaround you can simply open this setting and save it with the default
value. This will make the event deletion work as expected.
When you are affected, this may result in a way too huge Event Console archive
directory (<tt>~/var/mkeventd/history</tt>) which may result in slow
"Event Console History" views (depends on your filtering). You could clean up
the archive directory by hand to improve the situation.
After applying the update, the next housekeeping run will clean up all your old
archived events.