AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    This page explains how to set compatibility mode for the .NET Agent. Compatibility mode allows you to collect and view machine or server metrics on a server with Machine and .NET Agents installed. 

    Before You Begin

    Review the list of requirements and general information about compatibility mode: 

    • .NET Compatibility Mode is required for metrics from a Machine Agent and a .NET Agent on the same server to be visibly associated with the same node in the Controller UI.
    • Differences may exist between 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 on 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 may show the server name with "-java-MA" appended to the host ID. Thus, a 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 Machine Agent running in .NET Compatibility Mode. 
    • Do not specify the <application-name><tier-name>, or <node-name> properties on the Machine Agent. These properties are used with a Machine Agent on a host that has no other AppDynamics Agents installed.

    Enable Compatibility Mode

    To enable .NET Compatibility Mode:

    1. Enable .NET Compatibility Mode on the Agent using one of two methods: 
      • Set these options in <machine_agent_home>/conf/controller-info.xml
        1. <dotnet-compatibility-mode>true</dotnet-compatibility-mode>  
           You may 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 Machine Agent must use the same case-sensitive Unique Host ID used by the .NET Agent. See FAQs and Troubleshooting
      • Set the ./bin/machine-agent system property to: ./bin/machine-agent -Dappdynamics.machine.agent.dotnetCompatibilityMode=true

    2. Save the controller-info.xml file. 
    3. Start or restart the Machine Agent to apply the changes.
    • No labels