Observability now supports multi-level ingestion filtering for sessions, errors, logs, and traces. You can define multiple ordered filter rules with precise conditions and sampling rates to control which telemetry is sent to LaunchDarkly.

Not all telemetry is equally important. Multi-level filters let you stack and reorder rules. For example, always include critical errors from a key service, exclude debug logs, or sample a small percentage of traces in staging, giving you finer control over noise, cost, and signal quality.

How it works
Go to Observability → Settings → Filters, choose a signal type, and add multiple rules with attribute queries and rates. Rules are evaluated top-down, and the first matching enabled rule applies. Anything that matches no rule is included by default.

Learn more
Docs