Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - User Guide

Installing and configuring Multi-appliance clusters Configuring the appliance Specifying monitored web traffic Transforming monitored URLs Managing applications Foglight components and the appliance Using the console program Troubleshooting the appliance Appendix: Third party software Monitoring the user experience Customizing reports The alarm system Integrating the appliance SOAP-based web services

Managing path rules

The path rule definition and its component segment rules are displayed on the Path Rules > Edit Path Rule page.

You can manage path rules by editing the path rule definition and by adding, editing, removing, or reordering its segment rules. You can also click Test at the bottom of the page to open the Test Path Rule dialog box and test your path transformation rule.

1
On the Path Rules page, click Add a Path Rule to display the Path Rules > Edit Path Rule page.
6
Click Add a Segment Rule to begin constructing your path rule.
11
Ensure the Required check box is selected, if the segment is required to appear in the URL that is captured from monitored network traffic.
12
Select the Append a slash check box if the segment rule should append a slash (“/”) to the transformed segment.
13
Click OK to complete the definition of this segment rule.
15
When your segment rule set is complete, click Test to display the Test Path Rule window.
16
Enter test URLs into the Input URL field, then click Test.
NOTE: Even though you are building rules for the path portion of a URL, in the Test Path Rule dialog box you can input the full URLs you expect the appliance to monitor. For example, if the URL entered in the dialog box is
www.travel.com/states/florida/home.asp
any of the following URLs would be successfully processed:
http://travel.com/states/florida/home.asp
travel/states/florida/home.asp
//travel/states/florida/home.asp
18
On the Path Rules > Edit Path Rule page, click OK to accept the completed path rule definition.

Editing and removing path rules

On the Path Rules page, all current definitions are displayed.

To edit a path rule definition, or enable/disable a rule, click its corresponding Edit link to display the Path Rules > Edit Path Rule page, where you can modify the path rule definition.

To remove a path rule altogether, select its corresponding check box, then click Delete.

Managing variable rules

The Configuration > URLs > Variable Rules page lists all defined variable rules, and allows you to define new rules.

Variable rules allow you to specify how the system transforms the query and parameter segments of URLs, and also define how form variables (POST parameters), XML variables, cookies, and HTTP headers are appended to URLs that appear in the metrics.

In the Variable Rules section, all currently defined variable rules are listed, and the Type column indicates whether the corresponding variable rule applies to a query variable, form variable, HTTP variable, parameter, XML or Cookie variables.

For more information, see these topics:

Transforming query variables

When transforming URLs found in the network traffic into the URLs that appear in the database, the system masks the values of all query variables that appear with XX. This is done so as to prevent the number of URLs from rapidly proliferating as can happen when the values of a query variable continually change. An example of this is when a query variable contains a timestamp that changes every second.

To expose the values for any query variable, you can define a variable rule which causes a unique URL to be written to the database for every combination of values seen for the query variable. For example, consider the following URL, in which id and task are query variables:

If a variable rule for id was previously configured in the appliance, a different URL is stored in the database each time the id has a different value:

When configuring query variables, it is important to specify only those variables that have a limited range of values. For example, the following URL has includes resort and time as query variables:

In this case, you can define a variable rule that exposes resort which represents a fixed set of resorts in Mexico. However, it would probably not be appropriate to expose time which represents the time of day. If a variable rule was configured for time, the appliance would generate a new URL that would appear in the Page and Hit categories every time this value changed.

Within a single URL, the appliance alphabetically orders URL queries based on the query variable name.

For example, the following URL:

appears in the database as:

Related Documents