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

Configuring sequence analyzers

When adding, copying, or editing a sequence analyzer, you can define the following options.
 
* 
NOTE: When editing a sequence analyzer, click Properties to edit the Name, Description, Enabled, and Enable any Disabled Hit Analyzers used by the Sequence Analyzer options.
 
Table 54. Configuring sequence analyzers
Option
Setting the Option
Name
Specify a unique name.
Description
Optional—summarize the reason you created the analyzer, including the event actions it performs.
Enabled
Select this option to activate the analyzer as soon as you finish defining it.
Enable any Disabled Hit Analyzers used by this Sequence Analyzer
Select this option to activate­­ any disabled hit analyzers that are required by the sequence analyzer’s events.
Events
Define events for this sequence. Each event can have its own conditions and actions. If the events do not need to occur in order, select the Events not required to be sequential check box below the Events table. For more information, see Defining events for sequence analyzers.
Pivots
Optional—select categories for which you want to capture additional metrics. For more information, see Understanding pivots for analyzer metrics.
Storage
By default, the analyzer always saves data associated with a sequence, events, metric updates, and custom field updates. To change this behavior, see Defining storage options for sequence analyzers.

Introducing session analyzers

A session is a series of hits with the same session identifier that are submitted by the same browser client in the same visit to the site. A session analyzer is a collection of conditions and actions used to analyze completed sessions. Session analyzers give you a complete picture of the hits and sequences that occurred during a user session, providing a valuable context for your data.
Unlike hit analyzers and sequence analyzers, which evaluate hits and sequences as data is captured, session analyzers are evaluated after a session ends. A session ends when any of the following events occur:
•
A session times out
•
A sequence analyzer ends the session
•
A global Stop Session Event ends the session
Session analyzers are most powerful when used in conjunction with hit analyzers and/or sequence analyzers. For example, you can create session-scoped custom fields that are updated by hit analyzers and sequence analyzers, and then use the values of the custom fields as match conditions for a session analyzer.
For more information, see the following topics:
•
Tips for creating effective session analyzers
•
Configuring session analyzers

Tips for creating effective session analyzers

Keep in mind these tips for creating effective session analyzers:
•
Make the match conditions as specific as possible.
•
Avoid using the Script Output option in match conditions. Executing a script on all sessions can negatively affect performance.
•
When creating multiple conditions, if a condition uses regular expressions or scripting you should add it as the last condition. This allows simpler conditions to be evaluated first.

Configuring session analyzers

When adding, copying, or editing a session analyzer, you can define the following options.
 
* 
NOTE: When editing a session analyzer, click Properties to edit the Name, Description, and Enabled options.
 
Table 55. Configuring session analyzers
Option
Setting the Option
Name
Specify a unique name.
Description
Optional—summarize the reason you created the analyzer, including the action it performs.
Enabled
Select this option to activate the analyzer as soon as you finish defining it.
Match Conditions
Add conditions that need to be met before the analyzer’s actions run. Using match conditions, you can target the actions of an analyzer to specific types of web traffic. For more information, see Configuring conditions.
Metrics
Optional—add custom metrics, define pivots, and change how topology objects are created and named. For more information, see Working with metrics.
NOTE: Unlike hit analyzers, session analyzers always create standard metrics for the session; there is no option to avoid generating them.
Custom Fields
Optional—update the value of custom fields. For more information, see Updating custom fields.
Scripts
Optional—execute a script. For more information, see Executing scripts.
Error Conditions
Optional—add conditions that need to be met before changing the status of the completed session to Error. For more information, see Defining error and warning conditions.
Warning Conditions
Optional—add conditions that need to be met before changing the status of the completed session to Warning. For more information, see Defining error and warning conditions.
Options
By default, sessions that satisfy an analyzer’s match conditions are annotated with the analyzer’s name to support searching by analyzer. To change this behavior, see Setting searchability options for analyzers.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation