Remove non-existing CPU metrics #498
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
I couldn't find any Elasticsearch versions where these CPU metrics were exposed, so they are always set to 0. Signed-off-by: Jonathan Ballet <[email protected]>
Signed-off-by: Jonathan Ballet <[email protected]>
|
I can't confirm all versions, but I can say that these are always 0 for my 7.x setup |
SuperQ
approved these changes
Jan 19, 2022
SuperQ
added a commit
that referenced
this pull request
Jan 19, 2022
With PR #498, we only have one process CPU metric. * Drop the label. * Update the name to match Prometheus naming. Signed-off-by: SuperQ <[email protected]>
sysadmind
pushed a commit
that referenced
this pull request
Jan 19, 2022
With PR #498, we only have one process CPU metric. * Drop the label. * Update the name to match Prometheus naming. Signed-off-by: SuperQ <[email protected]>
iishabakaev
pushed a commit
to iishabakaev/elasticsearch_exporter
that referenced
this pull request
Jun 8, 2022
* Remove non-existing CPU metrics I couldn't find any Elasticsearch versions where these CPU metrics were exposed, so they are always set to 0. Signed-off-by: Jonathan Ballet <[email protected]> * remove more Signed-off-by: Jonathan Ballet <[email protected]> Signed-off-by: iishabakaev <[email protected]>
iishabakaev
pushed a commit
to iishabakaev/elasticsearch_exporter
that referenced
this pull request
Jun 8, 2022
With PR prometheus-community#498, we only have one process CPU metric. * Drop the label. * Update the name to match Prometheus naming. Signed-off-by: SuperQ <[email protected]> Signed-off-by: iishabakaev <[email protected]>
jnadler
pushed a commit
to jnadler/elasticsearch_exporter
that referenced
this pull request
Oct 27, 2022
* Remove non-existing CPU metrics I couldn't find any Elasticsearch versions where these CPU metrics were exposed, so they are always set to 0. Signed-off-by: Jonathan Ballet <[email protected]> * remove more Signed-off-by: Jonathan Ballet <[email protected]>
jnadler
pushed a commit
to jnadler/elasticsearch_exporter
that referenced
this pull request
Oct 27, 2022
With PR prometheus-community#498, we only have one process CPU metric. * Drop the label. * Update the name to match Prometheus naming. Signed-off-by: SuperQ <[email protected]>
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.
I couldn't find any Elasticsearch versions where these CPU metrics
were exposed, so they are always set to 0.