Exclusion

Generates a ready-to-paste config that silences or samples a log pattern. Two flavors: a Reducer mute-file entry (preferred — self-expiring, git-reviewable, no regex), or a native rule for your forwarder or log analyzer. Always run Dependency check first — a dashboard or alert that depends on the line will break silently otherwise.

Example

"cap Payment_Gateway_Timeout in Datadog at 5%, expire after 7 days"

Reducer mute-file entry (preferred):

Payment_Gateway_Timeout=0.05:1745712000:P1-incident-OPS-4821

Sample rate, expiry epoch, audit label. Commit to git; the Reducer reloads on its next poll.

More to ask

• "drop HealthCheck_Pass in fluent-bit, checkout-svc"
• "Splunk drop rule for DEBUG_Verbose_Output"
• "OTel filter for Retry_Backoff_Exhausted warnings only"

Prerequisites

No prerequisites. Mute-file entries are independent of the Reporter and work in CLI-only mode.

Tool schema (advanced)

Field	Type	Required	Default	Description
pattern	string	yes	—	Pattern name.
vendor	string	conditional	auto for log analyzers	Target vendor. Log analyzers (datadog, splunk, elasticsearch, cloudwatch) are auto-detected from env when exactly one is present; pass explicitly when ambiguous. Forwarders (datadog-agent, fluentbit, fluentd, otel, vector, logstash, filebeat, rsyslog, syslog-ng, promtail) always require explicit vendor=.
mode	string	no	config	config snippet or api command (API available for Datadog, Splunk, Elasticsearch).
service	string	no	—	Service for scoping the filter.
severity	string	no	—	Severity level.