Netflow and Parquet Integration

Input and output integration overview

The Netflow plugin is designed to collect traffic flow data from devices using the Netflow v5, v9 and IPFIX protocols. By capturing detailed flow information, this plugin supports network observability and analysis, enabling administrators to monitor traffic patterns and performance metrics effectively.

This plugin writes metrics to parquet files, utilizing a schema based on the metrics grouped by name. It supports file rotation and buffered writing for optimal performance.

Integration details

Netflow

The Netflow plugin serves as a collector for flow data using protocols such as Netflow v5, Netflow v9, and IPFIX. This plugin allows users to gather important flow metrics from devices that support these protocols, including a variety of operational insights about traffic patterns, source/destination information, and protocol usage. The plugin leverages templates sent by flow devices to decode incoming data correctly, and it supports private enterprise number mappings for vendor-specific information. With features like adjustable service addresses and buffer sizes, the plugin provides flexibility in how it can be deployed within various network architectures, making it an essential tool for network monitoring and analysis.

Parquet

The Parquet output plugin for Telegraf writes metrics to parquet files, which are columnar storage formats optimized for analytics. By default, this plugin groups metrics by their name, writing them to a single file. If a metric’s schema does not align with existing schemas, those metrics are dropped. The plugin generates an Apache Arrow schema based on all grouped metrics, ensuring that the schema reflects the union of all fields and tags. It operates in a buffered manner, meaning it temporarily holds metrics in memory before writing them to disk for efficiency. Parquet files require proper closure to ensure readability, and this is crucial when using the plugin, as improper closure can lead to unreadable files. Additionally, the plugin supports file rotation after specific time intervals, preventing overwrites of existing files and schema conflicts when a file with the same name already exists.

Configuration

Netflow

[[inputs.netflow]]
  ## Address to listen for netflow,ipfix or sflow packets.
  ##   example: service_address = "udp://:2055"
  ##            service_address = "udp4://:2055"
  ##            service_address = "udp6://:2055"
  service_address = "udp://:2055"

  ## Set the size of the operating system's receive buffer.
  ##   example: read_buffer_size = "64KiB"
  ## Uses the system's default if not set.
  # read_buffer_size = ""

  ## Protocol version to use for decoding.
  ## Available options are
  ##   "ipfix"      -- IPFIX / Netflow v10 protocol (also works for Netflow v9)
  ##   "netflow v5" -- Netflow v5 protocol
  ##   "netflow v9" -- Netflow v9 protocol (also works for IPFIX)
  ##   "sflow v5"   -- sFlow v5 protocol
  # protocol = "ipfix"

  ## Private Enterprise Numbers (PEN) mappings for decoding
  ## This option allows to specify vendor-specific mapping files to use during
  ## decoding.
  # private_enterprise_number_files = []

  ## Log incoming packets for tracing issues
  # log_level = "trace"

Parquet

[[outputs.parquet]]
  ## Directory to write parquet files in. If a file already exists the output
  ## will attempt to continue using the existing file.
  # directory = "."
  
  ## Files are rotated after the time interval specified. When set to 0 no time
  ## based rotation is performed.
  # rotation_interval = "0h"
  
  ## Timestamp field name
  ## Field name to use to store the timestamp. If set to an empty string, then
  ## the timestamp is omitted.
  # timestamp_field_name = "timestamp"

Input and output integration examples

Netflow

1. Traffic Analysis and Visualization: Use the Netflow plugin to collect traffic flow data and visualize it in real-time using an analytics platform. Administrators can create dashboards that display traffic patterns and anomalies, helping them understand bandwidth usage and user behavior.

2. Network Performance Optimization: Integrate the Netflow plugin with performance monitoring tools to identify bottlenecks and optimize the network. Analyze collected metrics to pinpoint areas where network resources can be improved, enhancing overall system performance.

3. Anomaly Detection for Security: Leverage the Netflow data for security analysis by feeding it into an anomaly detection system. This can help identify unusual traffic patterns that may indicate potential security threats, enabling quicker responses to prevent breaches.

4. Customized Alerts for Network Events: Configure threshold-based alerts using the Netflow plugin metrics to notify network administrators of unusual spikes or drops in traffic. This proactive monitoring can help in quickly addressing potential issues before they escalate.

Parquet

1. Data Lake Ingestion: Utilize the Parquet plugin to store metrics from various sources into a data lake. By writing metrics in parquet format, you establish a standardized and efficient way to manage time-series data, enabling faster querying capabilities and seamless integration with analytics tools like Apache Spark or AWS Athena. This setup can significantly improve data retrieval times and analysis workflows.

2. Long-term Storage of Metrics: Implement the Parquet plugin in a monitoring setup where metrics are collected over time from multiple applications. This allows for long-term storage of performance data in a compact format, making it cost-effective to store vast amounts of historical data while preserving the ability for quick retrieval and analysis later on. By archiving metrics in parquet files, organizations can maintain compliance and create detailed reports from historical performance trends.

3. Analytics and Reporting: After writing metrics to parquet files, leverage tools like Apache Arrow or PyArrow to perform complex analytical queries directly on the files without needing to load all the data into memory. This can enhance reporting capabilities, allowing teams to generate insights and visualization from large datasets efficiently, thereby improving decision-making processes based on accurate, up-to-date performance metrics.

4. Integrating with Data Warehouses: Use the Parquet plugin as part of a data integration pipeline that feeds into a modern data warehouse. By converting metrics to parquet format, the data can be easily ingested by systems like Snowflake or Google BigQuery, enabling powerful analytics and business intelligence capabilities that drive actionable insights from the collected metrics.

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.