Start node-problem-detector on deployed instances to collect memory stats #1523
Conversation
This file contains 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
Enables the Node Problem Detector on Container-Optimized OS, which collects metrics on memory usage, open tcp connections, processes, cpu steal, swap usage, on top of existing host-collected metrics.
dconnolly
added
A-infrastructure
|
Unfortunately this metadata flag doesn't seem to get picked up when using any of the |
|
These look good, but I'm not sure if they actually work, and if they need another review. Also I think there is a conflict with #1529. |
|
Moving to draft while I keep trying options that work with the |
dconnolly
changed the title
dconnolly
force-pushed
the
enable-node-problem-detector
branch
from
11b53f2 to
faff2de
Compare
|
When deploying containers to containers I just cannot get these memory metrics out. Closing. :/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
The current default metrics available in gcloud about our zebrad nodes deployed on VMs don't have metrics about memory usage.
Solution
Add google-monitoring-enabled=true metadata to deployed instances
Enables the Node Problem Detector on Container-Optimized OS, which collects metrics on memory usage, open tcp connections, processes, cpu steal, swap usage, on top of existing host-collected metrics.
Review
Not urgent.