Skip to content

Commit 182d138

Browse files
kleinskikleinski
authored
Merge branch 'Checkmk:master' into master
2 parents 6dda15f + 1ffc8c9 commit 182d138

578 files changed

Lines changed: 17920 additions & 9871 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.werks/15338.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
[//]: # (werk v2)
2+
# Improve HTML of 503 error document
3+
4+
key | value
5+
---------- | ---
6+
date | 2024-07-22T08:37:18+00:00
7+
version | 2.5.0b1
8+
class | fix
9+
edition | cre
10+
component | wato
11+
level | 1
12+
compatible | yes
13+
14+
The old error document had two flaws:
15+
16+
1. it was no valid HTML
17+
2. it contained some IE compatibility comment
18+
19+
Both issues are now resolved.
20+
21+
Only fresh installations will be affected, or if you manually
22+
call `omd update-apache-config SITE`.

‎.werks/17458.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
[//]: # (werk v2)
2+
# Fix postgres plugin crash if no data is available
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-22T03:39:37+00:00
7+
version | 2.5.0b1
8+
class | fix
9+
edition | cre
10+
component | checks
11+
level | 1
12+
compatible | yes
13+
14+
The postgres plugin collects data for services by running sql queries for it's sections.
15+
It can happen that a query does not yield a result, i.e. looking for long running queries.
16+
If no data was found on for a section our parser used to crash, generating a crash-report with the following error.
17+
18+
```
19+
File "/omd/sites/display/lib/python3/cmk/checkengine/sectionparser.py", line 121, in _parse_raw_data
20+
return parse_function(list(raw_data))
21+
File "/omd/sites/display/lib/python3/cmk/plugins/lib/postgres.py", line 26, in parse_dbs
22+
headers = next(lines)[1:]
23+
```
24+
25+
If our parser crashes it can happen that we do not discovery the services corresponding to the agent sections.
26+
The parsing is been fixed now.
27+
If you have been affected new services may appear on host monitoring postgres.

‎.werks/17959.md‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
[//]: # (werk v2)
2+
# REST-API: Move rule audit log messages
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-19T13:14:37+00:00
7+
version | 2.5.0b1
8+
class | fix
9+
edition | cre
10+
component | rest-api
11+
level | 1
12+
compatible | yes
13+
14+
This werk changes the audit log entries that generate when calling the
15+
"Move a rule to a specific location" endpoint.
16+
17+
Specifically, when the rule gets moved to a different folder the following
18+
message is used:
19+
`Moved rule ... of ruleset "..." from folder "x" to position #0 in folder "y"`
20+
21+
Otherwise, the following message is used (which matches the GUI):
22+
`Moved rule ... from position #0 to #1 in ruleset "..." in folder "..."`
23+
24+
Previously, the REST-API incorrectly reported the move to always be to the
25+
"top" of the folder. This is now fixed with this werk.

‎.werks/18066.md‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
[//]: # (werk v2)
2+
# Set proper alias for "no_permissions" user role
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-23T15:57:28+00:00
7+
version | 2.5.0b1
8+
class | fix
9+
edition | cre
10+
component | wato
11+
level | 1
12+
compatible | yes
13+
14+

‎.werks/18177.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
[//]: # (werk v2)
2+
# OTel: Merge resource metric datapoints across multiple datasets
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-18T16:07:20+00:00
7+
version | 2.5.0b1
8+
class | fix
9+
edition | cce
10+
component | checks
11+
level | 1
12+
compatible | yes
13+
14+
Previously we would only consider the latest received resource metric dataset during checking.
15+
Not all producers will send the complete set of datapoints in every resource metric dataset.
16+
This would lead to services flapping or the status UNKNOWN.
17+
18+
With this Werk metrics will now be merged before checking, as to consider all datapoints.

‎.werks/18178.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
[//]: # (werk v2)
2+
# otel: Improve histogram value calculation
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-19T15:32:15+00:00
7+
version | 2.5.0b1
8+
class | feature
9+
edition | cce
10+
component | checks
11+
level | 1
12+
compatible | yes
13+
14+
Improve the value used for metrics for histograms and exponential histograms by using the average value (sum/count)
15+
instead of just the count value.
16+

‎.werks/18179.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
[//]: # (werk v2)
2+
# datadog: Allow arbitraty service level titles
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-20T14:03:01+00:00
7+
version | 2.4.0p11
8+
class | fix
9+
edition | cre
10+
component | checks
11+
level | 1
12+
compatible | yes
13+
14+
When creating custom service levels and creating a datadog integration rule,
15+
it could happen that the rule cannot be created or saved due
16+
to the name of the service level.
17+
18+
The same also applies when migrating from 2.3.0 to 2.4.0.

‎.werks/18285.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
[//]: # (werk v2)
2+
# activate_changes: load only the changes for the sites selected
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-22T11:48:41+00:00
7+
version | 2.5.0b1
8+
class | fix
9+
edition | cre
10+
component | rest-api
11+
level | 1
12+
compatible | yes
13+
14+
When activating changes via the REST-API, you have the option to select
15+
the specific sites where you want the changes to be activated. However,
16+
the changes that are loaded, which were also returned in the response,
17+
were for all sites. This werk addresses the issue by only loading the
18+
changes for the sites selected. If no sites are selected, all sites'
19+
changes will be loaded.
20+

‎.werks/18299.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
[//]: # (werk v2)
2+
# postfix_mailq and nullmailer_mailq: Fix for mail queue size
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-18T11:33:24+00:00
7+
version | 2.5.0b1
8+
class | fix
9+
edition | cre
10+
component | checks
11+
level | 1
12+
compatible | yes
13+
14+
The reported mail queue size was wrong.
15+
16+
Previously, the agent reported queue size in kilobytes, but the Checkmk plugin read it as bytes. This caused inaccuracies.
17+
18+
With this werk, the agent consistently reports the size in bytes, so the plugin reads it correctly. Your mail queue metrics will be accurate again.

‎.werks/18350.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
[//]: # (werk v2)
2+
# Commandline interface: Support '--detect-sections' when operating on clusters
3+
4+
key | value
5+
---------- | ---
6+
date | 2025-08-21T10:56:42+00:00
7+
version | 2.5.0b1
8+
class | feature
9+
edition | cre
10+
component | checks
11+
level | 1
12+
compatible | yes
13+
14+
The commandline flag `--detect-sections` now also restricts the used sections
15+
when applied to a cluster.

0 commit comments

Comments
 (0)