liveBook · Manning

Log filtering

Log filtering is the selective retention, routing, or suppression of log records according to attributes such as type, severity, or namespace.

How 2 Manning books explain it

ASP.NET Core in Action, 3e

A logging filter is a configuration rule that selects log messages for output according to criteria such as severity and namespace.

How it is used
Reduces noisy output from selected providers or namespaces while keeping logs useful for monitoring and troubleshooting.
How deep it goes
Explains severity, category, provider, specificity, and layered configuration, but stops short of provider implementation internals.
Examples
Uses ILogger messages, Microsoft namespace filters, console and file providers, appsettings.json, and AddConfiguration().
What you can do after
Configure ASP.NET Core logging with category- and provider-specific minimum levels through appsettings.json or AddConfiguration().

Read how ASP.NET Core in Action, 3e explains log filtering →

Learn Docker in a Month of Lunches, Second Edition

Log filtering is the selective retention, routing, or suppression of log records according to their attributes or severity.

How it is used
Balances diagnostic detail against storage costs by filtering container logs before Elasticsearch storage.
How deep it goes
Explains tag-based Fluentd routing, enrichment, and configuration updates, but stops short of broader filtering strategies.
Examples
Demonstrates filtering gallery.access-log records to stdout while retaining other gallery logs in Elasticsearch.
What you can do after
Operate/configure Fluentd to route verbose container logs without changing application containers.

Read how Learn Docker in a Month of Lunches, Second Edition explains log filtering →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.