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!

Uncovering Multi-Account Fraud with Splunk Banking Analytics

Last month, I met with a Senior Fraud Analyst at a nationally recognized bank to discuss their recent success ...

Secure Your Future: A Deep Dive into the Compliance and Security Enhancements for the ...

What has been announced?  In the blog, “Preparing your Splunk Environment for OpensSSL3,”we announced the ...

New This Month in Splunk Observability Cloud - Synthetic Monitoring updates, UI ...

This month, we’re delivering several platform, infrastructure, application and digital experience monitoring ...