<?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: K8S reduction of monitored namespaces in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-reduction-of-monitored-namespaces/m-p/275397#M2994</link>
    <description>&lt;P&gt;Hi!&lt;BR /&gt;In classic full stack and Cloud Native Full Stack the licensing is billed based on the memory of the cluster's node, it doesn't depends by the number/memory of namespace monitored.&lt;BR /&gt;In your case you, you should migrate to &lt;A href="https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/deployment/application-observability" target="_blank"&gt;application-only approach&lt;/A&gt; and using a &lt;A href="https://docs.dynatrace.com/docs/shortlink/annotate" target="_blank"&gt;namespace selector&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 17 Apr 2025 10:27:01 GMT</pubDate>
    <dc:creator>yanezza</dc:creator>
    <dc:date>2025-04-17T10:27:01Z</dc:date>
    <item>
      <title>Kubernetes reduction of monitored namespaces</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-reduction-of-monitored-namespaces/m-p/275375#M2993</link>
      <description>&lt;P&gt;Hi, we are considering reducing the monitoring of some K8s namespaces to be able to contain license usage. We use the Classic fullstack, we have applied some rules of Container monitoring&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vpasinelli_0-1744880324588.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/27577i267F476AF499FB61/image-size/medium?v=v2&amp;amp;px=400" role="button" title="vpasinelli_0-1744880324588.png" alt="vpasinelli_0-1744880324588.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;However, even if we have applied this rule we still see the monitored namespace and cannot exclude it. Do you have any solution or had a similar experience or if you have other advice for the reduction of monitored entities would be really helpful.&lt;BR /&gt;&lt;BR /&gt;Thanks &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 10:57:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-reduction-of-monitored-namespaces/m-p/275375#M2993</guid>
      <dc:creator>vpasinelli</dc:creator>
      <dc:date>2025-05-06T10:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: K8S reduction of monitored namespaces</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-reduction-of-monitored-namespaces/m-p/275397#M2994</link>
      <description>&lt;P&gt;Hi!&lt;BR /&gt;In classic full stack and Cloud Native Full Stack the licensing is billed based on the memory of the cluster's node, it doesn't depends by the number/memory of namespace monitored.&lt;BR /&gt;In your case you, you should migrate to &lt;A href="https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/deployment/application-observability" target="_blank"&gt;application-only approach&lt;/A&gt; and using a &lt;A href="https://docs.dynatrace.com/docs/shortlink/annotate" target="_blank"&gt;namespace selector&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Apr 2025 10:27:01 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Kubernetes-reduction-of-monitored-namespaces/m-p/275397#M2994</guid>
      <dc:creator>yanezza</dc:creator>
      <dc:date>2025-04-17T10:27:01Z</dc:date>
    </item>
  </channel>
</rss>

