Default Profiler Element

The default profiler element is a child of the app-agents element. It defines customizations to the default profiler behavior for all instrumented .NET applications on the machine: IIS applications, application pools, Windows services, and standalone applications.

Optional Element: <profiler>

Profiler - Event Mask Element

The event-mask element is nested under the profiler element.
Important: Only modify this setting if directed by Splunk AppDynamics Support or if you require advanced control over CLR profiler event flags.
Optional Element:
CODE 
<event-mask value="<unsigned-long>" filter="<unsigned-long>" />
Attribute Description
value A 64-bit unsigned integer. The low 32 bits apply to CLR EventMask and the high 32 bits apply to CLR EventMask2.
filter It controls which bits from value are applied to the automatically calculated event mask.
Note: If you exclude the filter attribute and the value attribute is not zero, the configured event mask replaces the automatically calculated event mask for backward compatibility.

Profiler - Event Mask Overrides Element

The event-mask-overrides element is nested under the profiler element. Use this to define event-mask settings that take precedence over both automatic calculations and the standard event-mask configuration.

Optional element:
CODE 
<event-mask-overrides>
  <inlining mode="auto" />
</event-mask-overrides>

Profiler - Inlining Override Element

The inlining element is nested under the event-mask-overrides element. This element determines whether the CLR JIT inlining is enabled or disabled.

Value Description
auto Default: The agent does not modify the inlining bit after applying the event mask. When no custom event mask is provided, the agent automatically enables inlining for .Net Framework and .NET 9+, and disables it for .NET 8 Frameworks.
on Forces inlining to be enabled.
Important:

Exercise this setting with caution on .NET 8 because you may experience occasional deadlocks. See Calling RequestReJIT in the profiler API can cause a deadlock.

.
off Forces inlining disabled.
Example:
CODE 
<appdynamics-agent>
  <app-agents>
    <profiler>
      <event-mask value="8589934832" apply-mask-value="4295032831" />
      <event-mask-overrides>
        <inlining mode="off" />
      </event-mask-overrides>
    </profiler>
  </app-agents>
</appdynamics-agent>

Profiler - Disabled Features Element

The disabled-features element is a child of the profiler element. Use this property to disable data collection mechanisms at the agent level for security or privacy reasons. This configuration overrides any configuration set by the Controller.

Optional Element: <disabled-features value="NONE"/>

Disabled features value attribute

The disabled-features value attribute is a comma-separated list of features to disable. The available values are as follows:

  • LOG_PAYLOAD: Override the log-request-payload node property to suppress logging HTTP request payloads.
  • RAW_SQL: Override the capture-raw-sql node property to suppress logging raw SQL output.
  • CUSTOM_EXIT_SNAP_DATA: Suppress snapshot data from custom exits points.
  • METHOD_INV_DATA_COLLECTOR: Suppress method invocation data collector user data.
  • HTTP_DATA_COLLECTOR: Suppress HTTP request data collector user data.
  • INFO_POINT: Suppress information point metrics.
  • ALL: Disable all the available features.
  • NONE: Don't disable features.

Type: String

Default: NONE

Required: No

Profiler - Successful Exit Code Element

The successful-exit-code element is a child of the profiler element. The default successful exit code determines whether or not the agent flags a CLR restart event as graceful or not for Windows services or standalone applications. This configuration does not apply to IIS.

Optional Element: <successful-exit-code value="0"/>

Successful exit code value attribute

Type: Integer

Default: 0

Required: No

Profiler - Runtime Reinstrumentation Element

The runtime-reinstrumentation element is a child of the profiler element. Use this property to configure runtime reinstrumentation. See Configure Runtime Reinstrumentation for .NET.

Optional Element: <runtime-reinstrumentation enabled= "true" interval= "60000" optimize= "true" />

Runtime reinstrumentation enabled attribute

Set to true to enable runtime reinstrumentation.

Type: Boolean

Default: false

Required: No

Runtime reinstrumentation interval attribute

The frequency in milliseconds that the agent checks for configuration updates that initiate runtime reinstrumentation.

Type: Integer

Default: 60000 milliseconds

Minimum: Because runtime reinstrumentation adds a small amount of system overhead, Splunk AppDynamics recommends a minimum interval of 1 minute or 60000 milliseconds.

Required: No

Sample Default Profiler Configuration

CODE 
<app-agents>
    <profiler>
      <disabled-features value="LOG_PAYLOAD,RAW_SQL,CUSTOM_EXIT_SNAP_DATA"/>
	  <!-- Set the successful exit code for Windows services and standalone applications to "1." -->
      <successful-exit-code value="1"/>
      <!-- Enable Runtime reinstrumentation -->
      <runtime-reinstrumentation enabled="true" interval="60000" />
    </profiler>
...
</app-agents>