liveBook · Manning

Telemetry pipeline

As explained in Logs and Telemetry

A monitoring pipeline is an ordered flow that receives, processes, and delivers operational telemetry.

A telemetry pipeline is an ordered flow that receives, processes, and delivers operational telemetry. Fluent Bit defines this flow through CLI declarations that combine inputs, tags, outputs, and event matching. section 2.1.3

A minimal pipeline makes the data flow explicit:

  • Create events with the dummy input plugin and assign each source a tag such as dummy1. section 2.1.3
  • Send tagged events to stdout through an output declaration and match all events with the wildcard. section 2.1.3
  • Repeat input and output declarations to run multiple sources or configure multiple destinations; declaration order matters. section 2.1.3

Hello World with Fluent Bit

Run `fluent-bit -q -i dummy -p dummy="{\"hello\":\"my world\"}" -t dummy1 -o stdout -m '*'` to generate a JSON event and print every matching event to the console. section 2.1.3

How Logs and Telemetry covers it

How deep it goes
Explains inputs, tags, outputs, matching, JSON quoting, and declaration order, while deferring routing concepts.
Examples
Uses dummy-generated JSON events, stdout output, wildcard matching, and multiple-source CLI commands.
What it assumes
Assumes command-line use and JSON quoting, while introducing pipeline inputs, tags, outputs, and matching through a minimal example.
What you can do after
Build and run a basic Fluent Bit pipeline from the CLI, then extend it with additional inputs and outputs.
How it connects
Connects input plugins, output plugins, tags, event matching, routing, CLI configuration, and Kubernetes.
Cover of Logs and Telemetry
liveBookmanning.com
Read Logs and Telemetry on liveBook Get the book at manning.com

Related concepts

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.