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

Defining username rules

When adding or editing username rules, you can set the following options.
 
* 
NOTE: Recall that in URLs, characters that fall outside the ASCII character set are encoded. For example, a space is encoded as %20 and the dollar sign ($) is encoded as %24. When specifying variable names found in a URL, use the encoded value for these characters. For a list of encodings, see http://www.w3schools.com/TAGS/ref_urlencode.asp.
 
Table 13. Defining username rules
Option
Setting the Option
Name
Specify the name of the variable used to parse user names.
•
When Type=Request Field, specify the variable name to match in the POST request field or form. Encode all non-ASCII characters (see the preceding note).
•
When Type=XML Variable, include the context for the variable, such as body.variablename. For more information, see Identifying user names in XML.
•
When Type=NTLM or Type=SiteMinder Cookie, see Capturing user names in a single sign-on environment.
Description
Optional—provide more information about the variable. For example, you can include the name of the application that uses the variable.
Type
Select the type of variable you are defining. The most commonly-used type is Request Field, which is the type used for matching variable names found in POST request fields.
Regular Expression
Optional—specify a pattern to match and extract user names from a field that contains extra information. To test your expression, click to open the Extraction Rule dialog box. For more information, see Defining extraction expressions.
SiteMinder Servers
If your environment includes CA SiteMinder Servers, select whether you want to apply this rule to all servers (default) or to a selected server (when your servers use different variables for user names). For more information, see Capturing user names in a single sign-on environment.

Sessionizing policies—Targeting sessionizing policies to URL prefixes

You can target a non-default sessionizing policy to domain names with or without subdirectories. For example, if you want to monitor all hits associated with your web site, you can create a URL prefix policy with the site’s domain name, such as quest.com. You then only need to add the session identifier variables and user name variables relevant to this domain.
 
* 
IMPORTANT: You cannot add URL prefixes to the default sessionizing policy. The default policy applies to all web traffic that does not match the non-default sessionizing policies.
To specify URL prefixes, navigate to APM > Configure > Traffic Capture > Sessionizing Policies, and expand URL Prefixes.
Figure 22. URL Prefixes view
In the URL Prefixes view, you can perform the following tasks:
•
Discovering URL prefixes
•
Defining URL prefixes

Discovering URL prefixes

When you run the Discovery tool from the URL Prefixes view, it creates a list of URL prefixes accessed within the monitored environment. The tool updates the list continuously until you stop the discovery process.
Figure 23. URL Prefixes Discovery dialog box

Defining URL prefixes

When adding or editing URL prefixes, you can set the following options.
 
Table 14. Defining URL prefixes
Option
Setting the Option
URL Prefix
Specify the domain name—with or without subdirectories—that you want to monitor, omitting the server name (such as ftp or www).
Example
Figure 24. Add URL Prefix dialog box
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione