Frequently asked questions

Are all integrations available in Community?

Yes. Collection, Pipeline, fanout, routing, durable queues, diagnostics and the management API are included. Community deployment supports one local Worker.

Does activation require internet access?

No. Import an offline file issued by LicRegister. Signature, cluster binding, validity and quota are verified locally.

Are Worker queues automatically replicated?

No. Each Worker owns a local durable queue. Task takeover does not replicate queues or automatically move an old node’s backlog.

What does acknowledgement mean?

Source acknowledgement confirms local durable acceptance. Downstream acknowledgement follows each protocol. Retries may duplicate records, and there is no global transaction or ordering across destinations.

Can FlowPort read local files or container logs?

FlowPort focuses on remote ingestion. Use DataKit, Vector or another collector to collect local data and forward it over a supported protocol.

Does FlowPort accept every Vector option?

FlowPort does not import Vector configuration or claim full option or data-model equivalence. Its adapters are implemented natively in Go.