[receiver/awscontainerinsightreceiver] Add cAdvisor filesystem plugin imports #45535
+30
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib. Important reminders:
A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add cAdvisor filesystem plugin imports (vfs, overlay, tmpfs) to enable filesystem metrics collection.
cAdvisor v0.55.0 introduced a pluggable filesystem architecture (PR google/cadvisor#3794) that requires explicit plugin registration via blank imports. Without these imports,
fs.GetPluginForFsType()returns nil for all filesystem types and NodeFS/InstanceFS metrics are not emitted.Link to tracking issue
Fixes #45534
Testing
go test ./...)make lint)Documentation
No documentation changes needed.