• United States (English)
• Brazil (Português)
• China (中文)
• France (Français)
• Germany (Deutsch)
• Italy (Italiano)
• Japan (日本語)
• Korea (한국어)
• Mexico (Español)

• 로그인
• 지원 계정 생성

무료 트라이얼

• 포털 전문가 되기
• 인쇄
• 내 다운로드 ()

• 지원
• 기술 문서
• Foglight APM for Real User Experience 5.9.9
• Foglight APM for Real User Experience 5.9.9 - Administration and Configuration Guide

Foglight APM for Real User Experience 5.9.9 - Administration and Configuration Guide

콘텐츠 탐색  

Getting started

Understanding how Foglight captures real user data

Software components

Foglight Management Server Archiver Sniffer Browser instrumentation Relayer Archiver databases

Simplest monitoring solution Foglight APM Appliances and real user data

Logging in to Foglight Finding the Foglight APM dashboards Registering Sniffers and Archivers

Creating Capture Groups Registering Sniffers Registering Archivers

Verifying that you are capturing data Resolving gaps in traffic capture

Adding missing ports Capturing complete user sessions

Adding session identifier variables in cookies Adding other types of session identifier variables Prioritizing session identifiers

Monitoring secure web traffic

Step 1: Registering secure ports Step 2: Specifying monitored IP addresses Step 3: Providing private keys Step 4: Associating ports and keys with monitored IP addresses

Verifying configuration changes

Making your data more meaningful Focusing on selected web applications and web sites

Monitoring selected IP addresses only Excluding subnets

Assigning user roles Next steps

Configuring traffic capture

Managing Sniffers

Defining Sniffers Testing Sniffer communications

Managing Archivers

Defining Archivers Testing Archiver communications Setting database shard span and retention periods

Managing capture groups

Planning capture groups Defining capture groups Assigning Sniffers and Archivers to capture groups Testing capture group communications

Managing sessionizing policies

Understanding the default sessionizing policy Deciding when to add more sessionizing policies Understanding how sessionizing policies are applied Defining sessionizing policies Sessionizing policies—Identifying user sessions

Discovering session identifier variables in cookies Identifying session identifiers in URL paths Defining session identifiers Prioritizing session identifiers

Sessionizing policies—Associating user names with user sessions

Discovering user names Capturing user names in a single sign-on environment Identifying user names in XML Understanding missing user names Defining username rules

Sessionizing policies—Targeting sessionizing policies to URL prefixes

Discovering URL prefixes Defining URL prefixes

Sessionizing policies—Defining when a session has ended

Managing monitored ports

Discovering ports Defining monitored ports

Managing monitored IP addresses

Discovering IP addresses Defining monitored IP addresses Displaying host names instead of IP addresses Monitoring secure (HTTPS) web traffic

Managing monitored subnets

Discovering subnets Defining monitored subnets

Managing identifiers for virtual addressing schemes

Defining identifiers Capturing originating client IP addresses Capturing server IP addresses Capturing host names

Managing private keys

Managing local private keys Managing HSM private keys

Managing web services and SOAP operations

Creating web services automatically from WSDL files Defining web services and SOAP operations

Configuring traffic analysis

Managing custom fields

Predefined custom fields Setting and updating the value of custom fields Defining custom fields

Managing custom metrics

Editing custom metrics

Managing security policies for sensitive hit details

Hiding or replacing sensitive hit details Omitting sensitive hit details from the database Defining sensitive hit details

Managing security policies for sensitive content

Hiding or replacing sensitive content Omitting sensitive content from the database Defining sensitive content expressions

Managing pivots

Understanding pivot categories Enabling pivot categories and defining their membership Enabling global pivots for web sites and endpoints

Configuring advanced options Managing domain rules

Discovering aliases Defining domain rules

Storing large hit details

Defining large hit details

Managing special events

Defining global stop criteria for sessions Defining global stop criteria for sequences Defining special events

Troubleshooting improperly classified URLs

Defining URL classifiers

Managing user agent rules

Defining new user agent rules Setting the execution order for rule files

Defining additional parsed response types Defining captured request body types Modifying traffic analysis options Managing scripts

Before you begin Determining requirements

Select an appropriate API Define output variables Decide when to execute the script Decide how many uncaught failures are allowed

Creating scripts Testing scripts Defining scripts

Configuring analyzers

Introducing hit analyzers

Reviewing default hit analyzers Tips for creating effective hit analyzers Configuring hit analyzers

Introducing sequence analyzers

Configuring sequence analyzers

Introducing session analyzers

Tips for creating effective session analyzers Configuring session analyzers

Summary of options by analyzer type Configuring conditions

Defining match conditions Defining error and warning conditions Grouping multiple conditions Defining conditions

Working with metrics

Understanding standard metrics Creating custom metrics Changing the name of metric topology objects Understanding pivots for analyzer metrics Publishing hit metrics for use in the Geographical Perspective dashboard Defining service level agreement thresholds

Updating custom fields

Updating the value of custom fields Creating new custom fields Defining custom field updates

Executing scripts

Executing scripts Creating new scripts

Defining storage policies

Defining hit storage restrictions for hit analyzers Defining storage options for sequence analyzers

Setting searchability options for analyzers

Defining options for hit analyzers Defining options for session analyzers

Defining events for sequence analyzers

Understanding sequence states Defining event conditions

Defining event conditions

Recording the order of triggered events Defining sequence events

Capturing traffic outside the network

Deciding when to add browser instrumentation Introducing the instrumentation components Configuring an instrumented monitoring solution Verifying instrumentation payloads are received Viewing metrics collected by instrumentation

Configuring advanced options

Configuring internal settings

Archiver query settings Replay settings Metadata settings

Substituting static page elements

Defining static page elements

Excluding subnets from data collection

Defining subnet filters

Integrating Foglight APM with other products

Integrating with CA SiteMinder

Adding SiteMinder Server definitions in Foglight Registering Foglight as a SiteMinder agent Adding SiteMinder to a sessionizing policy

Integrating with SafeNet Hardware Security Modules

Planning a Foglight–HSM integration Registering HSM servers in Foglight Generating SafeNet HSM client certificates Associating HSM keys with monitored IP addresses

Maintaining and troubleshooting

Checking the health of Foglight APM Appliances

Investigating issues with appliance health Summary of Appliance Health views

Managing configuration changes

Reviewing change versions Understanding configuration modules and objects Exporting configuration modules and objects Restoring and importing configurations Reviewing warnings

Creating support bundles Updating appliance software Restarting the embedded Agent Manager

Appendix: Building regular expressions in Foglight

What is a regular expression? Where can I find regular expressions? Regular expression basics

Building a simple pattern Building a pattern that matches a specific character Building a pattern that matches multiple characters Using advanced quantifiers Using special characters and regular expression flags Grouping elements in a pattern Additional information

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

• Viewing Topics 177 - 180 of 328

×

Defining event conditions

Event conditions enable you to tie event actions to things like hit analyzers being triggered and the value of sequence-level and session-level metrics and custom fields.

 

IMPORTANT: Event conditions are evaluated only when the sequence is in the Sequence Entry State specified for the event.

Figure 92. Defining event conditions

You can add, edit, and group event conditions in the same way as other conditions. For more information, see Configuring conditions.

Defining event conditions

When adding or editing event conditions, you can set the following options.

 

Table 73. Defining event conditions

Option	Setting the Option
Type	Select the condition type. See Type option for sequence events. NOTE: The other available fields change depending on the selected Type.
<Type Detail>	The title of this field changes, depending on the option selected in the Type field. For example, you may be able to select a hit analyzer, a metric, or a custom field.
With Status	Optional—if available, you can specify an analyzer’s status, such as Error. In this case, the event condition matches only when a hit satisfies both the condition type and the analyzer status.
not	If available, select to cause an operator to perform its opposite action. For example, you can change “equal to” to “not equal to” by selecting this check box.
Operator	If available, select an operator that performs the type of match you want to make. Only the operators that make sense for a selected Type are available. For more information, see Operators.
Value	If available, specify a numeric or text value (as appropriate).
Extraction Expression	Optional—if available, you can create an extraction expression. For more information, see Defining extraction expressions.

Type option for sequence events

You can select any of the following values for the Type option.

 

NOTE: When reviewing the event 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 an analyzer status. To match the condition, a hit must trigger the hit analyzer AND have the specified analyzer status.

 

Table 74. Type option for sequence events

Event Condition Type	Description
Always True	Any hit matches this event condition. When a sequence analyzer has an entry state of Not Started, you can use this event condition type to trigger an action that starts a sequence when the first hit is registered.
Hit Analyzer Match	This is the most commonly used condition type. Hits that trigger the specified hit analyzer also trigger the sequence event.
Hit Analyzer Ordering	You specify 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. IMPORTANT: 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.
Post Sequence: Stopped by Global Stop Condition	Global stop conditions happen under the following circumstances: • A global stop-sequence event occurred • A global stop-session event occurred • The maximum session hit count is reached • The maximum session duration is reached • The “long session” timeout is exceeded • The “short session” timeout is exceeded You can use this condition type to annotate the stopped sequence or perform other actions.
Post Sequence: Stopped by Sequence Stop Condition	In most cases, the event that stopped the sequence can also handle other post-sequence event actions. However, if more than one sequence event can potentially stop the sequence, you can create an event that uses this condition type and then define post-sequence actions in one place, rather than in each individual sequence event.
Sequence/Session Custom Field	You specify a sequence or session custom field, an operator, and a value. The condition matches when the value of the custom field is updated to the specified value. • For session custom fields, the value may be updated by a hit analyzer or this sequence analyzer. • For sequence custom fields, the value of the custom field needs to be updated by the sequence analyzer to which the event belongs. This allows you to reference a sequence custom field set by one event in the match conditions of a later event.
Sequence/Session Duration	You specify 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.
Sequence/Session Hit Counts	You specify the type of hits that should be counted, an operator, and the hit count. Hit count is calculated from the start of the sequence or session. The condition matches when the hit count for the sequence or session matches the specified hit count.
Sequence/Session Hit Counts by Hit Analyzer	You specify 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 event 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 action run.

Recording the order of triggered events

You need to assign labels to your events so that Foglight can succinctly record the order in which events were triggered during a sequence. For more information, see Defining sequence events.

For example, consider a sequence analyzer that has a start event, three intermediate steps, and a stop event, and uses the labels S, 1, 2, 3, and F, respectively for these events. When viewing a list of sequences, the labels are used to display the order in which the events occurred, such as Sequence 1 = S,1,2,F (start, event1, event2, stop) or Sequence 2 = S,3,2,1,F (start, event3, event2, event1, stop).

If an event is triggered more than once (requires that the event’s Allow Multiples check box is selected), the event label will appear more than once in the sequence record. Using the preceding example, if all the intermediate events allowed multiple executions, you could conceivably see a session record like this: S,1,1,2,2,3,3,1,2,3,3,2,1,F.

Defining sequence events

When adding or editing an event, you can set the following options.

 

Table 75. Defining sequence events

Option	Setting the Option
Name	Specify a unique name.
Label	Specify a label for the event. Labels can be one or two characters. Labels are used to record the order in which events are triggered within a sequence. For more information, see Recording the order of triggered events.
Description	Optional—summarize the reason you created the event, including the actions it performs.
Sequence Entry State	Select the sequence state (Not Started, Active, Stopped) that needs to exist before the event conditions are evaluated. For more information, see Understanding sequence states.
Allow Multiples	Select to permit an event to trigger more than once during a sequence. Clear (default) to restrict the event so that its actions can be run only once in a sequence. In the latter case, a flag is set to prevent the event from being evaluated again during the current sequence.
Optional	When available, select to specify that the event does not need to be triggered in the sequence. Clear (default) to require the event to be triggered before the sequence ends. NOTE: Only available when the Events are not required to be sequential check box is cleared on the Sequence Analyzer - Edit page AND the event’s Sequence Entry State=Active.
Event Conditions	Add conditions that need to be met before the event’s actions run. For more information, see Defining event conditions.
Event Actions	By default, the sequence status and the sequence state are not changed when the event actions run. To change this behavior, see Event actions options.
Sequence Metrics	Optional—for the sequence, add custom metrics and change how topology objects are created and named. All metrics created for the sequence inherit the pivots specified for the sequence. For more information, see Working with metrics. NOTE: Unlike hit analyzers, sequence analyzers always create standard metrics for the sequence; there is no option to avoid generating them.
Sequence Event Metrics	Optional—for the event, add custom metrics and change how topology objects are created and named. All metrics created for the event inherit the pivots specified for the sequence. For more information, see Working with metrics. NOTE: Unlike hit analyzers, sequence analyzers always create standard metrics for sequence events; 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.

Event actions options

By default, the sequence status and the sequence state are not changed when the event actions run.

Set Sequence Status option

By default, all sequences have a default status of OK. If you create a sequence analyzer to detect problems within a series of steps, you can use the Set Sequence Status event action to change the sequence status to Warning or Error.

Start/Stop Actions option

By default, an event does not change the state of the sequence. For more information, see Understanding sequence states.

 

NOTE: Before choosing an event action that stops a session, you need to be sure that the web application ends the session under the conditions defined in the event conditions. For example, you can stop a session when an end user clicks a logout link, rather than waiting for the session to eventually time out.

You can select any of the following values for the Start/Stop Actions option.

 

Table 76. Start/Stop Actions option

Start/Stop Actions	Description	New Sequence State
No Change (default)	Leaves the sequence state in its current state.	Unchanged
Start Sequence	Starts a new sequence. By default, the first event you create for a sequence has the Start Sequence action assigned to it.	Active
Stop Sequence	Stops the current sequence.	Stopped
Start and Stop Sequence	Starts a sequence and immediately stops it. This can be used to identify activities such as repeated failed logins.	Stopped
Stop Session	Stops the sequence and the session.	Stopped
Start Sequence and Stop Session	Starts a sequence, immediately stops it, and then ends the session.	Stopped

 

•  이전
• Viewing Topics 177 - 180 of 328
• 다음 

이 문서 검색 모든 문서 검색

×

 지원 시작

계열사 지원 사이트에서 Quest *제품*에 대한 온라인 지원 도움말을 볼 수 있습니다. 올바른 *제품* 지원 콘텐츠 및 지원에 연결하려면 계속을 클릭하십시오.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택