From bcb080179c941c090499f6b16f5561b10c410cd5 Mon Sep 17 00:00:00 2001
From: Michael Klishin
+ 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
+ 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.
+
When DELETEing a queue you can add the query string
@@ -990,19 +1014,6 @@
+ 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 guide: TLS
+
+ 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
+
+ Set or delete per-vhost limit for
+ Relevant documentation guide: Virtual Hosts
+ The list of stream consumers in a specific virtual host.
Requires the
+ The list of feature flags.
+
+ Relevant documentation guide: Feature Flags
+
The list of deprecated features.
+
+ Relevant documentation guide: Feature Flags
+
The list of deprecated features currently being used.
+
+ Relevant documentation guide: Feature Flags
+ Reference
/api/queues
- A list of all queues returning a reduced set of fields. Use pagination parameters to filter queues.
- 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.
+
+
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.
+
@@ -505,7 +514,14 @@
Reference
/api/queues/detailed
- A list of all queues containing all available information about the queues. Use pagination parameters to filter queues.
+
+
@@ -514,7 +530,15 @@
Reference
/api/queues/vhost
- A list of all queues in a given virtual host. Use pagination parameters to filter queues.
+
+
- X
@@ -524,7 +548,7 @@ Reference
/api/queues/vhost/name
An individual queue. To PUT a queue, you will need a body looking something like this:
-
{"auto_delete":false,"durable":true,"arguments":{},"node":"rabbit@smacmullen"}
+ {"auto_delete":false,"durable":true,"arguments":{},"node":"rabbit@node.hostname"}
All keys are optional.
Reference
pattern
and definition
are mandatory, priority
and apply-to
are optional.
-
X
-
-
-
- /api/aliveness-test/vhost
-
- Declares a test queue on the target node, then publishes and consumes a
- message. Intended to be used as a very basic health check.
- Responds a 200 OK if the check succeeded,
- otherwise responds with a 503 Service Unavailable.
-
-
X
@@ -1010,8 +1021,14 @@ Reference
/api/health/checks/alarms
- Responds a 200 OK if there are no alarms in effect in the cluster,
- otherwise responds with a 503 Service Unavailable.
+
@@ -1021,8 +1038,13 @@
Reference
/api/health/checks/local-alarms
- Responds a 200 OK if there are no local alarms in effect on the target node,
- otherwise responds with a 503 Service Unavailable.
+
@@ -1033,15 +1055,32 @@
Reference
/api/health/checks/certificate-expiration/within/unit
+
+
+ Do not use this health check if some of these assumptions are not true.
+
@@ -1051,7 +1090,7 @@
@@ -1084,10 +1123,15 @@ Reference
/api/health/checks/port-listener/port
- Responds a 200 OK if there is an active listener on the give port,
+ Responds a 200 OK if there is an active listener on the given port,
otherwise responds with a 503 Service Unavailable.
Reference
/api/health/checks/node-is-quorum-critical
- 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.
+
@@ -1117,11 +1161,15 @@
Reference
/api/vhost-limits/vhost/name
- 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}'
+ 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}'
+
+
@@ -1142,7 +1190,7 @@
Reference
X
/api/rebalance/queues
- Rebalances all queues in all vhosts. This operation is asynchronous therefore please check
+ Rebalances all queues in all vhosts. This operation is asynchronous therefore please check
the RabbitMQ log file for messages regarding the success or failure of the operation.
@@ -1306,9 +1354,10 @@ curl -4u 'guest:guest' -XPOST localhost:15672/api/rebalance/queues/
Reference
/api/stream/consumers/vhost
- The list of stream consumers in a specific virtual host.
-
+ rabbitmq_stream_management
plugin to be enabled.
+
@@ -1318,7 +1367,12 @@
Reference
/api/feature-flags
- The list of feature flags.
+
@@ -1328,7 +1382,12 @@
Reference
/api/deprecated-features
+
@@ -1338,7 +1397,12 @@
From 5c7d643ab341e5f8f5be4a14b82aa4a7aaf3991d Mon Sep 17 00:00:00 2001
From: Michael Klishin Reference
/api/deprecated-features/used
+
Reference
The list of deprecated features.
- Relevant documentation guide: Feature Flags + Relevant documentation guide: Deprecated Features
@@ -1401,7 +1401,7 @@- Relevant documentation guide: Feature Flags + Relevant documentation guide: Deprecated Features