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

cluster agent not capturing transactions

Kenny.Yu
Maker

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?

 

 

1 REPLY 1

Kenny.Yu
Maker

An update: Support helped me figure out that the problem was from a version mismatch between the cluster agent, which fetches the latest, and the operator, which has a fixed version tag.

Ask the Experts Session: Hybrid Application Monitoring Deployment

Join us on Feb 26 to explore Splunk AppDynamics deployment strategies, SaaS models, agent rollout plans, and expert best practices.


Register Now

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here