-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
rabbitmq_queue_exchange_messages_published_total
in /metrics/per-object
has a duplicate vhost
label
#12347
Comments
Possibly relevant, our [
{
rabbit,
[
{ loopback_users, [] }
]
},
{
rabbitmq_management,
[
{ load_definitions, "/etc/rabbitmq/definitions.json" }
]
}
].
{
"users": [
{
"name": "test",
"password_hash": "<redacted>",
"hashing_algorithm": "rabbit_password_hashing_sha256",
"tags": "administrator,monitoring"
}
],
"vhosts": [
{
"name": "/"
}
],
"permissions": [
{
"user": "test",
"vhost": "/",
"configure": ".*",
"write": ".*",
"read": ".*"
}
],
"topic_permissions": [],
"parameters": [],
"global_parameters": [],
"policies": [],
"queues": [],
"exchanges": [],
"bindings": []
} |
Thank you. This looks like a blank node's config with a pre-configured user for remote access. I was able to reproduce with a blank node from
|
I think this is related to #11559 |
I noticed that |
is there ever a case where a queue's vhost and the exchange's vhost would be different? |
@pschichtel no, by definition, entities in different virtual hosts cannot be bound together. |
The labels may simply reflect the fact that there are two associated entities with certain metric samples, and they both belong to a virtual host. Ideally it should be just |
A fix was contributed by @LoisSotoLopez in #12364, merged in #12373 and (will be) backported in #12378. |
Describe the bug
Prometheus seems to choke on duplicate labels:
Note how
vhost
appears twice here:Versions used:
This seems to be a regression compared to 3.13.7 which we upgraded from.
Reproduction steps
rabbitmq_prometheus
pluginrabbitmq_queue_exchange_messages_published_total
metric is included/metrics/per-object
endpointExpected behavior
There should not be duplicate labels.
Additional context
No response
The text was updated successfully, but these errors were encountered: