[//]: # (werk v2)
# Extend Site Apache CustomLog LogFormat
key | value
---------- | ---
date | 2024-10-17T15:04:08+00:00
version | 2.3.0p19
class | feature
edition | cre
component | omd
level | 1
compatible | yes
The site Apache process writes to `var/log/apache/access_log`.
With this Werk, the log format includes the time taken to serve the request, in microseconds.
[//]: # (werk v2)
# mk_postgres.py: Enable using a system wide PGPASSFILE
key | value
---------- | ---
date | 2024-10-14T12:58:17+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The PGPASSFILE environment variable is only overwritten by the instance `pg_passfile` when it is not empty.
It is possible now to use a system-wide PGPASSFILE environment variable.
[//]: # (werk v2)
# mk_postgres.py: get_bloat exceeds char length under windows
key | value
---------- | ---
date | 2024-10-14T09:08:05+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
You may be affected by this werk if you're using `mk_postgres.py` under windows
and you have experienced issues with exceeding command-line character limits.
The query is now split up per database in order to avoid such failures.
[//]: # (werk v2)
# Distributed piggyback: Piggyback data for distributed setups
key | value
---------- | ---
date | 2024-10-21T08:58:28+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 3
compatible | yes
This feature allows the [piggyback mechanism](https://docs.checkmk.com/latest/en/piggyback.html) to be used across site borders.
In Checkmk versions prior to 2.4, the piggyback source and the piggybacked host always had to be monitored on the same site.
It now suffices if they are part of the same distributed setup.
This is achieved by the introduction of the `piggyback-hub`:
A service that will send incoming piggyback data to whatever site the piggybacked host is monitored on.
The transmitted data will be sent via the newly introduced message broker.
In most setups the messages will be routed via the central site, but direct (_"peer-to-peer"_) connections can be configured in the _Connections_ menu of the _Distributed Monitoring_ Setup page.
The data transport is secured via mTLS.
In the Checkmk MSP Edition, this layer also ensures that communication between different customers is not possible.
The _Piggyback Connector_ of the _Dynamic Configration Daemon_ now also supports the creation of hosts on other sites.
This feature is enabled by default, and can be disabled on one or all sites in the global settings.
[//]: # (werk v2)
# dell_powerconnect_cpu: Fix KeyError
key | value
---------- | ---
date | 2024-10-17T13:57:25+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The check plugin `dell_powerconnect_cpu` would crash with the following error:
```
File "/omd/sites/test/share/check_mk/checks/dell_powerconnect_cpu", line 59, in check_dell_powerconnect_cpu
("util1", "%d%%" % saveint(oneminuteperc), params[0], params[1], 0, 100),
KeyError (0)
```
The bug was introduced in the 2.3.0.
This Werk fixes the issue.
[//]: # (werk v2)
# Extend Site Apache CustomLog LogFormat
key | value
---------- | ---
date | 2024-10-17T15:04:08+00:00
version | 2.4.0b1
class | feature
edition | cre
component | omd
level | 1
compatible | yes
The site Apache process writes to `var/log/apache/access_log`.
With this Werk, the log format includes the time taken to serve the request, in microseconds.
Title: Opsgenie: use Checkmk CA trust store
Class: fix
Compatible: compat
Component: notifications
Date: 1729170956
Edition: cre
Level: 1
Version: 2.2.0p36
The Opsgenie notification plugin will now use the Checkmk CA trust store
(<code>~/var/ssl/ca-certificates.crt</code>) if an HTTP proxy is configured.
[//]: # (werk v2)
# Stop showing longer time ranges in size_trend
key | value
---------- | ---
date | 2024-10-18T07:12:43+00:00
version | 2.3.0p19
class | fix
edition | cre
component | checks
level | 1
compatible | yes
In case you're trend calculation (using `size_trend`) has a very small growth rate, your check may have displayed a very high "Time left until full".
We now stop showing the message if the time until your resource is full is more than 10 years.
[//]: # (werk v2)
# Opsgenie: use Checkmk CA trust store
key | value
---------- | ---
date | 2024-10-17T13:15:56+00:00
version | 2.3.0p19
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
The Opsgenie notification plugin will now use the Checkmk CA trust store
(`~/var/ssl/ca-certificates.crt`) if an HTTP proxy is configured.
[//]: # (werk v2)
# Stop showing longer time ranges in size_trend
key | value
---------- | ---
date | 2024-10-18T07:12:43+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
In case you're trend calculation (using `size_trend`) has a very small growth rate, your check may have displayed a very high "Time left until full".
We now stop showing the message if the time until your resource is full is more than 10 years.