I first thought we could log some data like:
$ rabbitmqctl list_queues name durable owner_pid messages_ready
messages_unacknowledged messages messages_ready_ram messages_unacknowledged_ram
messages_ram messages_persistent message_bytes message_bytes_ram
message_bytes_persistent memory state
via cron.
But then we don't know what exactly we look for yet.
I found that the service oriented
$ rabbitmqctl report
has all the data you could want.
If we don't gather it too often, and maybe even gzip it
In my test it had 7.5k raw and 2.6k zipped.
A real case might be bigger, but if we do that hourly or so we would see which
element grows over time.
Especially interesting is the definition of the base memory counter:
memory Bytes of memory consumed by the Erlang process associated with the
queue, including
stack, heap and internal structures.
Yeah could be useful next time this happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772236
Title:
rabbit died and everything else died
To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1772236/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
