Skip to main content

.NET Framework and .NET Core Telemetry

.NET Framework and .NET Core agents use telemetry to collect usage data. Telemetry is collected when an instrumented application first loads the agent’s sensors and then periodically (every few hours) afterwards.

Your privacy is important to us. The telemetry feature doesn't collect application data. The data is anonymized before being sent securely to Contrast. Then the aggregated data is stored encrypted and under restricted access control. Any collected data will be deleted after one year.

The telemetry feature collects the following data:

Agent versions


.NET Framework later than 2020.8.3

.NET Core later than 1.5.15

Agent version

Operating system and version

Whether the agent is running in a container

Whether the agent is running in Azure App Service

Hashed Media Access Control (MAC) address: a cryptographically (SHA256) anonymous and unique ID for a machine

Kernel version

Process running time

Whether Assess is enabled

Whether Protect is enabled

.NET Framework later than 2020.8.3

.NET Framework runtime version

.NET Core later than 1.5.15

.NET Core runtime version

.NET Framework later than 20.9.1

.NET Core later than 1.5.17

Hosted or on-premises Contrast instance

.NET Framework later than 20.9.3

.NET Core later than 1.5.19

CLR Instrumentation Engine (CIE) usage

Application framework

Chained profiler vendor

.NET Framework later than 20.10.1

.NET Core later than 1.5.20

Process hosting mode

CIE Raw Profiler Hook usage

.NET Framework later than 20.10.2

.NET Core later than 1.5.21

Names of configuration settings with non-default values

Names of disabled Assess rules

.NET Framework later than 20.12.2

.NET Core later than 1.7.2

Time elapsed for agent’s profiler component to initialize

Time elapsed for agent’s first request to the Contrast web interface

Time elapsed for agent’s profiler component to initialize

Time elapsed between agent initialization and end of the first request

.NET Framework later than 21.1.1

Metrics on IIS-hosted applications, including:

  • Total application count

  • Application count that will be analyzed (pass application allow list/deny list configuration)

  • Count of apps hosted on CLR4 application pools

  • Count of apps hosted on CLR2 application pools

Metrics on IIS applications pools

  • Total count

  • Count with agent attached

  • Count of CLR4

  • Count of CLR2

Minimum number of applications in a single app pool

Maximum number of applications in a single app pool

Median number of applications across all app pools

.NET Framework later than 21.1.2

.NET Core later than 1.7.5

Rule mode (i.e. Monitor vs. Block) for each Protect rule

.NET Framework later than 21.4.2

.NET Core later than 1.8.4

Exceptions thrown and caught within agent sensor code, including log message, exception type, exception message, and stack trace frames for System and Contrast methods.

.NET Framework later than 21.7.1

.NET Core later than 1.9.7

  • Process Architecture (x86/x64)

OS Architecture (x86/x64)

In Azure App Service, the values of the following environment variables:




.NET Framework later than 21.9.2

.NET Core later than 2.0.1

Description of location where YAML config file was loaded from (i.e., path specified by environment variable, default location, application directory).

To opt-out of the telemetry feature, set the CONTRAST_AGENT_TELEMETRY_OPTOUT environment variable to 1 or true.

Telemetry data is securely sent to You can also opt out of telemetry by blocking communication at the network level.