Chatta subito con l'assistenza
Chat con il supporto

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

Capturing complete user sessions

For Foglight to understand how user sessions are identified and managed within your monitored web applications, you need to define a sessionizing policy. Usually, you can edit the default sessionizing policy to include your application’s session identifiers. However, if you are monitoring Microsoft® SharePoint®, Oracle® PeopleSoft, or Oracle® Siebel, you need to create a new policy. For more information, see Deciding when to add more sessionizing policies.
By default, Sniffers look for session identifiers under the following default variable names:
•
aspsessionid (default for ASP applications)
•
asp.net_sessionid (default for ASP .NET® applications)
•
sessionid
•
jsessionid — cookie (default for Java™ applications)
•
jsessionid — URL parameter (default for Java™ applications)
•
phpsessid (default for PHP applications)
•
siteserver.id
If your web application uses different variables to pass session identifiers, you need to add them. If you know that the session identifiers are in cookies, you can try to discover the variable names in the live web traffic, as described in the first procedure. Alternatively, you can ask your application developers for the variable names and add them manually, as described in the second procedure.
 
* 
NOTE: If your network uses CA SiteMinder Servers for single sign-on, you need to integrate Foglight with your SiteMinder servers and add the SiteMinder cookie as the session identifier. For instructions, see Integrating with CA SiteMinder.
Typically, your sessionizing policies should align closely with the session management techniques employed by your applications. You can set options that define boundaries for sessions, such as the maximum number of hits per session, the maximum length of a session, and timeout rules. If the default values for these options do not match your session management values, you can change them (For more information, see Sessionizing policies—Defining when a session has ended.)
For more information, see the following topics:
•
Adding session identifier variables in cookies
•
Adding other types of session identifier variables
•
Prioritizing session identifiers
 

Adding session identifier variables in cookies

The easiest way to add session identifier variables found in cookies is to use the Discovery tool. For more information, see Sessionizing policies—Identifying user sessions.
To discover and add session identifier variables in cookies:
1
Click APM > Configure > Traffic Capture > Sessionizing Policies.
2
Expand Session Identifiers.
3
Click Discover.
The Session Identifiers Discovery dialog box appears, and begins displaying cookies found in live web traffic. You can sort the results by any column heading or use the search box to show only a subset of Cookies based on the cookie name.
4
When you see the cookies that you want to add, click Stop.
5
Select the check boxes beside the cookies you want to add.
6
Click Add.
The cookies appear as session identifier variables in the Session Identifiers table.

Adding other types of session identifier variables

For all other types of session identifier variables, you need to add them one at a time.
To add other types of session identifier variables:
1
Click APM > Configure > Traffic Capture > Sessionizing Policies.
2
Expand Session Identifiers.
3
Click Add.
4
In the Add Session Identifier dialog box, complete the options. For help with options, see Defining session identifiers.
5
Click Save.
The session identifier variable appears in the Session Identifiers table.

Prioritizing session identifiers

When you finish adding session identifier variables, you should prioritize the variables within the Session Identifiers table (using the Up and Down icons) so that the most significant variables appear at the top of the table. If a hit contains more than one registered session identifier, the first variable in the table that matches one of the session identifiers (searching from top to bottom) is used to track the current session. For more information, see Prioritizing session identifiers.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione