liveBook · Manning

Network interface input plugin

As explained in Logs and Telemetry

The network interface input plugin is a Fluent Bit input extension that periodically collects network traffic and error measurements.

The network interface input plugin periodically collects network traffic and error measurements as Fluent Bit events. Configure it with the netif name, a polling interval, an explicit tag, and optionally an interface such as eth0. Although the data represents metrics, log-shaped events provide flexible processing; another plugin can later transform or generate metrics. section 3.2.1

Listing 3.1 Performing basic OS monitoring
[INPUT]
  name disk           #1
  interval_sec 5
  tag book_vm_disk

[INPUT]
  name cpu          #2
  interval_sec 5
  tag book_vm_cpu

[INPUT]
  name mem         #3
  interval_sec 5
  tag book_vm_memory

[INPUT]
  name netif          #4
  interval_sec 5
  #interface eth0     #5
  tag book_vm_network

[OUTPUT]
  name stdout
  match *        #6

A basic Fluent Bit configuration polls netif every five seconds, tags the records as book_vm_network, and sends all events to stdout. section 3.2.1

How Logs and Telemetry covers it

How deep it goes
Explains periodic polling, interface selection, tags, and output routing, but does not detail collection internals.
Examples
Uses a netif block polling every five seconds, optionally targeting eth0, tagging records, and routing them to stdout.
What you can do after
Operate a Fluent Bit configuration that polls network interfaces and routes collected events for inspection or processing.
How it connects
Connects network events to Fluent Bit input and output plugins, tags, filtering, metrics, logs, and node_exporter.

This explainer was generated by Manning's knowledge graph from the text of Logs and Telemetry. The section links point to the parts of the book it draws on.