How to exclude pattern in <match> for fluentd config?

Better Stack Team
Updated on February 5, 2024

To selectively filter log events in Fluentd, you can use the <match> directive to specify which events to process and which to discard. Here's how you can do it:

To discard all events that match a specific tag and process all other tags, you can configure Fluentd like this:

/etc/fluent/fluentd.conf
<match the.tag.you.want.to.drop>
  @type null
</match>
<match **>
  # process everything else
</match>

The null output plugin effectively discards all log events that match the specified tag.

On the other hand, if you want to drop all events except those with a specific tag, the configuration would look like this:

/etc/fluent/fluentd.conf
<match the.tag.you.want.to.process>
  # process this specific tag
</match>

In this setup, only the events matching the.tag.you.want.to.process are processed, and all others are ignored. However, Fluentd will issue a warning for unprocessed tags.

To eliminate this warning and explicitly discard all other log events, you can direct them to the null output plugin, like this:

 
<match the.tag.you.want.to.process>
  # process this specific tag
</match>
<match **>
  @type null
</match>

This approach ensures a clean configuration where specific tags are processed, and all others are silently discarded, maintaining an efficient log management system.

🔭 Want to centralize and monitor your logs?

Go to Logtail and start your log management in 5 minutes. [/summary]

Better Uptime Dashboard

Make your mark

Join the writer's program

Are you a developer and love writing and sharing your knowledge with the world? Join our guest writing program and get paid for writing amazing technical guides. We'll get them to the right readers that will appreciate them.

Write for us
Writer of the month
Marin Bezhanov
Marin is a software engineer and architect with a broad range of experience working...
Build on top of Better Stack

Write a script, app or project on top of Better Stack and share it with the world. Make a public repository and share it with us at our email.

community@betterstack.com

or submit a pull request and help us build better products for everyone.

See the full list of amazing projects on github