topic Re: Is there a way to disable OneAgent from instrumenting on an Application/Pod/Deployment or Namespace level in Kubernetes in Container platforms

Disable Dynatrace OneAgent Instrumentation on Specific Kubernetes Namespaces

kapil_khanna — Tue, 27 Jan 2026 10:42:29 GMT

Summary: This post explains how to exclude Kubernetes namespaces from OneAgent instrumentation. It describes annotation‑based methods and configuration options in Dynakube.

Currently, OneAgent can be configured to disable injection on a per host or on a technology stack basis. I was wondering if there is any way to disable monitoring on a namespace or even more granular basis, e.g., Container, Pod, or Deployment basis via the use of environment variables or annotations?

Re: Is there a way to disable OneAgent from instrumenting on an Application/Pod/Deployment or Namespace level in Kubernetes

Enrico_F — Fri, 21 Feb 2020 18:21:10 GMT

Yes, have a look under Settings -> Processes & Containers -> Container monitoring:

Re: Is there a way to disable OneAgent from instrumenting on an Application/Pod/Deployment or Namespace level in Kubernetes

sivart_89 — Tue, 09 Aug 2022 16:18:41 GMT

Thanks for this, came in use today 🙂

Know of any plans to allow for more filtering when setting up do not monitor rules? In our case we have a namespace that is in 2 different kub clusters in our env. We ideally wanted to not monitor the namespace in just 1 of those clusters. I think an addition of the cluster name and the ability to use multiple options (AND logic) would be a good addition.