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
The count values are repeated not a single data point.
The number of repetitions is not predictable.
Expected Result
This is the result in Azure Monitor. There should be a single datapoint per timeinterval
Actual Result
This is the same metric received from the azuremonitor plugin and exported to otelhttp endpoint of Mimir and displayed in Grafana. The actual value is identical to Azure Monitor but repeated multiple times. It's not predictable how often the value is repeated so I cannot use that value for calculations.
Collector version
v0.109.0
Environment information
Environment
Running official docker container in kubernetes
Receiving metics from Azure Monitor via the otel collector.
Sending the metics to otel ingress of Mimir.
Evaluating the values in Grafana.
Thanks for raising this @TWpgo. Fixing the issue will involve a scraper refactor. I will be able to look into this next week. (And commenting to keep this from getting zapped by stale-bot)
Component(s)
receiver/azuremonitor
What happened?
Description
The count values are repeated not a single data point.
The number of repetitions is not predictable.
Expected Result
This is the result in Azure Monitor. There should be a single datapoint per timeinterval
Actual Result
This is the same metric received from the azuremonitor plugin and exported to otelhttp endpoint of Mimir and displayed in Grafana. The actual value is identical to Azure Monitor but repeated multiple times. It's not predictable how often the value is repeated so I cannot use that value for calculations.
Collector version
v0.109.0
Environment information
Environment
Running official docker container in kubernetes
Receiving metics from Azure Monitor via the otel collector.
Sending the metics to otel ingress of Mimir.
Evaluating the values in Grafana.
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: