Drop unwanted telemetry with the filter processor using OTTL conditions

Steps

1. Add filterprocessor to processors in your Collector config; set error_mode: ignore so a malformed condition does not halt the pipeline
2. Under the signal section (traces, metrics, or logs), add a span/datapoint/log_record block with a conditions list; any record matching at least one condition is dropped
3. Write conditions using OTTL syntax, for example: attributes["http.route"] == "/healthz" to drop health-check spans, or severity_number < SEVERITY_NUMBER_WARN to drop below-warning logs
4. Combine predicates with and / or inside a single condition string; use parentheses for grouping when mixing operators
5. For metrics, use metric.name or resource.attributes to drop entire metric families or per-resource streams; the datapoint block can filter individual data points within a metric
6. Validate dropped volumes by watching the otelcol_processor_dropped_* internal metrics (exposed on port 8888 by default) after deploying the filter processor