liveBook · Manning

Input block

As explained in Logs and Telemetry

An input block is a configuration section that declares an event source and its input-plugin settings.

An input block declares an event source and configures its input plugin. Set the plugin name, polling interval, and tag; multiple blocks let Fluent Bit collect different infrastructure signals independently. section 3.2.1

Configure each source with:

  • name, such as disk, cpu, mem, or netif, to select the source plugin. section 3.2.1
  • interval_sec or interval_nsec, expressed as an integer, to control collection frequency. section 3.2.1
  • tag, preferably explicit, so downstream filtering can use a stable event identity. 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

The configuration combines four input blocks for disk, CPU, memory, and network data, then sends every matching event to stdout. section 3.2.1

How Logs and Telemetry covers it

How deep it goes
Defines plugin names, polling intervals, and tags, but defers detailed metric handling and transformation to other plugins.
Examples
Uses disk, CPU, memory, and network-interface inputs polled every five seconds and routed to stdout.
What you can do after
Operate/configure Fluent Bit input sources with explicit collection intervals, tags, and a matching stdout output.
How it connects
Connects input plugins with tags, filtering, output plugins, and metric-generation plugins.

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.