Kibana search:allowConcurrentSearches resource capping

In Kibana 8.x, the search:allowConcurrentSearches setting enables the server to process multiple search requests simultaneously rather than sequentially. This configuration is essential for improving responsiveness in multi-user environments by preventing a single long-running query from blocking the request queue.

However, this setting operates as a boolean toggle. There is currently no native numeric constraint within the Kibana configuration to cap the maximum number of parallel requests allowed per session or per node. In resource-constrained environments, enabling this feature without a granular limit can lead to thread-pool saturation or amplify latency spikes if the backend Elasticsearch cluster reaches its capacity.

• Is there a documented method to implement a numeric limit on concurrent searches beyond the boolean toggle?
• What is the recommended strategy for determining the optimal concurrency threshold relative to Elasticsearch cluster capacity?