Profiler chaining for the .NET Core agent

You can use profiler chaining to run the .NET Core agent alongside another .NET Core APM profiler.

The Contrast .NET Core agent is tested and proven to be compatible with the following profiling tools, given the combination of runtime, deployment type, and OS:

Profiling tool

Versions tested

.NET Core runtime

Third-party profiler deployment type

OS

New Relic (see example)

8.23.107

3.1

NuGet Package

Windows

Note

The agent is likely compatible with other profiling tools if those tools follow the conventions of the CoreCLR Profiling API and do not make assumptions about the profiling environment.

To configure profiler chaining:

  1. Replace the CORECLR environment variables for the APM with CONTRAST_CCC_CORECLR versions. Any of these names should be transformed:

    Change this

    To this

    CORECLR_PROFILER 

    CONTRAST_CCC_CORECLR_PROFILER

    CORECLR_PROFILER_PATH

    CONTRAST_CCC_CORECLR_PROFILER_PATH

    CORECLR_PROFILER_PATH_32

    CONTRAST_CCC_CORECLR_PROFILER_PATH_32

    CORECLR_PROFILER_PATH_64

    CONTRAST_CCC_CORECLR_PROFILER_PATH_64

  2. Make the necessary changes in your APM profiler. Here are examples for New Relic.

In this section: