Werk 16176 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: postfix: Fix Postfix status monitoring for agents run in Docker
Class: fix
Compatible: compat
Component: checks
Date: 1710323821
Edition: cre
Level: 1
Version: 2.2.0p26
Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running.
Since docker containers don't have permissions to read /proc, the agent always reported
the Postfix instance as 'not running'.
This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.
------------------------------------<diff>-------------------------------------------
Title: postfix: Fix Postfix status monitoring for agents run in Docker
Class: fix
Compatible: compat
Component: checks
Date: 1710323821
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running.
Since docker containers don't have permissions to read /proc, the agent always reported
the Postfix instance as 'not running'.
This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.
Werk 16174 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: mongodb_replica_set: Fix replication lag and last replication time
Class: fix
Compatible: compat
Component: checks
Date: 1709804918
Edition: cre
Level: 1
Version: 2.2.0p26
Checkmk previously assumed that timestamps collected from MongoDB oplog
are provided in ms. This wasn't the case, which led to wrong values for
replication lag and last replication time being shown in
the 'MongoDB Replication Lag' service.
------------------------------------<diff>-------------------------------------------
Title: mongodb_replica_set: Fix replication lag and last replication time
Class: fix
Compatible: compat
Component: checks
Date: 1709804918
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Checkmk previously assumed that timestamps collected from MongoDB oplog
are provided in ms. This wasn't the case, which led to wrong values for
replication lag and last replication time being shown in
the 'MongoDB Replication Lag' service.
Werk 16485 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: host_config: Create hosts in folder with umlauts
Class: fix
Compatible: compat
Component: rest-api
Date: 1710161510
Edition: cre
Level: 1
Version: 2.2.0p26
When creating hosts in a folder with umlauts in the name via one of the
<code>host_config</code> endpoints the endpoint would return an error 400 even though
the query was correct.
Now the hosts are created correctly.
------------------------------------<diff>-------------------------------------------
Title: host_config: Create hosts in folder with umlauts
Class: fix
Compatible: compat
Component: rest-api
Date: 1710161510
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
When creating hosts in a folder with umlauts in the name via one of the
<code>host_config</code> endpoints the endpoint would return an error 400 even though
the query was correct.
Now the hosts are created correctly.
Werk 16484 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Crash when creating combined graphs with empty time filter
Class: fix
Compatible: compat
Component: multisite
Date: 1709884230
Edition: cre
Level: 1
Version: 2.2.0p26
When creating a combined graph with an empty time filter (e.g. Last service check),
the creation of the combined graph would crash.
This behavior is not consistent with the view filtering behavior,
where the filter is not applied if it is empty.
Now the filter is not applied to combined graphs either.
------------------------------------<diff>-------------------------------------------
Title: Crash when creating combined graphs with empty time filter
Class: fix
Compatible: compat
Component: multisite
Date: 1709884230
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
When creating a combined graph with an empty time filter (e.g. Last service check),
the creation of the combined graph would crash.
This behavior is not consistent with the view filtering behavior,
where the filter is not applied if it is empty.
Now the filter is not applied to combined graphs either.
Werk 16629 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Virtual host tree links work for more than three host tag groups
Class: fix
Compatible: compat
Component: multisite
Date: 1710494682
Edition: cre
Level: 1
Version: 2.2.0p26
A virtual host tree (Setup > General > Global settings > User interface > Virtual host trees) can be configured with more than three host tag tree levels. Yet, the corresponding views that are linked to from the sidebar element "Virtual host trees" were not able to display more than three rows in the "Host tags" filter and thus only filtered for the first three.
This is fixed. A virtual host tree link as described above now leads to a properly filtered view with all the given host tag filters shown in the filter popup.
------------------------------------<diff>-------------------------------------------
Title: Virtual host tree links work for more than three host tag groups
Class: fix
Compatible: compat
Component: multisite
Date: 1710494682
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
A virtual host tree (Setup > General > Global settings > User interface > Virtual host trees) can be configured with more than three host tag tree levels. Yet, the corresponding views that are linked to from the sidebar element "Virtual host trees" were not able to display more than three rows in the "Host tags" filter and thus only filtered for the first three.
This is fixed. A virtual host tree link as described above now leads to a properly filtered view with all the given host tag filters shown in the filter popup.
Werk 16498 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: cisco_redundancy: handle new swact reasons
Class: fix
Compatible: compat
Component: checks
Date: 1709890474
Edition: cre
Level: 1
Version: 2.2.0p26
Fixes a crash in the check plugin, caused by not handling two recently added switch of activity reasons.
------------------------------------<diff>-------------------------------------------
Title: cisco_redundancy: handle new swact reasons
Class: fix
Compatible: compat
Component: checks
Date: 1709890474
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Fixes a crash in the check plugin, caused by not handling two recently added switch of activity reasons.
Werk 16694 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Fix event statistics dashlet filters
Class: fix
Compatible: compat
Component: multisite
Date: 1712656769
Edition: cre
Level: 1
Version: 2.2.0p26
For the dashlet "Event statistics" you were able to configure "Host" and
"Service" Context/Search filter.
The "Service" filter had no effect and is now replaced with the "Event Console
event" filter option.
------------------------------------<diff>-------------------------------------------
Title: Fix event statistics dashlet filters
Class: fix
Compatible: compat
Component: multisite
Date: 1712656769
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
For the dashlet "Event statistics" you were able to configure "Host" and
"Service" Context/Search filter.
The "Service" filter had no effect and is now replaced with the "Event Console
event" filter option.
Werk 16612 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: notifications: Fix plugin permissions not loaded automatically
Class: fix
Compatible: compat
Component: notifications
Date: 1711549357
Edition: cre
Level: 1
Version: 2.2.0p26
Previously, it was possible for users with the "Notification configuration"
permission to edit notification rules even if they did not have the permission
to the plugin that was being used in the rule. When such a user edited
such a rule, they were able to overwrite the notification plugin with
any plugin they were allowed to use.
This werk stops users from editing rules that use notification plugins
they don't have access to.
------------------------------------<diff>-------------------------------------------
Title: notifications: Fix plugin permissions not loaded automatically
Class: fix
Compatible: compat
Component: notifications
Date: 1711549357
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Previously, it was possible for users with the "Notification configuration"
permission to edit notification rules even if they did not have the permission
to the plugin that was being used in the rule. When such a user edited
such a rule, they were able to overwrite the notification plugin with
any plugin they were allowed to use.
This werk stops users from editing rules that use notification plugins
they don't have access to.
Werk 16551 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Crash in agent bakery GUI after cloning a site
Class: fix
Compatible: compat
Component: agents
Date: 1711098828
Edition: cee
Level: 1
Version: 2.2.0p26
After cloning a site with <code>omd cp</code> or renaming it with <code>omd mv</code>, opening the agent bakery GUI
did result in a crash, showing a message like
C+:
Internal error: '/omd/sites/SITE/share/check_mk/agents/check_mk_agent.linux' is not in the subpath of '/omd/sites/SITE_COPY/share/check_mk/agents' OR one path is relative and the other is absolute.
C-:
As a workaround, you can delete the file <code>~/var/check_mk/wato/bakery_file_status.mk</code>
on the site.
------------------------------------<diff>-------------------------------------------
Title: Crash in agent bakery GUI after cloning a site
Class: fix
Compatible: compat
Component: agents
Date: 1711098828
Edition: cee
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
After cloning a site with <code>omd cp</code> or renaming it with <code>omd mv</code>, opening the agent bakery GUI
did result in a crash, showing a message like
C+:
Internal error: '/omd/sites/SITE/share/check_mk/agents/check_mk_agent.linux' is not in the subpath of '/omd/sites/SITE_COPY/share/check_mk/agents' OR one path is relative and the other is absolute.
C-:
As a workaround, you can delete the file <code>~/var/check_mk/wato/bakery_file_status.mk</code>
on the site.
Werk 16584 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: REST API: Fix httpie examples
Class: fix
Compatible: compat
Component: rest-api
Date: 1710939092
Edition: cre
Level: 1
Version: 2.2.0p26
Some httpie examples had a backslash at the end of the last line causing
these examples to fail when executed. This Werk fixes the way REST API
examples are generated to prevent backslashes at the end of the last line.
------------------------------------<diff>-------------------------------------------
Title: REST API: Fix httpie examples
Class: fix
Compatible: compat
Component: rest-api
Date: 1710939092
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Some httpie examples had a backslash at the end of the last line causing
these examples to fail when executed. This Werk fixes the way REST API
examples are generated to prevent backslashes at the end of the last line.