1. Edit the AppDynamicsConfig.json file with the following information:

      "controller": {
        "host": "<controller_host_name>",
        "port": <controller_port_name>,
        "account": "<controller_account_name>",
        "password": "<controller_account_key>",
        "ssl": <true if using https controller, or false>
        "proxy" : {
            "host": "proxy-host",
            "port": 9090,
               "authentication": {
                  "username": "proxy-user",
                  "password": "proxy-password"
      "application": {
        "name": "<application_name>",
        "tier": "<tier_name>",
        "node": "<node_name>"
      "log": {
        "directory": "<log_folder_path>",
        "level": "<log_level>"
  2. Add the following environment variables to your application, then rebuild or republish your application.

    Environment Variable NameValue
    CORECLR_PROFILER_PATHPath to the libappdprofilerdynamic library. For example, <application_folder_path>/

    The location of the library is determined by which .NET command you used to install the SDK. AppDynamics recommends using dotnet build, which is the first deployment command option in the following table.

    Type of DeploymentCommandWork DirectoryProfiler LocationExecutable Path
    Developmentdotnet build, dotnet run<project_path>


    Framework Dependentdotnet publish<project_path><project_path>/bin/<Flavor>/publish/runtimes/linux-x64/native/libappdprofiler.sobin/<flavor>/publish/linux-x64/<appname.dll>
    Self-containeddotnet publish -r linux_x64<project_path>

    /<project path>/bin/<Flavor>/linux_x64/publish/
    <project path> is the root directory of the application

    <flavor> can be something like release/netcoreapp2.0

    After you rebuild or republish your application, the agent registers to the Controller, and AppDynamics starts instrumenting your application. See .NET Core for Linux SDK Use Cases


  • No labels