[bugfix] Fixed some metrics of Jexlespression not matching in Elasticsearch #1894
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
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.
What's changed?
In ElasticSearch statistical metrics, the failures in obtaining
cpu_load_averageandcpu_percentare due to expression matching failures. This issue might have been introduced by pr #1859 , which I have already fixed.Before the fix:
cpu_load_averageandcpu_percentcould not be obtained due to expression matching errors.
After the fix:
cpu_load_averageandcpu_percenthas been resolved, allowing for successful retrieval of these statistical metrics.
Checklist