• 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 105 - 108 of 328

×

Omitting sensitive content from the database

Sensitive data is stored in the database by default, even if it is not visible to anyone using Foglight. If you do not want to store sensitive data, you can define a hit analyzer with a Hit Storage Restriction policy of Do not store request or response content marked “Always Sensitive.” For more information, see Defining hit storage restrictions for hit analyzers.

Defining sensitive content expressions

When adding or editing sensitive content expressions, you can set the following options.

 

Table 34. Defining sensitive content expressions

Option	Setting the Option
Name	Specify a unique name for the security policy.
Description	Optional—summarize the purpose for this security policy.
Regular Expression	Click the browse button. In the Extraction Rule dialog box, specify the regular expression to be used to identify sensitive data. The expression may contain one or more sets of parentheses. Each set of parentheses is implicitly assigned a group number, from left to right, starting at 1. The entire expression is assigned group number 0. For an example expression, see Example: Matching and replacing credit card numbers.
Sensitive Groups	Specify group numbers from the regular expression separated by spaces. For example: 1 2 3
Replacement Text	To hide the text without replacing it, leave this box blank. To replace the text, specify the replacement text. Each group uses the same replacement text. For example: XXXX
Content	Specify whether this policy applies to Request content, Response content, or both Request and Response content.
Always Sensitive	Select to hide sensitive data from all users. Clear (default) to permit users with the Sensitive Data Viewer role to view this sensitive data. TIP: If you do not want to store sensitive data, see Omitting sensitive content from the database.

Example

Figure 52. Add Sensitive Content Expression dialog box

Managing pivots

Pivots are global categories. When you enable pivots, Foglight can store additional sets of data. You can enable global pivot categories for hits, endpoints, and/or web sites.

To apply pivot categories to data, you need to configure analyzers that generate metrics and specify which pivots to apply to those metrics.

For more information, see the following topics:

•	Understanding pivot categories

•	Enabling pivot categories and defining their membership

•	Enabling global pivots for web sites and endpoints

•	Working with metrics

Understanding pivot categories

The following tables summarize the pivot categories and when they may be useful.

Pivots

The general categories enable metrics basis on technology used or content type.

 

Table 35. Pivot categories

Pivot	Enables metrics by	Suitable For
Browser	The browser version used to access applications. Example: Firefox® 4.0, Internet Explorer® 9.0, etc.	All Environments
Browser Category	The browser used to access applications. Version number is ignored for this category. Example: Chrome™, Internet Explorer®, Safari®, etc.	All Environments
Operating System	The operating system from which users accessed applications. Example: Linux®, UNIX®, Windows® 7, Windows® XP, etc.	All Environments
Endpoint	The server endpoints that are hosting the monitored web site or applications. Endpoint category members are dynamically generated based on the monitored traffic. Example:192.168.1.1, 192.168.1.2, etc.	All Environments
Content Category	The ContentCategory field associated with each hit. Content categories are based on file extension, content-type, or other criteria: • Favicon—file ends with favicon.ico • Download—extensions: bat, csv, doc, eml, pdf, ppt, pwd, rtf, txt, wri, xls, zip, pkg, msi, gz, z, bz2, iso, and jar • Image—extensions: bmp, gif, ico, jpe, jpg, jpeg, png, tga, tif, and tiff • JavaScript—extension js • Media—extensions: aif, asf, avi, flv, m3u, mp3, mp4, mpa, mpeg, mp1, mpg, mpv, pls, rmi, ra, rm, rmj, rp, wav, wma, wmv, or xpl • StyleSheet—css • HTML—hasHtmlTag=true • Instrumentation—isInstrumentationHit=true • SOAP—has a SOAP operation name • HTMLFragment—response content-type contains html • JSON—response content-type contains json • XML—response content-type contains xml • Other—none of the above	All Environments

Location Pivots

The location pivots enable metrics by location.

 

Table 36. Location pivots

Pivot	Enables metrics by	Suitable For
City	The city from which users accessed monitored applications.	Internet
Country	The country from which users accessed monitored applications.	Internet
Region	The region from which users accessed monitored applications.	Internet
ISP	The Internet Service Provider (ISP) through which users accessed monitored applications.	Internet
Subnet	The subnetwork through which users accessed monitored applications. The category members match the list monitored subnets you defined. For more information, see Managing monitored subnets.	Intranet

•  이전
• Viewing Topics 105 - 108 of 328
• 다음 

이 문서 검색 모든 문서 검색

×

 지원 시작

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

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택