Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: docs-1267


  • .NET Compatibility Mode is required for metrics from a Standalone Machine Agent and a .NET Agent on the same server to be visibly associated with the same node in the Controller UI.
  • This mode requires 4.2.4 (or higher) versions of both the Controller and the Standalone Machine Agent. 
  • There might be differences in metric values reported by the Machine Agent and the .NET Agent due to different averaging rates and measurement methods.
  • You must enable .NET Compatibility Mode must be enabled on both the Controller and the Machine Agent.  
  • When .NET Compatibility Mode is enabled:
    • Events from Service Availability and Custom Extensions appear in the Servers tab but are not associated with .NET applications in the Controller UI.
    • The Controller UI might show the server name with "-java-MA" appended to the host ID. Thus, a Standalone Machine Agent with a <unique-host-id> set to "ABC" might appear as "ABC-java-MA" in the Controller UI. This is expected behavior; the "-java-MA" suffix indicates that the host has a Standalone Machine Agent running in .NET Compatibility Mode. 
  • Do not specify the <application-name><tier-name>, or <node-name> properties on the Standalone Machine Agent. These properties are intended for use with a Standalone Machine Agent on a host that has no other AppDynamics agents installed.

To enable .NET Compatibility Mode:

  1. Download and install 4.2.4 (or higher) versions of both the Machine Agent and the Controller.
  2. .NET Compatibility Mode is enabled by default in the Controller (versions 4.3.and higher). If you are using a pre-4.3 SaaS Controller, contact AppDynamics Support. If you are using an pre-4.3 on-premises Controller, do the following:
    1. Log in to the Controller administration console using the root user password:
      http://<controller host>:<port>/controller/admin.jsp
    2. Set the following preference: 
      sim.machines.hostidMappingAllowed = true
  3. You need to enable .NET Compatibility Mode in the agent. Set the following options in <machine_agent_home>You need to enable .NET Compatibility Mode on the agent. There are two methods to do this:
    • Set the following options in <machine_agent_home>/conf/controller-info.xml
      1. <dotnet-compatibility-mode>true</dotnet-compatibility-mode>  
         You might need to add this line to the controller-info.xml file.
      2. <unique-host-id><unique-host-id-of-dot-net-agent></unique-host-id> 
        For both agents to report metrics to the same node, the Standalone Machine Agent must use the same case-sensitive Unique Host ID used by the .NET Agent.
      1. See FAQs and Troubleshooting
    • Set the ./bin/machine-agent system property as follows:

      ./bin/machine-agent -Dappdynamics.machine.agent.dotnetCompatibilityMode=true

  4. Save the controller-info.xml file file
  5. Start or restart the Machine Agent. You must do this to apply the previous changes.