Ingest settings
Every setting below is read once at startup and requires a restart to change.
Built-in defaults are overridden by nonempty environment values.
Unknown FANOUT_ names fail startup; platform-injected service names are tolerated.
Custom names use FANOUT_ plus a clear name, adding the area only when it clarifies.
Vendor credentials and endpoints keep the vendor’s documented names.
| Environment variable | Type | Default |
|---|---|---|
FANOUT_DEFAULT_NAMESPACE | string | default |
FANOUT_INGEST_BATCH_SIZE | integer | 50000 |
FANOUT_INGEST_MAX_IN_FLIGHT_BYTES | integer | 268435456 |
FANOUT_DEFAULT_NAMESPACE
Section titled “FANOUT_DEFAULT_NAMESPACE”Supplies the namespace for telemetry without one.
FANOUT_INGEST_BATCH_SIZE
Section titled “FANOUT_INGEST_BATCH_SIZE”Sets the group-commit row target; valid values are 1–50000. Individual requests remain atomic and can exceed this target.
FANOUT_INGEST_MAX_IN_FLIGHT_BYTES
Section titled “FANOUT_INGEST_MAX_IN_FLIGHT_BYTES”Caps the decoded telemetry the process will hold across concurrent requests. Concurrency is HTTP/2 streams times connections and each handler holds its batch until the commit is durable, so without a ceiling a burst is bounded only by memory. Zero is unbounded. A single request is admitted when no other request holds budget, even if it exceeds the limit.