Are you a member of the Splunk Community?
- Find Answers
- :
- Splunk Platform
- :
- Splunk AppDynamics
- :
- Re: Server details are not available for the respe...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
Just curious about why in the Application dashboard I'm not able to see the server details (Azure VMs) where the application is hosted.
I have installed Machine Agents on those Servers, but I am still not able to see any details in them. But I can see the servers in the Servers tab in the top column of AppDynamics. Is there any configuration I've missed during the instrumentation or installation of Agents?
Any insights will be Helpful!
Thanks in Advance!!!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Srinath
The reason this happens, especially in Cloud Environments, is that the machine agent running there will get a certain hostname back, which doesn't match the hostname being detected or set by the application agent.
You just have to look at what unique hostname the machine agent is returning, versus the unique hostname that the app agent is returning. They have to match for it to link and show the machine agent within the application dashboard. If it's not possible to auto detect, the easiest way is within the machine agent controller-info.xml or environment variable, set the unique host id to the exact same as the app agent host name value being returned by the app agent.
That will resolve it
Ciao
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Srinath
The reason this happens, especially in Cloud Environments, is that the machine agent running there will get a certain hostname back, which doesn't match the hostname being detected or set by the application agent.
You just have to look at what unique hostname the machine agent is returning, versus the unique hostname that the app agent is returning. They have to match for it to link and show the machine agent within the application dashboard. If it's not possible to auto detect, the easiest way is within the machine agent controller-info.xml or environment variable, set the unique host id to the exact same as the app agent host name value being returned by the app agent.
That will resolve it
Ciao
Why You Can't Miss .conf25: Unleashing the Power of Agentic AI with Splunk & Cisco
Deep Dive into Federated Analytics: Unlocking the Full Power of Your Security Data
Your summer travels continue with new course releases
