From fb83b0dbbf6d7036e16686a163eb164c3912393a Mon Sep 17 00:00:00 2001 From: Andrea Ieri Date: Fri, 29 Mar 2019 17:49:52 +0100 Subject: [PATCH] Clarify how to use queue_thresholds This commit clarifies syntax and semantics of the queue thresholds. * both yaml multi-line arrays and lists of lists are supported * explain that the order of the values does matter, especially if using wildcards Change-Id: I31ff1bfa94a708a4f7469bb3a9a5dbca33bb3607 Closes-Bug: 1822547 --- config.yaml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/config.yaml b/config.yaml index 4742027e..1b6f965a 100644 --- a/config.yaml +++ b/config.yaml @@ -95,11 +95,16 @@ options: type: string default: "[['\\*', '\\*', 100, 200]]" description: | - List of RabbitMQ queue size check thresholds. Interpreted as YAML - in format [, , , ] + List of RabbitMQ queue size check thresholds. Interpreted as YAML in + format [, , , ] + Per-queue thresholds can be expressed as a multi-line YAML array: - ['/', 'queue1', 10, 20] - ['/', 'queue2', 200, 300] + Or as a list of lists: + [['/', 'queue1', 10, 20], ['/', 'queue2', 200, 300]] Wildcards '*' are accepted to monitor all vhosts and/or queues. + In case of multiple matches, only the first will apply: wildcards should + therefore be used last in order to avoid unexpected behavior. connection-backlog: type: int default: @@ -292,4 +297,4 @@ options: TTL in MS for notification queues in the openstack vhost. Defaults to 1 hour, but can be tuned up or down depending on deployment requirements. This ensures that any un-consumed notifications don't build up over - time, causing disk capacity issues. \ No newline at end of file + time, causing disk capacity issues.