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

OneAgent Operator suddenly seems to be not working

It seems like suddenly, whatever pods generatored by Kubernetes is not injected with OneAgent anymore.

(because all existing or old pods are still monitoring by Dynatrace, but the new pods aren't anymore)


I am about to do a load-test, normally the developers would generate a new sets of pods with the namespace "stress-test".


The services created for the load-test is up and running. But I didn't see any containers nor services with the namespace "stress-test" in my dynatrace managed. What could be the reason behind this?


Best Reagrds,

Wai Keat

3 REPLIES 3

ChadTurner
DynaMight Legend
DynaMight Legend

Are you using a helm chart as the deployment method?

-Chad

Nope, I am using the operator

Is everything correct in your yaml file since that ultimately controls the deployment?

-Chad

Featured Posts