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

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

Changing SLA thresholds

To track web site and web application performance against your service level agreements (SLA), you can specify thresholds that match your SLA times. For more information, see Defining service level agreement thresholds.
You specify thresholds for key performance metrics and navigation time metrics in milliseconds. The maximum value is 5 minutes (300000 ms). To disable a threshold, specify 0.
To define SLA thresholds:
1
When defining a hit analyzer, expand Metrics.
2
Click SLA Thresholds.
3
In the SLA Thresholds dialog box, specify thresholds that match your SLA.
4
Click Save.

Adding custom field updates

When adding a custom field update, you start by selecting the custom field from a list. You then specify the source of the value that you will use to update the custom field. If you want, you can override some of the custom field options.
To add a custom field update:
1
When defining an analyzer, expand Custom Fields.
2
In the Custom Fields view, click Add.
The Custom Field Wizard opens. Use the Previous and Next buttons to navigate between screens.
3
On the Set Type screen, specify whether you want to modify an existing custom field or create a new one.
4
On the Set Properties screen, if you are modifying an existing custom field, select the custom field from the list. If you are creating a new custom field, specify the following options:
•
Name: Specify a name.
•
Description: Summarize the reason you created the 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.
•
Truncate large values: Select (default) to limit values to 2 KB (2,048 characters). Clear to store large values up to 64 KB.
5
On the Identify Source screen, specify the following options:
•
Source: Select the source of the value used to update this custom field—such as Fixed Value, Script Output, Session Custom Field, or one of the hit details. The other available fields change depending on the selected Source.
•
Source Detail: If available, specify some detail to further refine the Source selection. For example, if you selected Cookie, you need to select a cookie. You also have the option of using an extraction expression to extract part of the value of the cookie.
•
Extraction Expression: Optional—if available, you can create an expression that extracts a portion of the source’s value. For example, if your source contains “$99,” you can extract “99” as your value. For more information, see Defining extraction expressions.
•
Update if blank: Optional—override the setting defined for the custom field. Select to allow the custom field to be set to an empty (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.
6
On the Set Update Criteria screen, specify the following options:
•
Value Assignment: Select an option that reflects how you want to handle values for the custom field. For more information, see Value assignment mode option.
•
Separator: 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: By default, a custom field is always updated. You can change the update policy based on the analyzer status or the final hit status (which is the worst status of all the analyzers that match a hit). For more information, see Defining custom field updates.
7
Click Finish.
The wizard closes, and the custom field appears in the Custom Fields view.

Editing custom field updates

To edit a custom field update:
1
Expand Custom Fields.
2
In the row containing the custom field update that you want to edit, click Edit .
3
In the Edit Custom Field dialog box, edit the options as required. For help with options, see Defining custom field updates.
4
Click Save.

Adding scripts to an analyzer

When adding a script, you start by selecting the script from a list. You then specify when you want the script to be executed.
 
* 
NOTE: If you do not see a suitable script in the Scripts list, you can create one. See Creating new scripts on the fly.
To add a script:
1
Expand Scripts.
2
In the Scripts view, click Add.
3
In the Add Script dialog box, select a script or click New to create one on the fly.
4
In the Executing Criteria pane, select when you want the script to run.
5
Click Save.
Related Topics
•
Executing scripts
•
Creating new scripts on the fly
•
Editing scripts
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택