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

Testing capture group communications

After you create the capture groups for your environment, you can click Test to verify that the Sniffers and Archivers are communicating. If any errors appear, you may need to edit an Archiver definition or a Sniffer definition.
Figure 11. Testing capture group communication

Managing sessionizing policies

Sessionizing is the process by which Foglight correlates hits in the monitored web traffic with real user sessions. Sessionizing policies describe how user sessions are identified and managed within your monitored web applications.
You need to modify the default sessionizing policy (or create a new sessionizing policy) to include session identifiers for your monitored web applications. For example, many applications use cookies containing session identifiers to track user sessions. In the sessionizing policy, you can also 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. Typically, your sessionizing policies should align closely with the session management techniques employed by your applications.
 
* 
IMPORTANT: To collect accurate and complete session details, ensure that your sessionizing policies mirror your application session management policies. Hits containing session identifiers other than those identified in the sessionizing policy are still captured and stored, but they do not belong to a session and do not have any session details associated with them.
To define and manage sessionizing policies, navigate to APM > Configure > Traffic Capture > Sessionizing Policies.
Figure 12. Sessionizing Policy dashboard
In the Sessionizing Policy dashboard, you can perform the following tasks:
•
Defining sessionizing policies
For more information, see the following topics:
•
Understanding the default sessionizing policy
•
Deciding when to add more sessionizing policies
•
Understanding how sessionizing policies are applied
•
Sessionizing policies—Identifying user sessions
•
Sessionizing policies—Associating user names with user sessions
•
Sessionizing policies—Targeting sessionizing policies to URL prefixes
•
Sessionizing policies—Defining when a session has ended

Understanding the default sessionizing policy

The default sessionizing policy contains the common session identifier variables used by major programming languages to identify user sessions. By default, Foglight looks for session identifiers under the following 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
In many cases, the default policy is all you need. For more information, see Deciding when to add more sessionizing policies.
Figure 13. Edit Sessionizing Policy dashboard
You can edit the default sessionizing policy to add or remove session identifiers or to change the options to suit your environment. You can also add rules to associate user names with user sessions. The URL Prefix view is reserved for non-default sessionizing policies.

Deciding when to add more sessionizing policies

When web applications use different session identifiers to identify user sessions, you need to add the session identifiers to a sessionizing policy. Whether you create a new sessionizing policy or update the default sessionizing policy depends on the type of web application you want to monitor.
If you want to monitor one of the following applications, you need to create a new policy:
•
Microsoft® SharePoint®
•
Oracle® PeopleSoft
•
Oracle® Siebel
For all other types of applications, you should modify the default policy to add the session identifiers required by your web sites and web applications. If you discover a conflict later on, you can create a new policy to handle just the conflict situation.
Conflicts are unlikely, but they may occur. For example, if most of a site uses sessionid to pass identifiers, but a small section of the site uses sessionid for an entirely different purpose, you need to create a new sessionizing policy for the part of the site that is non-standard.
When defining an additional sessionizing policy, Foglight prompts you to select the type of application you want to monitor. It uses this information to populate the Add Sessionizing Policy dashboard with session identifiers and other settings appropriate for the selected type of application. The following table summarizes the sessionizing policy templates:
 
Table 8. When you need to add sessionizing policies
Template
Description
Other
This is a blank template with no default settings.
PeopleSoft
Contains default session identifiers and username rules appropriate for Oracle® PeopleSoft applications.
SharePoint
Contains default session identifiers and username rules appropriate for Microsoft® SharePoint® applications.
Siebel
Contains default session identifiers and username rules appropriate for Oracle® Siebel applications.
You can modify settings as required to suit your environment. You can also target the sessionizing policy to a specific domain name or extended URL prefix. For more information, see Defining sessionizing policies.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione