-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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/dockerstats] Featuregate for new mdatagen implementation + semantic convention alignment #12743
[receiver/dockerstats] Featuregate for new mdatagen implementation + semantic convention alignment #12743
Conversation
…t with legacy scrape now that the metrics are different
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.
Just a few comments on it but it is straight forward enough.
I do need to revisit what is the recommended time to give users for breaking changes.
Co-authored-by: Sean Marciniak <[email protected]>
Looks like there's an unrelated windows test failing the build |
@dmitryax is there anything left to do to get this PR merged? Perhaps a codeowner review from @rmfitzpatrick might help? |
@jamesmoessis LGTM. But it's better to submit separate PRs for unrelated even small changes |
Description:
This PR:
Link to tracking Issue: #9794
Testing:
Units are changed in
expected_metrics.json
files, as well as descriptions added. The legacy scrape implementation is now not tested in comparison to the new one, since they are have different units and descriptions. They have been proven equivalent by the last PR, and now they will start to diverge as we make enhancements to the new implementation.Documentation: Documented the feature gate in the README.