0

I'm using a Python application that had AppDynamics working correctly on Rancher, but it stopped working when migrated to EKS. This application is able to connect to AppDynamics and creates the agent, but then its proxy enters in a loop like this:

INFO [AD Thread Pool-Global1] ConfigurationChannel - Sending Registration request with: Application Name MYAPPLICATION, Tier Name [tier-MYTIER], Node Name [node-MYNODE], Host Name [MYHOST] Node Unique Local ID [node-MYNODE], Version [Tags]
Registered app server agent with Node ID[<ID NODE>] Component ID[<COMPONENT ID>] Application ID [<APPICATION ID>]
INFO [AD Thread Pool-Global1] ConfigurationChannel - Auto agent registration attempted: <my application name> Component Name [tier-MYTIER] Node Name [node-MYNODE]
INFO [AD Thread Pool-Global1] ConfigurationChannel - Auto agent registration SUCCEEDED!
INFO [AD Thread Pool-Global1] ConfigurationChannel - Registration information received Node ID[123455] Component ID[<COMPONENT_ID>] Application ID [<APPLICATION ID>]
INFO [AD Thread Pool-Global1] ConfigurationChannel - controllerGUID[null] accountGUID[null]
WARN [AD Thread-Metric Reporter1] MetricHandler - Metric Reporter Queue full. Dropping metrics.

What's happening? I suppose the problem is with the controllerGUID[null] accountGUID[null] but I don't know what is causing that, specially considering that this worked correctly just before the migration

asked Nov 17, 2025 at 11:59

0

Know someone who can answer? Share a link to this question via email, Twitter, or Facebook.

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.