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

Managing special events

Special events are global events—they can stop data collection for any in-progress session or sequence that meets the conditions defined in the special event. In a fresh installation, special events are purposely undefined. If desired, you can specify conditions required to trigger the special events. You can also specify other actions to occur when a special event stops a session or sequence.
 
* 
IMPORTANT: If someone else has defined special events for you, do not remove or edit these events until you understand all implications of the change.
To manage special events, navigate to APM > Configure > Traffic Analysis, select Advanced Options, and expand Special Events.
Figure 62. Special Events view
From the Special Events view, you can edit the action performed by a special event. You can also remove a special event using the standard control.
For more information, see the following topics:
•
Defining global stop criteria for sessions
•
Defining global stop criteria for sequences
•
Defining special events

Defining global stop criteria for sessions

While the Stop Session Event remains undefined, sessions can end in one of two ways: by a sequence analyzer event’s Stop Session action or by a session timeout. The rules for determining when a session times out are set in the sessionizing policy options. For more information, see Sessionizing policies—Defining when a session has ended.
You can define the Stop Session Event to trigger on one or more event conditions. This enables you to stop data collection on a session when something happens, such as an end user logs out, rather than waiting for the end user’s session to time out.
As with all analyzer conditions, these event conditions can be grouped by the boolean operators AND and OR. For more information, see Grouping multiple conditions.
For example, the following image shows a defined Stop Session Event triggered when an end user logs out.
Figure 63. Edit Special Event Page example

Defining global stop criteria for sequences

This event works much like the Stop Session Event, but rather than closing a session, it stops any active sequences within a session. To consider activating this special event, you would need some event that is common to all or many active sequences in your environment. For example, if you have multiple sequence analyzers related to a shopping cart, you could define a Stop Sequence Event when an Empty Cart hit analyzer matches.

Defining special events

When defining special events, you can set the following options.
 
Table 41. Defining special events
Option
Setting the Option
Description
Optional—summarize the conditions used in this event and the actions it performs.
Event Conditions
You can add, edit, and group special event conditions in the same way as analyzer conditions. For more information, see Configuring conditions.
To add events, click Add. In the Add Event Condition dialog box, you can add event conditions that are very similar to those available for sequence event conditions. For a description of the types of conditions you can create, see Type option for special event conditions (following this table).
Custom Fields
Optional—update the values of session-scoped custom fields. For more information, see Updating custom fields.
Scripts
Optional—execute a script. For more information, see Executing scripts.
For examples, see Defining global stop criteria for sessions and Defining global stop criteria for sequences.
Type option for special event conditions
When defining event conditions for a special event, you can select any of the following values for the Type option in the Add/Edit Event Condition dialog box.
 
* 
NOTE: When reviewing the condition types, keep in mind the following:
•
Some types are listed as “Sequence/Session.” In the software, there are two separate condition types, one for each.
•
For the “Hit Analyzer” conditions, you can optionally specify a hit status. To match the condition, a hit must trigger the hit analyzer AND have the specified hit status.
 
Table 42. Type option for special event conditions
Type Option
Description
Hit Analyzer Match
Hits that trigger the specified hit analyzer also trigger the event.
Hit Analyzer Ordering
Requires two hit analyzers and an operator. The operator defines a relationship between the two hit analyzers based on the timestamps of the hits that trigger the hit analyzers. For example, you can create the following set of conditions to compare the hit analyzers Foo and Bar within a given sequence: if Bar has triggered AND if Foo has triggered AND if the Bar timestamp is less than the Foo timestamp, then the event actions are triggered.
NOTE: If a hit analyzer matches more than one hit in a sequence, the hit analyzer timestamp reflects the most recent match. This may lead to confusing results if you were not expecting multiple matches.
Script Output
Requires a script, an operator, and an output value. The condition matches when the script’s output value matches the value you specify.
Session Custom Field
Requires a session custom field, an operator, and a value. The condition matches when the value of the custom field is updated to the specified value. The value may be updated by a hit, sequence, or session analyzer.
Session/Sequence Duration
Requires a metric, an operator, and a duration in seconds. The condition matches when the metric’s value matches the specified duration. Duration is calculated from the start of the sequence or from the first hit in the session.
Session/Sequence
Hit Counts
Requires the type of hits that should be counted, an operator, and the hit count. The condition matches when the hit count for the sequence or session matches the specified hit count. Hit count is calculated from the start of the sequence or session.
Session/Sequence
Hit Counts by Hit Analyzer
Requires a hit analyzer and a hit count for a given sequence or session. The condition matches when the hit analyzer is triggered the specified number of times. You can use this type of condition to identify recurring behavior. For example, you can create a condition where hits that trigger the hit analyzer Failed Login Page are counted. When the count reaches the specified hit count, let’s say five failed login attempts, the event’s actions run.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation