-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for specifying a custom SQL filter #1388
Comments
Hi @hugener . I can see the benefits for this. Also I think we will also need validation and correctness of the SQL query since now it will be free text as input. |
Hi @LiorBanai |
yeah the simple way is to catch the exception but I'll look for more elegant way. |
I gave it a try with the 4.9.0 release. It works well. Thanks! |
good. there more improvements to made (store last X queries for example, auto complete... etc) but for initial option it can be use. Feel free to suggest improvements/changes :) |
I'll close this one. Please reopen/submit new issue if there are problems :) |
Is your feature request related to a problem? Please describe.
While analogy has some support for filtering log files with the predefined inputs like, Source, Text etc. and the UI controls also allows build more complex queries with the query builder. For me clicking a query together is more work that just writing a SQL query.
Being able to write the query by hand also has the advantage of creating a collection of query for analysis.
The predefined queries as I understand it are limited to certain fields like: Source, Text, Date etc.
Describe the solution you'd like
It would be nice to have the possibility to write a custom SQL statement for filtering. I imagine an additional text input in the filtering section that just passes the statement to underlying query.
Describe alternatives you've considered
I was trying to save a query created by the query builder
The text was updated successfully, but these errors were encountered: