Splunk AppDynamics

Java agent shows successfully registered/Started but doesn't show up in Tiers and nodes

Sthitha_Madhir2
New Member

Our java agent isnt reporting to the controller thougn in the logs we see a message saying the agent was successfully started. I dont see any mesage that it is connected to the controller but the node is shown as [null]

Picked up _JAVA_OPTIONS: -Djdk.tls.maxCertificateChainLength=20
Java 9+ detected, booting with Java9Util enabled.
Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_APPLICATION_NAME] for application name [App_Name]
Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_TIER_NAME] for tier name [Tier_Name]
Full Agent Registration Info Resolver using selfService [false]
Full Agent Registration Info Resolver using selfService [false]
Full Agent Registration Info Resolver using ephemeral node setting [false]
Full Agent Registration Info Resolver using application name [App_Name]
Read property [reuse node name] from system property [appdynamics.agent.reuse.nodeName]
Full Agent Registration Info Resolver using tier name [Tier_Name]
Full Agent Registration Info Resolver using node name [null]
Install Directory resolved to[/opt/appdyn/javaagent/23.8.0.35032]
getBootstrapResource not available on ClassLoader
Class with name [com.ibm.lang.management.internal.ExtendedOperatingSystemMXBeanImpl] is not available in classpath, so will ignore export access.
[AD Agent init] Thu Oct 05 17:45:32 UTC 2023[DEBUG]: JavaAgent - Setting AgentClassLoader as Context ClassLoader
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - Low Entropy Mode: Attempting to swap to non-blocking PRNG algorithm
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - UUIDPool size is 10
Agent conf directory set to [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032/conf]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - Agent conf directory set to [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032/conf]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver is running
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_APPLICATION_NAME] for application name [App_Name]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Full Agent Registration Info Resolver found env variable [APPDYNAMICS_AGENT_TIER_NAME] for tier name [Tier_Name]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [false]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [false]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using ephemeral node setting [false]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [App_Name]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Read property [reuse node name] from system property [appdynamics.agent.reuse.nodeName]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [Tier_Name]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [null]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Agent runtime directory set to [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Agent node directory set to [Tier_Name-35-vvcbk]
Agent runtime conf directory set to /opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032/conf
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: AgentInstallManager - Agent runtime conf directory set to /opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032/conf
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - JDK Compatibility: 1.8+
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - Using Java Agent Version [Server Agent #23.8.0.35032 v23.8.0 GA compatible with 4.4.1.0 rc2229efcc98cb79cc989b99ed8d8e30995dc1e70 release/23.8.0]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - Running IBM Java Agent [No]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - Java Agent Directory [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - Java Agent AppAgent directory [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032]
Agent logging directory set to [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032/logs]
[AD Agent init] Thu Oct 05 17:45:33 UTC 2023[INFO]: JavaAgent - Agent logging directory set to [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032/logs]
[AD Agent init] Thu Oct 05 17:45:34 UTC 2023[INFO]: JavaAgent - Logging set up for log4j2
[AD Agent init] Thu Oct 05 17:45:34 UTC 2023[INFO]: JavaAgent - ####################################################################################
[AD Agent init] Thu Oct 05 17:45:34 UTC 2023[INFO]: JavaAgent - Java Agent Directory [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032]
[AD Agent init] Thu Oct 05 17:45:34 UTC 2023[INFO]: JavaAgent - Java Agent AppAgent directory [/opt/appdyn/javaagent/23.8.0.35032/ver23.8.0.35032]
[AD Agent init] Thu Oct 05 17:45:34 UTC 2023[INFO]: JavaAgent - Using Java Agent Version [Server Agent #23.8.0.35032 v23.8.0 GA compatible with 4.4.1.0 rc2229efcc98cb79cc989b99ed8d8e30995dc1e70 release/23.8.0]
[AD Agent init] Thu Oct 05 17:45:34 UTC 2023[INFO]: JavaAgent - All agent classes have been pre-loaded
getBootstrapResource not available on ClassLoader
Agent will mark node historical at normal shutdown of JVM
Started AppDynamics Java Agent Successfully.
Labels (1)
0 Karma

iamryan
Community Manager
Community Manager
0 Karma
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 ...