03 Jun 2026
03:51 PM
- last edited on
12 Jun 2026
07:56 AM
by
MaciejNeumann
Hi Team,
There should be a convenient feature for the user to search logs by adding filter pills.
As of now the users should write queries in your language to procure the logs they desire. Can you provide a GUI for the user to filter logs?
For example: If we want to remove three statements, we need to write a query in the filter: content!=*"statement 1"* AND content!=*"statement 2"* AND content!=*"statement 3"*
Instead how about giving a GUI as shown below:
You give many options to add such trios and now you give a search option to the right side.
Is there any reason why GUI part for log filter was skipped? Or was this never considered at all?
If there is a convenient way to filter logs, then the users can procure their logs with ease.
Writing a query is definitely not a convenient way for the end user.
Best Regards,
Vivek Malapaka
09 Jun 2026 12:04 PM
This feature actually already exists in the Logs app (new UI / Grail-based). The filter bar supports exactly what you're describing — pill-based content filtering with GUI operators.
When you add a filter on the content attribute, you get these operators without writing any DQL:
So for your example of excluding three statements, you can add multiple filter pills using "Doesn't contain" for each statement — no query syntax needed, see screenshot
Thanks,
Sujit
25 Jun 2026 03:42 PM
Hi Sujit,
You are theoretically correct, but practically not sure why there is so much of typing. We have to press a star, quotations, the string between them, use AND or OR or both. Dynatrace can give us a better interface for this.
Suppose you want to eliminate three strings in your query. Conventionally, you need to write:
Content!=*"string_1"* AND Content!=*"string_2"* AND Content!=*"string_3"*
So as described in image present in the description section of this ticket, why can't we have <Content> <is not> <"string_1", "string_2", "string_3"*> directly in the filter itself (Not the DQL)?
Don't you think that the interface needs to improve?
Best Regards,
Vivek Malapaka
26 Jun 2026 12:35 AM
That's a valid point. Currently, the Logs app filter bar in Dynatrace does not support multiple comma-separated values in a single filter condition like: Content → is not → "string_1", "string_2", "string_3"
As of now, you'd need to add separate filter entries for each value. This is a current GUI limitation — the filter bar only accepts one value per filter entry. There's no native "multi-value input" in the GUI today.
Thanks,
Sujit
Featured Posts