If set to true, the Agents will require that all Kafka clients authenticate themselves with proper SASL credentials.
The port the Agent will listen on for Kafka client TCP connections.
The port the Agent will use for serving HTTP requests (Kinesis API requests, distributed file cache requests, exposing Prometheus metrics, etc).
Override the Availability Zone name which is discovered by the WarpStream Agent automatically using Cloud Instance Metadata.
We do not recommend overriding this in the general case.
Override the log level of the WarpStream Agent from the default value of
info. Acceptable values are
Controls the maximum amount of time the WarpStream agents will allow a produced record to remain buffered in batch before flushing it to object storage. Increasing this value reduces object storage API costs, but increases latency, and vice versa.
Note the WarpStream agents never acknowledge data until it has been flushed to object storage so this value has no impact on correctness or durability guarantees, only latency.
Defaults to 250ms, minimum is 50ms.
Size of the Agent file cache size in bytes. This cache is used to reduce the number of object storage GET requests that required to serve consumers.
Defaults to 0.5GiB/vCPU if omitted.
If set to true, the WarpStream Agents will report their IP6 address instead of IP4 to the WarpStream discovery system.
This is useful when running in VPCs that only support IP6, like fly.io.
Overrides the hostname that the WarpStream Agents will report to the WarpStream discovery system (instead of the default of reporting their private IP4 address).
This is useful when running the Agents behind a network load balancer which requires that the Agents report their hostname as the hostname of the network load balancer instead of their private IP.
Which hostname strategy should be used the agent should advertise itself on. Accepted values:
auto-ip4 means that it will try to automatically find an IP v4 that makes sense
auto-ip6 will do the same with an IPv6.
If you select
custom them you have to also define
Custom hostname value to advertise to service discovery for clustering purposes if the
custom advertise strategy is selected.