-
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
[connector/spanmetrics] CHANGELOG is fixed to reflect the correct fea… #35852
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR looks good, please sign the CLA @tbeemster
I've just signed the CLA and rebased |
Looks like your commit has 2 authors @timbeemster @tbeemster and both need to sign CLA or you can create a new PR with commit only from @tbeemster |
…ture gate The wrong feature gate was exposed in the CHANGELOG, this has been corrected to the correct feature gate 'connector.spanmetrics.legacyMetricNames'
Hi @songy23 , sorry for the late response. Best regards, Tim |
open-telemetry#35852) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description The wrong feature gate was exposed in the CHANGELOG, this has been corrected to the correct feature gate 'connector.spanmetrics.legacyMetricNames' <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#35766 <!--Describe the documentation added.--> #### Documentation CHANGELOG.md is updated to have the correct feature gate name. <!--Please delete paragraphs that you did not use before submitting.-->
Description
The wrong feature gate was exposed in the CHANGELOG, this has been corrected to the correct feature gate 'connector.spanmetrics.legacyMetricNames'
Link to tracking issue
Fixes #35766
Documentation
CHANGELOG.md is updated to have the correct feature gate name.