The same configs (cluster-agent, and app deployment) are working in an existing k8s cluster.  When I copy (the intention is to move) to a new cluster, the new cluster successfully registers on the appd console, but no tier or transaction show up. The cluster agent log says: containermonitoringmodule.go:455 - Either there are no containers discovered or none of the containers are due for registration and repeats: agentregistrationmodule.go:145 - Successfully registered agent again DTVUS-IT-DTVCP-EPOCH-Dev-East The cluster-aget has: tierNameStrategy: manual instrumentationRules: - namespaceRegex: nodejs tierName: dev-east instrumentContainer: select containerMatchString: epoch-awsmw-offerms-dcp   # I verified that this matches the container name. What am I missing? ... View more

My current cluster-agent.yaml has appName repeated 3 times. I hope there is a way for setting a tiername such that on the report, I can separate the results by cluster, or even better, by namespace. I can put the same k8s deployment in either different k8s namespaces (cheaper) or clusters, and need appd to report on them separately. ========= cluster-agent.yaml ======= spec: appName: "EPOCH-svc" image: "docker.io/appdynamics/cluster-agent:latest" serviceAccountName: appdynamics-cluster-agent nsToMonitor: [nodejs,dev1,dev2,perf1] stdoutLogging: "true" instrumentationMethod: Env nsToInstrumentRegex: nodejs defaultAppName: EPOCH-svc logLevel: "DEBUG" instrumentationRules: - namespaceRegex: nodejs instrumentContainer: select containerMatchString: epoch-awsmw-offerms-dcp language: nodejs appName: EPOCH-svc imageInfo: image: "docker.io/appdynamics/nodejs-agent:22.7.0-16-stretch-slim" ... View more