• 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 93 - 96 of 328

×

Managing custom fields

Custom fields are user-defined variables that are scoped for hits, sequences, or sessions. Using custom fields, you can attached additional information to individual hits, sequences, or sessions to make them easier to find when searching or to provide more context for the data when viewing results.

 

NOTE: To create a sequence-scoped custom field, you need to define it from a sequence analyzer. For more information, see Introducing sequence analyzers.

To define hit- and session-scoped custom fields, navigate to APM > Configure > Traffic Analysis, and expand Custom Fields.

Figure 42. Custom Fields view

The following table describes the data columns contained in the view.

 

Table 27. Managing custom fields

Column Name	Description
Name	The name of the custom field.
References	Analyzers that update the custom field.
Scope	Scope of the custom field: Hit, Sequence, or Session.
Type	Data type of the custom field: Text or Numeric.

In the Custom Fields view, you can perform the following tasks:

•	Predefined custom fields

•	Setting and updating the value of custom fields

•	Defining custom fields

Predefined custom fields

Foglight uses the following predefined custom fields to track web page views that provide boundary information about user sessions.

•	Entry Page—identifies the first HTML page visited by the user during a session.

•	Initial Referer—identifies the web page the user was visiting prior to starting a session.

•	Last Page Visited—identifies the last HTML page visited by the user during a session.

You may find it useful to review to the predefined custom fields in the software to get a sense of how they are defined and used.

Setting and updating the value of custom fields

To set and update the value custom fields, you need to define analyzers. For more information, see Updating custom fields.

Defining custom fields

When adding or editing a custom field, you can set the following options.

 

Table 28. Defining custom fields

Option	Setting the Option
Name	Specify a unique name for the custom field. NOTE: Custom fields with different scopes can have the same name.
Description	Optional—summarize the purpose for this custom field.
Scope	Set the scope for the custom field by selecting either Hit or Session. The custom field can be updated only by an analyzer with access to the selected scope. For example, a hit analyzer can update both kinds of custom fields, but a session analyzer can update only session custom fields.
Storage	Select an option that determines whether the value for the custom field is stored, and if so, how the custom field is treated in search results. When Scope=Session, you can select options that enable audit logging on the custom field. For a description of the options, see Storage option.
Storage Format	Set the storage format by selecting either Numeric or Text as the data type. When Numeric is selected, you can search using operators. For example, you can define a search that returns the value of the custom field “shopping cart value” when the value is greater than 100. You can also sort numeric data.
Value Assignment Mode1	Select an option that reflects how you want to handle values for the custom field. For a description of the options, see Value assignment mode option.
Separator1	Optional—when the Value Assignment Mode is set to one of the Append options, you can define a separator to be inserted between values. Typical separators are a comma or a colon, but you can use any character or combination of characters that suits your needs.
Update if blank1	Select to allow the custom field to be set to an empty (or blank) value. Clear (default) to ignore blank values, that is, an existing value is not replaced by a new value if the new value is blank.
Truncate large values	Select (default) to limit values to 2 KB (2,048 characters). Clear to store large values up to 64 KB.

---

1

These options can be overridden by analyzers that update the values of custom fields. For more information, see Defining custom field updates.

Storage option

You can select any of the following values for the Storage option. For session-scoped custom fields, you can select storage options that enable audit logging. With audit logging enabled, you can track the custom field when Foglight users view sessions.

 

Table 29. Storage option values

Storage Option	Description
Available only during traffic analysis	The value of the custom field is required while monitoring traffic, but does not need to be stored in the Archiver database. For example, an analyzer may use the value when matching conditions.
Show in search results	The custom field appears in search results.
Not in search results	The custom field does not appear in search results, but can be seen when examining details for a specific hit or session (depending on the scope).
First column in search results	The custom field appears in search results. When a hit or session has multiple custom fields associated with it, a custom field with this storage option is listed before other custom fields.
Show in search results (+ audit log)	Session scope only. The custom field appears in search results. The field is flagged for audit logging.
Not in search results (+ audit log)	Session scope only. The custom field does not appear in search results, but can be seen when examining details for a specific hit or session (depending on Scope). The field is flagged for audit logging.
First column in search results (+ audit log)	Session scope only. The custom field appears as the first column in a table of search results. The field is flagged for audit logging.

Value assignment mode option

You can select any of the following values for the Value Assignment Mode option. The Result column shows the final custom field value in the case where four assignments to the same field occur in the following sequence: 1, 2, 3, 2.

 

TIP: A custom field with its Value Assignment Mode set to “Increment value” behaves the same as a custom metric. For more information, see Creating custom metrics.

 

Table 30. Value assignment mode option

Value Assignment Mode	Description	Result
Append to value on each match	Concatenates values as they are encountered. If a Separator is defined, it is inserted between the values.	1232
Append to value on each match (if unique)	Similar to Append to value on each match, but only unique values are added.	123
Append to value on each match (if unique ignoring case)	Similar to Append to value on each match (if unique), but values like “foo” and “Foo” are considered identical.	123
Increment value	Increments a numeric value by the current value.	8
Reset value on each match	Sets the custom field to the current value.	2
Set value on first match if not already set	Sets the custom field to the first value and never updates it.	1

Example

Figure 43. Add Custom Field dialog box

•  이전
• Viewing Topics 93 - 96 of 328
• 다음 

이 문서 검색 모든 문서 검색

×

 지원 시작

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

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택