<?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: Kubernetes pod alert in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269830#M2897</link>
    <description>&lt;P&gt;FYI&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/40718"&gt;@florian_g&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Feb 2025 08:00:05 GMT</pubDate>
    <dc:creator>Michal_Gebacki</dc:creator>
    <dc:date>2025-02-12T08:00:05Z</dc:date>
    <item>
      <title>Kubernetes pod alert</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269826#M2895</link>
      <description>&lt;P&gt;My client requirement is like whenever the cluster or pod goes down or restarts/recycles then it needs to generate an problem alert into the DT environment. The Kubernetes platform configured already to DT and the pod recycle alert needs to be triggered for a specific container/pod.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I checked the documentation "&lt;A title="Kubernetes-Alerting" href="https://community.dynatrace.com/t5/Alerting/Kubernetes-Alerting/m-p/262393#M5067" target="_self"&gt;Kubernetes-Alerting&lt;/A&gt;&amp;nbsp;" but did not get it as it shows the configuration for entire Kubernetes platform my requirement is for specified cluster/pod.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please assist and help with the correct steps.&lt;/P&gt;
&lt;P&gt;Hope the query is clear.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2025 07:18:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269826#M2895</guid>
      <dc:creator>gauravpayghan__</dc:creator>
      <dc:date>2025-02-17T07:18:59Z</dc:date>
    </item>
    <item>
      <title>Re: Kubernetes pod alert</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269827#M2896</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/6884"&gt;@gaddenna_n_k&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/18264"&gt;@dannemca&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/44566"&gt;@Michal_Gebacki&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/56036"&gt;@dynadynat&lt;/a&gt;&amp;nbsp;please assist&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 07:31:36 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269827#M2896</guid>
      <dc:creator>gauravpayghan__</dc:creator>
      <dc:date>2025-02-12T07:31:36Z</dc:date>
    </item>
    <item>
      <title>Re: Kubernetes pod alert</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269830#M2897</link>
      <description>&lt;P&gt;FYI&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/40718"&gt;@florian_g&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 08:00:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269830#M2897</guid>
      <dc:creator>Michal_Gebacki</dc:creator>
      <dc:date>2025-02-12T08:00:05Z</dc:date>
    </item>
    <item>
      <title>Re: Kubernetes pod alert</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269834#M2898</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/76461"&gt;@gauravpayghan__&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;There are few options. First you can switch off the env level Kubernetes anomaly settings and then swith on namespace level. Or if it still not acceptable you can create individual metric events. Metric for restarts:&amp;nbsp;&lt;SPAN&gt;builtin:kubernetes.container.restarts, metric for pod count:&amp;nbsp;builtin:kubernetes.pods (woth pod_status or pod_phase dimension).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I hope it helps.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;János&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2025 08:24:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-pod-alert/m-p/269834#M2898</guid>
      <dc:creator>Mizső</dc:creator>
      <dc:date>2025-02-12T08:24:58Z</dc:date>
    </item>
  </channel>
</rss>

