<?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: Creating a fully configured anomaly detector in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Creating-a-fully-configured-anomaly-detector/m-p/252220#M4695</link>
    <description>&lt;P&gt;You can create an anomaly detector on time series regardless of origin—whether generated with&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://docs.dynatrace.com/docs/platform/grail/dynatrace-query-language/commands/aggregation-commands#makeTimeseries" target="_blank"&gt;makeTimeseries&lt;/A&gt;&lt;/SPAN&gt;&amp;nbsp;from events, bizevents, logs, or other sources.&lt;/P&gt;
&lt;P&gt;If you have the pre-defined DQL for your use case and know which analyzer to use, you can create a Davis anomaly detector in the &lt;SPAN&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/davis-ai-anomaly-detection-app" target="_blank"&gt;Davis Anomaly Detection app&lt;/A&gt;&lt;/SPAN&gt;.&lt;/P&gt;
&lt;P&gt;However, I recommend simulating the Davis AI analyzer in Notebooks (&lt;SPAN&gt;&lt;A href="https://www.youtube.com/watch?v=-GxLlr9oGGA&amp;amp;list=PLqt2rd0eew1YFx9m8dBFSiGYSBcDuWG38&amp;amp;index=9" target="_blank"&gt;explained here&lt;/A&gt;&lt;/SPAN&gt;) to understand better how it behaves with your DQL and optimize it according to your needs.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Aug 2024 08:26:30 GMT</pubDate>
    <dc:creator>DavidBruendl</dc:creator>
    <dc:date>2024-08-01T08:26:30Z</dc:date>
    <item>
      <title>Creating a fully configured anomaly detector</title>
      <link>https://community.dynatrace.com/t5/Alerting/Creating-a-fully-configured-anomaly-detector/m-p/252219#M4694</link>
      <description>&lt;P&gt;How can you create an anomaly detector in Davis Anomaly Detection app?&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2024 08:25:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Creating-a-fully-configured-anomaly-detector/m-p/252219#M4694</guid>
      <dc:creator>GosiaMurawska</dc:creator>
      <dc:date>2024-08-01T08:25:22Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a fully configured anomaly detector</title>
      <link>https://community.dynatrace.com/t5/Alerting/Creating-a-fully-configured-anomaly-detector/m-p/252220#M4695</link>
      <description>&lt;P&gt;You can create an anomaly detector on time series regardless of origin—whether generated with&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://docs.dynatrace.com/docs/platform/grail/dynatrace-query-language/commands/aggregation-commands#makeTimeseries" target="_blank"&gt;makeTimeseries&lt;/A&gt;&lt;/SPAN&gt;&amp;nbsp;from events, bizevents, logs, or other sources.&lt;/P&gt;
&lt;P&gt;If you have the pre-defined DQL for your use case and know which analyzer to use, you can create a Davis anomaly detector in the &lt;SPAN&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/davis-ai-anomaly-detection-app" target="_blank"&gt;Davis Anomaly Detection app&lt;/A&gt;&lt;/SPAN&gt;.&lt;/P&gt;
&lt;P&gt;However, I recommend simulating the Davis AI analyzer in Notebooks (&lt;SPAN&gt;&lt;A href="https://www.youtube.com/watch?v=-GxLlr9oGGA&amp;amp;list=PLqt2rd0eew1YFx9m8dBFSiGYSBcDuWG38&amp;amp;index=9" target="_blank"&gt;explained here&lt;/A&gt;&lt;/SPAN&gt;) to understand better how it behaves with your DQL and optimize it according to your needs.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2024 08:26:30 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Creating-a-fully-configured-anomaly-detector/m-p/252220#M4695</guid>
      <dc:creator>DavidBruendl</dc:creator>
      <dc:date>2024-08-01T08:26:30Z</dc:date>
    </item>
  </channel>
</rss>

