Metric Analysis pages allows you to search the database for extreme values of the selected metric.
The precise meaning of each extreme depends on the metric currently being viewed. In the above example, the metric is time-based, thus selecting Top displays the content types with the highest (slowest) hit end-to-end times.
For more information about metrics, see Types of Metrics in the Foglight Experience Monitor Metric Reference Guide.
IMPORTANT: No HTTPS data is available if SSL keys used by secure servers are not uploaded to the appliance. For more information see, Monitoring Secure HTTP Servers in the Foglight Experience Monitor Installation and Administration Guide. |
All variable rule definitions and modifications take place on the URLs > Edit Variable Rule page.
Configuration of a variable rule requires that you specify actions on both parts of the name-value pair. For example, consider the URL www.store.com?catalog=pet. This URL consists of a single variable whose name is catalog, that may have many values such as pet.
By defining a variable rule, you can control how both the name and value are transformed when the appliance adds the URL to the database. You could choose to ignore catalog altogether, to mask its values as XX, or to expose all of its values in the database.
1 |
On the Configure > URLs > Variable Rules page, click Add a Variable Rule. |
2 |
In the Name Action section, begin by entering a string in the Variable name box that identifies the variable that appears in monitored URLs. |
3 |
Select, or leave the Evaluate as regular expression check box clear, depending on whether you want to use a regular expression to define multiple variable names, or use a literal string to find an exact match. |
4 |
From the Variable type box, select whether the variable that you are looking for is a query, form, XML, cookie, parameter or HTTP variable. |
6 |
If you wish the path rule to also apply to hits transmitted from the Foglight Experience Monitor to the Foglight Experience Viewer, enable the Apply to Foglight Experience Viewer hits check box. |
8 |
Click OK to save the variable rule definition. |
The name that is entered must precisely match that which you wish to find in monitored URLs. For example, if you enter catalog as the variable name, this sample URL:
www.store.com?catalog=pet
will be affected by this rule, but this URL:
www.store.co.uk?catalogue=pet
will not be transformed.
If you select the Evaluate as regular expression check box, then the value that you entered in the Variable Name box is treated as a regular expression. With this setting selected and the string catalog.* specified in the Variable Name box, this rule would affect both of the URLs:
www.store.com?catalog=pet
www.store.co.uk?catalogue=pet
The Variable type list allows you to specify the variable type:
• |
Query Variable - These are query strings that appear after the question mark in a URL, and are the most common type of variable to which you can apply transformations. |
• |
Form Variable - These are variables that appear in HTTP POST requests, and are typically tied to HTML elements that allow the user to enter data, such as text entry boxes. |
• |
XML Variable - These are variables that appear in HTTP POST requests, but are encoded as XML. |
• |
Cookie Variable - These are variables that appear in cookies contained in the HTTP header. From the perspective of end users, cookies are transparent, and are not visible in URLs. |
• |
Parameter Variable - These are values that appear after the path portion of a URL. |
• |
HTTP Variable - These are value that appear in the HTTP headers and contain information about the client, server and the web page. Some applications can create custom HTTP headers that contain useful state information relevant to the application itself. In these cases, you can configure these HTTP variables and expose their values in the user interface. |
When you select the Show as is option button, the name portion of the name-value pair is not transformed, and only the operation performed on the value portion of pair changes the URL.
Selecting the Replace with option button requires that you enter a direct replacement string in the accompanying text entry box.
Selecting the Transform with option button necessitates the entry of a regular expression in the accompanying text entry box.
Selecting the Mask with XX option button causes all values of the name-value pair to be replaced with XX in the transformed URL.
Selecting the Decode as XML option button indicates XML is embedded in the variable value, and needs to be expanded.
Consider the following example:
http://www.store.com/page.asp?xml=<Screen Action=”Save” Panel=”Address”>
In this URL, there are two XML variables in the XML string:
Screen.Action, and Screen.Panel.
By default, the appliance would detect and display the URL as:
http://www.store.com/page.asp?myxml=XX
In the Name Action section, if you identify xml as the variable name, and in the Value Action section, choose to Decode as XML, the URL would transform to:
http://www.store.com/page.asp?xml=<Screen Action=XX Panel=XX>
If you continued by defining another variable rule for Screen.Action, the URL would then be transformed to:
http://www.store.com/page.asp?xml=<Screen Action=”Read” Panel=XX>
Selecting the Decode as URL option button indicates the variable value is an embedded URL, and needs to be expanded.
Consider the following example:
http://www.store.com/page.asp?step=http://www.store.com/
actualstep.asp?action=save&session=12345
In this URL, you can create a variable rule that instructs the appliance to decode step as a URL. This allows you to further manipulate variables that are embedded in the step URL (that is, action, and session).
By default, the appliance would detect and display the URL as:
http://www.store.com/page.asp?step=XX
If you identify step as a variable name in the Name Action section, and in the Value Action section, choose Decode as URL, the URL would transform to:
http://www.store.com/page.asp?step=http://www.store.com/
actualstep.asp?action=XX&&session=XX
If you continued by adding an additional variable rule for action, the URL would then be transformed to:
http://www.store.com/page.asp?step=http://www.store.com/
actualstep.asp?action=save&&session=XX
Click the Details link to see a page displaying all the information recorded about the SOAP fault.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy