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

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

Editing identifiers

You edit client identifiers, server identifiers, and host identifiers in the same way.
To edit an identifier:
1
On the navigation panel, under Dashboards, click APM > Configure > Traffic Capture > Identifiers.
The Identifiers dashboard appears, containing three panes: Client Identifiers, Server Identifiers, and Host Identifiers.
2
In the row containing the identifier you want to edit, click Edit .
3
In the Edit [Client|Server|Host] Identifier dialog box, edit the options as required. For help with options, see Defining identifiers.
4
Click Save.
The identifier’s details are updated in the table.

Finding IP addresses in HTTP headers

You can check to see if the originating IP address is being passed in an HTTP header using the Search Hits dashboard. For more information, look up Search Hits in the Foglight APM User Guide.
For client IP addresses, when selecting an IP address you should look for the client IP address that you saw repeated in your data (likely a proxy server). For more information, see Capturing originating client IP addresses.
For server IP addresses, you should look for the IP address of the load balancer and look for the custom header name. For more information, see Capturing server IP addresses and Configuring a custom HTTP header using Microsoft IIS Manager.
To find IP addresses in HTTP headers:
1
On the navigation panel, under Dashboards, click APM > Search > Hits.
2
Click Search.
Results for the last 15 minutes appear in the table.
3
Locate the IP address.
4
In the row for the IP address, select Hit Detail View .
The Search Hits > Detail View appears.
5
In the Request Header (for client IP addresses) or Response Header (for server IP addresses) pane, scan the Values column to see if any of the values are IP addresses.
•
If you see an IP address, you have found the originating IP address. Make a note of the corresponding header name. You can now configure an identifier with this name.
•
If you do not see an IP address, the proxy server or load balancer is not passing the originating IP address. Contact your Network Administrator to see if this feature can be enabled.

Configuring a custom HTTP header using Microsoft IIS Manager

When configuring a server identifier, you may also need to configure your web servers to include their actual IP addresses in an HTTP response header. You can use Microsoft Internet Information Services (IIS) Manager for this task. Your web server may also offer its own tool. See your web server documentation. For more information, see Capturing server IP addresses.
 
* 
NOTE: If the application you are monitoring is publicly available on the Internet, the best practice is to use a fictitious IP address to protect the identity of your physical servers. Foglight APM does not require the physical IP address, only a standard formatted IP address.
After you complete this procedure, you need to perform the following tasks in Foglight:
•
In the Search Hits dashboard, verify that the custom HTTP header exists in the web traffic. For more information, see Finding IP addresses in HTTP headers.
•
In the Identifiers dashboard, configure a server identifier using the Custom Header Name that you specified for the web server. For more information, see Adding identifiers.
•
In the Monitored IP Addresses dashboard, add the load balancer IP address and all the web server IP addresses that you specified as Custom Header Values. The archiver can now store metrics by IP address. For more information, see Adding or editing monitored IP addresses.
To configure an HTTP header in IIS:
1
On the web server, navigate to Start > Programs > Administrative Tools > Internet Information Server (IIS) Manager.
2
In the left pane, expand the Web Server node and then expand Web Sites.
3
Select a web site from the list.
4
Right-click the web site and select Properties.
5
In the Properties dialog box, select the HTTP Headers tab.
6
Click Add.
The Add/Edit Custom HTTP Header dialog box appears.
a
Type a unique value for the Custom Header Name. For example, SERVER-IP.
b
Type the IP address for the web server (physical or fictitious) in the Custom Header Value field. For example, 192.168.1.1.
c
Click OK.
The Add/Edit Custom HTTP Header dialog box closes. The custom header appears in the Custom HTTP Headers list.
7
Click OK.
The Properties dialog box closes.
8
Configure your other web sites, using the same Custom Header Name (in this example, SERVER-IP), with unique custom header values representing the various web server IP addresses.

Adding and editing local private keys

To add a local private key:
1
On the navigation panel, under Dashboards, click APM > Configure > Traffic Capture > Private Keys.
2
Do one of the following:
•
To load a new local private key, click Add Local Key.
•
To edit an existing local private key, click its Edit icon.
3
In the dialog box, complete the options. For help with options, see Defining local private keys.
4
Click Save.
The new key appears in the Private Keys table.
5
If your web server supports multiple domains from the same IP address and TCP port number, specify the domain that requires this key.
a
In the Domains column, click the monitored IP address’ Click to add domains link.
b
In the Domains dialog box, click Add.
c
Specify the domain name, and click Save.
The domain appears in the table.
d
Repeat to add any other domains that require this key.
e
Click Save.
The dialog box closes. The domains appear in the Private Keys table.
Related Topics
•
Managing private keys
•
Understanding how local private keys are stored
•
Exporting local private keys
•
Troubleshooting local private keys
•
Supported encryption technologies
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択