立即与支持人员聊天
与支持团队交流

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

Managing identifiers for virtual addressing schemes

Identifiers enable you to expose IP addresses or host names concealed by virtual addressing schemes. For example, a proxy server may conceal the originating IP addresses of clients, while a load balancer may replace the IP addresses of the servers using a monitored application. While virtual addressing is important for security purposes, this practice prevents Foglight from capturing and storing data with the originating client or server IP address, which in turn makes the data you see less meaningful. In this case, you need to configure identifiers to extract the originating IP addresses from the tags of HTTP headers. You may also need to configure your web servers to insert the IP addresses into the headers.
 
* 
NOTE: To define session identifiers, see Managing sessionizing policies.
To define and manage identifiers, navigate to APM > Configure > Traffic Capture > Identifiers.
Figure 36. Identifiers dashboard
In the Identifiers dashboard, you can perform the following tasks:
•
Defining identifiers

Defining identifiers

Before defining identifiers, read more about the different identifiers in the following sections:
•
Capturing originating client IP addresses
•
Capturing server IP addresses
•
Capturing host names
When adding or editing a client identifier, server identifier, or host identifier, you can set the following options.
 
Table 22. Defining identifiers
Option
Setting the Option
Name
Specify the HTTP header that contains the IP address or host name. You can use the browse button to select a request header (client identifiers) or a response header (server and host identifiers) from a list.
Description
Optional—summarize the purpose for this identifier.

Capturing originating client IP addresses

In typical network environments, client traffic is routed through a proxy server that replaces the originating client IP addresses with the IP address of the proxy server. You can configure client identifiers to capture the originating client IP addresses. Client identifiers reference HTTP request headers that contain the IP addresses of the client computers accessing your applications.
By default, client identifiers come pre-configured for the following commonly used headers:
•
client-ip
•
client-iv
•
true-client-ip
•
x-forwarded-for
These request headers are industry standards for identifying the originating IP address of a client connecting to a web server through an HTTP proxy server or other virtual addressing scheme. If your environment uses different request headers, you need to configure additional client identifiers.
To capture originating client IP addresses, you need to complete the following tasks:
•
Locate the request header used to pass the client IP address; you may be able to find the headers by running a Search Hits query, opening the Hit Detail View, and reviewing the values in the Request Headers pane. For more information, see Finding IP addresses in HTTP headers.
•
Configure a client identifier with the same request header used in your environment. For more information, see Defining identifiers.

Capturing server IP addresses

In many networks, client requests and server responses are routed through a load balancer and/or reverse proxy. A load balancer typically uses a virtual addressing scheme to strip out server IP addresses in the IP layer of any communication it receives from its server farm. While this behavior is important for security purposes, it means that Foglight attributes the data for all web servers to the load balancer IP address. Usually, you want data attributed to individual web servers.
To capture server IP addresses, you need to complete the following tasks:
•
Configure each web server in the server farm to insert an extra shared HTTP response header into the traffic, such as SERVER-ID, and assign a unique, fictitious (for security purposes) IP address to this header for each web server. For information about how to insert a response header tag into outgoing traffic, see your web server documentation.
•
Configure a server identifier with the same response header. For instructions, see Defining identifiers.
For example, you can configure a web server to use the response header SERVER-ID with an IP address of 177.18.1.89. In Foglight, you configure a server identifier called SERVER-ID. Now when you view data, you see metrics for IP address 177.18.1.89 instead of the load balancer’s IP address. The new server IP addresses are used wherever IP addresses appear in the interface, such as when running the Discovery tool from the Monitored IP Addresses dashboard. For more information, see Discovering IP addresses.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级