Chatee ahora con Soporte
Chat con el soporte

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

Understanding how sessionizing policies are applied

If you have only one sessionizing policy, Foglight uses the rules defined in that policy to correlate hits into user sessions. When you have more than one sessionizing policy, Foglight first checks the URL of the hit against the URL prefixes defined in non-default sessionizing policies. If there is a match, the matching sessionizing policy is applied to user sessions. If they do not match, the default sessionizing policy is used.
In either case, if the user session does not contain any of the session identifiers listed in the applicable sessionizing policy, the hits for that session are saved but do not contain session details.

Defining sessionizing policies

When adding, copying, or editing a sessionizing policy, you can set the following options.
 
Table 9. Defining sessionizing policies
Option
Setting the Option
Name
Specify a meaningful name for the policy.
Description
Optional—provide information about the sessionizing group. For example, describe which web applications this policy handles.
Type
Select the template that matches the web application. For more information, see Deciding when to add more sessionizing policies.
URL Prefixes
Non-default Sessionizing Policies Only—Optional—specify URL prefixes. In the monitored web traffic, when a hit occurs on a URL that matches the URL prefix, the hit is sessionized using this policy. For more information, see Sessionizing policies—Targeting sessionizing policies to URL prefixes.
Session Identifiers
Review the list of default session identifier variables included in the selected template Type. If your application uses different variables, you need to add them. For more information, see Sessionizing policies—Identifying user sessions.
Username Rules
Optional—if you want to attempt to capture user names and associate them with sessions, see Sessionizing policies—Associating user names with user sessions
Options
Options define when a session should be considered terminated. You can edit these options to suit your monitored web applications. For more information, see Sessionizing policies—Defining when a session has ended.
Example
Figure 14. Adding sessionizing policy example

Sessionizing policies—Identifying user sessions

Foglight checks the session identifier to determine when a user session starts and to capture and organize session details for all hits that share the same session identifier. If your web applications use session identifier variables that are not currently included in a sessionizing policy, you need to add them. If you do not specify them, Foglight cannot capture session details for hits containing the unidentified session identifier variables.
Typically, the session identifiers are located in cookies. Session identifiers can also be found in URLs (in the path, as a parameter, or as query variable), request fields (as POST parameters), and client IP addresses (used by some intranet applications). Each session requires a distinct session identifier.
To find out which session identifier variables are used by your in-house applications, you can ask your application developers. For session identifiers located in cookies, you can use the built-in Discovery tool to identify likely candidates. Finally, you can use a freely available tool, such as Mozilla® Web Developer Add-on, to help you identify the session identifier variables.
 
* 
NOTE: ASP .NET® applications typically append numbers to the session identifier prefix aspsessionid. When you include the aspsessionid variable in a sessionizing policy (default behavior), Foglight automatically sessionizes all cookies that begin with the string aspsessionid. You do not need to add each numeric variation on aspsessionid as a separate entry.
To specify session identifier variables, navigate to APM > Configure > Traffic Capture > Sessionizing Policies, and expand Session Identifiers.
Figure 15. Session Identifiers view
In the Session Identifiers view, you can perform the following tasks:
•
Discovering session identifier variables in cookies
•
Defining session identifiers
•
Prioritizing session identifiers

Discovering session identifier variables in cookies

When you run the Discovery tool from the Session Identifiers view, it creates a list of candidate cookies. Your monitored applications may or may not be using these cookies for session management. You need to select the ones used by your applications. The tool updates the list continuously until you stop the discovery process.
Figure 16. Session Identifiers Discovery dialog box
The following table summarizes the information in the Session Identifiers Discovery dialog box.
 
Table 10. Session Identifiers Discovery information
Column Name
Description
Cookies
A cookie that may contain a session identifier. The session identifier variable appears as the cookie name. For more information, see Discovering session identifier variables in cookies.
Hit Count
The number of times the cookie was found in the traffic.
TIP: Cookies with a low hit count are probably not being used as session identifiers. Look for high hit counts.
# Distinct Values
The number of unique values associated with the cookie that were found in the traffic.
Variation
A ranking that indicates the percentage of unique values associated with the cookie.
TIP: Session identifiers require a unique value for each unique user session, so look for cookies with a high variation percentage.
Sample Values
Real values associated with the cookie. Displays up to three of the most used values. Displays a maximum of ten characters per value.
TIP: If you know the pattern used for session identifier values in your application, you can confirm that the values in the Sample Values column conform to that pattern.
The most likely candidate cookies appear at the top of the discovery list with their check boxes selected by default. The Variation and Sample Values columns can be particularly helpful in determining the cookies that may contain session identifiers. When you stop the discovery process, you can order the results by the Variation column to identify cookies with a high percentage of unique values. You can use the sample values to confirm that you are looking at the right cookie for your application.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación