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

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 web services and SOAP operations

Web services support automated machine-to-machine interaction designed to accomplish specific tasks. They typically use XML over HTTP following the SOAP specification. Web services provide one or more SOAP operations (or methods) that provide specific functions to the consumer of the SOAP service. When a Sniffer processes a hit containing a SOAP message in the monitored traffic, it parses the message and extracts the name of the SOAP operation. The extracted SOAP operation becomes a hit detail.
The Sniffer also attempts to extract the name of the web service from the SOAP message’s SOAPAction HTTP header tag. As of SOAP v.1.2, however, the SOAPAction tag is no longer mandatory. When this tag is missing from a SOAP message, the resulting hit includes the SOAP operation, but does not include the web service to which the operation belongs. You can remedy this situation by using the Web Services dashboard to specify how SOAP operations map to web services.
 
* 
NOTE: While unlikely, it is possible for more than one web service to have SOAP operations with the same name. In this case, the SOAP operation maps to the first web service in the list.
To manage web services, navigate to APM > Configure > Traffic Capture > Web Services.
Figure 40. Web Services dashboard
In the Web Services dashboard, you can perform the following tasks:
•
Creating web services automatically from WSDL files
•
Defining web services and SOAP operations

Creating web services automatically from WSDL files

You can create a web service mapping automatically by importing the web service’s WSDL file. When you import the file, the Add Web Service dialog box is automatically populated with the web service name and SOAP operations. You can modify the list of operations, if necessary. If the elements in the WSDL file use some other prefix than the standard wsdl:message, you need to specify it.
Only the web service and SOAP operation names are saved. Foglight does not save any other information from the WSDL file.

Defining web services and SOAP operations

When adding or editing web services, you can set the following options.
 
Table 26. Defining web services and SOAP operations
Option
Setting the Option
Name
Specify the name of the web service.
Description
Optional—provide more information about the web service.
Operations
Click Add. Add a list of SOAP operations performed by the web service.
Example
Figure 41. Add Web Service dialog box
 

Configuring traffic analysis

In the Traffic Analysis dashboard, you set the options that affect how data is updated, annotated, indexed, secured, and displayed. This section describes all the traffic analysis options (except analyzers) and tells you when and how to set them. Analyzers are discussed in the next major section, Configuring analyzers.
 
* 
TIP: If you are not satisfied with changes that you make to the traffic analysis configuration, you can roll back your changes through the Change Configuration Log dashboard. For more information, see Managing configuration changes.
Traffic analysis includes the following activities:
•
Managing custom fields
•
Managing custom metrics
•
Managing security policies for sensitive hit details 
•
Managing security policies for sensitive content
•
Managing pivots
•
Configuring advanced options
•
Managing domain rules
•
Storing large hit details
•
Managing special events
•
Troubleshooting improperly classified URLs
•
Managing user agent rules
•
Defining additional parsed response types
•
Defining captured request body types
•
Modifying traffic analysis options
•
Managing scripts
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択