<?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: Template Creation for Davis Anomaly Detectors in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Template-Creation-for-Davis-Anomaly-Detectors/m-p/281334#M5753</link>
    <description>&lt;P&gt;Here is an updated to the fields that we are currently use:&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jul 2025 22:21:29 GMT</pubDate>
    <dc:creator>jeffscelza76</dc:creator>
    <dc:date>2025-07-10T22:21:29Z</dc:date>
    <item>
      <title>Template Creation for Davis Anomaly Detectors</title>
      <link>https://community.dynatrace.com/t5/Alerting/Template-Creation-for-Davis-Anomaly-Detectors/m-p/270990#M5463</link>
      <description>&lt;P&gt;I am creating some custom Davis Anomaly Detectors for logs and metrics and was wondering if anyone had a set of properties that they recommend. The goal is to better populate the Davis Problem once triggered to ensure seamless resolution. It would be nice to have links to logs as well as affected entities, but not sure how best to do this. Below is some Event Properties I am adding to my template:&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="50%"&gt;dt.source_entity&lt;/TD&gt;&lt;TD width="50%"&gt;{dims:dt.source_entity}&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="50%"&gt;event.type&lt;/TD&gt;&lt;TD width="50%"&gt;CUSTOM_ALERT&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="50%"&gt;event.description&lt;/TD&gt;&lt;TD width="50%"&gt;&amp;nbsp;Threshold [{threshold}] for [{alert_condition}] in your logs for entity [{dims:dt.source_entity}]&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;event.name&lt;/TD&gt;&lt;TD&gt;Service - Found errors in logs&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;owner&lt;/TD&gt;&lt;TD&gt;team_name&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know if I am missing something or there is a better way to do it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2025 19:37:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Template-Creation-for-Davis-Anomaly-Detectors/m-p/270990#M5463</guid>
      <dc:creator>jeffscelza76</dc:creator>
      <dc:date>2025-02-25T19:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: Template Creation for Davis Anomaly Detectors</title>
      <link>https://community.dynatrace.com/t5/Alerting/Template-Creation-for-Davis-Anomaly-Detectors/m-p/281194#M5746</link>
      <description>&lt;P&gt;This is great and can be expanded to support any organization. For example, If you leverage Xmatters, and this alert is unique for the specific team, you can always add in the Xmatters group name.&amp;nbsp; We also add in the variable for the defined threshold/baseline so its clear to the team why the alert was triggered.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jul 2025 19:13:31 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Template-Creation-for-Davis-Anomaly-Detectors/m-p/281194#M5746</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2025-07-09T19:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: Template Creation for Davis Anomaly Detectors</title>
      <link>https://community.dynatrace.com/t5/Alerting/Template-Creation-for-Davis-Anomaly-Detectors/m-p/281334#M5753</link>
      <description>&lt;P&gt;Here is an updated to the fields that we are currently use:&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 22:21:29 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Template-Creation-for-Davis-Anomaly-Detectors/m-p/281334#M5753</guid>
      <dc:creator>jeffscelza76</dc:creator>
      <dc:date>2025-07-10T22:21:29Z</dc:date>
    </item>
  </channel>
</rss>

