Is there a way to configure the .NET agents in AppDynamics to not have to restart when making a code level change like creating an Information point?
Question ID: 106984
0
0

I don’t like having to restart my .net application every time I need to configure an Information Point in AppDynamics. Is there a way around this?

Marked as spam
Posted by (Questions: 89, Answers: 0)
Asked on July 26, 2016 8:12 pm
112 views
Answers (1)
0
Private answer

Yes. In 4.2 you can now perform what is called ''Runtime Reinstrumentation'' for .NET.

a. In .NET you need to restart the application that is instrumented in .NET for the following reasons:

i. POCO transaction detection entry points

ii. POCO service endpoints

iii. custom exit points

iv. method invocation and http data collectors

v. information points

New for 4.2 you can add an xml tag to the .NET agent configuration file so you no longer have to perform a restart.

Here is how it is done:

i. Open the config.xml file for editing as an administrator..

ii. Copy the code block below to a child element of the App Agents element.

v. If appropriate configure the runtime reinstrumentation options:

1. enabled: Set to ''true'' to enable runtime reinstrumentation. Default: ''false''.
2. interval: The frequency the agent checks for configuration updates in milliseconds. Default: 60000.

a. Because runtime reinstrumentation adds a small amount of system overhead, AppDynamics recommends a minimum interval of 1 minute or 60000 milliseconds.

b. The .NET Agent checks for configuration updates every minute, so it may take up to 2 minutes for reinstrumentation to take effect with the default setting of 60000 milliseconds.

vi. Save the config.xml file.

vii. Restart the AppDynamics.Agent.Coordinator Service.

viii. Restart instrumented applications for your changes to take effect.

Marked as spam
Posted by (Questions: 0, Answers: 90)
Answered on July 26, 2016 8:29 pm
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

X
Scroll to Top