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

• Sign In
• Create Support Account

FREE TRIALS

• Become a portal pro
• Print
• My Downloads ()

• Support
• Technical Documentation
• 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

Table of Contents  

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 189 - 192 of 328

×

Archiver query settings

To modify settings, navigate to APM > Configure Advanced Options > Settings. The first few Archiver Query settings affect interactions between Archivers and the management server. The remaining settings affect the time taken for searches on the distributed Archiver database.

The following table describes all the options. Remember to save after making changes.

 

Table 77. Archiver query settings

Option	Setting the Option
Network Keep Alive	Sets how long server network connections stay connected to Archivers with no active communication. Valid values are 10,000 to 100,000,000 milliseconds.
Hit Search Result Limit	Sets the maximum number of hits that can be returned from a single Archiver in response to a single hit search. Default is 200 per Archiver searched. For example, in an installation with three Archivers and a result limit of 200 hits per search, up to 600 hits may be returned in one search. Value must be an integer. Larger values may increase the time required to complete a search.
Session Search Result Limit	Sets the maximum number of sessions that can be returned from a single Archiver in response to a single session search. Default is 200 per Archiver searched. For example, in an installation with three Archivers and a result limit of 200 sessions per search, up to 600 sessions may be returned in one search. Larger values may increase the time required to complete a search.
Sequence Search Result Limit	Sets the maximum number of sequences that can be returned from a single Archiver in response to a single sequence search. Default is 200 per Archiver searched. For example, in an installation with three Archivers and a result limit of 200 sequences per search, up to 600 sequences may be returned in one search. Larger values may increase the time required to complete a search.
Search Time Range Limit	Sets the maximum time range that can be selected for a search. All Search dialog boxes inherit this setting. For example, if you select last hour for this setting, anyone who runs a search can select only time ranges from last minute to last hour in the Search dialog boxes. Larger values may increase the time required to complete a search.

Replay settings

To modify settings, navigate to APM > Configure Advanced Options > Settings. Replay settings affect how user sessions are replayed.

Figure 93. Replay settings

The following table describes all the options. Remember to save after making changes.

 

Table 78. Replay settings options

Option	Setting the Option
Page Element Path Endings	Specifies a comma-separated list of URL path endings (no spaces) that should always be treated as elements of a page. A URL path ending can be a file extension or any text that ends a URL. Any query parameters appended to path endings are ignored. Example: .gif,.jpg,.png,.ico,.pdf,.swf,.js,.css,          .xml,.xsl,/dynamicallyGeneratedImage
Rewrite JavaScript	Select Yes to enable JavaScript when replaying captured HTML hits. Because JavaScript may sometimes cause problems during replay, the default is No.
Disable JavaScript Functions	Disables JavaScript functions that may interfere with replay. To list a function that should not run during replay, click Add and specify the name of the JavaScript function.
Treat JavaScript Variable Names as Anonymous Functions	Select (default) to detect all variables which are instances of functions and disable them. Clear to enable these functions.
Disable Google Analytics During Replay	Select (default) to disable callbacks from Google® Analytics to avoid sending duplicate data to Google Analytics. Clear to enable Google Analytics during replay.
Less Strict Replay with User Input (Forms)	Select Yes (default) to improve the replay of user input data when JavaScript is used to manipulate form field values. Select No if JavaScript is never used.
Less Strict Replay with User Input (Links)	Select Yes to attempt to improve the replay of user clicked links when hit referers are not present. Default is No.
Display Mode	Specifies the content to display when first opening the Replay browser. Default is Response Replay. For a description of each of the available values, see Values for Display Mode (following this table).
User Input Highlighting - Primary Color	Sets the primary color to be used when highlighting user input. You can specify any valid CSS color value, such as #FC0, RGB(255,204,0), or lime.
User Input Highlight - Secondary	Sets the secondary color to be used when highlighting user input. This color is used for highlighting specific items, such as the option a user selected from a pull-down menu. You can specify any valid CSS color value, such as #FF0, RGB(255,255,0), or yellow.
Use Elements from Unrelated Sessions	Select Yes to use page elements, such as images and stylesheets, from unrelated sessions when replaying sessions. Default is No. NOTE: Enabling this option may cause unexpected results if more than one element shares the same file name. You may prefer to have the Replay browser substitute locally-stored static page elements. For more information, see Substituting static page elements.
When Element Content not Available	Specifies the action to take when page elements, such as images, JavaScript, and CSS files, are not available for the session being replayed and cannot be found in static page elements (if defined) or in other sessions (when the Use Elements from Unrelated Sessions option is enabled). The following actions are available: • Redirect to ‘live’ web server (default)—retrieves page elements from the live web server. Select this option only when the live server is reachable from the Replay browser and the server does not require a login to reach the page elements. This option may cause unexpected results if more than one element in the live traffic share the same file name. • Send 404 Response—sends a 404 error code to the Replay browser. For missing images, a broken image icon is displayed. For missing style sheets or JavaScript, the HTML page may not render correctly.

Values for Display Mode

 

Table 79. Values for Display Mode

Display Mode	Description
Response Replay	Displays an approximation of the HTTP hit’s response content as the end user originally viewed it. If the response content is not available for any of the page elements (for example, if the browser used a cached image), the Replay browser refers to the Use Elements from Unrelated Sessions and When Element Content not Available options for next steps.
Response Replay (Show Submitted Input)	Displays hits similarly to Response Replay mode, except that the final values for any form fields where user entered data are populated with the data that was submitted to the web server. Any links or submit buttons clicked to move to the next page are highlighted as well. Submitted user input cannot be shown for forms or links that are manipulated by JavaScript on the client browser, including actions that are purely client-side.
Response Source	Displays the source code that was captured for HTML hits. Useful for debugging dynamic web applications. If a selected hit is not an HTML page, the result is equivalent to that displayed using the Response Replay mode.
Hit Details	Displays network and HTTP details about the selected hit, including response time, hit analysis, request and response fields, and headers, cookies, and Archiver details.
Request Content Body	Displays as text the HTTP request message body of the hits that use POST as the HTTP request method. Useful for viewing data POST-ed from the browser, including special request content-types (for example, XML and JSON formats).
Instrumentation	Displays raw instrumentation data. Requires that an APM Administrator implemented the Foglight instrumentation JavaScript library on the monitored web site or application.

Metadata settings

To modify settings, navigate to APM > Configure Advanced Options > Settings. Metadata settings affect the content of choosers and Captured Metadata lists.

Figure 94. Metadata settings

The following table describes all the options. Remember to save after making changes.

 

Table 80. Metadata settings options

Option	Setting the Option
Metadata Cache Timespan	Sets the amount of time between updates to the server’s metadata cache. Valid values are 1,000 to 1,000,000 milliseconds.
Metadata Sensitivity	Sets the number of times the name of a particular request field, request header, response header, or cookie must appear in a given database segment before it is considered significant enough to be returned by metadata queries. Valid values are 1 to 1,000,000 hits per segment, where 1 returns all values, regardless of how often they occur. NOTE: If you use an extremely large number of unique names (for example, dynamically-generated field names), you should set this field to a higher number, such as 5000, to avoid excessively long metadata lists.
Filtered Path Extensions	Specifies file extensions to ignore when generating the list of paths captured by the system for display in the Path chooser and Captured Path metadata list. This field must be a comma-separated list of extensions (no spaces, no dots). Example: gif,jpg,png,ico,bmp

Substituting static page elements

Static page elements are resources, such as images and JavaScript, stored on a local drive (not in the Archiver database) and substituted during session replays when the original resource is not available in the session data. You can use static page elements to provide a richer, more accurate session replay experience. For more information, see “Replaying hits, sequences, and sessions” in the Foglight APM User Guide.

For example, when a browser caches a resource, such as the image of a company logo on the initial visit to a web site, the web server no longer needs to serve that image on subsequent hits in other sessions. If you attempt to replay a user session that references a cached image, by default the replayer checks the live web traffic to see if it can find the missing image. If it does, it displays the image. If not, it displays a broken image icon. In either case, the session replay may not be identical to the session experienced by the user. By defining a static page element, the session replay can use a local copy of the original image, which makes for a more authentic replay experience.

You can also use static page elements to substitute resources that are not served by the web servers being monitored. For example, you may have some page elements being served by an external content delivery network (CDN). Because hits in a CDN cannot be captured by Sniffers, they cannot be replayed without accessing the original content source. You can provide the original content as a static page element.

 

TIP: You have other alternatives for handling missing content. Instead of looking for resources in live traffic (resources that may have changed since the session was recorded), you can choose to always return a 404 error. Or you can have the session replay look for missing resources in unrelated sessions, which may identify the session during which the original image was retrieved by the web server and cached by the browser. For more information, see the When Element Content not Available and Use Elements from Unrelated Sessions options in Configuring internal settings.

To configure Static Page Elements, navigate to APM > Configure Advanced Options > Static Page Elements.

Figure 95. Static Page Elements dashboard

In the Static Page Elements dashboard, you can add, edit, and remove static page elements using the standard controls. You can also view the contents of an uploaded resource file.

For more information, see the following topic:

•	Defining static page elements

•  Previous
• Viewing Topics 189 - 192 of 328
• Next 

Search this document Search all documents

×

 Welcome to Quest Support

You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating