-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[processor/attributes] Metric tests are broken #8393
Comments
Pinging code owners: @boostchicken. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I added the following lines to the
The reason the tests pass without this change is that the I think the bug being surfaced by fixing this problem is here: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/internal/coreinternal/processor/filtermetric/filtermetric.go#L33-L36 where there is a case for an expression matcher, a name matcher, but there is no usage of the Therefore, no matching happens based on this filter:
I'm not very familiar with the code base, so I was hoping someone (@pmm-sumo ?) could verify my hypothesis. It seems like the function I linked above would need to be modified to add functionality to return a |
Updated link to suspected bug location (I think this is where it moved to): opentelemetry-collector-contrib/internal/filter/filtermetric/filtermetric.go Lines 51 to 60 in ddaa684
|
It's not just resources, the metric data point attributes filter is also non-functional |
I've created a draft PR that implements both resources and data point attribute filtering: #17017 I published this PR to take advantage of Cunningham's law. Let me know what you think! |
@boostchicken I think you might be an owner for this processor? If so, could you provide some feedback on what I have so far? Also, I was not sure what to do with the |
Also, please assign me to this issue |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Describe the bug
generateMetricData function does not generate actual data points. When it is fixed to generate some data points, the tests fail
What version did you use?
The bug was introduced in #8111
Additional context
Thanks to @hughsimpson for spotting this while working on #7930
The text was updated successfully, but these errors were encountered: