filter processor
7 complete collector configs on this site use the filter processor. Each is a whole file, validated with otelcol-contrib v0.161.0.
- Enforce required resource attributes (semantic conventions)Refuse telemetry that cannot be attributed - drop anything without service.name, service.namespace and deployment.environment.name.Logs · Metrics · Traces
- Drop health-check logs and spansStop paying to store Kubernetes probe traffic: drop /healthz, /readyz and /livez logs and spans on the collector.Logs · Traces
- Keep only error logsShip only ERROR and FATAL log records from a noisy source, and drop the rest on the collector.Logs
- Filter logs by severity (WARN and above)Drop DEBUG and INFO on the collector, without silently losing the logs that never set a severity.Logs
- Drop all telemetry from a serviceDrop everything a load generator or synthetic probe sends, by service.name, across logs, metrics and traces.Logs · Metrics · Traces
- Drop the collector's own metricsKeep the collector's own otelcol_* metrics out of the application metrics you pay to store.Metrics
- Windows event logs, reduced: noisy events dropped, rendered text removedWindows events with the structured fields kept, the duplicated rendered text removed and the chattiest event IDs dropped.Logs