Converse agora com nosso suporte
Chat com o suporte

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

Testing scripts

While you create a script, you can check the syntax and test regular expressions. After you are done with the script, you can run a test on the entire script using some sample data.
 
* 
IMPORTANT: To ensure your scripts produce the results you expect, test scripts before using them.
In the Script - Add dashboard or dialog box, click Test Script. To run a test, add some sample data, specify the expected results, and click Execute Test.
Each test data element consists of up to four parts. The general form of the test data is:
dataType.dataElement[#argumentValue ... ]=dataValue
where:
•
dataType is one of: hit, session, sessionHA, sequence or sequenceHA
•
dataElement is the specific piece of data you are specifying for that dataType
•
argumentValue is optional and consists of the arguments passed to the method used to access the dataElement
•
dataValue is the value you wish to assign this dataElement.
For example, the test data for specifying the value of a hit custom field whose name is cartValue to a value of 100.00 would be hit.customField#cartValue=100.00. For data elements that are retrieved by API methods that do not take any arguments, simply omit the argumentValue. For example, the test data for specifying the client IP would be hit.clientIP=10.2.2.1.
For a list of valid test data elements, click Help.
The following image shows the results of testing the TransformData script.
Figure 74. Test Script dialog box

Defining scripts

When adding, copying, or editing scripts, you can set the following options.
 
* 
IMPORTANT: To be able to save a script, the script must be syntactically correct. If you need to save before your script is finished, you can comment out any statements that contain syntax errors.
 
Table 51. Defining scripts
Option
Setting the Option
Name
Specify a unique name for the script.
Description
Optional—summarize the actions perform by this script.
Type
Select the Traffic Analysis API that you want to use for this script based on your data requirements and where the script will be executed. For more information, see Select an appropriate API.
Execute
Select the context (hit/sequence/session) in which the script executes. Scripts execute once for each matching hit/sequence/session. Any generated output variable values are cached. For more information, see Decide when to execute the script.
Maximum Number of Uncaught Failures
Specify the number of uncaught failures that can occur before the script no longer executes or use 0 to indicate unlimited failures. For more information, see Decide how many uncaught failures are allowed.
Output Variables
Click Add. Specify a name for the output variable. You can create as many output variables as your script requires. For more information, see Define output variables.
Script Body
Display Only—to add or edit a script, click Edit Script. For more information, see Creating scripts.
Example
Figure 75. Script—Add dialog box
 

Configuring analyzers

Analyzers are tools that you can use to collect additional data about hits and sessions, define and collect data about sequences (a subset of hits or transactions within a session), annotate data, perform calculations, and control data storage. When creating analyzers, you define a set of conditions and a series of actions. For example, you can create an analyzer that matches every hit and, if the hit status is an error, the analyzer increments an error counting metric and discards all other data about the hit.
Foglight offers three types of analyzers: hit, session, and sequence. This section introduces you to each type of analyzer and describes how to create and use them. To get started with analyzers, select one of the following topics:
•
Introducing hit analyzers
•
Introducing sequence analyzers
•
Introducing session analyzers
The following table lists common tasks and identifies the analyzer required to perform each task.
 
Table 52. Analyzer types
Task
Type of Analyzer
Monitor web application performance against service-level agreements
Hit analyzer—Main phase
Monitor the performance of an important workflow in your web application, such as a shopping to checkout sequence
Sequence analyzer
View selected hits geographically in the Geographic Perspective dashboard
Hit analyzer—Main phase
Discard hits that you do not care about, for example, you may want to ignore hits generated by crawlers and bots
Hit analyzer—Filtering phase
Mark interesting hits so that you can retrieve them later using a search by analyzer name
Hit analyzer—Main phase
Generate a set of standard metrics, create and update your own metrics (custom metrics), or generate metrics by category, such as operating system or region (pivots)
Depends on the type of metrics required:
•
hit-level: Hit analyzer—Main phase
•
session-level: Session analyzer
•
sequence-level: Sequence analyzer
Annotate data with custom text (custom fields)
Depends. Custom fields have a scope, and in some cases, more than one type of analyzer can update them. For example, you could define a session-scoped custom field, and then use one or more hit analyzers to set its value. When sessions end, you may want to use the final value of a session-scoped custom field as a match condition in a session analyzer.
Extract hit details embedded in various types of content and store the details (custom fields)
Hit analyzer—Main phase
Run your own calculations (scripts)
Depends on the data required:
•
Hit-level: Hit analyzer—Main or Final phase
•
Session-level: Session analyzer
•
Sequence-level: Sequence analyzer
Avoid storing sensitive data in the database (security)
Hit analyzer—Main or Final phase
NOTE: Sessions and sequences may include hits that contain sensitive data, but the sequence and session objects themselves do not have sensitive data associated with them.
For more details, see the following topics:
•
Summary of options by analyzer type
•
Configuring conditions
•
Working with metrics
•
Updating custom fields
•
Executing scripts
•
Defining storage policies
•
Setting searchability options for analyzers
•
Defining events for sequence analyzers

Introducing hit analyzers

A hit analyzer analyzes hits as they are captured. When a hit matches the analyzer’s conditions, the analyzer actions run.
You can define hit analyzers to perform any of the following types of actions:
•
Monitor performance against service level agreements
•
Detect and alert on any per-hit condition
•
Mark interesting hits for later searching
•
Manage hit storage
•
Calculate performance measurements
•
Populate custom fields
•
Increment/decrement metrics
•
Extract data from hit details, using extraction expressions
•
Filter out hits you are not interested in
Foglight ships with a set of default hit analyzers to help you get started. Before creating your own hit analyzers from scratch, you may want to review how the default analyzers are defined.
For more information, see the following topics:
•
Reviewing default hit analyzers
•
Tips for creating effective hit analyzers
•
Configuring hit analyzers
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação