Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - Installation and Administration 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 Appendix: Dell PowerEdge system appliance

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.

To define an instrumented application component:
1
Click Add a new Instrumented Application Component, located at the bottom of the Instrumented Application Components section.
This displays the Instrumented Application Components > Edit page.
2
Name the Application Component Definition
In the Name box, type the symbolic name you want to associate with this instrumented application component.
Each instrumented application component must have a unique name. Use this name to locate the metrics recorded for it in the web console.
3
Add Regular Expressions
For existing application components, the Regular Expressions section lists all the regular expressions that have been defined. Since you are defining a new application component, this section is empty.
a
Type a regular expression in the box. For example, if you know where the application components are located (all components are found under quest.com/support/), enter the expression (in this case, quest.com/support/.*).
Multiple regular expressions can be added.
b
Click Add.
The regular expression appears in the Regular Expressions section.
c
To display a list of URLs that match the regular expression and application component definition, click Test.
 
* 
NOTE: This test is performed against the list of URLs that have been monitored and recorded by the appliance in the past.
d
Close the Application Test window when you are finished reviewing the resource list.

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.

 
* 
NOTE: If you modify the name of an existing instrumented application component, this change takes up to 30 minutes to propagate throughout the metrics that are displayed in the web console.

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

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.
•
Configuring services auto-discovery
•
Configuring synthetic transactions
•
Managing existing service definitions
•
Using alternative methods to define a service

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

To define a service:
1
To begin defining a service, on the Services page navigate to Configure > Applications > Services and then click Add a new Service. This displays the Services > Edit page.
Naming the service
2
In the Name box (in the Service Definition section), type the symbolic name you want to associate with this service.
Each service must have a unique name, and users can use this name to locate the metrics recorded for it in the web console.
Setting service-related service levels
3
In the End-to-End Time Service Level Threshold box, type the service level objective for the total time taken for all pages to be delivered to the user.
For example, if you decide that most of the services should be fulfilled within 15 seconds, enter 15000 (units are in milliseconds).
The Service End-to-End Time Service Level metric then shows you the percentage of services that satisfy this service level. For information on how this metric is calculated, see Service End-to-End Time in the Foglight Experience Monitor Metric Reference Guide.
4
In the Processing Time Service Level Threshold box, type the service level objective for the time taken by the web server farm to process all of the page requests in the service.
For example, if you decide that the time to process the pages in this service should generally not exceed six seconds, enter 6000 (units are in milliseconds).
The Service Processing Time Service Level metric shows you the percentage of transactions pages whose processing time satisfies this service level. For information on how this metric is calculated, see Service Processing Time in the Foglight Experience Monitor Metric Reference Guide.
5
In the Timeout box, type the period of time that is used as an expiration timer for users of the service.
If any user exceeds the time specified they are considered to be timed out and their activity cannot influence the metrics collected for the service. The Service Timeout metric reflects the number of times the service has timed out based on the timeout setting that you specified.
6
In the End-to-End Time Distribution Configuration box, select the distribution configuration that you would like to use for this service.
Distribution configurations allow you to specify the buckets and ranges of the distribution. By default, the Service End-to-End Time Distribution is selected when you create a new service. If you have defined additional distribution configurations for this metric they appear in this list and can be chosen for this service. For more information about how this metric is calculated, see End-to-End Time Service Level in the Foglight Experience Monitor Metric Reference Guide.
7
In the Processing Time Distribution Configuration box, select the distribution configuration that you would like to use for this service.
Distribution configurations allow you to specify the buckets and ranges of the distribution. By default, the Service Processing Time Distribution is selected when you create a new service. If you have defined additional distribution configurations for this metric, they appear in this list and can be chosen for this service. For more information about distributions see Distribution metrics.
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.
By default, this check box is cleared, but in some cases you may want to allow non-sequential traversal. For example, if users are interacting with a web application that uses HTML frames, you may define a service that includes the URLs for all of the frames that appear as a single page to the user. In this scenario, the frames are accessed simultaneously so the order in which they are accessed by the end user is not significant.
9
Click OK.

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.

To add a service step:
1
In the Name box, type the symbolic name you want to associate with this service step.
Every service step must have a unique name among all of the services that you have defined. This is required in order to be able to uniquely identify service steps in the web console. It is recommended that you use a naming convention for service steps that includes the name of the service. For example, if your service is named Checkout you could name your service steps Checkout - Step 1.
2
From the Type list, select one of the following choices:
•
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.
3
In the Service Step Criteria box, type a regular expression and then click Add.
Each service step can be defined by a single URL, regular expression or a list of URLs and regular expressions. To define URLs in the service step, see Configuring services auto-discovery.
4
Click OK.

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

To define pages in a service step:
1
From Services > Service > Edit page, click Add a Page.
A Resource List window appears, displaying all pages that the system has seen up to this point in time.
2
In the Protocol list, select All to display all pages, HTTP (insecure) or HTTPS (secure) pages displayed.
Service steps always match the defined URLs whether they are accessed using HTTP or HTTPS.
 
* 
IMPORTANT: There is no way to define a service step that is restricted by HTTP or HTTPS.
3
Narrow the list to a more specific set of pages by entering a search string in the Search box, then clicking Go.
You can use an asterisk (*) as a wild card to define a segment of the string that matches any combination of characters.
•
Optionally, reduce the list further by opting to display only secure (HTTPS) or insecure (HTTP) web pages from the Protocol list, then clicking Go.
•
Show URLs with encoding or decoding.
4
When you have located the page you would like to add to the service definition, click the URL.
When a page has been selected, the Resource List window closes, and the selected page appears in the Service Step Criteria list back on the Services > Service > Edit page.
5
Continue to add pages to the list until the service step has been completely defined.
6
Click OK.
Defining the order of service steps

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

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating