Ensure nvme_exporter can work with nvme-cli v2.11 #2
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
…rter into add-nvme-2.11-support
Add support for nvme-cli 2.11
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.
Newer versions of nvme-cli have different output formats to JSON. The JSON can also change, depending on how many nvme controllers are present. This works with all current releases. Added some basic unittests to ensure that conversions/JSON parsing is good.
This also gives the ability to change the temperature exporter, to Kelvin (as per NVMe spec), Celcius (as per Prometheus node_exporter and other tools), and Fahrenheit (used in some environments).