Web Server sensor for NGINX

The Web Server Sensor traces PurePath for all HTTP requests including redirects, served by the web server. It also traces relevant information about these connections, including URI, query, method response code of the HTTP request/response. It can also be configured to capture request/response headers and request parameter.

Sensor Configuration

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

Web Server Sensor properties

  • Measure Request/Response Sizes: Captures the sizes of request and response in bytes.
  • Always add Dynatrace header to responses: Forces 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.

Headers and parameters

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