feat(ui): use time range in flux Schema Explorer #5858
Merged
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
sranka
changed the title
ivankudibal
approved these changes
Feb 17, 2022
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.
Closes #5849
Briefly describe your proposed changes:
Flux Schema Explorer shows data in the user-selected time range and also reacts upon change of the time range. Schema tree shows that its data are controlled by a selected time range,
Additionally
What was the problem?
The explorer always used -30d as a time range to show schema data. It caused high latencies or timeouts in the schema queries over huge data sets.
What was the solution?
The user can choose the time range for showing the Schema Explorer data and thus reduce the time required for schema queries.