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

Configuring services auto-discovery

Services auto-discovery displays a list of URLs accessed by a user while logged into a user session. The URLs are used to create a service definition with each URL being considered a step in the service.

Often environments are controlled using Network Address Translation (NAT) which involves removing the client IP address from the IP headers by an HTTP proxy and making it difficult to identify the user session by IP. If your environment is controlled by NAT you can use either the Session Identifier or the Login Name option so that the appliance can determine which URLs are specific to the user session.

Before you can use Auto-Discover Service you must configure user sessions and define service steps. For more information, see Configuring user session identification and Configuring a service involves defining the sequence of steps, assigning service level thresholds, and choosing appropriate distribution configurations..

To configure Auto-Discover service:
1
From the Service page click Auto-Discover Service.
2
In the Session Identification area configure select one of the following options to tell the system how to discover your usage of the monitored application for auto-discovery:
•
Select the IP Address option and type a valid IP address in the box. This option works only if your client IP address is not being translated by an HTTP proxy before it reaches the monitored application.
•
Select the Session Identifier option. Select a Session Identifier from the list. In the Value box, type the value for the selected session identifier that has been assigned to your session (typically, a session identifier is a cookie). Determine what value has been assigned to your session cookie using a tool like the Mozilla® Web Developer Toolkit. For more information, see Managing user session identification variables.
•
Select the Login Variable option. Enter a login name then choose a Session Identification variable from the list to tell the system how to track your session after the login name you defined has been discovered.
3
Click Start.
The appliance begins to detect URLs based on the session identification option that you configured. The Services Auto-Discovery page updates every few seconds, adding any newly detected session identification to the list.
4
Click Stop at any point to cancel the search, and use the list that has been compiled up to that point.
All session identifications discovered up to that point are displayed in a list with accompanying check box. The following information for each is displayed:
•
the time in milliseconds for each URL based on the session identifier
•
the type of data returned in the URL (for example HTML, Text or a graphic type)
•
the URL
•
details link for each session identification
5
Click the details link for any entry in the list.
The Hit Details window opens displaying the following information.
 
* 
NOTE: The Services Auto-Discovery window remains open until it is manually closed.
 
Table 28. Hit Details information
Data
Description
Hit Details

Full URL—The URL address as it was captured by the appliance from monitored traffic.

Transformed URL—Displayed the URL with transformation rules applied.

Cookies

Any cookies found in the request.

Request Header

Any HTTP request headers found in the request.

Form Variables

Any form variables.

6
Select the check boxes that correspond to any URL that you would like to use as a service step in a service.
7
Click Add.
The URLs is added to the Service Steps section on the Services > Edit page.

Configuring synthetic transactions

The Foglight Transaction Recorder is a Foglight component that provides the ability to monitor end-user response time for web applications, whether they are packaged applications such as PeopleSoft, Siebel eBusiness Applications, Oracle® E-Business Suite, or custom applications. The Foglight Transaction Recorder uses simulated business transactions to test performance, and notifies administrators of performance degradation before end users are affected.

Foglight Transaction Recorder users can interactively record scripts through an embedded web browser that simulates the activity generated by an actual user of your web site. It captures and records all mouse movement, link or button clicks, and any data entry that may occur during the session.

If you are using Foglight for Synthetic Transactions against your monitored applications, the transactions appear in the Synthetic Transactions category of metrics on the appliance. You can configure a Service that matches the Synthetic Transaction using the Synthetic Transactions section of the Configure > Applications > Services page.

Viewing synthetic transaction scripts

In the Foglight Experience Monitor web console, click Configure > Applications > Services. This displays the Services page which includes the Synthetic Transactions section.

Figure 77. Services page

Any synthetic transactions scripts monitored by the appliance are listed. When viewing detected Synthetic Transactions scripts, whether a script is currently associated with an existing Foglight Experience Monitor service, clicking Create or Edit takes you to the Services > Edit page.

Creating and editing synthetic transactions scripts

When viewing detected Synthetic Transactions scripts, if a a script is currently associated with an existing Foglight Experience Monitor service, clicking create or edit takes you to the Services > Edit page.

Figure 78. Services: Edit page

To create and edit Synthetic Transaction Scripts:
1
For new service definitions, provide the service with a symbolic name in the Name box. This name references the service definition throughout the Foglight Experience Monitor console.
2
If required, continue to edit the service definition. (See Managing services definitions for more information.)
3
Click OK.
You are returned to the Services page.

Managing existing service definitions

You can managing service definitions by editing or removing them.

Removing a service

When viewing the list of defined services on the Services page, you can delete an entry by selecting its corresponding check box, then clicking Delete. Use the Check All option to select all entries for deletion. The Clear All option is used to clear any entries that were selected for deletion.

Editing a service

You can also modify a service definition by clicking its corresponding Edit link. Doing so takes you do the Services > Edit page, which allows you to rename the service set service level thresholds and choose distribution configuration.

 
* 
NOTE: If you modify an existing service definition name, this change takes up to 30 minutes to propagate throughout the metics that are displayed in the web console.

You can also modify the list of steps that comprise the service. Remove steps by clicking their corresponding check boxes, then clicking Delete. Reorder steps by using the and buttons. When you have finished making changes to the service, click OK.

Editing a service step

You can modify a service step definition by clicking its corresponding Edit link. Doing so takes you do the Services > Edit page, which allows you to modify the service step definition.

Using alternative methods to define a service

Defining a service by selecting the steps manually is just one method that you can use. This section describes alternative approaches.

Using user sessions

From the User Sessions Log you can drill-down into the All Metrics View for a user session. At the bottom of that page, the link Create a Service based on this User Session appears. By clicking that link, you can begin the process of defining a service that matches all of the pages traversed during the user session. Clearly, this option is only useful if you are controlling the pages accessed by that user so that it matches the service you would like to define.

Using paths

The Path category tracks commonly accessed sequences of pages. By navigating to Analysis > Metric Analysis and selecting Path > Path Count you can generate a report that displays the most commonly traversed paths in the application you are monitoring. By clicking the link for one of the paths you will be taken to a Metric View for that path. At the bottom of that page, the link Create a Service based on this Path appears. By clicking that link you can begin the process of defining a service that matches all of the pages recorded in this path.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating