action check-queues does not report the size of queues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack RabbitMQ Server Charm |
In Progress
|
Low
|
Robert Gildein |
Bug Description
When running 'juju run-action rabbitmq-server/0 check-queues' the output is a list of queues from the vhost, but this does not include the sizes of the queues as the code appears to intend at https:/
It would be very helpful for environments where ssh is blocked to have this additional queue depth 'size' in the returned output.
After running juju run-action rabbitmq-server/0 check-queues queue-depth=1, I get the following output:
results:
outcome: Success
output: '[''alarm.
status: completed
timing:
completed: 2019-07-01 19:03:52 +0000 UTC
enqueued: 2019-07-01 19:03:41 +0000 UTC
started: 2019-07-01 19:03:50 +0000 UTC
I believe the "list()" wrapper around the dict-comprehension may be returning only the keys of the dictionary, rather than the intended [queue, size, queue, size, queue, size...] result.
Changed in charm-rabbitmq-server: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in charm-rabbitmq-server: | |
status: | Triaged → In Progress |
assignee: | nobody → Robert Gildein (rgildein) |
Apart from this, there should be a juju config parameter to limit the size of certain (unconsumed) queues. "notification-ttl" limits per time, but a queue could grow too much and affect rest of (consumed) queues performance.