Skip to content
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

[receiver/azuremonitor] Count values not usable #35155

Open
TWpgo opened this issue Sep 12, 2024 · 3 comments
Open

[receiver/azuremonitor] Count values not usable #35155

TWpgo opened this issue Sep 12, 2024 · 3 comments
Assignees
Labels
bug Something isn't working receiver/azuremonitor

Comments

@TWpgo
Copy link

TWpgo commented Sep 12, 2024

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

image
This is the result in Azure Monitor. There should be a single datapoint per timeinterval

Actual Result

image
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

@TWpgo TWpgo added bug Something isn't working needs triage New item requiring triage labels Sep 12, 2024
@TWpgo TWpgo changed the title Count values not usable [receiver/azuremonitor] Count values not usable Sep 12, 2024
Copy link
Contributor

Pinging code owners:

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

@nslaughter
Copy link
Contributor

nslaughter commented Sep 20, 2024

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)

@atoulme atoulme removed the needs triage New item requiring triage label Oct 2, 2024
@TWpgo
Copy link
Author

TWpgo commented Nov 28, 2024

Any news on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working receiver/azuremonitor
Projects
None yet
Development

No branches or pull requests

3 participants