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

Verifying instrumentation payloads are received

When the instrumentation library sends an instrumentation payload to the web server using the POST command, the server sees the post and returns a response. The Sniffer monitors this conversation. You can verify that the conversation is occurring by searching hits.
 
* 
NOTE: By default, the instrumentation library posts its payloads to <host_URL>/empty.txt.
To verify that instrumentation payloads are received:
1
On the navigation panel, under Dashboards, click APM > Search > Hits.
2
Click Simple Search.
3
From the Content Category list, select Instrumentation.
4
Click Search.
The results table displays instrumentation payload hits. If the table is empty, ensure that the web site is in use and wait a few minutes before re-running the search. If the table is still empty, review your instrumentation setup for issues.

Viewing metrics collected by instrumentation

You can view hits that contain instrumentation data from the Search Hits dashboard. Instrumentation data includes navigation timing metrics—client-side metrics collected from the browser. Navigation timing metrics include things like content delivery time and page completion times. For metric definitions and explanations of calculated data, see “Navigation timing metrics” in the Foglight APM Reference Guide.
To view hits with instrumentation data:
1
On the navigation panel, under Dashboards, click APM > Search > Hits.
2
Click Simple Search.
3
From the Content Category list, select HTML.
4
From the Hit Analyzer list, select a hit analyzer that you know is collecting metrics for instrumented web pages.
5
Click Search.
Hits on instrumented pages appear in the results table. Values for the following calculated navigation timing metrics are displayed for the HTML pages that include the instrumentation JavaScript.
•
Navigation Page Completion Time—the total time taken from the beginning of a navigation action (such as a click on a hyperlink) to the end of the load event when the page has been completely displayed in the browser. For an example, see “Tracking time spent on a page using instrumentation” in the Foglight APM Reference Guide.
•
Navigation Content Delivery Time—the amount of time from the beginning of the request to the beginning of the response. For an example, see “Tracking time spent on a hit using instrumentation” in the Foglight APM Reference Guide
6
To view all navigation timing details for an instrumented hit, in the Hits column, click Hit Detail View and open the page in a new window.
7
Scroll to the bottom of the page to see the Navigation Timing Details view.
 

Configuring advanced options

The advanced options affect the software components and user interface elements.
Advanced configuration options include the following activities:
•
Configuring internal settings
•
Substituting static page elements
•
Excluding subnets from data collection

Configuring internal settings

The Settings dashboard contains configuration options that affect how Foglight APM components operate. Avoid modifying these options until you understand how the changes affect your installation.
 
* 
TIP: For settings that affect how real user data is captured, transformed, analyzed, and stored, see Configuring traffic analysis.
The dashboard organizes the settings into three groups based on which components are affected: Archiver query settings, Replay settings, and Metadata settings.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação