Comments (8)
I can take care of this issue. I'll be waiting to hear core dev team opinion on whether the strategy suggested on #11217 (comment) should be taken.
from rabbitmq-server.
It sounds like a good approach to me
from rabbitmq-server.
We discuss this every now and then and overall I think we agree - we expose too many metrics and the high-cardinality metrics shouldn't be there at all probably. As always, it's a matter of time and effort required to clean this up. Perhaps you'd be interested in contributing this? As a start, I'd say the exact list of changes would be nice. Your overall description is good, but I'm thinking more about a TODO list:
- metric a_b_c should not have label L
- metric x_y_z should be removed altogether
- ...
This would allow us to discuss individual changes if needed and would guide the implmentation of these changes.
from rabbitmq-server.
As far as I'm concerned, the only metric label that causes issues here is channel
, so all metrics that only have this label should be removed (I've verified that all of them are already available aggregated in /metrics
), all metrics that also have other labels should have this label removed (so they're grouped by exchange/queue).
Alternatively, metrics that make sense without this label (see below) could be exposed under another name without the channel
label, keeping the existing ones, however I don't really see a use case where it makes sense to look at per-channel metrics (as the channel id is basically meaningless as it is).
In some cases (like people creating temporary queues with UUIDs in the name or something) other metrics could cause high cardinality as well, but in that case, those metrics can be easily dropped in Prometheus using metric_relabel_configs
.
(Documentation for reference: https://www.rabbitmq.com/docs/prometheus#detailed-endpoint)
Listing each metric individually doesn't make sense as it always affects entire groups of metrics:
Metrics including channel
that make sense without it (channel
should be removed):
- everything grouped under
channel_exchange_metrics
- everything grouped under
channel_queue_metrics
- everything grouped under
channel_queue_exchange_metrics
Metrics including channel
that don't make sense without it (can be removed altogether as available aggregated through /metrics
):
- everything grouped under
connection_coarse_metrics
- everything grouped under
connection_metrics
- everything grouped under
channel_metrics
- everything grouped under
channel_process_metrics
from rabbitmq-server.
Thanks. As I said - I think it's a valid request and it concurs our own experience. Therefore, I will leave this open but note that we are not actively working on this at this time. Contributions would be very much appreciated. It's mostly about deleting stuff, so shouldn't be too hard. :)
from rabbitmq-server.
If I was an Erlang dev I'd be happy to contribute code, but getting used to Erlang and setting up a dev environment to test the changes is too much for me right now I think.
Maybe I'll get annoyed enough at the lack of metrics I'll take a look at it some day 😅
from rabbitmq-server.
Coming up with a list of specific actionable changes (like in #11217 (comment) but I assume the list is not necessarily complete) is considered to be a partial contribution by our team.
Those seven is a good starting point. Well, at least the first four, I am less certain about removing entire metrics as it is always particularly hard to remove features/data. But for 4.x, that's certainly a good idea.
from rabbitmq-server.
My suggestion to make this a non-breaking change would be to add these metrics under new names (as all of them except rabbitmq_detailed_queue_messages_published_total
contain channel
in the metric name, which doesn't make sense if it's not channel-specific anymore) and group them in new categories:
- group
queue_metrics
(already exists)rabbitmq_detailed_queue_get_ack_total
rabbitmq_detailed_queue_get_total
rabbitmq_detailed_queue_messages_delivered_ack_total
rabbitmq_detailed_queue_messages_delivered_total
rabbitmq_detailed_queue_messages_redelivered_total
rabbitmq_detailed_queue_messages_acked_total
rabbitmq_detailed_queue_get_empty_total
- group
exchange_metrics
(new)rabbitmq_detailed_exchange_messages_published_total
rabbitmq_detailed_exchange_messages_confirmed_total
rabbitmq_detailed_exchange_messages_unroutable_returned_total
rabbitmq_detailed_exchange_messages_unroutable_dropped_total
- group
queue_exchange_metrics
(new)rabbitmq_detailed_queue_exchange_messages_published_total
this doesn't cause name collisions when exporting all metrics and in the 4.x release, all per-channel metrics could be removed.
from rabbitmq-server.
Related Issues (20)
- Streams: consider allowing non-numerical values for publishingId HOT 3
- Log tls handshake timeouts HOT 1
- Include x-death header in Stream messages HOT 1
- 4.x: reduce default maximum message size further (e.g. to 64 or 50 MiB) HOT 13
- Publish `amqp_client` 3.13.x GA versions to hex
- Emit event if configured queue length is reached
- Don't close connection if channel without finished publish is closed HOT 3
- Logout action does not fully work on management UI
- Consul peer discovery: nodes can leave behind a service record in case of an unresolvable address HOT 2
- Output "last write" time for Streams
- Peer Discovery with DNS record wont cluster HOT 2
- 3.13.2: "x-opt-rabbitmq-received-time" only available for new messages HOT 5
- Allow Khepri post-migration step to not delete certain files or dirs HOT 1
- 3.12.x: AMQP 1.0 connection authentication fails with an external HTTP auth service HOT 11
- k8s peer discovery : rabbitmq pods are booting as a standalone nodes on ipv6 environment. HOT 4
- prometheus.filter_aggregated_queue_metrics_pattern has no effect HOT 3
- Shovels cant be deleted if they dont connect HOT 2
- rabbit_heartbeat.erl compile error with erlang OTP 27 HOT 2
- x-death header count is no longer incremented from RabbitMQ version 3.13.0+ HOT 14
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rabbitmq-server.