<?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: Alert Setup for DaemonSet Pod in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Alert-Setup-for-DaemonSet-Pod/m-p/290145#M6027</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/82918"&gt;@Gyanendra&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;Here is a Documentation article about Node alerts:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/alerts-k8s#node" target="_self"&gt;Alert on common Kubernetes/Openshift issues - Node alerts&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;Available alerts are including detecting node readiness issues and detecting problematic node conditions. Would those solve your use case?&lt;BR /&gt;&lt;BR /&gt;Right below the table in the article you can check Node metrics and DQL queries, that are used for creating those alerts.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 24 Nov 2025 13:45:14 GMT</pubDate>
    <dc:creator>MaciejNeumann</dc:creator>
    <dc:date>2025-11-24T13:45:14Z</dc:date>
    <item>
      <title>Alert Setup for DaemonSet Pod</title>
      <link>https://community.dynatrace.com/t5/Alerting/Alert-Setup-for-DaemonSet-Pod/m-p/266192#M5304</link>
      <description>&lt;P&gt;I need to create an alert in Dynatrace for a DaemonSet to trigger a problem if any pod is not running or goes down, regardless of the node count. For example:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Cluster 1 has 10 nodes&lt;/LI&gt;
&lt;LI&gt;Cluster 2 has 5 nodes&lt;/LI&gt;
&lt;LI&gt;Cluster 3 has 8 nodes&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Each cluster has a Fluentd DaemonSet running on all nodes. The alert should dynamically monitor all clusters and generate a problem if any DaemonSet pod fails, without relying on a fixed threshold, as node counts vary across clusters.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 13:46:37 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Alert-Setup-for-DaemonSet-Pod/m-p/266192#M5304</guid>
      <dc:creator>Gyanendra</dc:creator>
      <dc:date>2025-11-24T13:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: Alert Setup for DaemonSet Pod</title>
      <link>https://community.dynatrace.com/t5/Alerting/Alert-Setup-for-DaemonSet-Pod/m-p/290145#M6027</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/82918"&gt;@Gyanendra&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;Here is a Documentation article about Node alerts:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/alerts-k8s#node" target="_self"&gt;Alert on common Kubernetes/Openshift issues - Node alerts&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;Available alerts are including detecting node readiness issues and detecting problematic node conditions. Would those solve your use case?&lt;BR /&gt;&lt;BR /&gt;Right below the table in the article you can check Node metrics and DQL queries, that are used for creating those alerts.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 13:45:14 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Alert-Setup-for-DaemonSet-Pod/m-p/290145#M6027</guid>
      <dc:creator>MaciejNeumann</dc:creator>
      <dc:date>2025-11-24T13:45:14Z</dc:date>
    </item>
  </channel>
</rss>

