Skip to content
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/kubeletstatsreceiver] Emit network metrics without a direction attribute #12588

Merged
merged 12 commits into from
Aug 12, 2022

Conversation

mwear
Copy link
Member

@mwear mwear commented Jul 18, 2022

Description:
This PR updates the kubeletstatsreceiver so that it can emit metrics without a direction attribute (see #11815). The behavior of the direction attribute is currently controlled by the feature gates receiver.kubeletstatsreceiver.emitMetricsWithoutDirectionAttribute and receiver.kubeletstatsreceiver.emitMetricsWithDirectionAttribute. The feature gates will be available for a grace period to help users transition to metrics without a direction attribute, which will eventually become the default.

Link to tracking Issue:
#12164

Testing:
Unit tests

Documentation:
The readme has been updated to document the feature gates and transition plan.

@mwear mwear requested a review from a team July 18, 2022 21:21
@mwear mwear requested a review from dmitryax as a code owner July 18, 2022 21:21
@mwear mwear force-pushed the kubeletstats_direction branch from b8272f4 to 405807b Compare July 18, 2022 23:44
@mwear mwear force-pushed the kubeletstats_direction branch 2 times, most recently from eda8a45 to 1cd7138 Compare July 27, 2022 20:22
receiver/kubeletstatsreceiver/README.md Outdated Show resolved Hide resolved
1. v0.56.0, July 2022:

- The new metrics are available for all scrapers, but disabled by default, they can be enabled with the feature gates.
- The old metrics with `direction` attribute are deprecated with a warning.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The warning log still needs to be added

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added warnings. In doing so, I noticed that some were removed in this PR: #12105. They were supposed to be added back in before the v0.56.0 release, but it doesn't appear that happened. I can make an issue and add them back if that's something we'd like to do. I used the phrasing from the original warnings. If we'd like to make any changes, suggest them here and I can apply them when adding the warnings elsewhere.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @mwear, sorry for the delayed response. As mentioned #11815, we would like to avoid showing the warnings for now. Can you please remove them.

Sorry for raising the contradicting comments.

@mwear mwear requested a review from dmitryax July 29, 2022 15:23
@mwear mwear force-pushed the kubeletstats_direction branch 3 times, most recently from 3e5c01c to c7530b3 Compare August 10, 2022 16:26
@mwear mwear force-pushed the kubeletstats_direction branch from c7530b3 to 6d1359c Compare August 10, 2022 18:16
receiver/kubeletstatsreceiver/scraper.go Outdated Show resolved Hide resolved
@dmitryax dmitryax merged commit 64bc925 into open-telemetry:main Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants