<?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 service uptime in Dashboarding</title>
    <link>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286925#M5427</link>
    <description>&lt;P&gt;Many thanks.&lt;/P&gt;&lt;P&gt;Above approach helped!&lt;/P&gt;</description>
    <pubDate>Sun, 28 Sep 2025 05:17:11 GMT</pubDate>
    <dc:creator>nsethurama</dc:creator>
    <dc:date>2025-09-28T05:17:11Z</dc:date>
    <item>
      <title>Kubernetes service uptime</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286709#M5418</link>
      <description>&lt;P&gt;How could we get uptime for a k8s cluster (backend) services?&lt;/P&gt;
&lt;P&gt;We are setup our SLO calculations based on the number of error free requests by total number of requests received!&lt;/P&gt;
&lt;P&gt;However, when the service is completely down, we are worried it may affect the actual SLA but it will not change the calculation method as there won't be any change in terms of requests rate!&lt;/P&gt;
&lt;P&gt;Hence, we would like to know the metric for k8s backend service availability or uptime monitoring!&lt;/P&gt;
&lt;P&gt;Kinldy advise!&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Nava&lt;/P&gt;</description>
      <pubDate>Thu, 25 Sep 2025 06:51:33 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286709#M5418</guid>
      <dc:creator>nsethurama</dc:creator>
      <dc:date>2025-09-25T06:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: Kubernetes service uptime</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286724#M5421</link>
      <description>&lt;P&gt;Hi Nava,&lt;/P&gt;&lt;P&gt;You are right — if you calculate SLO only as error-free requests / total requests, then a complete outage with zero traffic won’t change the ratio, even though the service is down. To cover this gap you should add a time-based availability metric from Kubernetes.&lt;/P&gt;&lt;P&gt;A simple approach is to use the ratio of available replicas vs desired replicas for each deployment:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;( k8s.deployment.available:splitBy() / k8s.deployment.desired:splitBy() ) * 100&lt;/LI-CODE&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;When all desired replicas are running, the value = 100%.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;If some pods are not available, the percentage drops.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;If the whole deployment is down (available = 0, desired &amp;gt; 0), the metric = 0%.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;You can use this ratio either in a dashboard tile or directly as the numerator/denominator in a &lt;STRONG&gt;metric-based SLO&lt;/STRONG&gt;. That way you combine your &lt;STRONG&gt;request-based SLO&lt;/STRONG&gt; with a &lt;STRONG&gt;replica-based uptime SLO&lt;/STRONG&gt;, and you can report SLA only when both conditions are satisfied.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Sep 2025 11:16:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286724#M5421</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2025-09-24T11:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: Kubernetes service uptime</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286785#M5422</link>
      <description>&lt;P&gt;We are in Dynatrace managed and i am not able to see any metric related to&amp;nbsp;&lt;/P&gt;&lt;PRE&gt; k8s.deployment.available&lt;/PRE&gt;&lt;P&gt;or&lt;/P&gt;&lt;PRE&gt;k8s.deployment.desired&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know, if i am missing something here!&lt;/P&gt;</description>
      <pubDate>Thu, 25 Sep 2025 04:45:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286785#M5422</guid>
      <dc:creator>nsethurama</dc:creator>
      <dc:date>2025-09-25T04:45:53Z</dc:date>
    </item>
    <item>
      <title>Re: Kubernetes service uptime</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286821#M5423</link>
      <description>&lt;P&gt;Unfortunately, I don’t have a way to test this myself, but you can try the following approach.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Metric keys (Classic):&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;builtin:kubernetes.pods — count of pods (filter by phase “Running”)&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;builtin:kubernetes.workload.pods_desired — desired pods per workload&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Metric selector (Advanced mode), grouped by cluster/namespace/workload:&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;(
  builtin:kubernetes.pods
    :filter(eq(k8s.pod.phase,"Running"))
    :splitBy("k8s.cluster.name","k8s.namespace.name","k8s.workload.name")
    :sum
)
/
(
  builtin:kubernetes.workload.pods_desired
    :splitBy("k8s.cluster.name","k8s.namespace.name","k8s.workload.name")
    :avg
)
*100&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Sep 2025 12:16:06 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286821#M5423</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2025-09-25T12:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Kubernetes service uptime</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286925#M5427</link>
      <description>&lt;P&gt;Many thanks.&lt;/P&gt;&lt;P&gt;Above approach helped!&lt;/P&gt;</description>
      <pubDate>Sun, 28 Sep 2025 05:17:11 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Kubernetes-service-uptime/m-p/286925#M5427</guid>
      <dc:creator>nsethurama</dc:creator>
      <dc:date>2025-09-28T05:17:11Z</dc:date>
    </item>
  </channel>
</rss>

