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

Defining an instrumented application component

Configuring an instrumented application component involves defining a set of regular expressions that match the URLs in use on your site.

1
Click Add a new Instrumented Application Component, located at the bottom of the Instrumented Application Components section.
b
Click Add.

Editing an instrumented application component

You can modify an instrumented application component definition by clicking its corresponding Edit link, which takes you to the Instrumented Application Components > Edit page.

In the Application Component Definition section, you can edit the application component name.

You can also modify the regular expressions that identify the instrumented application component. Select the check box that corresponds to an expression, and click Delete to remove it. You can then replace it by adding regular expressions in the manner outlined in the previous section.

Deleting an instrumented application component

To delete an instrumented application component from the list displayed in the Application Components page, select its corresponding check box and click Delete.

Managing services definitions

A service represents a sequence of pages that a user must traverse to complete a specific process (for example, checking out and completing a purchase on an e-commerce site). You can define a service by identifying a sequence of pages, then giving the sequence a name, which is used to identify the service in the web console.

Figure 76. Services page

For more information, see these topics:

Configuring a service involves defining the sequence of steps, assigning service level thresholds, and choosing appropriate distribution configurations.

8
Select the Non-sequential page traversal included box if users do not have access to the pages in the listed sequence. This option needs to be selected in order for that action to be considered an instance of a service.
9

You can add a service step to the service by clicking Add a Step. Doing so requires navigating to the Services > Service > Edit page, which allows you to provide a symbolic label for the service step, define its type, and list the pages and regular expressions that determine which URLs qualifies as instances of this service step.

Required: The user must traverse this step in order to complete an instance of the service.
Optional: The user does not have to traverse this step in order to complete an instance of this service. If they do traverse this step then the metrics for this step are included in the overall metrics for the service. Note that the last step of a service cannot be optional.
Abort: This step indicates the end of the service. When a user hits this step the service is considered to have been stopped prematurely. The abort count is incremented. All other service metrics are not updated.
4

Next a service step can be defined to reference one or more pages (or URLs).

2
In the Protocol list, select All to display all pages, HTTP (insecure) or HTTPS (secure) pages displayed.
You can use an asterisk (*) as a wild card to define a segment of the string that matches any combination of characters.
6

From the Service > Edit page, if required, resort the list of pages into the desired order by using the and buttons. Click OK to save this service definition.

Related Documents