[receiver/azuremonitor] Count values not usable

[TWpgo]

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

receivers:
  azuremonitor:
    subscription_id: "****"
    auth: "managed_identity"
    client_id: "***"
    resource_groups:
      - my-rg

Log output

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/azuremonitor: @nslaughter @codeboten

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[nslaughter]

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)

[TWpgo]

Any news on this?

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/azuremonitor: @nslaughter

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[celian-garcia]

Hello @TWpgo, I'm new maintainer of the azuremonitorreceiver component and I don't reproduce your problem. We basically have one point every collection_interval which is by default equal to 1m.

Is this something that has been solved already in the past?

[celian-garcia]

/label waiting-for-author

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/azuremonitorreceiver: @nslaughter @celian-garcia

See Adding Labels via Comments if you do not have permissions to add labels yourself.