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

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

Discovering user names

When you run the Discovery tool from the Username Rules view, it creates a list of candidate variables. Your monitored applications may or may not be using these variables for user names. You need to select the ones used by your applications. The tool updates the list continuously until you stop the discovery process.
Figure 20. Username Rules Discovery dialog box
The following table summarizes the information found in each column of the Username Rules Discovery dialog box.

Table 12. Username Rules Discovery
Column Name
Description
Variable
A variable that may contain a user name.
TIP: If you see the Authorization variable, your network includes a single sign-on environment for end users. For more information, see Capturing user names in a single sign-on environment.
Instances
The number of times the variable was found in the traffic.
TIP: Variables with low number of instances are probably not being used as a login variable. Look for high instance counts.
Sample Values
Real values associated with the variable. Displays up to three of the most used values.
The Discovery tool has an algorithm that attempts to determine which fields may contain user names. If your field does not show up in the results, you can configure it manually. For more information, see Defining username rules.

Capturing user names in a single sign-on environment

Foglight can match user names to user sessions in a single sign-on environment.
NTLM
NTLM is a suite of authentication and session security protocols used in various Microsoft® network protocol implementations. Originally used for authentication and negotiation of secure DCE/RPC, NTLM is now used throughout Microsoft's systems as an integrated single sign-on mechanism. It is recognized as part of the Integrated Windows Authentication stack for HTTP authentication; however, it is also used in Microsoft implementations of SMTP, POP3, and IMAP (all part of Exchange). Sniffers decode NTLM authentication exchanges between clients and web servers, and extract the user name that end users enter when logging into an NTLM-enabled system.
To enable Foglight to capture the user names, all you need to do is add a username rule called Authorization. No other action is required. If you use the Discovery tool, the Authorization username shows up in the list whenever NTLM exchanges are found in the monitored traffic.
CA SiteMinder
CA SiteMinder is a centralized web access management system that enables user authentication and single sign-on, policy-based authorization, identity federation, and auditing of access to web applications and portals. To monitor applications that use SiteMinder, you need to configure Foglight so that it performs the same type of user authentication with CA SiteMinder that your applications currently perform with SiteMinder. For more information, see Integrating with CA SiteMinder.
To enable Foglight to capture the user names, add a username rule with the same name as the session cookie used by SiteMinder. This is usually SMSESSION or GMWSESSION. For more information, see Defining username rules 

Identifying user names in XML

When creating a username rule for XML variables, you need to specify the variable within the context of its root element. Use a period to separate the elements, as in root.child.
For example, if you have the following XML request body:
<body>
<variable1>not_a_username</variable1>
<variable2>userXYZ</variable2>
</body>
You can create a username rule to capture the contents of variable2 (which contains the user name) using this format:
body.variable2
In this example, the rule extracts userXYZ as the username.
Figure 21. Adding username rule example

Understanding missing user names

In the Session Explorer, you may find instances where the user name is missing from the results even though you created a username rule. Foglight can capture user names only if users are required to log in using a web page at the beginning of each session. Some applications, like Siebel, cache user credentials, which means users do not need to log in every time. In these cases, the user name is not available from the web traffic and therefore Foglight cannot associate the user name with these sessions.
Another reason user names may be missing is if the application presents the login page before assigning a cookie that you are using as a session identifier. In this case, the user name is not associated with the user session and therefore is unavailable in the web traffic.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択