-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[receiver/azuremonitorreceiver] metrics
aggregation filter unused and slightly with current use_batch_api:true
implementation
#40079
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
Labels
bug
Something isn't working
good first issue
Good for newcomers
help wanted
Extra attention is needed
never stale
Issues marked with this label will be never staled and automatically removed
receiver/azuremonitor
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
metrics
aggregation filter unused and slightly with current use_batch_api:true
implementationmetrics
aggregation filter unused and slightly with current use_batch_api:true
implementation
/labels -needs-triage help-wanted good-first-issue |
/labels never-stale |
Well considered, I will check it myself, as I have a good understanding of the problem and it's easy to unblock. |
dragonlord93
pushed a commit
to dragonlord93/opentelemetry-collector-contrib
that referenced
this issue
May 23, 2025
…en ``use_batch_api: true`` (open-telemetry#40091) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This is following a previous PR for adding support of Azure Batch API, in which I failed to backport the support of metrics aggregation filter. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#40079 Mentioned as an issue in open-telemetry#40078 <!--Describe what testing was performed and which tests were added.--> #### Testing Changed one of the mocked data to cover the problems mentioned in the issue. Useless to create a specific config with metric aggregation filters as it would create query option ignored by the mock and the code is driven behind by the mock data. <!--Describe the documentation added.--> #### Documentation N/A <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: Célian Garcia <[email protected]> Co-authored-by: Antoine Toulme <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
good first issue
Good for newcomers
help wanted
Extra attention is needed
never stale
Issues marked with this label will be never staled and automatically removed
receiver/azuremonitor
Uh oh!
There was an error while loading. Please reload this page.
Component(s)
receiver/azuremonitor
What happened?
Description
From the following thread #38895 (comment)
There are two issues that should be fixed at once:
if metricValue.Average != nil {
before processing the metrics, which is obviously unwanted now that we can filter out the metrics. The reason of that choice and possible solutions are explained in the thread.Steps to Reproduce
Special thanks to @andrewegel with this perfect reproduction #40078
I'm copy pasting it there
Expected Result
We expect the metrics for which you don't have average in the filter (e,g ByteCount, SYNCount, ...) to appear in the result.
Actual Result
Only metrics that does have "average" in their filter appear in the result.
Collector version
v0.126.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: