Splunk AppDynamics

cluster agent not capturing transactions

Kenny_Yu
Path Finder

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?

Labels (3)
Tags (1)
0 Karma
1 Solution

Kenny_Yu
Path Finder

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.

View solution in original post

Kenny_Yu
Path Finder

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.

Get Updates on the Splunk Community!

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...