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
What is the actual behavior?
This fails silently in the CollectorMetricsExporter.export() method.
I suspect that is comes from the get_collector_point() function which tries to set point.int64_value = metric_record.aggregator.checkpoint where point.int64_value should be an int (protobuf schema) but metric_record.aggregator.checkpoint is a minmaxsumcount tuple for a Measure metric.
The text was updated successfully, but these errors were encountered:
A OTLP metrics exporter is being implemented. As well, there is a proposal to make MinMaxSumCountLast as the default aggregation for ValueRecorder (previously Measure) and the data point type will be added to the protobuf schema.
srikanthccv
pushed a commit
to srikanthccv/opentelemetry-python
that referenced
this issue
Nov 1, 2020
The metrics SDK is still experimental and will likely be updated very shortly again. Closing this issue as it's unclear if the bug will still exist when that work is done.
Describe your environment
Using Python 3.7 and opentelemetry-ext-otcollector and opentelemetry-sdk version 0.7b1.
Steps to reproduce
What is the actual behavior?
This fails silently in the
CollectorMetricsExporter.export()
method.I suspect that is comes from the
get_collector_point()
function which tries to setpoint.int64_value = metric_record.aggregator.checkpoint
wherepoint.int64_value
should be an int (protobuf schema) butmetric_record.aggregator.checkpoint
is a minmaxsumcount tuple for a Measure metric.The text was updated successfully, but these errors were encountered: