AppD Archive

Basic process to setup machine agent on Amazon aws EC2 Linux micro

CommunityUser
Splunk Employee
Splunk Employee

Hello all -

New user testing out Appdynamics for the first time. I'm running a t2.micro with all ports open. I'm not seeing anything on the dashboard.

Steps I took...

I've downloaded the machine agent to the server, unziped it and configured the controller-info.xml file as such...

<controller-host>[MYAPPD_ACCOUNTNAME].saas.appdynamics.com</controller-host>

<controller-port>8181</controller-port>

<controller-ssl-enabled>true</controller-ssl-enabled>

<account-name>[MYAPPD_ACCOUNTNAME]</account-name>

<account-access-key>[MYAPPD_ACCESSKEY]</account-access-key>

<application-name>AWS</application-name>

<tier-name>EC2</tier-name>

<node-name>apm4</node-name>

<force-agent-registration>false</force-agent-registration>

<machine-path></machine-path>

Question:

Since the url is HTTPS I used 8181 and true for SSL. But, do I need anything on a standard-out-of-the-box t2.micro for SSL comunications?

I'm seeing this in the log file:

WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.

and

feign.RetryableException: Connect to [MYAPPD_ACCOUNTNAME].saas.appdynamics.com:8181 [na16.saas.appdynamics.com/198.169.195.55] failed: connect timed out executing POST http://[MYAPPD_ACCOUNTNAME].saas.appdynamics.com:8181/controller/sim

Why 198.169.195.55 vs the public IP assigned to my EC2 server? 

and a lot of this:

at feign.FeignException.errorExecuting(FeignException.java:66)

at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:97)

at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:71)

at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:94)

at com.sun.proxy.$Proxy70.registerMachine(Unknown Source)

at com.appdynamics.agent.sim.registration.RegistrationTask.run(RegistrationTask.java:102)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:745)

What am I missing? I was unable to find anything that walks through basic steps specifically for EC2 servers leading me to think that there isn't anything special.

Thanks for the help

Kevin

0 Karma

Scott_Young
Explorer

Try port 443 instead for SaaS

https://docs.appdynamics.com/display/PRO14S/Use+a+SaaS+Controller

This doc is a little old but has the right info.

0 Karma
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 ...