<?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 Full stack coverage report for Kubernetes report in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Full-stack-coverage-report-for-Kubernetes-report/m-p/305342#M40398</link>
    <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I monitor multiple Kubernetes clusters with full stack (classic or application observability) and Kubernetes monitoring. I would like to monitor the full stack monitoring coverage every month compared to the pods reported by Kubernetes monitoring.&lt;BR /&gt;This is useful for real full-stack reporting and also to detect Kubernetes workloads that have some monitoring gaps or that are not monitored at all.&lt;BR /&gt;&lt;BR /&gt;To date, I would like to use the billing data `fetch dt.system.events | filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Full-Stack Monitoring"` that contains the host property and&amp;nbsp; compare to pods detected by the Kubernetes monitoring feature. The issues is that this makes a lot of data to gather.&lt;BR /&gt;&lt;BR /&gt;Do you know if there is any ready-made metric for calculating this rate ? or a more simple solution ?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 15 Oct 2026 11:42:35 GMT</pubDate>
    <dc:creator>ftmazzone</dc:creator>
    <dc:date>2026-10-15T11:42:35Z</dc:date>
    <item>
      <title>Full stack coverage report for Kubernetes report</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Full-stack-coverage-report-for-Kubernetes-report/m-p/305342#M40398</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I monitor multiple Kubernetes clusters with full stack (classic or application observability) and Kubernetes monitoring. I would like to monitor the full stack monitoring coverage every month compared to the pods reported by Kubernetes monitoring.&lt;BR /&gt;This is useful for real full-stack reporting and also to detect Kubernetes workloads that have some monitoring gaps or that are not monitored at all.&lt;BR /&gt;&lt;BR /&gt;To date, I would like to use the billing data `fetch dt.system.events | filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Full-Stack Monitoring"` that contains the host property and&amp;nbsp; compare to pods detected by the Kubernetes monitoring feature. The issues is that this makes a lot of data to gather.&lt;BR /&gt;&lt;BR /&gt;Do you know if there is any ready-made metric for calculating this rate ? or a more simple solution ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Oct 2026 11:42:35 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Full-stack-coverage-report-for-Kubernetes-report/m-p/305342#M40398</guid>
      <dc:creator>ftmazzone</dc:creator>
      <dc:date>2026-10-15T11:42:35Z</dc:date>
    </item>
  </channel>
</rss>

