administration: document shared HTTP ingress queue settings

Signed-off-by: Eduardo Silva <edsiper@gmail.com>

Author: edsiper

administration/configuring-fluent-bit/yaml/pipeline-section.md

@@ -81,13 +81,27 @@ The `name` parameter is required and defines for Fluent Bit which input plugin s
 
 Some HTTP-based input plugins share the same listener implementation and support the following common settings in addition to their plugin-specific parameters:
 
+These settings are shared by HTTP-based inputs such as `http`, `splunk`,
+`elasticsearch`, `opentelemetry`, and `prometheus_remote_write`.
+Use these keys the same way across those plugins.
+
+If a plugin page shows one of the `http_server.*` keys in its configuration
+table, it is documenting one of these shared listener settings, not a
+plugin-specific behavior.
+
 | Key | Description | Default |
 | --- | ----------- | ------- |
 | `http_server.http2` | Enable HTTP/2 support for the input listener. | `true` |
 | `http_server.buffer_max_size` | Set the maximum size of the HTTP request buffer. | `4M` |
 | `http_server.buffer_chunk_size` | Set the allocation chunk size used for the HTTP request buffer. | `512K` |
 | `http_server.max_connections` | Set the maximum number of concurrent active HTTP connections. `0` means unlimited. | `0` |
 | `http_server.workers` | Set the number of HTTP listener worker threads. | `1` |
+| `http_server.ingress_queue_event_limit` | Set the maximum number of deferred ingress queue entries. This setting applies only when `http_server.workers` is greater than `1`. | `8192` |
+| `http_server.ingress_queue_byte_limit` | Set the maximum size of the deferred ingress queue. This setting applies only when `http_server.workers` is greater than `1`. | `256M` |
+
+When `http_server.workers` is `1`, Fluent Bit does not use the deferred
+ingress queue, so the two `http_server.ingress_queue_*` settings have no
+effect.
 
 For backward compatibility, some plugins also accept the legacy aliases `http2`, `buffer_max_size`, `buffer_chunk_size`, `max_connections`, and `workers`.
 

administration/configuring-fluent-bit/yaml/service-section.md

@@ -36,7 +36,7 @@ The `service` section of YAML configuration files defines global properties of t
 | `streams_file` | Path for the [stream processor](../../../stream-processing/overview.md) configuration file. This file defines the rules and operations for stream processing in Fluent Bit. Stream processor configurations can also be defined directly in the `streams` section of YAML configuration files. | _none_ |
 | `windows.maxstdio` | If specified, adjusts the limit of `stdio`. Only provided for Windows. Values from `512` to `2048` are allowed. | `512` |
 
-The `service` section only controls the built-in monitoring and control HTTP server. Plugin-specific HTTP listener settings such as `http_server.http2`, `http_server.buffer_max_size`, `http_server.buffer_chunk_size`, `http_server.max_connections`, and `http_server.workers` are configured on the relevant input plugin in the [`pipeline.inputs`](../yaml/pipeline-section.md#shared-http-listener-settings-for-inputs) section.
+The `service` section only controls the built-in monitoring and control HTTP server. Plugin-specific HTTP listener settings such as `http_server.http2`, `http_server.buffer_max_size`, `http_server.buffer_chunk_size`, `http_server.max_connections`, `http_server.workers`, `http_server.ingress_queue_event_limit`, and `http_server.ingress_queue_byte_limit` are configured on the relevant input plugin in the [`pipeline.inputs`](../yaml/pipeline-section.md#shared-http-listener-settings-for-inputs) section.
 
 ## Storage configuration
 

installation/upgrade-notes.md

@@ -25,6 +25,8 @@ The HTTP-based input plugins now use a shared HTTP listener configuration model.
 - `http_server.buffer_max_size`
 - `http_server.max_connections`
 - `http_server.workers`
+- `http_server.ingress_queue_event_limit`
+- `http_server.ingress_queue_byte_limit`
 
 Legacy per-plugin names such as `http2`, `buffer_chunk_size`, and `buffer_max_size` are still accepted as compatibility aliases, but new configurations should use the `http_server.*` names.
 

installation/whats-new-in-fluent-bit-v5.0.md

@@ -44,6 +44,8 @@ HTTP-based inputs now use a shared listener configuration model. The preferred s
 - `http_server.buffer_max_size`
 - `http_server.max_connections`
 - `http_server.workers`
+- `http_server.ingress_queue_event_limit`
+- `http_server.ingress_queue_byte_limit`
 
 Legacy aliases such as `http2`, `buffer_chunk_size`, and `buffer_max_size` still work, but new configurations should use the `http_server.*` names.