Skip to content

Network Flow Handling #7386

@sempervictus

Description

@sempervictus

Use-cases

Network devices such as switches and firewalls export sFlow/NetFLow (or the perverse vendor variants) to provide ongoing trace of network traffic details without having to store and capture all of the data involved. Tools like ElastiFlow utilize LogStash to ingest and enrich flow data with DNS and AS lookups, GeoIP information, etc. Vector seems like a much better platform for the ingest, enrichment, and forwarding given its memory and concurrency models, as well as portability across systems for localized collection.

Proposal

  1. Implement ingest for the common flow formats: sFlow, NetFlow, IPFix, and JFlow - data and counters.
  2. Implement internal formatting
  3. Implement attribute-based lookups and enrichment
  4. Implement output formatting - ElastiFlow already provides an ES template

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain: logsAnything related to Vector's log eventstype: featureA value-adding code addition that introduce new functionality.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions