Comment 2 for bug 1939084

Reviewed: https://review.opendev.org/c/openstack/charm-rabbitmq-server/+/803669
Committed: https://opendev.org/openstack/charm-rabbitmq-server/commit/242167b6bad190dd7aa2b885272906551d390c8a
Submitter: "Zuul (22348)"
Branch: master

commit 242167b6bad190dd7aa2b885272906551d390c8a
Author: Julien Thieffry <email address hidden>
Date: Fri Aug 6 02:16:54 2021 +0000

    Display busiest queues in check_queues NRPE plugin

    When invoking the check_rabbitmq_queues script with wildcards for vhost
    and/or queue parameters, script output does not reflect precisely which
    queues are having a high number of oustanding messages as information is
    consolidated under the wildcard.

    This change fixes this behaviour by adding a new charm configuration
    parameter which allows the user to specify the number of busiest queues,
    n, to display should the check_rabbitmq_queues script reports any
    warnings or errors. The default, n=0, keeps the current script output.
    This option is applicable regardless of the vhost:queue combination but
    is specifically relevant when wildcards are passed as arguments.

    Implementation displays the first n items in the stats list re-organized
    in decreasing message count order.

    Closes-Bug: #1939084
    Change-Id: I5a32cb6bf37bd2a0f30861eace3c0e6cb5c2559d