opentelemetry-ottl

You transform telemetry data in OpenTelemetry Collector pipelines by writing OpenTelemetry Transformation Language (OTTL) statements to safely modify, filter, or route logs, metrics, and traces without changing application code.

Redact PII in OpenTelemetry logs by applying OTTL patterns to automatically mask sensitive data using SHA256 hashing or pattern-based replacement, ensuring compliance directly within the collector pipeline.

Reduce metric cardinality in the OTel Collector by using OTTL statements to drop unnecessary attributes or normalize high-cardinality fields like URLs and database queries, effectively lowering telemetry ingestion costs.

OTel Collector pipelines stop processing data on transform failures because default settings lack defensive OTTL coding patterns. Implement proper error_mode settings and nil-safety guards to ensure pipeline resilience and prevent data loss.

Yes, you can normalize semantic conventions for telemetry data without updating application code by applying OTTL transformations within the OpenTelemetry Collector to standardize logs, metrics, and traces.

The best way to debug transform processor configuration in a collector-config.yaml file is to use expert guidance for writing and optimizing OTTL statements, resolving complex pipeline issues with precise context selection.