Elasticsearch: Allow setting a custom limit for log queries #32422
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
ivanahuckova
approved these changes
Mar 29, 2021
Elfo404
force-pushed
the
gio/feat/configurable-logs-limit
branch
from
6137fb0 to
608baa0
Compare
Elfo404
force-pushed
the
gio/feat/configurable-logs-limit
branch
from
608baa0 to
b33f82b
Compare
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.
Related to #24236.
As pointed out in #24236 (comment) it's not a definitive solution to the issue, but it may mitigate the pain a bit.
also, it fixes the behavior of the query editor as In the previous version bucket aggregations and other metrics were ignored, so they are now removed from the editor as well.
/cc @simianhacker do you think this could be a viable short term solution?