enable_queue_totals=true can be used in combination with the
- disable_stats=true parameter to return a reduced set of fields and significantly
- reduce the amount of data returned by this endpoint. That in turn can significantly reduce
- CPU and bandwidth footprint of such requests.
+ + A list of all queues across all virtual hosts returning a reduced set of fields. +
++ Use pagination parameters to filter queues, + otherwise this endpoint can produce very large JSON responses and waste a lot of bandwidth and CPU resources. +
+
+ The parameter enable_queue_totals=true can be used in combination with the
+ disable_stats=true parameter to return a reduced set of fields and significantly
+ reduce the amount of data returned by this endpoint. That in turn can significantly reduce
+ CPU and bandwidth footprint of such requests.
+
+ A list of all queues containing all available information about the queues (over 50 fields per queue). +
++ Use pagination parameters to filter queues, + otherwise this endpoint can produce very large JSON responses and waste a lot of bandwidth and CPU resources. +
+ A list of all queues in the given virtual host containing all available information about the queues (over 50 fields per queue).. +
++ Use pagination parameters to filter queues, + otherwise this endpoint can produce very large JSON responses and waste a lot of bandwidth and CPU resources. +
+{"auto_delete":false,"durable":true,"arguments":{},"node":"rabbit@smacmullen"}
+ {"auto_delete":false,"durable":true,"arguments":{},"node":"rabbit@node.hostname"}
All keys are optional.
When DELETEing a queue you can add the query string @@ -990,19 +1014,6 @@
pattern and definition are mandatory, priority and apply-to are optional.
+ Responds a 200 OK if there are no alarms in effect in the cluster, + otherwise responds with a 503 Service Unavailable. +
+ ++ Relevant documentation guide: Resource Alarms +
+ Responds a 200 OK if there are no local alarms in effect on the target node, + otherwise responds with a 503 Service Unavailable. +
++ Relevant documentation guide: Resource Alarms +
- Checks the expiration date on the certificates for every listener configured to use TLS. + Checks the expiration date of every certificate found in the PEM certificate bundles used by + all TLS-enabled listeners on the node, regardless of the "type" of the certificate (leaf/server identity, + intermediary or any CA). +
+Responds a 200 OK if all certificates are valid (have not expired), otherwise responds with a 503 Service Unavailable.
++ This health assumes that + +
Valid units: days, weeks, months, years. The value of the within argument is the number of units. So, when within is 2 and unit is "months", the expiration period used by the check will be the next two months.
++ Relevant documentation guides: TLS, Encrypted Inter-node Communication +
+ Checks if there are quorum queues with minimum online quorum (queues that + would lose their quorum and availability if the target node is shut down). + Responds a 200 OK if there are no such quorum queues, + otherwise responds with a 503 Service Unavailable. +
++ Relevant documentation guide: Quorum Queues +
vhost. The name URL path element
- refers to the name of the limit (max-connections, max-queues).
- Limits are set using a JSON document in the body: {"value": 100}. Example
- request:
- curl -4u 'guest:guest' -H 'content-type:application/json' -X PUT localhost:15672/api/vhost-limits/my-vhost/max-connections -d '{"value": 50}'
+
+ Set or delete per-vhost limit for vhost. The name URL path element
+ refers to the name of the limit (max-connections, max-queues).
+ Limits are set using a JSON document in the body:
{"value": 100}. Example request:
+ curl -4u 'guest:guest' -H 'content-type:application/json' -X PUT localhost:15672/api/vhost-limits/my-vhost/max-connections -d '{"value": 50}'
+
+ + Relevant documentation guide: Virtual Hosts +
curl -4u 'guest:guest' -XPOST localhost:15672/api/rebalance/queues/
The list of stream consumers in a specific virtual host.
+
Requires the rabbitmq_stream_management plugin to be enabled.
+
+ The list of feature flags. +
++ Relevant documentation guide: Feature Flags +
The list of deprecated features. +
++ Relevant documentation guide: Deprecated Features +
The list of deprecated features currently being used. +
++ Relevant documentation guide: Deprecated Features +