<?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 Alert if the log &amp;quot;pattern&amp;quot; changes in Log Analytics</title>
    <link>https://community.dynatrace.com/t5/Log-Analytics/Alert-if-the-log-quot-pattern-quot-changes/m-p/292854#M1518</link>
    <description>&lt;P&gt;I've configured openpipeline to move the logs from various applications to dedicated buckets. I've also create metric that is counting the messages per loglevel, host and logsource.&lt;/P&gt;&lt;P&gt;Now I'm struggling with setting up Anomoly dectection to alert the application teams when the log pattern changes, eg. more warnings/criticals than usual &amp;gt; send alert.&lt;/P&gt;&lt;P&gt;The issue seems to be with the setting the scope, it can only handle one timeseries. In one app I get ~600 metrics (loglevel x hosts x logsource).&amp;nbsp; Removing the log source still results in 50ish splittings. Even just using the loglevel means 4 and thats too inaccurate for alerting.&amp;nbsp; The app has a two digit number of servers that are loadbalances, so knowing which servers log behalvior is changing is helping the team to quickly go to the right machine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help appreciated.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Jan 2026 15:51:10 GMT</pubDate>
    <dc:creator>gschramm</dc:creator>
    <dc:date>2026-01-12T15:51:10Z</dc:date>
    <item>
      <title>Alert if the log "pattern" changes</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Alert-if-the-log-quot-pattern-quot-changes/m-p/292854#M1518</link>
      <description>&lt;P&gt;I've configured openpipeline to move the logs from various applications to dedicated buckets. I've also create metric that is counting the messages per loglevel, host and logsource.&lt;/P&gt;&lt;P&gt;Now I'm struggling with setting up Anomoly dectection to alert the application teams when the log pattern changes, eg. more warnings/criticals than usual &amp;gt; send alert.&lt;/P&gt;&lt;P&gt;The issue seems to be with the setting the scope, it can only handle one timeseries. In one app I get ~600 metrics (loglevel x hosts x logsource).&amp;nbsp; Removing the log source still results in 50ish splittings. Even just using the loglevel means 4 and thats too inaccurate for alerting.&amp;nbsp; The app has a two digit number of servers that are loadbalances, so knowing which servers log behalvior is changing is helping the team to quickly go to the right machine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2026 15:51:10 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Alert-if-the-log-quot-pattern-quot-changes/m-p/292854#M1518</guid>
      <dc:creator>gschramm</dc:creator>
      <dc:date>2026-01-12T15:51:10Z</dc:date>
    </item>
  </channel>
</rss>

