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!

Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...

This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...