CSV Transform Processor
Overview
The CSV Transform Processor uses CSV-backed lookup and replacement rules to transform telemetry fields. It can read lookup data from a CSV file path or from base64-encoded CSV content and apply the rules to logs, metrics, and traces.
Supported types: Logs · Metrics · Traces
Configuration
General Settings
| Parameter | Type | Default | Required | Description |
|---|---|---|---|---|
| csv_file_path | string | none | No | Path to the CSV file on the collector containing lookup and replacement values. |
| base64_csv_string | string | none | No | Base64-encoded CSV content used for lookup and replacement. |
Note: Provide either
csv_file_pathorbase64_csv_stringas the source for the CSV lookup data.
Transformation Rules
Each item in rules defines one CSV-based transformation rule.
CSV Columns
| Parameter | Type | Default | Required | Description |
|---|---|---|---|---|
| match_column | string | none | Yes | CSV header name used for matching values. |
| replace_column | string | none | Yes | CSV header name used for replacement values. |
Field Mapping
| Parameter | Type | Default | Required | Description |
|---|---|---|---|---|
| otel_field | string | none | Yes | OpenTelemetry field to read and match against. |
| otel_field_to_update | string | none | No | Destination field to update. If empty, the matched OTel field is updated in place. |
| match_type | string | none | Yes | Matching mode used for the CSV column mapping. |
Example Configuration
{
"csv": "", // default: none
"base64_csv": "", // default: none
"rules": [
// required
{
"match_column": "", // required, default: none
"replace_column": "", // required, default: none
"otel_field": "", // required, default: none
"otel_field_to_update": "", // default: none
"match_type": "", // required, default: string
},
],
}