AppD Archive

Machine Agent on AppD Controller

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I want to install a machine Agent on the server where the AppD controller is running.

I am using this properties:

<controller-host>127.0.0.1</controller-host>

<controller-port>8090</controller-port>

<account-name>system</account-name>

<application-name>AppDynamics Controller</application-name>
<tier-name>App Server</tier-name>
<node-name>Node1</node-name>

The registration of the machine agent looks good but there is no application associate and I cannot correlate the metrics of the machine agent with the metrics of the app agent.

Is the configuration wrong?

Regards,

Thomas

0 Karma
1 Solution

CommunityUser
Splunk Employee
Splunk Employee

Hi,

here the final configuration that worked for me:

    <controller-host>localhost</controller-host>
    <controller-port>8090</controller-port>
    <controller-ssl-enabled>false</controller-ssl-enabled>
    <application-name>AppDynamics Controller</application-name>
    <tier-name>App Server</tier-name>
    <node-name>Node1</node-name>
    <agent-runtime-dir></agent-runtime-dir>
    <enable-orchestration>false</enable-orchestration>
    <account-name>system</account-name>
    <account-access-key>SJ5b2m7d1$354</account-access-key>
    <force-agent-registration>false</force-agent-registration>

thx for support

Regards,

Thomas

View solution in original post

Arun_Dasetty
Super Champion

Hi Thomas,

Controller internal application will not be listed in UI at URL http://<controllerhost>:8090/controller you would need to logout current controller UI and hit URL http://<controllerhost>:8090/controller?enableAccounts=true and login ui and see whether h/w stats shows fine under Node1 node dashbaord -> Hardware secion ?

If you do not h/w stats under Node1 dashboard in controller internal application, can you provide the system account password in machine agent contorller-info.xml file and see how it goes after restart:

   <account-access-key>SJ5b2m7d1$354</account-access-key>

Let us know if that information helps. If issue persists, please send the machine agent logs we suspect we need not provide tier and node name details apart from controller host and account/access key for machine agent as providing Node1 might result in duplicate internal agent node registration. Keep us posted how it goes.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

here the final configuration that worked for me:

    <controller-host>localhost</controller-host>
    <controller-port>8090</controller-port>
    <controller-ssl-enabled>false</controller-ssl-enabled>
    <application-name>AppDynamics Controller</application-name>
    <tier-name>App Server</tier-name>
    <node-name>Node1</node-name>
    <agent-runtime-dir></agent-runtime-dir>
    <enable-orchestration>false</enable-orchestration>
    <account-name>system</account-name>
    <account-access-key>SJ5b2m7d1$354</account-access-key>
    <force-agent-registration>false</force-agent-registration>

thx for support

Regards,

Thomas

Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...