Showing results for 
Show  only  | Search instead for 
Did you mean: 

"Deep monitoring is not activate" error message

Frequent Guest

Hello everyone,

After I installed OneAgent with CloudNativeFullStack template in our AKS cluster, I'm not able to obtain any metrics. I have a message saying that the "Deep monitoring is not active" : 



Do you have any idea or did you face this issue before?


Best regards



We are seeing this same issue within our environment, kindly let us know what could be the issue with cloudNative installation approach.

Our troubleshooting operator logs also shows error : "[31m X Unknown OneAgentCodeModules image[0m"

For GO apps, there are a variety of things that can prevent instrumentation.  
Have you checked your 'GO' rules in these 2 places within settings.

Monitored Technologies -> GO 


Also then check that the old GO static process monitoring rule is not enabled. There is a default duplicate inbuilt process monitoring rule that counters this primary enablement.

Process & containers -. built in monitoring rules.  -> rule 47


These will prevent static GO apps from being instrumented. 

Frequent Guest

We're seeing this as well in a cluster we're using to test the cloud native full stack deployment model.  Specifically we're seeing this issue with Go applications.  Java applications are being instrumented correctly.  We also have a single js frontend application that's being instrumented correctly, I noticed the OP screenshot is js.

DynaMight Guru
DynaMight Guru

Can you all check for this?

You may using some annotation/labels rules that are excluding the pods/namespaces.

Site Reliability Engineer @ Kyndryl

In my case we're using a pretty vanilla dynakube config and are not explicitly adding any Dynatrace related annotations to our deployments / pods.  We're also not excluding any namespaces explicitly in the dynakube config.

We're seeing all Go services failing to be instrumented with deep monitoring, whether that's our services we've created in-house or third party type services like ingress-nginx or Prometheus.

From inspecting one of the pods for one of these Go services, it looks like oneagent is appending the correct annotations to indicate deep monitoring should be enabled:



apiVersion: v1
kind: Pod
  annotations: "true" "true" "true"




DynaMight Pro
DynaMight Pro

We are facing this exact issue on multiple process, with multiple technologies (not only Go but Java - Springboot as well).

@Nissou , did you solve your issue? If so, can you share what you did, please? Thanks!

Best regards, Pedro Deodato


I have same issue in Tomcat JAVA technology. This is a very serious problem. I need help 

I am also getting the same error for java, .net technologies in our cluster. Any suggestion on how to resolve this? Thanks in advance. 

Featured Posts