Chatee ahora con Soporte
Chat con el soporte

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

Grouping multiple conditions

If you have multiple conditions, you can arrange the conditions in the order you want them evaluated. You can also create simple and complex Boolean expressions using the logical operators AND, OR, and NOT.
 
* 
TIP: While sequence event conditions can be grouped, they rarely need to be grouped in this fashion.
OR example
You can join all conditions with the OR operator. For example, consider these conditions:
1
Request Path contains “shopping” OR
2
Value of the “cartValue” cookie is >0 OR
3
HTTP response code is >=500
Web traffic has to match only one condition for the analyzer actions to run. For more information, see Creating a simple Boolean expression.
AND example
You can join all conditions with the AND operator. For example, consider these conditions:
1
Request Path contains “shopping” AND
2
Value of the “cartValue” cookie is >0 AND
3
HTTP response code is >=500
In this case, web traffic must satisfy all three conditions for the analyzer actions to run. For more information, see Creating a simple Boolean expression.
Complex example
When you define at least three conditions, you can choose to create an expression that uses more than one kind of logical operator. For example, given the following conditions:
1
Request Path contains “shopping”
2
Value of the “cartValue” cookie is >0
3
HTTP response code is >=500
You can create complex expressions to express the following kinds of relationships:
•
1 matches AND either 2 OR 3 matches
•
1 matches OR both 2 AND 3 match
•
1 AND 2 match but NOT 3
Any valid combination is possible. For more information, see Creating a complex Boolean expression.

Defining conditions

When adding or editing conditions, you can set the following options.
 
Table 58. Defining conditions
Option
Setting the Option
Source
Select the type of web traffic matched by this condition. For example, Request Path, Request Field, Browser, Cookie, and so on.
NOTE: The other available fields change depending on the selected Source.
Source Detail
If the Source you selected requires additional detail, specify the detail in this box. For example, if you chose Source=Cookie, type the name of the cookie you want to reference.
not
If available, select to cause the Operator to perform its opposite action. For example, you can change equal to to not equal to by selecting this check box.
Operator
If available, select an operator that performs the type of match you want to make. Only the operators that make sense for a selected Source type are available. For more information, see Operators.
Value
If available, specify a numeric or text value (as appropriate). For example, you can specify that a match occurs when Client Time (ms) is greater than 600. Or, for Country, you can select a text string from a list, such as “Canada (CA)”.
Extraction Expression
Optional—if available, you can create an extraction expression. For more information, see Defining extraction expressions.
Operators
The Operators list includes only the operators that make sense for the selected Source type.You can cause an operator to perform its opposite behavior by selecting the not option. The following table contains all the possible operators.
 
Table 59. Complete list of operators
Operator
Matches when a traffic element...
= 1
Equals the value in the Value field.
Starts With1
Starts with the value in the Value field.
Ends With1
Ends with the value in the Value field.
Contains1
Includes the value in the Value field.
Matches
Matches a condition specified in a regular expression.
<
Is less than the value in the Value field.
>
Is greater than the value in the Value field.
<=
Is less than or equal to the value in the Value field.
>=
Is greater than or equal to the value in the Value field.
Exists
Exists, that is, the specified Source/Source Detail occurs in monitored traffic.
1
You can select a version of this operator that ignores case.

Example
Figure 78. Add Match Condition dialog box

Working with metrics

Foglight APM supports different groups of metrics:
•
Standard metrics—Metrics such as Hits Captured, Back End Time, and End to End Time, generated when a hit matches an analyzer’s match conditions. For more information, see the Foglight APM Reference Guide.
•
Custom metrics—User-defined metrics that can be created and updated using analyzers.
•
Pivot metrics—Metrics by category, which means that an Archiver stores the same set of metrics for different segments of users defined by, for example, the browser they use or the operating system of the device they use to access the monitored applications. Pivots apply to standard metrics and custom metrics.
Because analyzers serve different purposes, each type of analyzer organizes the options for metrics slightly differently. For example, while hit and session analyzers control pivots in the Metrics view, sequence analyzers control pivots at the analyzer level and offer two kinds of metrics (sequence metrics and sequence event metrics) at the event level. In all cases, however, you can define custom metrics, define the name of the topology objects created (the name used for storage purposes), and specify pivots. For hit analyzers only, you can also choose not to generate standard metrics, specify SLA thresholds, and make metrics available for mapping purposes. The following image shows a hit analyzer with all the options available.
Figure 79. Metrics view
For more information, see the following topics:
•
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

Understanding standard metrics

Standard metrics are a set of metrics suitable for analyzing data about hits, sequences, and sessions. Standard metrics are updated whenever the match conditions defined for an analyzer or sequence event are satisfied. For lists of standard metrics, see the Foglight APM Reference Guide.
For hit analyzers only, you have the option of turning off standard metrics. For example, if an analyzer is designed to match a failed login attempt, you may be interested in a counting the failed attempt (using a custom metric), but you may not want to generate and save all the standard hit metrics. In this case, you can clear the Generate Standard Metrics option.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación