ASP.NET sensor

The ASP.NET Sensor traces incoming requests in the ASP.NET pipeline. The sensor places an additional HTTP tag X-dynatrace. In certain scenarios, the ASP.NET pipeline might split the processing of a request.

Internally, ASP.NET sets the response code to 200 (OK) by default. It might occur that only one thread sees a change in the response status, leading to different response codes in the details of each ASP.NET node.

Supported technologies

ASP.NET sensor also supports OWIN/Katana version 3.0.0+. This requires to switch the agent platform as OWIN/Katana support is not available in Classic Agent.

Sensor configuration

To edit the System Profile specific settings, open the System Profile Preferences dialog box and select Agent Group/tier with .NET technology > Sensor Configuration and then select the ASP.NET item in the Sensor Configuration list.

Sensor properties

Always add Dynatrace header to responses: Force adding the AppMon header to responses, even if it was not available in the request (useful for Load-Test scenarios). You cannot change this value if a DC-RUM appliance is configured. See Integration for details.

URI filter

You can filter captured data by URI. There are two possible scenarios:

  • Capture listed URIs only.
  • Capture all URIs, except for the listed ones.

Select the appropriate option button and list URIs or URI patterns to be included/excluded from the capture.

Parameters and attributes

You can capture certain parameter and attributes values like request headers, session attributes, request attributes, and request parameters as strings. To specify a captured attribute explicitly, provide its name in the Attribute column. To capture an attribute that contains a certain name, provide a partial name in the Attribute column. To capture all available attributes, leave the Attribute column empty or type '*'. Keep in mind that may cause a high overhead, Dynatrace does not recommend usage of wildcards in production environments.

You can use the Parameters and Attributes table to configure the Sensor to capture the following Source types:

  • Parameter: Captures the form parameters of the request if the given tring is a substring of the parameter's name.
  • Request Header: Captures the HTTP headers sent with the request if the given tring is a substring of the header's name.
  • Server Variable: Captures the server variable for the request if the given string is a substring of the server variable name.
  • Request Cookie: Captures the cookie value of the request if the given string is a substring of the cookies name.
  • Session Entries: Captures the session item for this request if the given tring is a substring of the session item's name.

For Tomcat and WebLogic platforms, servlets providing static content like images are excluded from diagnosis by default. However, the method doFilter is instrumented, which may result in creation of PurePaths for servlets that create static content on other platforms. To exclude such servlets, which usually listen on a URI ending with an image name, add exclusion rules for the expected image types to the Servlet Sensor Properties, as shown in the following figure.