By default, you must restart your monitored application after you create or update:

  • POCO transaction detection entry points
  • POCO service endpoints
  • Custom exit points
  • Method invocation and HTTP data collectors
  • Information points

When you enable runtime reinstrumentation, the .NET Agent detects the types of instrumentation changes and automatically requests the CLR to recompile the affected code. With runtime reinstrumentation enabled, you do not need to restart your application for the instrumentation changes to take effect. See Administer the .NET Agent.


Runtime reinstrumentation works for .NET Framework >= 4.5.2. To verify the framework version in the web.config file of your application, enter:

    <compilation targetFramework="4.5.2" />
    <httpRuntime targetFramework="4.5.2" />

Configure Runtime Reinstrumentation for .NET

Configure all instrumentation settings for the .NET Agent in the config.xml file:

  1. Open the config.xml file for editing as an administrator. See Administer the .NET Agent.
  2. Copy the code block below to a child element of the app-agents element. See Default Profiler Element.

       <runtime-reinstrumentation enabled="true" interval="60000" />

    For example:

    <?xml version="1.0" encoding="utf-8"?>
    <appdynamics-agent xmlns:xsi="" xmlns:xsd="">
          <!-- Enable runtime reinstrumentation -->
          <runtime-reinstrumentation enabled="true" interval="60000"/>
  3. If appropriate configure the runtime-reinstrumentation options:
    • enabled: Set to true to enable runtime reinstrumentation. Default: false

    • interval: The frequency the agent checks for configuration updates in milliseconds. Default: 60000

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

      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.

  4. Save the config.xml file.
  5. Restart the AppDynamics.Agent.Coordinator service.
  6. Restart instrumented applications for your changes to take effect.