-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GCP Trace exporter failing due to "invalid utf-8" #35723
Comments
Our collector exporter uses the SDK exporter under the hood, but that shouldn't actually matter. We probably want to make the trace client remove invalid UTF-8 similar to what we do for metrics: https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/16bba4f4e879814de7d3354ef83bcfd597e44b15/exporter/metric/metric.go#L583. It probably needs to be done somewhere around here: https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/16bba4f4e879814de7d3354ef83bcfd597e44b15/exporter/trace/trace_proto.go#L168 |
Opened GoogleCloudPlatform/opentelemetry-operations-go#901 to track this in that repo |
Component(s)
exporter/googlecloud
What happened?
Description
While using the googlecloud exporter to forward traces to GCP Tracing, I occasionally get the following error:
Steps to Reproduce
Unclear - I haven't been able to figure out what trace data is triggering this condition. The only related issue appears to be open-telemetry/opentelemetry-go#3021 which was fixed almost 2 years ago (though unclear to me if the googlecloud exporter depends on opentelemetry-go)
Expected Result
Export all spans regardless of whether or not they are well-formed. Alternately, drop only the spans that are malformed, so that the rest of the batch remains intact.
Actual Result
A whole batch of spans is being dropped, presumably due to a few malformed spans.
Collector version
v0.108.0
Environment information
Environment
otel operator v0.108.0
GKE 1.30.4-gke.1348000
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: