ID: 12180
Title: Display services of unimplemented check plugins
Component: Checks & agents
Level: 2
Class: New feature
Version: 2.1.0i1
Previously services which were discovered by check plugins
that are not available anymore have been filtered, and
where (almost) never seen.
They were reported as 'vanished' by the Checkmk Discovery check,
but did *not* show on the discovery page, nor in the services
page.
They are now treated as regular services, with the service
description "Unimplemented check <name>".
They will always be in {{UNKNOWN}} state.
This situation can occur for instance if you uninstall an MKP, or
modify a plugin locally and make a mistake.
If you suddenly encounter such services after an upgrade to Checkmk 2.0,
it means that you had such services in your configuration all along.
You can remove them from your configuration just as any other service.
ID: 11851
Title: Windows agent MSI checks that Windows OS is appropriate for installation
Component: Setup
Level: 2
Class: New feature
Version: 2.1.0i1
Previously, it was possible to configure the Windows agent in WATO in such
a way that installing on older operating systems would cause the Windows
agent updater to fail( or make such plugins as mk_jolokia or mk_logwatch more
inoperable). For example: setting of the <tt>Standard python environment(3.8+ )</tt>
and deploy such MSI on Windows 2008. This could cause complete falling out of the
host of the monitoring, because the installed standard Python, 3.8+, can't work
on Windows 2008.
With this release the problem has been solved. If during deployment configuration
is not supported by Windows OS, the installation will not be performed: the
MSI will always check Windows version and stops own installation if, Windows OS
doesn't match to MSI requirements. The host will continue to operates normally in
any case.
Nevertheless, you need to fix the configuration in WATO in the order to make
the update for older Windows system. In the case of the aforementioned example,
you have to select <tt>Deploy legacy environment (Python 3.4 + standard set of modules)</tt>
in the rule <tt>Install Python runtime environment</tt>, activate changes and bake
the agent.
ID: 11849
Title: Windows agent's Python supports obsolete Windows OS's
Component: Setup
Level: 2
Class: New feature
Version: 2.1.0i1
Since this release it's possible to choose the legacy Python environment, i.e. Python 3.4, thus
enabling full support for obsolete(EOL) Windows OS's. For example, Windows Server 2008, Windows
Server 2008R2, Windows Vista and Windows 7 require legacy Python environment.
To enable Python support for obsolete Windows OS's you should choose in the Bakery the ruleset
<tt>Install Python runtime environment</tt> and set value of the drop list <tt>Python environment</tt>
to the <tt>Deploy legacy environment(Python 3.4 + standard sets of modules)</tt> .
Despite the legacy python environemnt is fully compatible with any current Windows OS's, for
security and performance reasons it is highly recommended, if possible, to use only standard python
environment.
ID: 12135
Title: More detailed audit logging
Component: Setup
Level: 2
Class: New feature
Version: 2.1.0i1
With Checkmk 2.0 the audit logging of the setup has been extended to be more
detailed. We added the general capability of tracking changes to configuration
objects on attribute level.
The audit log can be opened going to "Setup > General > Audit log". On that
page you have the list of recorded changes with the new "Details" column. You
also have the general filter form that can be used for filtering the changes
you are interested in.
You can also find context related links from hosts, users and rules to the audit
log entries that are specific to this object.
You may notice that the "Details" column is empty for a lot of changes.
This is because we need to turn on the recording of details specific to each
action. In Checkmk, we have implemented this for the most common actions first.
These are:
<ul>
<li>Create, edit and delete hosts</li>
<li>Create, edit and delete folders</li>
<li>Service discovery (bulk and single host discovery)</li>
<li>Create, edit and delete users</li>
<li>Create, edit, move and delete rules</li>
</ul>
Over time, we will increase the level of detail of the other existing log messages.
ID: 12168
Title: Handle non-persistent comments correctly
Component: Core & setup
Level: 3
Class: Bug fix
Version: 2.1.0i1
You can add non-persistent host/service comments via Livestatus, and these
should vanish when the monitoring core is restarted. The CMC effectively
ignored the "persistent" flag for these user comments, so even
non-persistent comments survived a restart. This has been fixed, the CMC
now behaves like Nagios.
Note that this fix doesn't affect comments added via the GUI, because these
are always persistent.
ID: 12167
Title: Fixed acknowledgement expiry
Component: Core & setup
Level: 2
Class: Bug fix
Version: 2.1.0i1
Previously, the expiration mechanism for acknowledgements ignored the
"persisten" flag, so the corresponding comments always vanished after
expiration. Furthermore, the expiration of one acknowledgement didn't
remove all other acknowledgements for the same host/service.
Both aspects were inconsistent with the behavior of the manual removal of
acknowledgements, which was quite confusing and unintended. This has been
fixed, so acknowledgement expiry is identical to manual removal at the given
point in time.
ID: 12166
Title: Fixed comment/downtime WaitTriggers
Component: Livestatus
Level: 3
Class: Bug fix
Version: 2.1.0i1
The "comment" and "downtime" WaitTriggers were not always triggered when a
corresponding entity has been changed. This has been fixed.
ID: 10134
Title: Fixed logging of acknowledgements in monitoring history
Component: Core & setup
Level: 3
Class: Bug fix
Version: 2.1.0i1
Previously, the manual removal of persistent acknowledgements was not logged
in the monitoring history, this has been fixed: Now all acknowledgement
removals are logged, regardless of their persistent state.
ID: 10133
Title: Fixed source attribute of user comments
Component: Livestatus
Level: 3
Class: Bug fix
Version: 2.1.0i1
The CMC always reported all comments as coming from an "external" source,
even acknowledgements. Nagios considers the latter as "internal", so we do
the same now for consistency.
There is no impact on Checkmk's GUI, it doesn't use the "source" column from
the "comments" table. You can only observe the change directly via
Livestatus if you use that column, which is highly unlikely.
ID: 10132
Title: Fixed acknowledgement type of shadow hosts/services
Component: Core & setup
Level: 3
Class: Bug fix
Version: 2.1.0i1
The acknowledgement type of shadow hosts/services was always "none", even
when the corresponding host/service is actually acknowledged. Now we report
"normal" in these cases, which is more correct. Note that due to a
limitation in cmcdump, we do not know if the acknowledgement is "sticky" or
not.