サポートと今すぐチャット
サポートとのチャット

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

Registering Archivers

When using an All-in-One Appliance, the Archiver component comes preregistered as the Local Archiver—you do not need to register it. For installations with standalone Archiver Appliances, you need to add and configure the Archivers.
To add an Archiver definition:
1
Click APM > Configure > Traffic Capture > Archivers.
2
Click Add.
3
In the Add Archiver dialog box, complete the options. For help with options, see Defining Archivers.
 
* 
IMPORTANT: From the Capture Group list, you can select a capture group you defined earlier. For more information, see Creating Capture Groups.
4
Click Save.

Verifying that you are capturing data

To verify that registered Sniffers are actively capturing data, perform a Search Hits search.
To verify that the default Sniffer is capturing data:
1
Click APM > Search > Hits.
2
In the Search Hits dashboard, click Search.
The Search button reruns the last search performed. In a new installation, the search returns all hits that occurred within the last 15 minutes. You can find the search parameters beside Search Description at the top of the dashboard.
If you see data in the table, you know that Sniffers are capturing data.
If the search ends with no data, the Sniffers’ appliances may not be installed or configured correctly. Contact your Network Administrator.

Resolving gaps in traffic capture

The next step is to ensure that Sniffers can capture, and if necessary decrypt, the traffic for all the web applications and web sites you want to monitor. For example, you may need to register a (non-default) port number used by your application or provide private keys to decrypt secure web traffic.
To determine if you need to adjust your Sniffer-based settings, consider the situations and symptoms in the following table, and then click the related link to get instructions on how to update options. When you finish making changes, run another hit search to ensure the data gaps are resolved. For more information, see Verifying configuration changes.
 
* 
NOTE: To locate the issues described in the Symptom column, look in the Search Hits results that you generated earlier in this workflow. For more information, see Verifying that you are capturing data.
 
Table 1. Resolving gaps in traffic capture
Situation/Requirement
Symptom (in Search Hit results)
Instructions
Your web applications use ports other than the default ports 80, 443, and 8080.
In the Hits column, you are missing HTTP hits for some web applications.
Adding missing ports
Your web applications use session identifier variables other than the defaults or you use single sign-on technology.
Find an HTML hit in the table and click its Session Explorer icon. In the Session Explorer, the user sessions seem incomplete or you do not have any session-level information.
Capturing complete user sessions
You want to monitor secure (HTTPS) web traffic.
In the Hits column, you are missing HTTPS hits for all web applications.
Monitoring secure web traffic
You want to monitor Web 2.0 applications, web sites/applications hosted in the cloud, performance of content delivery networks, or mashup web sites and applications.
In the Hits column, you are missing details for activities occurring outside your network, such as browser-level processing, external web server activity, or linked social network activity.
Finish all the Getting Started topics. Request the document “Capturing Traffic Outside the Network” from Dell Support.
This section covers the following topics:
•
Adding missing ports
•
Capturing complete user sessions
•
Monitoring secure web traffic
•
Verifying configuration changes

Adding missing ports

By default, a Sniffer monitors ports 80, 443, and 8080. If your web applications use different port numbers, a Sniffer cannot capture data until you include those port numbers in the traffic capture settings. You can use the Discovery tool to generate a list of ports that are currently handling live web traffic, and then select and add ports from the list. For more information, see Managing monitored ports.
To discover and add monitored ports:
1
Click APM > Configure > Traffic Capture > Monitored Ports.
2
Click Discover.
The Port Discovery dialog box appears, and begins displaying ports in use in the monitored environment. You can use the Search field to narrow the results.
3
When you see the ports that your web applications use, click Stop.
4
Select the check boxes beside the ports you want to add.
 
* 
NOTE: You do not need to select the default ports 80, 443, and 8080.
5
Click Add.
All Sniffers begin monitoring traffic on these ports.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択