From ffaf395994569d5b1c4628f894d977ac34a62b79 Mon Sep 17 00:00:00 2001 From: Michal Kuratczyk Date: Tue, 15 Apr 2025 18:46:28 +0200 Subject: [PATCH 1/2] [skip-ci] Additional Prometheus-related release notes (cherry picked from commit b03b3cabf3ce7493aec5d0caf26cb4e75fd129de) --- release-notes/4.1.0.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/release-notes/4.1.0.md b/release-notes/4.1.0.md index 0e1bf96f42f9..6b9ce94aafc3 100644 --- a/release-notes/4.1.0.md +++ b/release-notes/4.1.0.md @@ -408,6 +408,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) + * `queue_identity_info` metric is now available + + `queue_identity_info` metric is exposed, with labels describing 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` 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. + + GitHub issue: [#13218](https://github.com/rabbitmq/rabbitmq-server/pull/13218) + ### Grafana Dashboards #### Bug Fixes From 4506725b7d8af67cb170d2025e5ce9cc94ddfe78 Mon Sep 17 00:00:00 2001 From: Michael Klishin Date: Tue, 15 Apr 2025 13:17:54 -0400 Subject: [PATCH 2/2] 4.1.0 release notes edits (cherry picked from commit 4d162257b4591c3d761ac81596a33d40fa472b22) --- release-notes/4.1.0.md | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/release-notes/4.1.0.md b/release-notes/4.1.0.md index 6b9ce94aafc3..540e201c2bfd 100644 --- a/release-notes/4.1.0.md +++ b/release-notes/4.1.0.md @@ -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`. + + The label allows operators differntiate between metrics scraped from different + RabbitMQ endpoints (the per-object one and the aggregated one). - `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. + 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)