fix: cpufreq collector enable #3318
Merged
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
hysyeah
force-pushed
the
fix/cpufreq-collector-enable
branch
from
333e847 to
ab3e6be
Compare
Signed-off-by: hys <[email protected]>
hysyeah
force-pushed
the
fix/cpufreq-collector-enable
branch
from
ab3e6be to
c0aa373
Compare
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.
Start node-exporter by specifying both the --collector.cpu.info and --collector.cpufreq parameters， but I can't get the
node_cpu_frequency_hertzmetric from the metrics api.