Ingest settings
Every setting below is read from the environment variable in the second
column, or from the same key in a YAML configuration file. An unrecognised
FANOUT_-prefixed variable is a startup error, so a renamed setting surfaces
as a refusal to start rather than as a default nobody chose.
| Setting | Environment variable | Type | Default |
|---|---|---|---|
ingest.advertised_endpoint | FANOUT_INGEST_ADVERTISED_ENDPOINT | string | — |
ingest.default_namespace | FANOUT_DEFAULT_NAMESPACE | string | default |
ingest.flush_batch_size | FANOUT_FLUSH_BATCH_SIZE | integer | 50000 |
ingest.flush_interval | FANOUT_FLUSH_INTERVAL | duration | 15s |
ingest.otlp_grpc_addr | FANOUT_OTLP_GRPC_ADDR | string | 127.0.0.1:4317 |
ingest.otlp_http_addr | FANOUT_OTLP_HTTP_ADDR | string | 127.0.0.1:4318 |
ingest.advertised_endpoint
Section titled “ingest.advertised_endpoint”The OTLP endpoint shown in collector setup guidance (e.g. “https://ingest.example.com”). It is an operator hint for trusted services and collectors, not a public-client or mobile endpoint; unlike OTLPGRPCAddr, it does not control the bind/listen address. Empty means derive host:port from the browser request and OTLPGRPCAddr as a best effort.