Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Setting the execution order for rule files

User agent rules are order-dependent, both within a file and across multiple files. When two files transform the same hit detail, the first file wins. When you finish adding new agent rules files, ensure that the order of the files in the table reflects the order in which you want the rules applied. Use the Up and Down icons to control the order of the other files.

Defining additional parsed response types

For response content, Foglight captures and stores all response content, but only response content with a content type containing one of the following patterns undergoes processing for traffic analysis:
•
text/.*   (includes content types such as text/html, text/plain, and text/xml)
•
.*javascript.*
You can specify additional text-based content types for traffic analysis.
 
* 
NOTE: Binary content types such as image, are automatically captured and stored, but are not processed for traffic analysis.
Processing includes:
•
Parsing and storing response content
•
Indexing content for keyword search (if enabled)
•
Applying sensitive content rules. For more information, see Managing security policies for sensitive content
•
Applying hit and sequence analyzers. For more information, see Configuring analyzers.
To define parsed response types, navigate to APM > Configure > Traffic Analysis, select Advanced Options, and expand Additional Parsed Response Types.
Figure 67. Additional Parsed Response Types view
From the Additional Parsed Response Types view, you can add, edit, and remove content types using the standard controls. When adding or editing response types to parse, specify the value of the content type in the Name box.
Example
Figure 68. Additional Parsed Response Types dialog box

Defining captured request body types

Request body content is treated a little differently than response content. Foglight captures and parses text-based POST data sent with either of the following content types:
•
application/x-www-form-urlencoded
•
multipart/form-data
The parsed content is stored as request fields. Unlike response content, the raw request body content is discarded. These request fields are not keyword indexed or subjected to sensitive content rules, but are available for traffic analysis purposes.
To define request body types for capture, navigate to APM > Configure > Traffic Analysis, select Advanced Options, and expand Captured Request Body Types.
Figure 69. Captured Request Body Types view
From the Captured Request Body Types view, you can add, edit, and remove content types using the standard controls. When adding or editing a capture request body type, specify a POST data content type (text-based only) in the Name box.
Example
Figure 70. Captured Request Body Types dialog box

Modifying traffic analysis options

The traffic analysis options enable you to modify the maximum size for content capture and hit details. To modify traffic analysis options, navigate to APM > Configure > Traffic Analysis, click Advanced Options, and expand Traffic Analysis Options.
Figure 71. Traffic Analysis Options view
The following table describes all the options. Remember to save after making changes.
 
Table 46. Modifying traffic analysis options
Option
Setting the Option
Maximum Request Size
Specify the largest request to be captured. The maximum size is 1,048,576 Bytes (1 MB). Requests that exceed the specified size are truncated.
Maximum Response Size
Specify the largest response to be captured. The maximum size is 1,048,576 Bytes (1 MB). Responses that exceed the specified size are truncated.
Maximum Hit Detail Size
Specify the size of the largest hit detail to be captured. The maximum size is 65,535 bytes. Hit details that exceed the specified size are truncated. For more information, see Storing large hit details.
NOTE: Web browsers may encode some characters before sending them to the web server. Encoded characters require three bytes rather than one byte. If hit details might contain encoded characters, specify a maximum size equal to the largest hit detail size * 3. For example, the default value of 6,144 bytes was determined by multiplying the default hit detail size of 2 KB (that is, 2048 bytes) by 3.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation