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

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

Summary of options by analyzer type

The following table summarizes the conditions and actions that you can set for each type of analyzer and provides links to the topics in the rest of this section.
 
Table 56. Summary of options by analyzer type
Option
Hit
Analyzer
Sequence Analyzer
Session Analyzer
For help defining options, see:
Conditions
Match,
Error,
Warning
Event
Match,
Error,
Warning
Configuring conditions
and Defining event conditions
Metrics
Yes
Yes (scoped to analyzer or event)
Yes
Working with metrics
Custom Fields
Yes (scoped to hit or session)
Yes (scoped to sequence or session)
Yes (scoped to session)
Updating custom fields
Scripts
Yes
Yes, using events
Yes
Executing scripts
Storage Policies
Yes
Yes
n/a
Defining storage policies
Options
Yes
n/a
Yes
Setting searchability options for analyzers
Event Actions
n/a
Yes, using events
n/a
Defining events for sequence analyzers

Configuring conditions

You define all types of conditions—match conditions, error conditions, warning conditions, and event conditions—in the same way. You can add, edit, and remove conditions using the standard controls. When you have multiple conditions, you can also group the conditions and create Boolean expressions with them.
 
* 
NOTE: While you can use the same procedures to add, edit, and group event conditions, the types of conditions you can define are unique to event conditions. Therefore, event conditions are discussed with other event topics. For more information, see Defining event conditions.
For more information, see the following topics:
•
Defining match conditions
•
Defining error and warning conditions
•
Grouping multiple conditions
•
Defining conditions

Defining match conditions

Match conditions enable you to target the actions of an analyzer to specific types of web traffic. When the conditions are met, the analyzer runs its actions.
 
* 
IMPORTANT: It is possible to define an analyzer with no match conditions, in which case the analyzer always matches. Be careful to avoid assigning time-consuming actions to these kinds of analyzers, or they can adversely affect the performance of your monitoring system.
The Match Conditions view appears near the top of the Add Analyzer or Edit Analyzer view. For more information, see Defining conditions.
Figure 76. Edit Hit Analyzer view

Defining error and warning conditions

For sessions, the completed session status is always OK unless you explicitly change it using an analyzer. For hits, Foglight APM automatically sets the hit status to Warning or Error under the conditions outlined in the following table.
 
Table 57. Defining error and warning conditions
Hit Status
Description
Error
At least one of the following responses or exceptions occurs:
•
HTTP Client Error—status code between 400 and 499, excluding 401.
•
HTTP Server Error—status code between 500 and 598.
•
Content Error—content is incomplete, possibly due to an application error or network data loss.
•
Server Reset—the server sent a TCP reset. Some reasons for server resets include unexpected behavior by the client or a server becomes overloaded.
•
Server Timeout—the server stopped sending content on the TCP connection. This is usually caused by some kind of server overload situation.
•
Client Timeout—the client stopped acknowledging receipt of data from the server. Two common reasons for client timeouts are that the client loses power or the client becomes disconnected from the network.
Warning
Client Reset—the client sent a TCP reset. TCP resets are most often triggered by a real user clicking the browser’s Back or Stop buttons or closing the browser.
You can override the default hit status assignment or set the completed session status by defining an analyzer’s error or warning conditions. First, you define the match conditions for the analyzer. Then you use the Error Conditions and/or Warning Conditions panes to specify the circumstances under which the status should be changed to Error or Warning (respectively). For more information, see Defining conditions.
Figure 77. Warning Conditions view
Multiple analyzers can potentially evaluate the status of a hit or session differently. The rule in this case is “worst status wins”. That is, if any analyzer sets the status to Error, the final status is Error. If one analyzer sets the status to Warning and another sets it to Error, the final status is Error. There are situations where it may be important to distinguish between the status according to analyzer X and the final status (after all analyzers have evaluated the hit or session and set the status).
Example: How the status for a hit or completed session is resolved
Consider the error conditions and warning conditions for the following analyzers.
•
Analyzer A does not set the status.
•
Analyzer B sets the status to Warning.
•
Analyzer C sets the status to Error.
In this case, the final status is Error. However, the status according to the individual analyzers remains the same: Analyzer A is OK; Analyzer B is Warning; and Analyzer C is Error.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택