-
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/metricstransformprocessor bug report, more detail in description #23886
Comments
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. |
@JimChenWYU I just tried your test on the latest version of the collector, and it's passing as expected.
Can you test again? Sorry for taking so long to respond! |
I thought a bit more about this and I think this can be closed as completed since the test is passing. Feel free to open a PR adding the test, or let us know if there's anything else to do here. |
Component(s)
processor/metricstransform
What happened?
Description
In
processor/metricstransformprocessor/metrics_transform_processor_testcases_test.go
, I add a test caseSteps to Reproduce
Run unit test
Expected Result
out should be
Actual Result
Is it a bug?
Collector version
v0.79.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OS: macOSX
Compiler: go1.20.4
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: