Add identity request management in gateway

versioned_docs/version-8.4/self-managed/zeebe-deployment/configuration/gateway.md

@@ -354,3 +354,9 @@ If you are using an embedded gateway, refer to the [broker configuration guide](
 multiTenancy:
   enabled: true
 ```
+
+### Experimental configuration
+
+See the experimental section of the [gateway.yaml.template](https://github.com/camunda/camunda/blob/stable/8.4/dist/src/main/config/gateway.yaml.template#L298).
+
+Be aware that all configuration properties which are part of the experimental section are subject to change and can be dropped at any time.

versioned_docs/version-8.4/self-managed/zeebe-deployment/operations/backpressure.md

@@ -12,6 +12,13 @@ If the broker keeps accepting new requests from the client, the backlog increase
 
 To avoid such problems, Zeebe employs a backpressure mechanism. When the broker receives more requests than it can process with an acceptable latency, it rejects some requests (see [technical error handling](/apis-tools/zeebe-api/technical-error-handling.md)).
 
+:::note
+When [multi-tenancy](./../../concepts/multi-tenancy.md) is enabled in Camunda 8, a large number of concurrent requests
+may also lead to issues with Camunda Identity. In such cases, it is recommended to enable and configure the management of
+Identity requests in the Zeebe Gateway. This allows Zeebe to employ a backpressure mechanism against these requests.
+For more information, see the Zeebe Gateway [experimental configuration documentation](./../configuration/gateway.md#experimental-configuration).
+:::
+
 ### Terminology
 
 - **RTT** - Round-Trip Time, known as the time between when the request is accepted by the broker and when the response to the request is sent back to the gateway.

versioned_docs/version-8.5/self-managed/zeebe-deployment/configuration/gateway.md

@@ -431,3 +431,9 @@ If you are using an embedded gateway, refer to the [broker configuration guide](
 multiTenancy:
   enabled: true
 ```
+
+### Experimental configuration
+
+See the experimental section of the [gateway.yaml.template](https://github.com/camunda/camunda/blob/stable/8.5/dist/src/main/config/gateway.yaml.template#L298).
+
+Be aware that all configuration properties which are part of the experimental section are subject to change and can be dropped at any time.

versioned_docs/version-8.5/self-managed/zeebe-deployment/operations/backpressure.md

@@ -12,6 +12,13 @@ If the broker keeps accepting new requests from the client, the backlog increase
 
 To avoid such problems, Zeebe employs a backpressure mechanism. When the broker receives more requests than it can process with an acceptable latency, it rejects some requests (see [technical error handling](/apis-tools/zeebe-api/technical-error-handling.md)).
 
+:::note
+When [multi-tenancy](./../../concepts/multi-tenancy.md) is enabled in Camunda 8, a large number of concurrent requests
+may also lead to issues with Camunda Identity. In such cases, it is recommended to enable and configure the management of
+Identity requests in the Zeebe Gateway. This allows Zeebe to employ a backpressure mechanism against these requests.
+For more information, see the Zeebe Gateway [experimental configuration documentation](./../configuration/gateway.md#experimental-configuration).
+:::
+
 ### Terminology
 
 - **RTT** - Round-Trip Time, known as the time between when the request is accepted by the broker and when the response to the request is sent back to the gateway.

versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/gateway.md

@@ -484,3 +484,9 @@ If you are using an embedded gateway, refer to the [broker configuration guide](
 multiTenancy:
   enabled: true
 ```
+
+### Experimental configuration
+
+See the experimental section of the [gateway.yaml.template](https://github.com/camunda/camunda/blob/stable/8.6/dist/src/main/config/gateway.yaml.template#L298).
+
+Be aware that all configuration properties which are part of the experimental section are subject to change and can be dropped at any time.

versioned_docs/version-8.6/self-managed/zeebe-deployment/operations/backpressure.md

@@ -19,6 +19,13 @@ control write rate limits](/docs/self-managed/operational-guides/configure-flow-
 be used with static write rate limits or throttling. This prevents the
 partition from building an excessive backlog of records not exported.
 
+:::note
+When [multi-tenancy](./../../concepts/multi-tenancy.md) is enabled in Camunda 8, a large number of concurrent requests
+may also lead to issues with Camunda Identity. In such cases, it is recommended to enable and configure the management of
+Identity requests in the Zeebe Gateway. This allows Zeebe to employ a backpressure mechanism against these requests.
+For more information, see the Zeebe Gateway [experimental configuration documentation](./../configuration/gateway.md#experimental-configuration).
+:::
+
 ### Terminology
 
 - **RTT** - Round-Trip Time, known as the time between when the request is accepted by the broker and when the response to the request is sent back to the gateway.