Group: Forum Members
thanks for the positive feedback. I'm aware of the little inconsistence ORing AND filters and that the approach would not allow arbitrary logical expressions. And I like the idea of a general query language. I would favor the following approach.
First, I would implement the OR filter to be expandable as shown in the picture. However not adding AND filters as subtrees to the OR filter. So the same filter functionality as is now. The big advantage I see is, that the OR filters can then easily be modified this way (deleting parts of the filter, adding new filters, modifying current filters, using drag and drop). This should cover at least 90% of the standard use cases in an easy, intuitive manner. You would have on one side the classical AND filters to filter the log entries starting from all filters and narrowing down the messages step by step from top to bottom. And you have the classical OR filters to start bottom up by single messages and adding them up. This would be the first release.
Second, I would later implement the general query language filter you suggested. Very powerful, but probably not so easy to use as the normal filters and drag and drop. This would be used only for special cases. And additionally this new filter could be used inside the classical AND or OR expressions. This would then be a future release.
Thanks for listening,