지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Troubleshooting improperly classified URLs

Foglight is typically able to identify which URLs represent the start of a new page download, and then from these URLs it can correctly identify which URLs are hits that belong to the page. However, there may be cases where Foglight is unable to correctly distinguish a page from a hit. For example, a URL is not recognized as the starting point for a new page download, or a URL is incorrectly recognized as a new page, when it is actually an element of the current page download. These situations typically arise with HTML frame-based applications and with some rich internet applications. If you are not seeing accurate page metrics for some set of URLs, you should add URL classifiers rules to classify the URLs.
To classify URLs, navigate to APM > Configure > Traffic Analysis, select Advanced Options, and expand URL Classifiers.
Figure 64. URL Classifiers view
From the URL Classifiers view, you can add, copy, edit, and remove rules using the standard controls.
For more information, see the following topics:
•
Defining URL classifiers

Defining URL classifiers

When adding, copying, or editing URL classifier rules, you can set the following options.
 
Table 43. Defining URL classifiers
Option
Setting the Option
Name
Specify a unique name for the rule.
Description
Optional—summarize the purpose for this URL classifier rule.
Class
Select a classification. The class determines whether hits on the specified URLs should be treated as the start of a new page or as a hit within the current page. The asynchronous classifications are useful with Rich Internet Applications (RIAs)—such as those built using the AJAX framework—where pages do not need to be fully downloaded before another page starts. See Class option (following this table).
Regular Expression
Specify a pattern to match against URLs in the monitored traffic. To test your expression, click to open the Extraction Rule dialog box. For more information, see Defining extraction expressions.
Request Header
Optional—specify a request header that must also be present in the URL request before this classification rule is applied.
Value
Optional—specify a value for the Request Header that must be present in the URL request before this classification rule is applied.
Sessionizing Policy
When set to None (default), this rule applies to all URLs found in the monitored traffic. There may be cases where it is advantageous to apply a rule only to the URLs covered by a specific sessionizing policy. In this case, select the sessionizing policy from this list.
Class option
You can select from the following classifications.
 
Table 44. Class option
 
 
 
 
Class Option
 
 
 
 
Description
Starts a New
Page
Ends Current
Page Download
Is a Component
of Current Page
Generates
Page Metrics
Page
Treats any hit on matching URLs as the start of a new page.
Yes
Yes
No
Yes
Hit
Treats hits on matching URLs as hits on the current page.
No
No
Yes
No
Asynchronous Page
Treats any hit on matching URLs as a standalone page.
Yes
No
No
Yes
Asynchronous Hit
Treats a hit on matching URLs as a standalone hit without attributing the hit to any page.
No
No
No
No
Example
Figure 65. Add URL Classifiers dialog box

Managing user agent rules

User agent rules transform strings found within the user-agent HTTP header into more meaningful strings for display and categorization purposes. They can be used to rename the browser, browser category, and operating system associated with a hit. Foglight applies the transformations before storing these items as hit details. For definitions of hit details, see “Archiver Database Details” in the Foglight APM Reference Guide.
You only need to add user agent rules if the default categorizations do not suit your needs. For example, you see a session where the browser, browser category, and operating system fields are empty. This usually indicates that a newly-released browser is not yet categorized. You can categorize the new browser yourself by creating a new user agent rule.
To review or upload user agent rules, navigate to APM > Configure > Traffic Analysis, select Advanced Options, and expand User Agent Rules.
Figure 66. User Agent Rules view
 
In the User Agent Rules view, you can perform the following tasks:
•
Defining new user agent rules
•
Setting the execution order for rule files

Defining new user agent rules

You define new user agent rules in an XML file using the elements in the following table. Rules are order-dependent.
 
* 
CAUTION: Do not edit the Default Rules. This file is updated periodically, and you will lose your changes.
 
Table 45. Defining new user agent rules
Element
Attribute
Description
osrule
 
Use this element to categorize an operating system.
find
The OS string contained in the user-agent header.
replace
The OS name you want to use for display and categorization purposes.
useragent
 
Use this element to set the browser category, the browser name, and the OS name.
browsercategory
A string that identifies the device used to create the hit, such as Browser or Mobile Device.
 
find
A regular expression used to parse the user-agent header. For more information, see Appendix: Building regular expressions in Foglight.
ossource
Either a string or a token ($1, $2, etc.) matching one of the sets of brackets in the regular expression.
browser
Either a string or a token ($1, $2, etc.) matching one of the sets of brackets in the regular expression.
Example <osrule>
The following rules reassign two versions of Windows® NT to Windows® 8 for analysis and reporting purposes.
<osrule>
<find>Windows NT 7.0</find>
<replace>Windows 8</replace>
</osrule>
<osrule>
<find>Windows NT 6.2</find>
<replace>Windows 8</replace>
</osrule>
Example <useragent>
The following rule finds any version of Internet Explorer® Mobile and assigns it to the Mobile Device browser category. The find attribute is defined as a regular expression that parses out the version numbers and the OS. The operating system and browser hit details are dynamically assigned those values using tokens.
<useragent>
<browsercategory>Mobile Device</browsercategory>
<find>.*\(compatible; MSIE ([0-9]*)\.([0-9]*);.*(Windows Phone [0-9]*\.
[0-9]*).*</find>
<ossource>$3</ossource>
<browser>Internet Explorer Mobile $1.$2</browser>
</useragent>
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택