Foglight for Microsoft DOT NET 5.9.13 - Application Servers Administration and Configuration Guide

Using the text editor

If you are familiar with the recording settings from previous version of Foglight for Java EE Technologies, and you are comfortable editing the settings in a plain text format, you can edit the Nexus recording settings manually.

The recording.config file opens in a text editor.

For information about the settings contained in this file, see the following topics:

Request sampling

Use the Request Sampling tab Nexus Recording editor for the Nexus to configure request separation rules, URL transformation rules, and filtering rules. Request separation is the first process that occurs when the agent collects request metrics. Next, any rule transformations are applied. Filtering occurs after request separation and URL transformation rules are applied. As a result, the filters can refer to parameter names and values from request separation, and must reference the transformed URL.

For more information, see:

Setting rules for separating requests

Request separation is the first process that takes place when collecting request metrics. On the Request Sampling tab, you can specify how to separate a request into multiple request types based on the request's parameters and cookies. Separation occurs if any of the parameters in a request match the request separation rules (SeparationRules) for that URL, meaning that a request may be separated based on more than one parameter. SeparationRules are configured in the recording.config property file.

The default setting is:

SeparationRules = {
};

Keys and values can be used to customize the SeparationRule parameter.

NOTE: Do not include the HTTP method in this rule.

2	Click Edit beside SeparationRules.

Setting rules for transforming URLs

The Nexus recording settings define transformation of URLs. If separation parameters are defined for a URL that is to be transformed, the transformation is performed on the resulting separated URL, which includes the path and separation parameters. There may be more than one transformation defined. Each transformation may contain more than one replacement definition.

The URL transformation rules also control how requests are grouped for display on the Requests view of the Application Servers Monitor dashboard. A set of default transformations shorten the request URLs. Request types that have request separation configured are not transformed by the default rule. Static file requests (for example, images) are also not transformed.

NOTE: Changing any of these settings requires advanced knowledge of the product. Do not modify any of the settings if you are unfamiliar with this product. Make a backup of the Nexus profile before editing. You do not have to restart your instrumented application servers after editing the Nexus recording settings. Data collection is stopped and restarted automatically when the recording settings change.

NOTE: These default transformations are only available for new installations. Upgrading from a previous version does not change your existing transformation rules.

3	Click Edit beside URLTransformationRules.

4	In the Settings Editor, click Add URL transformation.

NOTE: Regular expression special characters that should be matched as literal characters in the URL must be escaped with a “\” character; for example, “\?” to match a literal “?” in the URL.

8	Click Add URL replacement. In the new row that appears, click in each box to type the required information.

NOTE: Regular expression special characters that should be matched as literal characters in the URL must be escaped with a “\” character; for example, “\?” to match a literal “?” in the URL.

NOTE: Regular expression special characters that should be matched as literal characters must be escaped with a “\” character; for example, “\?” to match a literal “?”.

where:

<url-regex> is a regular expression used to match the URLs that need to be transformed. The ‘/’ and ‘?’ characters must be escaped with a ‘\’ character.

<text-in-url-regex> is a regular expression used to match the text that needs to be replaced in the URL. The ‘/’ and ‘?’ characters must be escaped with a ‘\’ character.

<replacement-literal> is a string literal of the replacement text, as described in Step 10 in the previous procedure. Backslashes must be doubled (“\\”) .

NOTE: Check the Separation Rules to confirm if the separation parameters are defined. For more information, see Setting rules for separating requests.