Prometheus Plugin "rabbitmq_disk_space_available_limit_bytes " parse error #2826
Replies: 5 comments 1 reply
-
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
The limit can be provided as a number of bytes or as an information unit ( |
Beta Was this translation helpful? Give feedback.
-
Using the following config file: disk_free_limit.absolute = 3GB and the following effective configuration setting (
the metrics returned by the Prometheus scraping endpoint is
which for me returns |
Beta Was this translation helpful? Give feedback.
-
The metric is collected as a computed value. The limit is computed once when free disk space monitor is started on the node. So the only way this value can change is if the limit is updated somehow. Node log files will contain traces of node restarts and limit changes via CLI tools. Without this information I don't know how this can be reproduced. We also haven't seen this reported elsewhere. |
Beta Was this translation helpful? Give feedback.
-
thanks you helped me greatly.. server where not restarted, the only changge was taht the dyntrace oneagent was shutdown cli output:
logs:
|
Beta Was this translation helpful? Give feedback.
-
hi
used versions: RabbitMQ 3.8.9 Erlang 23.2.2 Prometheus 2.23.0
Prometheus plugin seems to have a conversion problem with "rabbitmq_disk_space_available_limit_bytes", on startuo everything was fine 3GB of the config was converted to bytes... but after 4 days the metric turned from float to string and couldnt be parsed by prometheus anymore making all the metrics of rabbitmq unreachable.
Beta Was this translation helpful? Give feedback.
All reactions