You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
string A string must always contain UTF-8 encoded or 7-bit ASCII text, and cannot be longer than 232.
The issue here that spans containing invalid data get processed and batched up together with valid data, then it fails on the ingestion side since Ingestion actually follows the Protocol buffer spec. The batching up with good data makes it so some valid data gets lost
My proposal is to basically deny bad data coming to Collector. We could do that by basically switching either to official, non deprecated protocol buffer library or find alternative non-deprecated that has support for utf8 checks. Alternatively we could modify otlp receivers and add checks for utf8 ourselves.
Describe the bug
Because opentelemetry-collector uses deprecated gogo protobuf library OpenTelemetry Collector is able to accept invalid protobuf data.
In protocol buffers string fields cannot contain utf-8 data:
https://protobuf.dev/programming-guides/proto3/#scalar
The issue here that spans containing invalid data get processed and batched up together with valid data, then it fails on the ingestion side since Ingestion actually follows the Protocol buffer spec. The batching up with good data makes it so some valid data gets lost
Example issue: open-telemetry/opentelemetry-collector-contrib#35723
My proposal is to basically deny bad data coming to Collector. We could do that by basically switching either to official, non deprecated protocol buffer library or find alternative non-deprecated that has support for utf8 checks. Alternatively we could modify otlp receivers and add checks for utf8 ourselves.
Relevant issue: open-telemetry/opentelemetry-collector-contrib#35723
Steps to reproduce
What did you expect to see?
I expect the request to fail.
What did you see instead?
Request passed
What version did you use?
v0.111.0
What config did you use?
Environment
Additional context
The text was updated successfully, but these errors were encountered: