Data Collection

Fluency can receive and analyze event logs from a wide variety of sources. This section covers the transport methods used to get data into the platform:

• Fluency Collector — a virtual appliance (VM) that acts as a local collection server, forwarding events (Syslog, NetFlow, LDAP) to the Fluency Cloud.
• Syslog — direct syslog ingestion, via the cloud syslog endpoint, virtual collectors, or an on-prem collector.
• HEC (Splunk-compatible) — a token-authenticated HTTP Event Collector endpoint for applications that already support Splunk data export.
• LDAP — directory synchronization via a local collector.

For instructions specific to a vendor product or cloud service, see the Applications catalog.

In this section

• Fluency Collector — installing and registering the virtual appliance.
• Syslog Import — the cloud syslog endpoint, the collector's listeners, and which to use.
• HEC (Splunk-compatible) — the token-authenticated HTTP Event Collector endpoint.
• LDAP (Requires collector) — directory synchronization through a local collector.
• Ingress Management — watching what is arriving, and noticing when it stops.

Related

• Applications — per-vendor instructions, and the templates that build a pipeline for you.
• Platform — what happens to data once it has arrived.
• Troubleshooting — no data arriving.