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
It only check for AggregationTemporalityCumulative, not AggregationTemporalityDelta.
So for the proposal solution:
Fix these lines from prometheusexporter to check the other AggregationTemporality types as well before dropping the metric.
The text was updated successfully, but these errors were encountered:
Another attempt from @nabam I found in the PR list #9006 - this one also updated the accumulateDoubleHistogram function but doesn't include the fix for statsd receiver side in #9919
Describe the bug
The counting-type metric from StatsD receiver will always be dropped by the prometheusexporter
Steps to reproduce
c
metric:echo "locmai.test:30|c" | nc -w 1 -v -u 0.0.0.0 8127
What did you expect to see?
The locmai_test metric being exported in the Prometheus Exporter http://0.0.0.0:9090
What did you see instead?
No metric be exported from the prometheusexporter, check the metrics.json and the metric is exported there.
What version did you use?
Version: v0.29.0
What config did you use?
Config:
Environment
OS: CentOS, Kubernetes, MacOS,
Additional context
This was due to the logic for the statsdreceiver that set SetAggregationTemporality(pdata.AggregationTemporalityDelta)
opentelemetry-collector-contrib/receiver/statsdreceiver/protocol/metric_translator.go
Line 32 in 139e7dc
And the prometheusexporter is dropping any metric without the AggregationTemporalityCumulative
https://github.com/open-telemetry/opentelemetry-collector/blob/cc41009d95166f0c5ab9a9bddbab9ec903ed163d/exporter/prometheusexporter/accumulator.go#L198
It only check for AggregationTemporalityCumulative, not AggregationTemporalityDelta.
So for the proposal solution:
Fix these lines from prometheusexporter to check the other AggregationTemporality types as well before dropping the metric.
The text was updated successfully, but these errors were encountered: