cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

NET (Agent, Installation)

How can I install appdynamics .net agent on aws elastic beanstalk?

Ajit
New Poster

How can I install appdynamics .net agent on aws elastic beanstalk?

I'm new to AppD .NET Agent intallation process. It might be an obvious question but i need help on that.

We have .NET Applications hosted in AWS Cloud using AWS Elastic Benstalk. We need to instrument the .NET Applications Servers and Applications using AppD. So, we need to install the AppD .NET Agent on AWS Elastic Beanstalk. Could you please let me know what are the steps i have follow?

Tags (1)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
How can I install appdynamics .net agent on aws elastic beanstalk?
1 REPLY 1
Raunak.Mohanty
AppDynamics Team (Retired)

Hi Ajit,

 

The installation part should remain the same. All you need to do is install the MSI.

The issue can occur when multiple instance get created. Agent uses HostName to name the nodes but since all the instances at AWS have the same hostname node conflicts occur and you end up loosing metrics.

 

In case you have single .Net Application hosted on these instances you can set up environment variable APPDYNAMICS_AGENT_UNIQUE_HOST_ID to any value and it will be used to uniquely identify the machine and generate node names using this value. 

For example, following powershell commands will fetch IP (full) and set it as system level environment variable-

$envVariableName="APPDYNAMICS_AGENT_UNIQUE_HOST_ID"
$ip = $(ipconfig | where {$_ -match 'IPv4.+\s(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})' } | out-null; $Matches[1])
$uniqueID = "Optional_Prefix"+$ip
SETX $envVariableName $UniqueID /m

We can call this during system startup and this will take care of the problem. 

I am assuming that you are using .NET agent version 4.3 or newer, in that case we only need to set this env variable and we should be good. 

 

Let us know if you are hosting mutiple .Net applications on these AWS instance.

 

Thanks,

Raunak



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.