ID: 10710
Title: systemd: Do not mark the agent unit failed on single agent failure
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
When the agent is queried via systemd, the socket unit creates an instance
of the agent service unit template. These are named something like
<tt>check-mk-agent@842-127.0.0.1:6556-127.0.0.1:33196.service</tt>.
When one of these services failed in the past for some reason, the unit was
left in a failed state and reported by the Checkmk systemd service monitoring
as a failed service.
In reality such errors can occur sporadically for various reasons. However,
they are usually uninteresting. For this reason, the agent is now executed in
such a way that erroneous executions do not lead to a faulty unit.
ID: 10739
Title: send notifications chronologically
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
Due to a bug in the notification spooler new spoolfiles were processed before
old spoolfiles. This may lead to suprising results. If e.g. a host goes DOWN
and UP in a short time interval the UP notification may arrive before the
DOWN notification.
Now the notification spooler processes the notifications in the order of
occurance, i.e. the DOWN notification will be sent before the UP notification.
SUP-1708
ID: 10759
Title: agent_jira, jira_workflow, jira_custom_svc: New special agent and checks to gather statistics from Jira instances
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
With this special agent and checks, it's possible to query given projects and
there workflows. This will result in one service per project and workflow that
outputs the number of issues. Furthermore, you can define custom Jira Query
Language (JQL) searches with different options on the result. Therefore, you
have to define a service description for the resulting check and what result
you expect (the count of found issues or the summed up or average values of a
given numeric field). It's also possible to limit the number of processed
results.
ID: 10763
Title: Opsgenie: Fixed authentication error on european accounts
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
If you use an european account, the notification plugin fails with an
authentication error. To prevent this, you can now configure the domain in the
associated notification rule.
ID: 10704
Title: Agent bakery: Fix rules of non-main folder matching for GENERIC agent
Component: agents
Level: 1
Class: Bug fix
Version: 1.6.0p9
The generic agent package should only be affected by agent related rules that
are assigned to the main folder. In previous 1.6 releases the GENERIC agent
was affected by rules from all folders.
ID: 10709
Title: Fix site certificate being overwritten during version update
Component: Site Management
Level: 1
Class: Bug fix
Version: 1.6.0p9
The sites SSL certificate (etc/ssl/sites/[site].pem), which is used by
encrypted livestatus communication, was replaced with a fresh certificate
during each "omd update".
When using certificates issued by the site CA, this was not an issue, because
the trust at the central site was established with the site CA. It was only an
issue when trying to replace the site certificate with a certificate signed
by an external CA.
ID: 10590
Title: esx_vsphere_vm: Check age of oldest snapshot
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Since a regression in version 1.6.0 the maximum allowed age of the *oldest* snapshot
(WATO rule parameter "Age of the oldest Snapshot") has only been checked if more than
one snapshot was present. This has been fixed.
ID: 10682
Title: Windows: Inventory correctly reports IP addresses for more than one network card
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously the inventory reported only IP address(s) of the last network card.
Now the error is fixed.