root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity

4.1.0 release notes edits

This commit is contained in:
Michael Klishin 2025-04-15 13:17:54 -04:00
parent b03b3cabf3
commit 4d162257b4
No known key found for this signature in database
GPG Key ID: FF4F6501646A9C9A
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
release-notes/4.1.0.md
View File

@ -97,9 +97,9 @@ This release series supports upgrades from `4.0.x` and `3.13.x`.
[Blue/Green Deployment](https://www.rabbitmq.com/docs/blue-green-upgrade)-style upgrades are avaialble for migrations
from RabbitMQ `3.12.x` series.
### Required Feature Flags
### New Required Feature Flags
None/TBD.
None. The required feature flag set is the same as in `4.0.x`.
### Mixed version cluster compatibility
@ -407,19 +407,21 @@ This section can be incomplete and will be expanded as 4.1 approaches its releas
GitHub issue: [#12765](https://github.com/rabbitmq/rabbitmq-server/pull/12765)
* New metric: `queue_identity_info`.
* `queue_identity_info` metric is now available
`queue_identity_info` metric is exposed, with labels describing the type
`queue_identity_info` is a new metric whose labels describe the type
of the queue and its membership status (leader/follower) on the scraped node.
GitHub issue: [#13583](https://github.com/rabbitmq/rabbitmq-server/pull/13583)
* `rabbitmq_identity_info` now contains `rabbitmq_endpoint` label
* `rabbitmq_identity_info` now includes a new label, `rabbitmq_endpoint`.
`rabbitmq_identity_info` metric has an additional label that allows to differntiate between
metrics scraped from different RabbitMQ endpoints. Some metric names are the same
when scraped from `/metrics` and `/metrics/per-object`, which can lead to duplicates.
The label allows operators differntiate between metrics scraped from different
RabbitMQ endpoints (the per-object one and the aggregated one).
Since some metric names are identical regardless of whether they were
scraped from `/metrics` and `/metrics/per-object`, scraping both endpoints could lead to
duplicates and confusion.
GitHub issue: [#13218](https://github.com/rabbitmq/rabbitmq-server/pull/13218)