-
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
GMP exporter claims unsupported metric data type (data_type empty) #29556
Comments
can you configure the logging exporter with the It it hitting this error: https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/a227a2319903eb2170c2cdf7c9c7aedf73df5503/exporter/collector/metrics.go#L780, which happens when it is sent a metric that is not one of the valid OTel metric types. |
Thanks, I added the
It will sometimes have the DataType be histogram but it's almost entirely Empty. I'm using OTLP in Python to record my metrics like this:
and my OTel config is using the googlamanagedprometheus exporter. |
Interesting. That sounds like an issue with OTel python. I would expect the DataType to still have a Histogram data point type in that case... @aabmass |
@dashpole @aabmass Actually it seems my issue is the same as this error open-telemetry/opentelemetry-python#3277, where Histograms are being exported as an empty DataType. I'm using these OTel packages:
Do we know if there's a version I can upgrade to that has fixed this error? It looks like there's been some PR's to fix this issue open-telemetry/opentelemetry-python#3277 (comment) |
Based on open-telemetry/opentelemetry-python@3a651c7, it is fixed in v1.21.0 of opentelemetry-python. I'd bump all the deps that are at 1.20 to 1.21 |
Component(s)
exporter/googlemanagedprometheus
Describe the issue you're reporting
Hi, I have a cloud run and a kubernetes deployment for my OTel collector. But I notice both will have logs with this error at about every second:
I'm using the logging exporter as well, yet right before this error I get the info message
Does anyone know how to resolve this? It seems it will sometimes prevent my data from being exported properly to Google Cloud Monitoring.
The text was updated successfully, but these errors were encountered: