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

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

Configuring traffic capture

The Getting started section walked you through setting some of the traffic capture options that are important when you first begin monitoring your web traffic. This section describes all the tasks you can perform in each of the Traffic Capture dashboards.
 
* 
NOTE: You can fine-tune your data collection and analysis by configuring the traffic analysis options and analyzers. These topics are covered in Configuring traffic analysis and Configuring analyzers.
Traffic capture includes the following activities:
•
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

Managing Sniffers

Sniffers capture, decrypt, and analyze web traffic, and transmit content and metrics to one or more Archivers within the same capture group as the Sniffer. For more information about how Sniffers work, see Understanding how Foglight captures real user data.
An installation of Foglight APM Appliances requires at least one Sniffer component. Smaller installations may use only a single Sniffer, but larger installations usually require many Sniffers running simultaneously. When using an All-in-One Appliance, the Sniffer component comes preregistered as the Local Sniffer—you do not need to register it. For installations with standalone Sniffer Appliances, you need to add and configure the Sniffers.
Later on if you define additional monitored ports or decide to use monitored IP addresses, you can choose which Sniffers monitor the web traffic running through those devices. For more information, see Defining monitored ports and Defining monitored IP addresses.
To define and manage Sniffers, navigate to APM > Configure > Traffic Capture > Sniffers.
Figure 3. Sniffers dashboard
In the Sniffers dashboard, you can perform the following tasks:
•
Defining Sniffers
•
Testing Sniffer communications

Defining Sniffers

When adding, copying, or editing a Sniffer definition, you can set the following options.
 
Table 4. Defining Sniffers
Option
Setting the Option
Name
Specify a unique name for the Sniffer.
Description
Optional—provide information about the Sniffer. For example, describe where the Sniffer is located or which applications and sites it is primarily intended to monitor.
Sniffer Host
Specify the Sniffer’s host name as a DNS name, an IP address, or as localhost (if appropriate).
Foglight IP Address
Specify the IP address of your Foglight Management Server. Occasionally, you may need to specify a different IP address to connect to Foglight, such as when a Sniffer is deployed remotely and the network uses network address translation to hide the true IP address of the Management Server.
Capture Group
Use the Default Capture Group or select a different capture group. The Sniffer sends the data it collects to the Archivers within its capture group. For more information, see Managing capture groups.
NOTE: Selecting None as the capture group means the Sniffer does not send data to any Archivers, effectively disabling the Sniffer.
TCP Connection Timeout
By default, Sniffers stop tracking inactive monitored TCP connections after 160 seconds. If your site uses proxies that keep TCP connections open without transmitting any data for extended periods of time, specify the TCP timeout period enforced by the applications this Sniffer monitors.
Filter by IP Address
Clear (default) to capture web traffic for all IP addresses in the monitored environment. Select to capture only the traffic to and from the web servers whose IP addresses are listed on the Monitored IP Addresses dashboard. For more information, see Managing monitored IP addresses.
NOTE: In most cases, the Sniffer consumes fewer CPU and memory resources when filtering by IP address.
Perform Traffic Filtering in Kernel
Select (default) to filter monitored traffic at the kernel level. This setting uses CPU and memory resources most efficiently. Clear to filter traffic within the Sniffer’s process rather than in the kernel. If the kernel filter becomes too large, Foglight APM automatically begins filtering at the Sniffer level regardless of this setting.
NOTE: You should filter at the kernel level unless your network uses a non-standard variant of the IEEE802.1ad standard.
Example
Figure 4. Adding Sniffer example

Testing Sniffer communications

After you register all Sniffers in your environment, click Test to verify that the Sniffers are reachable.
The Test Sniffer dialog box shows if Foglight can successfully communicate with the Sniffer, and lists any Sniffer diagnostic messages. If any errors appear, you may need to edit a Sniffer definition.
Figure 5. Test Sniffers example
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択