Normalizing URLs reported by Dynatrace Application Monitoring server

NAM Console, Deployment ► Manage devices, AppMon ServerOpen configuration, URLs configuration

Use the Dynatrace Application Monitoring Configuration screen to control the way in which the URLs monitored by the Dynatrace Application Monitoring Server should be reported by the NAM Server.

Dynatrace Application Monitoring Server reports the URLs recorded as the result of the User Experience Management browser instrumentation. You can use the Dynatrace Application Monitoring Configuration screen to strip the URLs of unwanted strings for the NAM Server reporting.

Click URLConfiguration in the left pane of the Dynatrace Application Monitoring Configuration screen.

Define the URL definition.

  • To manually add a URL to the list, type it in the New URL field and click Add.

  • To select a URL from existing definitions, click Edit in the Actions column.

To search for a specific URL, type it in the Filter box. To clear the filter settings, click x.

You can either add an Monitored URL to create a new definition for the NAM Server reporting or Excluded URL to create a new definition for a URL excluded from the NAM Server reporting. When adding a Monitored URL definition, you can select one of the three available types:.

Virtual HTTP server

This option refers to monitoring a host where many websites reside under a single IP address. Using a virtual HTTP server causes all of the reported pages that have no separate definitions to be aggregated into one record and reported together. This does not apply to those pages from the IP address that are defined separately in a monitoring configuration. Such individual definitions do not require that you select this option.

For example, a valid virtual HTTP server address is http://server.domain.com, without a trailing slash.

Static URL part

A fully qualified URL, containing the protocol to be used, the server to be contacted, and the file to be requested, such as http://server.domain.com/page .

This URL is added to the list of monitored URLs regardless of the limit of monitored URLs.

URL as a Regular Expression

When adding the definition, use a regular expression to match the URL as reported by the Dynatrace Application Monitoring Server. The syntax allows you to use parentheses “()” to select one or more sub-expressions (specific portions of the results). If this mechanism is used, only the specified portions are reported; if more than one portion is specified, the portions are concatenated. Note that the syntax must comprise the rules for Java regular expressions, which is slightly different from POSIX used in the NAM Probe configuration.

Note

When using a regular expression to specify a set of URLs to monitor, you must:

  • Explicitly include the string “http:// ” or “https:// ” in the expression. Thus, for example, you should not start the expression with “.* ” and expect that the “http:// ” or “https:// ” strings will be assumed or resolved as a part of the regular expression.

  • The parentheses you use to select the part of the URL to be extracted must include the above strings “http:// ” or “https:// ” and they must also include the name of the host. However, the name of the host does not have to be provided explicitly, but can be resolved by the regular expression. Thus, for example, “(http://www.someserver.com/)report/(myreport) ” is correct, and so is “(http://.*/)report/(myreport) ”.

Configure URL Parameters.

For each URL, you can also fine tune the reporting based on the reported parameters. To configure the parameters reporting, select Define URL Parameters in the Actions column.

Select the Report only URL part when parameters do not match check box.

As a result, all of the pages that do not meet the constraints are reported under the main URL. If the check box is not selected, these URLs are not reported at all.

In the Group box, type the name under which you want the parameters that match the definition to appear on NAM Server reports. Note that this name is applied to all URLs matching the criteria.

In the Parameter column, specify the parameter constraints for a page.

The constraint defines which pages are reported under a given URL. You can define up to four constraints per parameter group. Similarly to adding URLs, you can type the parameters or you can use the parameters listed in the traffic preview.

Use the Match list to specify the parameter matching method.

The following matching methods are supported:

Exact - Report the specified parameter or the parameter and value.

Usage syntax - 'name=value' or just 'name' .

Limitations - A case-insensitive match is performed; no wildcard characters are permitted in the string. So, the wildcard character “*” is taken literally.

Combining parameters - If you have defined more than one parameter for a given URL, for a match to be successful all specified parameters have to be matched. When all matches are found, the reported string then contains a concatenation of all the matched parameters, separated by the ampersand “&” character.

Examples - You can specify 'john', to match http://host.com/page?john, though note that in this case http://host.com/page?john=123 will not be reported because the parameter value '=123' was not explicitly specified. To match it, you would need to specify 'john=123' .

Start - Report parameters that begin with a specified string; report only the matched pattern, truncate any remainder of the parameter.

Usage syntax - 'name=value' or any initial part of it this string, including string of the form 'name=' or just 'name' .

Limitations - A case-insensitive match is performed; no wildcard characters are permitted in the string.

Combining parameters - If you have defined more than one parameter for a given URL, for a match to be successful all specified parameters have to be matched. When all matches are found, the reported string then contains a concatenation of all the matched parameters, separated by the ampersand “&” character.

Examples - 'fred=5' will match http://host.com/page?fred=500ab but it will be reported as http://host.com/page?fred=5 . The value 'fred' will match http://host.com/page?fred=500ab as well as http://host.com/page?fred and it will be reported as http://host.com/page?fred .

Start (expand) - Report parameters which begin with a specified string; report the entire parameter, not only the matched pattern.

Usage syntax - 'name=value' or any initial part of it this string, including string of the form 'name=' or just 'name' .

Limitations - A case-insensitive match is performed; no wildcard characters are permitted in the string.

Combining parameters - If you have defined more than one parameter for a given URL, for a match to be successful all specified parameters have to be matched. When all matches are found, the reported string then contains a concatenation of all the matched parameters, separated by the ampersand “&” character.

Note that for a single URL, different parameters can be extracted from different portion of the HTTP packet, request URL, POST body, or HTTP header, and combined into a single match.

Examples - 'fred=5' will match http://host.com/page?fred=500ab and it will be reported as http://host.com/page?fred=500ab . The value 'fred' will match http://host.com/page?fred=500ab and http://host.com/page?fred and it will be reported as http://host.com/page?fred=500ab and http://host.com/page?fred .

End - Report parameters which end with a specified string; report the entire parameter, not only the matched pattern.

Usage syntax - 'name=value' or any final part of it this string, including string of the form '=value' or just 'value' .

Limitations - A case-insensitive match is performed; no wildcard characters are permitted in the string.

Combining parameters - If you have defined more than one parameter for a given URL, for a match to be successful all specified parameters have to be matched. When all matches are found, the reported string then contains a concatenation of all the matched parameters, separated by the ampersand “&” character.

Examples - For http://host.com/page?john=100' to be matched, you can specify the following ends: '0', '00', '100', '=100', 'n=100' and so on, up to 'john=100' . Thus http://host.com/page?john=100 is reported.

Value RegEx - Report parameters which begin with a specified string; optionally attempt to match the remainder of the parameter with a regular expression; report the start string and selected portions of the regular expression, if any.

Usage syntax - Parameter is entered as name=value or any initial part of it this string including string of the form name= or just name . A regular expression (regex) is entered as an extended Java regular expression.

Limitations - A case-insensitive match is performed on the Parameter part; the regex part is matched as a case-sensitive Java regular expression.

Combining parameters - If you have defined more than one parameter for a given URL, for a match to be successful all specified parameters have to be matched. When all matches are found, the reported string then contains a concatenation of all the matched parameters, separated by the ampersand “&” character.

Note that for a single URL, different parameters can be extracted from different portion of the HTTP packet, request URL, POST body, or HTTP header, and combined into a single match.

Examples - parameter specification fred= and a regular expression AB(C?E) will match http://host.com/page/fred=ABCDE but it will be reported as http://host.com/page/fred=CDE because the AB portion of the regular expression was not included in round braces.

Custom RegEx - Report parameters that match the given regular expression; report those portions that have been selected within the regular expression.

Usage syntax - Enter an extended Java regular expression to match the desired string. Mark portions to be reported by using round braces “(” and “)”.

Limitations - The regular expression is entered according to Java syntax.

Combining parameters - If you have defined more than one parameter for a given URL, for a match to be successful all specified parameters have to be matched. When all matches are found, the reported string then contains a concatenation of all the matched parameters, separated by the ampersand “&” character.

Examples - Regular expression fred=AB(C?E) will match http://host.com/page/fred=ABCDE but it will be reported as http://host.com/page/CDE .

Regular expression (.*=)AB(C?E) will match http://host.com/page/fred=ABCDE as well as http://host.com/page/joe=ABCDE and it will be reported as http://host.com/page/fred=CDE and as http://host.com/page/joe=CDE respectively.

Click Save and publish the configuration to the NAM Server.