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

deep monitoring is not working

romil618
Participant

Hi,

Could you please help me understand why deep monitoring is not active? I've added below dynakube annotations. I see the pods are injected with these annotations, but I dynatrace I still see the message the deep monitoring not active.

feature.dynatrace.com/automatic-injection: "true"

oneagent.dynatrace.com/inject: "true

 

romil618_0-1747518098014.png

 

6 REPLIES 6

p_devulapalli
Leader

@romil618 Did you get a chance to take a look at the below thread, its a similar issue with different solutions that might help

https://community.dynatrace.com/t5/Container-platforms/Kubernetes-injection-was-not-configured-for-t...

 

Phani Devulapalli

@p_devulapalli  Yeah I looked at that before, but I couldn't find a single solution that fits my case. We don't have any rules that could be causing it. I don't think we can switch back to classicFullStack as some of them have suggested. Since we have the annotations added in the dynakube, do we need to still annotate namespace as one solution suggest?

Doc: https://docs.dynatrace.com/docs/shortlink/annotate#monitor-specific-namespaces

As far as I know, deep monitoring for Cloud Native Full Stack is not enable at least you specify what namespaces, pods, etc. you want to monitor.

On my experience, I had to do that for having deep monitoring in the namespaces in which we wanted to have deep monitoring."

Any other suggestion to resolve this?

Does anyone have any insights on how to get this deep monitoring feature working?

@romil618 there can be many reasons for that. If still in doubts, collect a support archive from your operator and check the log files. 
Provide the kubectl describe for the particular pod and your dynakube configuration.

Certified Dynatrace Master | Alanata a.s., Slovakia, Dynatrace Master Partner

Thank you!! We have created a support ticket and have provided the details.

Featured Posts