Filters

Filters run per handler. That means the same record can be accepted by one handler and rejected by another.

Built-in filters

Filter	Purpose
`LevelLogFilter`	Minimum severity threshold
`LayerLogFilter`	Allow only selected architectural layers
`TypeLogFilter`	Allow only selected log categories
`FeatureLogFilter`	Allow only selected feature tags
`CompositeLogFilter`	Combine multiple filters with `and` or `or`
`AllPassLogFilter`	Accept everything

ConsoleLogHandler(
  filter: const LevelLogFilter(LogLevel.WARNING),
)

This keeps warnings and above while dropping INFO and lower.

ConsoleLogHandler(
  filter: const TypeLogFilter({LogType.network}),
)

Useful when you want one handler dedicated to HTTP or database traffic.

const filter = CompositeLogFilter(
  [
    LevelLogFilter(LogLevel.INFO),
    TypeLogFilter({LogType.network}),
  ],
  mode: CompositeMode.and,
);

This accepts only network records at INFO or above.

Filtering happens before handle(record).
Rejected records never reach the output sink.
Filters with nullable tags usually let missing values pass unless they are explicitly checking for membership.

Use different filters per sink:

That is usually better than trying to force one global threshold for every consumer.