liveBook · Manning

Match

As explained in Logs and Telemetry

An event match is a Fluent Bit output-selection pattern that determines which tagged events an output receives.

An event match is a Fluent Bit output-selection pattern that determines which tagged events an output receives. The CLI applies it with -m after declaring the output with -o. section 2.1.3

Use event matches to control which events reach an output:

  • Use the wildcard * to send all tagged events to the output. section 2.1.3
  • Quote the wildcard in shell scripts so the shell does not interpret it; direct console commands can omit the quotes. section 2.1.3

Send every event to stdout

Run `fluent-bit -q -i dummy -p dummy="{\"hello\":\"my world\"}" -t dummy1 -o stdout -m '*'`. The dummy input receives tag `dummy1`, and the stdout output matches every event. section 2.1.3

Listing 2.1 Command-line-configured Fluent BIt
fluent-bit -q -i dummy -p dummy="{\"hello\":\"my world\"}" -t dummy1
 -o stdout -m '*'

Inspect the complete command-line configuration showing an output connected to a wildcard event match. section 2.1.3

How Logs and Telemetry covers it

How deep it goes
Defines -m and wildcard behavior with a runnable pipeline, but defers broader routing patterns.
Examples
Uses a dummy input tagged dummy1 and a stdout output matched with '*'.
What it assumes
Assumes basic Fluent Bit CLI configuration and introduces matching through input tags and output declarations.
What you can do after
Operate Fluent Bit from the CLI by matching tagged events to outputs.
How it connects
Connects input tags, output plugins, wildcard matching, and routing.

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.