Defining user session options
Access the User Sessions page by clicking Configure > Monitoring > User Sessions. The Options section enables you to configure sessionizing, capture and timeout settings.
By default, all user sessions are recorded in the database. For performance reasons, it may be desirable not to capture every user session by clearing the Capture all User Sessions check box in the Options section of the User Sessions page.
In the User Session timeout period box, you can adjust the amount of time a user session is inactive before the system considers the session to be terminated and writes the associated record to the database. Generally, you should only need to adjust this setting if your users tend to have long periods of time in which they leave an application inactive. By increasing the timeout period, you can cause user sessions that would have been regarded as distinct to be combined into one record. This setting should reflect the session timeout period that your application enforces.
In the TCP timeout period box, you can adjust the timeout period that the system applies to inactive TCP connections before closing them. You may need to adjust this if your site makes use of proxies that keep TCP connections open without transmitting any data for extended periods of time. This setting should reflect the TCP timeout period that your application enforces.
Configuring client IP tags
For more information, see Configuring client IP tags and Using X-Forwarded-For.
and 
arrows to reorder the items in the list. Tags that are not in use on your site may be removed from the list although this is not required.The list of logout patterns updates to include your addition.
Select the check boxes that corresponds to the Client IP Tag you would like to remove, then click the Delete button.
Augmenting user sessions log information
You can add information in the User Session Log by using the login names as identifiers.
In the Login Variables section, you can define the names of variables that are used to contain login names in your application. While login variables are typically contained in form variables, the system can also extract them from cookies or query variables embedded in a URL.
In the Login Variables section, enter a variable that will be used to identify a user login, then click Add. The list of login variables is updated to include your addition.
Instead of entering variable names manually, you can choose the auto-discovery links to have the system generate a list of variables that are used to log in to the monitored application in the network traffic. For information about NTML authentication, see Extracting login names from NTLM.
|
1 |
|
2 |
To cancel the search, click Stop at any point. |
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 also 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).
Foglight Experience Monitor has the ability to decode NTLM authentication exchanges between clients and web servers, and extract the login name that users enter when logging into an NTLM-enabled system. To enable this functionality, you need only to add Authorization to the list of Login Variables. No other action is required.
|
NOTE: Authorization will also show up when you choose the Auto-Discovery Login Variables function if NTLM exchanges are found in the monitored traffic. |
Select the check boxes that correspond to the login variables you would like to remove, then click the Delete button.
Using logout patterns to detect completed sessions
By default, the appliance considers a user session active until the timeout period has expired. (See Defining session timeout periods for more information about timeout periods.) Defining logout patterns helps the appliance determine if and when a user has actively logged out of their application. Being aware of a user that actively logs out, compared to waiting for a timeout period to be reached, means the user session is written to the User Sessions Log more quickly than it would be otherwise. This can assist with the troubleshooting of user issues in real time.
In the Logout Patterns section, you can enter a regular expression (e.g., .*logout.*) that matched against the URL that the user is accessing. If the user accesses a page that matches any of the defined logout patterns
(in this example, https://company.com/app/sessions?logout=true), the user session is considered terminated and the record is written to the database.
The list of logout patterns updates to include your addition.
Select the check boxes that correspond to the expressions you would like to remove, then click the Delete button.
Some applications embed session identifiers in the path of a URL. For example the following URL:
http://yoursite/yourpage.asp/234agt438c3k/index.html
uses 234agt438c3k as the session identifier.
For general information on how transformations are performed on the path portion of URLs, see Defining path rules. For specific information, see Managing variable rules.
