<?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: Log monitoring wildcards in Log Analytics</title>
    <link>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283884#M1417</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/78719"&gt;@Agoyals&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It’s strange that ** didn’t work, as it should recursively ignore the number of nested directories.&lt;BR /&gt;Perhaps a possible solution would be to define in Grail “File name equals abc.gc.log” along with the condition “Path contains /logs/”.&lt;/P&gt;</description>
    <pubDate>Fri, 15 Aug 2025 06:07:21 GMT</pubDate>
    <dc:creator>lubrman</dc:creator>
    <dc:date>2025-08-15T06:07:21Z</dc:date>
    <item>
      <title>Log monitoring wildcards</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283609#M1407</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I am new to Dynatrace. Looking to monitor some logs which present in multiple directory (multi depth). Trying to find a way where can define a single source so it can cover all the matching pattern logs recursively in all sub directories.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;example:&lt;BR /&gt;/logs/abc.gc.log&lt;BR /&gt;/logs/xyz/abc.gc.log&lt;BR /&gt;&lt;SPAN&gt;/logs/zys/xyz/abc.gc.log&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I was trying something like this but seems incorrect&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;/logs/**/abc.gc.log&amp;nbsp; &amp;nbsp;(this doesn't cover multiple depths)&lt;/P&gt;&lt;P&gt;Is there any way where we can define this in single source&amp;nbsp; ?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Aug 2025 09:25:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283609#M1407</guid>
      <dc:creator>Agoyals</dc:creator>
      <dc:date>2025-08-12T09:25:18Z</dc:date>
    </item>
    <item>
      <title>Re: Log monitoring wildcards</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283719#M1408</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;You can check &lt;A title="Log file matching" href="https://docs.dynatrace.com/docs/shortlink/log-monitoring-custom-source#log-file-matching" target="_blank" rel="noopener"&gt;Log file matching&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Wed, 13 Aug 2025 09:36:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283719#M1408</guid>
      <dc:creator>AntonPineiro</dc:creator>
      <dc:date>2025-08-13T09:36:44Z</dc:date>
    </item>
    <item>
      <title>Re: Log monitoring wildcards</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283721#M1409</link>
      <description>&lt;P&gt;Its not mentioned there that's why checking here. if any one else experienced such requirement and have idea how to configure such use case.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Aug 2025 10:01:20 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283721#M1409</guid>
      <dc:creator>Agoyals</dc:creator>
      <dc:date>2025-08-13T10:01:20Z</dc:date>
    </item>
    <item>
      <title>Re: Log monitoring wildcards</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283871#M1416</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Do you see which logs are autodiscovered by OneAgent?&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Thu, 14 Aug 2025 18:58:49 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283871#M1416</guid>
      <dc:creator>AntonPineiro</dc:creator>
      <dc:date>2025-08-14T18:58:49Z</dc:date>
    </item>
    <item>
      <title>Re: Log monitoring wildcards</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283884#M1417</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/78719"&gt;@Agoyals&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It’s strange that ** didn’t work, as it should recursively ignore the number of nested directories.&lt;BR /&gt;Perhaps a possible solution would be to define in Grail “File name equals abc.gc.log” along with the condition “Path contains /logs/”.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Aug 2025 06:07:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Log-monitoring-wildcards/m-p/283884#M1417</guid>
      <dc:creator>lubrman</dc:creator>
      <dc:date>2025-08-15T06:07:21Z</dc:date>
    </item>
  </channel>
</rss>

