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

About

This page provides information about your Foglight Experience Monitor.

Adding a user agent definition

1
2
In the Find box, type a string or regular expression that will be used to match against the user-agent HTTP header.
Alternatively, click Select User Agent to select from a list of user agents that the appliance has encountered so far.
b
If you need to search by Perl regular expression, check the Interpret as a regular expression option.
c
3
In the Display box, type a string that the system will use as the resource name for user agents matching the Find string.
4
Select the Interpret find string as a regular expression check box if you want the regular expression implemented in Perl.
5
Select the Extract version following the find string check box if you would like the user agent version number to appear with the agent name in the Web console.
For example, if a transformation rule’s Find value is mozilla, and its Display value is Mozilla, Mozilla 4.0 and Mozilla 5.0 will appear as separate entries in the user agents list.
6
Select Applies only to major version numbers check box if the transformation rule you are creating should only be applied to user agent versions that fall within the defined range entered in the from and to boxes.
7
Click the Test link to test the Find string against the current list of User Agents.
8
Click OK to save the user agent transformation rule.

All existing transformation rules are listed on the User Agents page.

To edit a user agent transformation rule, click its corresponding Edit link to display the User Agents > Edit page, where you can modify the string the rule matches against incoming user agent strings, the display name in the Web console, or how user agent version numbers are handled.

To remove an individual transformation rule, select its corresponding check box, then click Delete.

To remove the default set of transformation rules, click Reset User Agent Rules (located at the bottom of the page).

The Has Version and the Applies only to major version numbers check boxes can be configured differently in multiple user agent transformation rules to differentiate user agent versions ranges whose performance you wish to evaluate separately or differently.

For example, the appliance’s default handling of the Mozilla Web browser as user agent is as follows:

Rule A:
Find: mozilla
Display: Netscape
Has Version: yes
Applies only to major version numbers: from 0 to 4

Rule B:
Find: mozilla
Display: Mozilla
Has Version: yes
Applies only to major version numbers: n/a

If mozilla is found in the user agent, it is displayed as Mozilla, along with its version number unless is it found as version 0 through 4, in which case, it is displayed as Netscape along with its version number.

Use multiple overlapping transformation rules to distinguish or consolidate user agent types and versions as required in order to effectively evaluate your Web applications.

Identifying user sessions

The User Sessions page, accessed by clicking Configure > Monitoring > User Sessions, allows you to define how the appliance should identify user sessions, and what login variables are in use on your site.

To see user sessions that have been captured by the appliance navigate to the User Sessions Log which can be accessed by clicking Analysis > User Sessions Log.

The log displays a list of user sessions that have been recorded by the system and is sorted by the time the user session ended. In the Identifier column either the login name or the IP address associated with the user session is displayed. Other information such as the name of an alarm triggered by the user session, the originating subnet or city, the duration of the session and the number of pages downloaded by the user is displayed.

Session identification variables are the entities that are used by the applications you are monitoring to distinguish one user session from another. Typically, these are cookie variables but they can also be embedded in the URL either in the path, parameter or as a query variable. In some cases, form variables (POST parameters) can also be used to identify user sessions.

By configuring the Client IP tags in the User Session page, you can define the tags of HTTP headers that contain IP addresses of client machines accessing your monitored applications. In typical network environments, client traffic is routed through a proxy server that replaces the originating client IP addresses with the IP address of the proxy server.

The following HTTP headers are industry standards for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer, and display as the default Client IP Tags in the appliance:

If your site is using different HTTP headers than those listed above, you may notice that the client IP addresses appearing in the User Sessions Log are the same. To ensure that the correct originating IP addresses appear in the appliance web console, you will need determine which HTTP header (if any) you will need to configure in the Client IP Tags list.

If there are no HTTP headers containing the originating IP address you will need to contact your network administrator to determine if this feature can be enabled in your HTTP proxy or load balancer.

This list is in priority order (if you have more than one header containing the Client IP) so make sure that the order reflects the configuration of your network. Use the and arrows to reorder the items in the list. Tags that are not in use on your site may be removed from the list although this is not required.

In the Client IP Tags section, enter the name of the tag that matches HTTP header containing the IP address of the client machine, then click Add.

The list of logout patterns updates to include your addition.

Select the check boxes that corresponds to the Client IP Tag you would like to remove, then click the Delete button.

Many applications check the credentials of users logging into the application by displaying a page that prompts the user to enter an account name and password. When the user enters this information, the login name is typically transmitted to the application server in a form (or POST) parameter. The appliance has the ability to extract these fields from the traffic and associate the login name for the user with the user session. This greatly facilitates the use of the User Sessions Log and makes it much easier to identify the user associated with a session.

In the Login Variables section, you can define the names of variables that are used to contain login names in your application. While login variables are typically contained in form variables, the system can also extract them from cookies or query variables embedded in a URL.

With this configuration setting, you are able to see the login names of your users in the Identifier column of the User Sessions Log and in the All Metrics View report. You can also define an alarm based on the value of the login name that triggers whenever it matches a pattern that you define.

By default, the appliance considers a user session active until the timeout period has expired. (For more information, see Defining session timeout periods.) Defining logout patterns helps the appliance determine if and when a user has actively logged out of their application. Being aware of a user that actively logs out, compared to waiting for a timeout period to be reached, means the user session is written to the User Sessions Log more quickly than it would be otherwise. This can assist with the troubleshooting of user issues in real time.

In the Logout Patterns section, you can enter a regular expression (for example, .*logout.*) that matched against the URL that the user is accessing. If the user accesses a page that matches any of the defined logout patterns
(in this example, https://company.com/app/sessions?logout=true), the user session is considered terminated and the record is written to the database.

Access the User Sessions page by clicking Configure > Monitoring > User Sessions. The Options section of this page displays the sessionizing switch.

If the appliance is configured to use hits to detect user sessions, every incoming hit is examined for user session variables. This means that a session can be easily identified, but the application needs to provide the same identifier in every hit for the duration of the session.

When the appliance is configured to sessionize by TCP connection, it identifies a user session by detecting the session identification variable in the first few hits, then applies that determination to the remainder of the TCP connection.

By default, the appliance is configured to detect user sessions by individual hit.

Adding metric tables

When you click Add Metric Table while editing a report set, the Edit Report Set > Metric Table page is displayed.

In the Definition section, configure how the metric table is displayed in the Report to which it is being added.

This name appears in the Reports section of the Edit Report Set page, and it is also used as the title of the chart when the report set is displayed.
2
Use the Time Frame box to select a predefined time frame for the chart. See also Time Frames in Which Metrics Are Viewed in the Foglight Experience Monitor Metric Reference Guide.
1
In the Metrics section, click Add Metric to display the Metric List window, from which you can select the first metric this report displays (for a review of the Metric List, see Choosing a metric to add to a report).
5
Metrics for which historical data is available presents a Show Baseline check box. Select this if you would like the baseline values for this metric and resource to appear in the table.

You must select the specific resource that provides the data to be displayed. Click Choose Resource to display the Resource List window, and select a resource from the list.

All known resources in the particular metric category are presented in the Resource List. Browse through it (it may be spread across multiple pages), or enter a search term to refine the list.

When you click a resource, the Resource List window closes, and you are returned to the Edit Report Set > Metric Table page. Your selection is listed in the Resource box.

You can continue to edit and combine resources that are added to your Report by clicking the Add Metric link, found at the bottom of the Add Metric section.

Whenever you complete the addition of another metric to your metric table, the Metrics section is updated to include all of them.

The order in which the metrics appear here is identical to how their data is displayed in the report set. You can also reorder the metrics by using the and buttons. Remove a metric by selecting its check box, and clicking Delete.

When you have completed defining and modifying the contents of the metric table, click OK. Doing so returns you to the main Edit Report Set page, where you can continue to add other reports.

Related Documents