<?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 Alerting for custom Prometheus and Cloudwatch metrics in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Alerting-for-custom-Prometheus-and-Cloudwatch-metrics/m-p/291206#M6072</link>
    <description>&lt;P&gt;Hi ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I happend to come across multiple discussions , but yet unclear.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Am able to create&amp;nbsp; Davis anomaly detection alerts for DT metrics and define problems that includes all metadata.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However i have two other sources of data ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Prometheus metrics sourced via&amp;nbsp; opentelemetry from k8s.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Cloudwatch metrics pushed to DT , via cloudwatch streams.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would like to setup alerts that generate problems with all metadata.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What choices do i have , i have several dimensions for the alert , for example by cluster, namespace, account etc.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;stuck with this problem for a while one after another.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 18 Dec 2025 10:14:30 GMT</pubDate>
    <dc:creator>mailvk23</dc:creator>
    <dc:date>2025-12-18T10:14:30Z</dc:date>
    <item>
      <title>Alerting for custom Prometheus and Cloudwatch metrics</title>
      <link>https://community.dynatrace.com/t5/Alerting/Alerting-for-custom-Prometheus-and-Cloudwatch-metrics/m-p/291206#M6072</link>
      <description>&lt;P&gt;Hi ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I happend to come across multiple discussions , but yet unclear.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Am able to create&amp;nbsp; Davis anomaly detection alerts for DT metrics and define problems that includes all metadata.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However i have two other sources of data ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Prometheus metrics sourced via&amp;nbsp; opentelemetry from k8s.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. Cloudwatch metrics pushed to DT , via cloudwatch streams.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would like to setup alerts that generate problems with all metadata.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What choices do i have , i have several dimensions for the alert , for example by cluster, namespace, account etc.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;stuck with this problem for a while one after another.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Dec 2025 10:14:30 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Alerting-for-custom-Prometheus-and-Cloudwatch-metrics/m-p/291206#M6072</guid>
      <dc:creator>mailvk23</dc:creator>
      <dc:date>2025-12-18T10:14:30Z</dc:date>
    </item>
  </channel>
</rss>

