Chatta subito con l'assistenza
Chat con il supporto

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

Defining service level agreement thresholds

Service level agreements (SLA) define quality goals for delivery of service. You use hit analyzers to specify SLA thresholds. For every hit analyzer you create, a set of default SLA thresholds are also created. You can change these defaults to match your SLAs.
You can specify thresholds for key performance metrics and navigation time metrics (in milliseconds) as described in the following table. The maximum value is 5 minutes (300000 ms). To disable a threshold, specify zero (0). For detailed instructions, see Changing SLA thresholds.
 
Table 62. Defining service level agreement thresholds
SLA Threshold
Description
Hits Back End Time
Maximum amount of time that web servers should spend processing hit requests sent from client browsers.
Hits End to End Time
Maximum amount of time that clients should experience when downloading a hit.
Pages Back End Time
Maximum amount of time that web servers should spend processing page requests sent from client browsers.
Pages End to End Time
Maximum amount of time that clients should experience when downloading a page.
Navigation Timing1 Content Delivery Time
Maximum amount of time that should elapse from the start of the HTTP request to the start of the HTTP response, as measured using browser-based instrumentation and following the W3C Navigation Timing standard.
Navigation Timing1 Page Completion Time
Maximum amount time of time that should elapse from the start of a navigation request (such as a user click on a hyperlink in a web page) to the end of the load event, as measured using browser-based instrumentation and following the W3C Navigation Timing standard. This is also sometimes referred to as “click to glass” time.
1
To enable the navigation timing thresholds, you need to instrument the web application or site that you want to monitor. For more information, see Capturing traffic outside the network.

Example
Figure 84. SLA Thresholds dialog box

Updating custom fields

Custom fields are useful for associating additional information with individual hits, sequences, or sessions. For more information, see Managing custom fields.
Figure 85. Custom Fields view
You can update the value of custom fields using analyzer actions or special event actions. You can add, edit, and remove custom field updates using the standard controls.
For more information, see the following topics:
•
Updating the value of custom fields
•
Creating new custom fields
•
Defining custom field updates

Updating the value of custom fields

A custom field update requires two things: the name of a properly scoped custom field and the source of the value that you want to use to update the custom field. Different types of analyzers can update custom fields with different scopes, as summarized in the following table. For more information, see Adding custom field updates.
 
* 
NOTE: You can update custom fields scoped for hits or sessions using more than one analyzer. For sequence-scoped custom fields, only the analyzer that defines the custom field can update it.
 
Table 63. Updating the value of custom fields
Analyzer/Event
Custom Field Scope
Hit
You can update custom fields with the following scopes:
•
Hit scope
•
Session scope (for the session that contains the hit)
Sequence (Event)
You can update custom fields with the following scopes:
•
Sequence-analyzer scope (only the analyzer that defines the custom field can update it)
•
Session scope (applies to the session that contains the sequence)
Session
Session scope
Special Event
Session scope
An analyzer can update custom fields using any of the following value types:
•
Fixed values—You can replace the value of a custom field with a new value or increment/decrement an existing value.
•
Script outputs—Analyzers can use any data that is exposed as an output variable by a Groovy script. The script is executed as needed.
•
Session custom fields—Analyzers can update custom fields using the data from a session-scoped custom field.
•
Details—Analyzers can update custom fields using data that is already associated with a hit, sequence, or session. For example, you can update a custom field with a Request Header value. The type of details available to an analyzer changes depending on the type of analyzer.
A special event can use fixed values, script outputs, and session-scoped custom fields.
By default, analyzers update custom fields whenever the analyzer’s actions run. For hit and session analyzers, you can specify the update criteria for each individual custom field update. For sequence analyzers, all custom fields are updated at the same time. For more information, see Update criteria option.

Creating new custom fields

If an existing custom field does not suit your purposes, you can create a new custom field on the fly. In the Custom Field Wizard, select Create New Custom Field. For more information, see Managing custom fields and see Adding custom field updates.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione