Before you can start instrumenting your applications with the .NET Core for Linux SDK, you need to get the current version of the .NET Core for Linux SDK. The topic describes how to connect the .NET Core for Linux Agent in your application to the Controller.
Once you have the deployed the SDK, you can customize the instrumentation of your application as described here. The SDK provides routines for creating and managing business transactions, transaction snapshots, backends, exit points and collecting custom metrics. This topic provides an overview of these concepts.
Configuration
Edit the AppDynamicsConfig.json file with the following information:
Add the following environment variables to your application, then rebuild or republish your application.
Environment Variable Name
Value
CORECLR_PROFILER
{57e1aa68-2229-41aa-9931-a6e93bbc64d8}
CORECLR_ENABLE_PROFILING
1
CORECLR_PROFILER_PATH
Path to the libappdprofilerdynamic library. For example, <application_folder_path>/libappdprofiler.so
The location of the libappdprofiler.so 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.
/<project path>/bin/<Flavor>/linux_x64/publish/libappdprofiler.so <project path> is the root directory of the application
bin/<flavor>/linux_x64/publish/<appname> <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