You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Recommendations related to [virtual hosts, users and permissions](#users-and-permissions)
47
47
*[Monitoring and resource usage](#monitoring-and-resource-usage)
48
-
*[Per-virtual host and per-user limits](#limits)
48
+
*[Configurable limits](#limits)
49
49
*[Security](#security)
50
50
*[Clustering](#clustering) and multi-node deployments
51
51
*[Application-level](#apps) practices and considerations
@@ -306,17 +306,18 @@ It is highly recommended that logs of all RabbitMQ nodes and applications (when
306
306
and aggregated. Logs can be crucially important in investigating unusual system behaviour.
307
307
308
308
309
-
## Per-Virtual Host and Per-User Resource Limits {#limits}
309
+
## Configurable Limits {#limits}
310
310
311
-
It is possible to [limit the maximum number of concurrent connections and queues](./vhosts#limits) a virtual host will
312
-
allow the users to open (declare).
311
+
Production clusters should adopt at least some configurable limits
312
+
that act as guard rails that prevent poorly behaved
313
+
applications from leaking resources and affecting cluster stability.
313
314
314
-
These limits can be used as guard rails in environments where applications
315
-
cannot be trusted and monitored in detail, for example, when RabbitMQ clusters
316
-
are offered as a service.
315
+
RabbitMQ provides a comprehensive set of [configurable limits](./limits) at multiple levels: from cluster-wide to [per virtual host](./vhosts#limits) and [per user](./user-limits), down to individual connections, channels, queues, and streams.
317
316
318
-
Similarly, it is possible to [configure concurrent connection and channel limits
319
-
for individual users](./user-limits).
317
+
Adopting these limits is particularly important in multi-tenant environments or when RabbitMQ is offered as a service.
318
+
Even in single-tenant deployments, limits help prevent resource leaks and provide early detection of application issues.
319
+
320
+
Consult the [Configurable Limits guide](./limits) for detailed information on available limits and how to configure them.
0 commit comments