サポートと今すぐチャット
サポートとのチャット

Foglight APM for Real User Experience 5.9.9 - Administration and Configuration Guide

Getting started Configuring traffic capture
Managing Sniffers Managing Archivers Managing capture groups Managing sessionizing policies Managing monitored ports Managing monitored IP addresses Managing monitored subnets Managing identifiers for virtual addressing schemes Managing private keys Managing web services and SOAP operations
Configuring traffic analysis Configuring analyzers Capturing traffic outside the network Configuring advanced options Integrating Foglight APM with other products Maintaining and troubleshooting Appendix: Building regular expressions in Foglight Appendix: Traffic analysis processing
Understanding the traffic analysis workflow Stage 1: Run hit analysis Stage 2: Run sequence analysis Stage 3: Finalize stopped sequences Stage 4: Finalize the session Example of interdependent analyzers Online-Only Topics
Removing items from a table Defining extraction expressions Adding, copying, and editing archivers Testing archivers Configuring archiver database shard settings Adding, copying, and editing sniffers Testing sniffers Adding and editing capture groups Testing capture groups Adding and copying sessionizing policies Editing sessionizing policies Selecting session identifiers from a discovery list Adding and editing session identifier variables Organizing session identifiers Selecting user name variables from a discovery list Adding and editing username rules Selecting URL prefixes from a discovery list Adding or adding URL prefixes Selecting ports from a discovery list Adding or editing monitored ports Selecting IP addresses from a discovery list Adding or editing monitored IP addresses Looking up host names for all monitored IP addresses Associating private keys with IP addresses Selecting subnets from a discovery list Adding and editing monitored subnets Adding identifiers Editing identifiers Finding IP addresses in HTTP headers Configuring a custom HTTP header using Microsoft IIS Manager Adding and editing local private keys Adding and editing HSM private keys Exporting keys using Microsoft Management Console Adding or editing web services Importing WSDL files to define web services Managing custom fields and metrics Adding, copying, and editing custom fields Removing custom fields Editing custom metrics Removing custom metrics Managing sensitive data Adding, copying, and editing sensitive hit detail policies Adding, copying, and editing sensitive content expression policies Modifying members of pivot categories Selecting aliases from a discovery list Adding, copying, and editing domain rules Adding, copying, and editing large hit details Adding, copying, and editing URL classifiers Reviewing rules for browser category, browser, and operating system hit details Adding user-defined user agent rules Adding and editing additional parsed response types Adding and editing captured request body types Adding, copying, and editing scripts Removing scripts Referencing configuration objects in a script Testing regular expressions Syntax for test data Adding simple hit analyzers using the Setup Wizard Adding simple sequence analyzers using the Setup Wizard Adding analyzers Copying analyzers Editing analyzers Adding and editing conditions Creating a simple Boolean expression Creating a complex Boolean expression Disabling standard metrics generated by a hit analyzer Adding custom metrics Editing custom metrics Selecting pivot categories Breaking out metrics into dynamically-named topology objects Publishing metric timeslices for the Geographical Perspectives dashboard Changing SLA thresholds Adding custom field updates Editing custom field updates Adding scripts to an analyzer Editing scripts Creating new scripts on the fly Adding hit storage restrictions Editing hit storage restrictions Adding sequence events Editing sequence events Adding static page elements Editing static page elements Viewing resource files defined by static page elements Adding and editing subnet filters Exporting configurations Exporting encrypted configurations Restoring a previous configuration Importing saved configurations Importing hit analysis configurations from Foglight Experience Viewer Using the Import Configuration Wizard

Identifying session identifiers in URL paths

Some applications use URL rewriting to embed a session identifier in the URL path. For example, the following URL contains the session identifier value 123A456789B012:
•
http://www.quest.com/this-topic/123A456789B012/that-action.do
If one of the applications you want to track uses URL rewriting, you need to define a session identifier of type URL Path and specify a regular expression to match the session identifier portion of the URL path. For more information, see Defining session identifiers.
Example: Matching and extracting session identifiers
Consider the following URLs:
•
    www.example.com/products/sid=ABC/content/page1.html
•
    www.example.com/products/sid=XYZ/content/page2.html
The session identifier variable is sid, and it is embedded after products/ and before /content. In the Regular Expression box, we use the following regular expression as the pattern to match:
    .*/sid=(.*)/content.*
The parentheses show the part of the path to be used as the session identifier. In the example URLS, the session identifiers are ABC and XYZ.
Figure 17. Adding session identifier example

Defining session identifiers

When adding or editing a session identifier variable, you can set the following options.
 
Table 11. Defining session identifiers
Option
Setting the Option
Name
Specify a unique name for the session identifier.
NOTE: When Type=URL Path, the value in the Name field is not used by the Archiver. However, you should specify a name for administration purposes.
Description
Optional—provide more information about the session identifier variable. For example, you can include the name of the application that uses the variable.
Type
Select the type of session identifier variable you are defining. For example, select Cookie if session identifiers are located in cookies.
Regular Expression
When Type=URL Path, specify the pattern for the embedded session identifiers as a regular expression. To test your expression, click to open the Extraction Rule dialog box. For more information, see Defining extraction expressions. For an example, see Identifying session identifiers in URL paths.

Prioritizing session identifiers

After you finish adding your session identifiers, you should arrange them in priority order from top to bottom in the table. If a hit contains more than one configured session identifier—for example, some sites use different tools to develop different sections of the site which may result in multiple identifiers—the order of the session identifier variables in the table tells the system which session identifier to use to track the current session. You can change the location of a variable within the table by clicking its Up or Down icon.
Figure 18. Session Identifiers view

Sessionizing policies—Associating user names with user sessions

Many web applications prompt end users to log into the application using a user name and password. When the user enters the login credentials on the web page, the application transmits the user name to the application server, typically in a form (or POST) parameter, but potentially in an XML variable, cookie, or HTTP header. Foglight can extract the user name from the web traffic and associate the user name with the user session.
 
* 
NOTE: Username rules do not affect how user sessions are identified; they only affect how sessions are labeled in the Session Explorer, search results, and reports.
To include user names in your session details, navigate to APM > Configure > Traffic Capture > Sessionizing Policies, and expand Username Rules.
Figure 19. Username Rules view
In the Username Rules view, you can perform the following tasks:
•
Discovering user names
•
Defining username rules
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択