<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Ease of log procurement in Dynatrace in Log Analytics</title>
    <link>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/301234#M1591</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/104546"&gt;@VivekMalapaka&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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:&amp;nbsp;Content → is not → "string_1", "string_2", "string_3"&lt;/P&gt;&lt;P&gt;As of now, you'd need to add separate filter entries for each value.&amp;nbsp;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.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sujit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Jun 2026 23:35:16 GMT</pubDate>
    <dc:creator>sujit_k_singh</dc:creator>
    <dc:date>2026-06-25T23:35:16Z</dc:date>
    <item>
      <title>Ease of log procurement in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/300304#M1573</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;There should be a convenient feature for the user to search logs by adding filter pills.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;
&lt;P&gt;For example: If we want to remove three statements, we need to write a query in the filter: content!=*"statement 1"* AND&amp;nbsp;content!=*"statement 2"* AND&amp;nbsp;content!=*"statement 3"*&lt;/P&gt;
&lt;P&gt;Instead how about giving a GUI as shown below:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="VivekMalapaka_0-1780498702203.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/33350iD7FFA72EA304D6D8/image-size/medium?v=v2&amp;amp;px=400" role="button" title="VivekMalapaka_0-1780498702203.png" alt="VivekMalapaka_0-1780498702203.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You give many options to add such trios and now you give a search option to the right side.&lt;/P&gt;
&lt;P&gt;Is there any reason why GUI part for log filter was skipped? Or was this never considered at all?&lt;BR /&gt;If there is a convenient way to filter logs, then the users can procure their logs with ease.&lt;BR /&gt;Writing a query is definitely not a convenient way for the end user.&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Vivek Malapaka&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jun 2026 06:56:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/300304#M1573</guid>
      <dc:creator>VivekMalapaka</dc:creator>
      <dc:date>2026-06-12T06:56:04Z</dc:date>
    </item>
    <item>
      <title>Re: Ease of log procurement in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/300489#M1579</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/104546"&gt;@VivekMalapaka&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;This feature actually already exists in the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Logs app (new UI / Grail-based). The filter bar supports exactly what you're describing — pill-based content filtering with GUI operators.&lt;/P&gt;&lt;P class=""&gt;When you add a filter on the&amp;nbsp;content&amp;nbsp;attribute, you get these operators without writing any DQL:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Contains / Doesn't contain&lt;/LI&gt;&lt;LI&gt;Starts with / Doesn't start with&lt;/LI&gt;&lt;LI&gt;Ends with / Doesn't end with&lt;/LI&gt;&lt;LI&gt;Equals / Doesn't equal&lt;/LI&gt;&lt;LI&gt;Matches phrase / Does not match phrase&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;So for your example of excluding three statements, you can add multiple filter pills using&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;"&lt;/STRONG&gt;Doesn't contain&lt;STRONG&gt;"&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;for each statement — no query syntax needed, see screenshot&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sujit_k_singh_1-1781002909449.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/33396i2E3C161942AE3999/image-size/large?v=v2&amp;amp;px=999" role="button" title="sujit_k_singh_1-1781002909449.png" alt="sujit_k_singh_1-1781002909449.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sujit&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jun 2026 11:04:46 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/300489#M1579</guid>
      <dc:creator>sujit_k_singh</dc:creator>
      <dc:date>2026-06-09T11:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: Ease of log procurement in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/301214#M1589</link>
      <description>&lt;P&gt;Hi Sujit,&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Suppose you want to eliminate three strings in your query. Conventionally, you need to write:&lt;BR /&gt;&lt;BR /&gt;Content!=*"string_1"* AND&amp;nbsp;Content!=*"string_2"* AND&amp;nbsp;Content!=*"string_3"*&lt;/P&gt;&lt;P&gt;So as described in image present in the description section of this ticket, why can't we have &amp;lt;Content&amp;gt; &amp;lt;is not&amp;gt; &amp;lt;"string_1", "string_2", "string_3"*&amp;gt; directly in the filter itself (Not the DQL)?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Don't you think that the interface needs to improve?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Vivek Malapaka&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jun 2026 14:42:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/301214#M1589</guid>
      <dc:creator>VivekMalapaka</dc:creator>
      <dc:date>2026-06-25T14:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: Ease of log procurement in Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/301234#M1591</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/104546"&gt;@VivekMalapaka&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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:&amp;nbsp;Content → is not → "string_1", "string_2", "string_3"&lt;/P&gt;&lt;P&gt;As of now, you'd need to add separate filter entries for each value.&amp;nbsp;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.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sujit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jun 2026 23:35:16 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Ease-of-log-procurement-in-Dynatrace/m-p/301234#M1591</guid>
      <dc:creator>sujit_k_singh</dc:creator>
      <dc:date>2026-06-25T23:35:16Z</dc:date>
    </item>
  </channel>
</rss>

