Splunk AppDynamics

Machine agent is reporting in 2 applications

CommunityUser
Splunk Employee
Splunk Employee

The machine agent is reporting in two applications. Even we updated the correct application name in appdmcagent file but still whenever we are starting service, it started reporting in old n new application both. Checked for appD process in that agent, the correct one is showing but in appd controller, that host is running 2 applications. Can anyone suggest on it?

Labels (3)
0 Karma
1 Solution

Naoto_Yamamoto
Path Finder
Hi Amritesh,
 
Thanks for posting the question on the Community.
 

First, could you check different application name value is set in 2 agents’ controller-info.xml? 
If this is the case, single machine agent will surely get associated to both APM nodes, because controller associates machine to APM based on hostname.
 
You can also check whether this happens by clicking “Settings”->”AppDynamics Agents”, and search your hostname in search query.
 
In this case, this is the steps to solve issue: 
  1. Please stop one of the APM agent for which machine agent do not want to report
  2. Start APM Java agent with this argument:-Dappdynamics.agent.uniqueHostId=X_new
This makes machine agent not be associated to APM agent node because nodes have different hostname.
Let me know if this helped you.
 
Many thanks,
Naoto

View solution in original post

Naoto_Yamamoto
Path Finder
Hi Amritesh,
 
Thanks for posting the question on the Community.
 

First, could you check different application name value is set in 2 agents’ controller-info.xml? 
If this is the case, single machine agent will surely get associated to both APM nodes, because controller associates machine to APM based on hostname.
 
You can also check whether this happens by clicking “Settings”->”AppDynamics Agents”, and search your hostname in search query.
 
In this case, this is the steps to solve issue: 
  1. Please stop one of the APM agent for which machine agent do not want to report
  2. Start APM Java agent with this argument:-Dappdynamics.agent.uniqueHostId=X_new
This makes machine agent not be associated to APM agent node because nodes have different hostname.
Let me know if this helped you.
 
Many thanks,
Naoto
Get Updates on the Splunk Community!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...