지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Stage 2: Run sequence analysis

If the hit belongs to a session, the Archiver evaluates sequence analyzer events and special events. A hit may belong to one session and zero or more sequences.
The analysis starts by evaluating events that can start sequences and end the session, that is, sequence events with an entry state of Not Started and the Stop Session Event special event. For each match, the Archiver runs the actions defined (if any) for the event. Typically, for a sequence event, this means starting a sequence, but it can also set the sequence status, set custom fields, and run scripts. If this hit matches an event that ends the session, the Stop Session flag is set as well as Stop Sequence flags for all active sequences within the session.
 
* 
NOTE: While an event can update a metric in memory, the metric is not stored in the database until the finalize sequence stage. For more information, see Stage 3: Finalize stopped sequences.
Next, the analysis evaluates active sequences and events that can end sequences. An active sequence is any sequence that has been started and has not yet been finalized, including sessions and sequence flagged as stopped. If there are no active sequences, the Archiver ends the sequence analysis. Otherwise, the Archiver evaluates sequence events with an entry state of Active and the Stop Sequence Event special event against all active sequences, including any sequences started in the previous phase. For each matching event, the Archiver runs the actions defined (if any) for the event. If an event ends a sequence, a Stop Sequence flag is set.
Finally, if there are sequences flagged as stopped in the previous two stages, the Archiver evaluates all sequence analyzer events where the entry state is Stopped. If any event conditions match the hit, the Archiver performs the actions associated with the event.
 
* 
NOTE: It is possible for a hit to start and stop a sequence during the sequence analysis stage. In this case, you get a sequence with one hit.
 
Figure 117. Run sequence analysis

Stage 3: Finalize stopped sequences

When the Stop Sequence flag is set for one or more sequences, the Archiver iterates through the list. For each stopped sequence, it sets the sequence analyzer status, sets storage policies and updates metrics based on the sequence analyzer status, and writes the sequence data to the database.
 
* 
NOTE: All other actions—such as, updating a custom field, executing a script, setting the status, starting or stopping the sequence, and stopping the session—are performed when the event conditions are evaluated during the sequence analysis stage.
Figure 118. Finalize stopped sequences

Stage 4: Finalize the session

When the Stop Session flag is set, the Archiver evaluates session analyzers. It sets a final analyzer status for each analyzer and runs the actions associated with that status. When the session analyzers are resolved, the Archiver determines the final session status and runs the actions associated with that status. After the session is resolved, the Archiver writes session details and any updated session data to the database.
Figure 119. Finalize the session
Sessions can also end due to a session timeout. The end-of-session steps are the same as those shown here.

Example of interdependent analyzers

Let's say you have four different login pages depending on the type of user or location of user (internal versus external, new versus existing). You want to track information about that user, such as the user’s name, that is specific to the login page they used. While the name may not be specific to the login page, how you extract the name from the hit details may be tied to the login page.
You can set up four hit analyzers to count the number of logins of each type and save the name of the user in a session custom field. However, you also want to count the total number of times a login page was accessed. You can set up a Final phase analyzer to count the number of times any of the four hit analyzers matched.
 
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택