influxdata / influxdata/influxdb-observability
Fields dropped by opentelemetry input plugin
- Dominant language
- Go
- Stars
- 56
- Forks
- 29
- Avg merge
- 12d 13h
- Merged PRs (30d)
- 4
Description
I am trying to process OTEL data using telegraf OTEL input plugin. I have created some sample input files for telemetry i.e. traces, logs and metrics. I have tried with several permutations but following fields are always dropped, they do not appear in the output.
- parentSpanId
- scope.name
- scope.version
- and some other fields
I see that the extraction logic for these fields is visible in the Otel2Influx library. Still, these fields do not appear in the output. When i debug, I see that the fields are lost before the data reaches processor block. It seems to be a bug in the otel2influx conversion library.
Please refer to details of the study (input data, output data, field-wise comparison) from [here](https://drive.google.com/file/d/1Py1Vr_10CwkP17udTjcR4JaY8LGiK75v/view?usp=sharing)
PS: This was discussed in the influxdata community [here](https://community.influxdata.com/t/fields-dropped-by-opentelemetry-input-plugin/57710/9).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Otel2Influx conversion logic and the point where data reaches the processor block. Reproduce the report with the sample traces, logs, and metrics from the linked study, then compare output for parentSpanId, scope.name, scope.version, and the other missing fields. Done means the affected fields survive conversion and appear in the output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100