This repository has been archived by the owner on Nov 22, 2017. It is now read-only.
Add filter fields action on logs #296
Open
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hello
When you're browsing logs, searching with a field, refining and refining your query, sometimes you need to re-query with just one of the field of one of your previous results.
So I added a "filter" action that cleans previous query parameters and use this only field to build the query.
Use case : find some errors in your distributed system, refine with just one source type and then want to see the whole path of the request with one uuid field
TODO : refactor code / add this features to every popup that contains an action (analysis, trend, etc...)
Bonus : I've fixed URL highlighting for URLs containing "," and "-"