ID: 10557
Title: MKP manager: Links to package download URLs are now opened in new window / tab
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
The download URLs of extension packages could not be opened in previous 1.6 releases,
because the Content Security Policy blocked opening external URLs in the content area
of the GUI. The links are now opened in a new page to prevent this issue.
ID: 10558
Title: Extension packages: Fixed performance issue
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.6.0p7
The performance of the calculation of the packaged files has been improved to
make the extension package management faster. Especially when managing a larger
number of files, this change can improve the user experience of the package
management.
ID: 10512
Title: mk_oracle: Fixed wrong check for oracle version
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
There has been a regression in werk #10359. This werk changed accidentally
the check for the oracle version in the tablespace section. This is now
working again.
ID: 10556
Title: Fix adding host/service label filters to views
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
When trying to add host or service label filters to views,
this resulted in an error message like this when displaying
the filter again after saving the view:
C+:
Failed to parse labels: No JSON object could be decoded
C-:
ID: 10573
Title: msoffice_licenses: Fixed ZeroDevisionError
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The check could got to UNKN state, if zero licenses where active. This
has been fixed. Such licenses now show the infotext "No active
licenses".
ID: 10431
Title: New agent rule for Checkmk agent service on Linux
Component: agents
Level: 1
Class: New feature
Version: 1.7.0i1
It is now possible to choose which, if any, network service should
be shipped and installed with a baked Linux Checkmk agent package.
This can be configured with the new agent ruleset "Checkmk agent network service (Linux)"
It is possible to choose between the following services/super servers setups:
<li>Ship service files for xinetd and systemd, prefer to activate xinetd service,
fallback to systemd if xinetd is not available</li>
<li>Ship and activate xinetd service</li>
<li>Ship and activate systemd service</li>
<li>Don't ship any service files</li>
If no rule is configured, the behavior will be identical to the first of the mentioned
choices (prefer xinetd, fallback to systemd).
If the super server(s) of your choice is/are not available at the target system, you
will be noticed about this on agent installation.
The last option (no service) is a reasonable choice if you want to monitor the hosts
without the use of a super server, e.g. via SSH.
ID: 10555
Title: Contact group deletion: Ensure not used by notification rules
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
When trying to delete contact groups, WATO now ensures that no contact group is
referencing the group anymore and prevents the deletion in case there is a
reference.
ID: 10411
Title: Customer specific macro replacements for reporting
Component: Multisite
Level: 1
Class: New feature
Version: 1.7.0i1
Within the customer properties there is now the option to define individual
replacement macros to use in reports. It is possible to set up an arbitrary
number of macros per customer.
Per default, two macros are initiated $CUSTOMER_ID$ and $CUSTOMER_NAME$,
corresponding to the customer properties ID and Name.
ID: 10413
Title: Sites can not be assigned to global scope
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
Users can be assigned to configured customers and the provider or to a
global scope to have access to all sites. The same option generators is
used for passwords and sites.
In the case of users and passwords, this objects are available for a
customer or globally. For site the global scope does not make sense as the
site is not available globally, but assigned to a global customer which
doesn't exist. Thus this option is removed to avoid misconfiguration.
ID: 10412
Title: Site filter in slave site only holds itself as filter target
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
Site filter within a customer assigned remote site is quite redundant as
the site only has access to itself, thus never actively used. However, the
filter available targets where poorly listed.
When configuring reports, this site filter aids to establish context for
the report and a poor listing of the single available site(itself) led to
empty results.