Top web requests

The highly flexible Top web requests view enables you to analyze the top web requests across all your services and to look for requests that originate from or are destined to specific URLs. This view is easily configurable and serves as a convenient entry point for in-depth analysis of your services.

To access the Top web requests analysis page

  1. Select Diagnostic tools from the navigation menu.
  2. Click the Top web requests tile.

Top web requests

Configure view

The Top web requests page lists all web requests that occurred during the selected timeframe and within the selected management zone. The Configure view pane offers multiple filtering capabilities. The view updates automatically as you change the parameters.

Parameter Description
Metric The metric to be analyzed. By default set to Request count.
Aggregation How the metric values are aggregated. Available aggregations depend on the selected metric.
Split mode How dimensions specified in Split by dimension are treated.
  • Split by services—each dimension is displayed separately for each service.
  • Merge by services—same dimensions from different services are merged into one.
Split by dimension A list of dimensions by which the requests are split. By default the request name ({Request:Name}) dimension is set.

You can specify several dimensions. Place your cursor in the input field to see the available options. The requests are split by dimension in the specified order.
Filter requests Filter the requests to be included to the view. By default the following criteria are set:
  • Service type: Web service
  • Service type: Web request service

    You can provide additional criteria. Place your cursor in the input field to see the available options.

    Criteria of the same type are grouped by the OR logic. Criteria of different types are grouped by the AND logic.

Once the view is configured, you can save it for quick access in the future. Just select Save view and provide a name.

You can also save the configuration as a calculated service metric and use it as any other metric in Dynatrace (for example, for alerting).

View

The chart on the Top web requests page shows the top 15 dimensions (all other dimensions are aggregated into a single dimension) and the table beneath contains up to 85 more dimensions, bringing the total number of chartable dimensions to 100. The view instantly adapts to the changes you make in the Configure view pane.

The Actions column of the table contains the filter button Filter, which filters the view to the specified dimension, and the menu button drill, which provides quick access to further analysis options.

Example use cases

Here you can find some use cases for the Top web requests view.

Find a particular URL

With Top web request view you can focus your analysis on requests that come from or are going to a particular URL.

  1. Specify {URL:Host}{Relative-URL} in the Split by dimension field to split your requests based on URLs.
  2. Now filter the requests to a particular URL. In the Filter requests field, select the Web request URL filter type and provide the pattern for the URL. Note that this filter uses the CONTAINS operator.

Find requests with error response codes

You can easily narrow down your requests to those that returned an error response code (that is, any error code in the range 4xx). After you configure the dimensions that you're interested in, place your cursor into the Filter requests field and select the HTTP response code filter type (you can start typing to narrow down the suggestions). Then select the 4xx criteria and wait for data processing to complete.

Find POST HTTP requests

You have two options for viewing your POST (or any other HTTP method) at a glance: (1) set the HTTP method dimension or (2) filter the request by HTTP method.

Dimension

In this case you'll see all your requests grouped by HTTP method and by any other dimension you provide. Just specify {HTTP-Method} in the Split by dimension field.

Filter

In this case, all non-POST requests are filtered out, so you can focus your analysis. Just specify the HTTP method and select POST value in the Filter requests field.