Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - Installation and Administration Guide

Installing and configuring Multi-appliance clusters Configuring the appliance Specifying monitored web traffic Transforming monitored URLs Managing applications Foglight components and the appliance Using the console program Troubleshooting the appliance Appendix: Third party software Appendix: Dell PowerEdge system appliance

Extensions

To view all extensions that are used by your site for different purposes, navigate to Configure > URLs > Advanced Options and click Extensions. The Advanced Options > Extensions page lists all hits, by their extension, that the appliance is configured to recognize.

Figure 73. Advanced Options: Extensions page

Content types are divided into categories and include:

•
active extensions (such as PHPs and JSPs)
•
static extensions (such as JARs and class files)
•
image extensions (such as PNG tunes and GIF files)
•
audio extensions (such as MIDI tunes and WAV files)
•
video extensions (such as MPEG and RealMedia)
•
document extensions (such as text files or PDFs)

These lists assist the appliance in differentiating between a Page and a Hit. If you discover URLs that are not appearing in the correct category, you may need to add some items to these lists.

The image, video, and static extension lists ensure that URLs with those extensions are treated as Hits. The document extension list ensures that URLs with those extensions are treated as Pages. URLs on the active extensions list will be treated as Pages unless a consistent pattern is observed where the URL is accessed after another active URL and refers back to that same active URL. If this occurs, the URL is treated as a Hit of the previous URL.

To add an additional extension, simply enter it in the appropriate category’s text entry box, then click Add. When you have finished adding all new extensions, click Apply to return to the main URLs page.

To remove an extension, select its corresponding check box, then click Delete.

Response codes

To identify HTTP response codes that should be excluded from the HTTP Fault Log, navigate to Configure > URLs > Advanced Options and click Response Codes. The Advanced Options > Response Codes page allows you to define HTTP response codes that should be ignored in the HTTP Fault log.

Figure 74. Advanced Options: Response Codes page

Type the code in the box and then click Add. Once configured, faults with the response codes you defined will no longer appear in the HTTP Fault log.

 

Managing applications

The Foglight Experience Monitor’s configuration options include those that allow you to customize how the appliance monitors and analyzes network traffic. This section explains how you can define and manage services, applications, application components, and SOAP transactions.

For more information, see these topics:

•
Integrating with CA SiteMinder
•
Integrating with SafeNet Hardware Security Modules (HSMs)
•
Managing application components
•
Managing services definitions
•
Monitoring Microsoft Office SharePoint Servers
•
Monitoring PeopleSoft applications
•
Monitoring Siebel applications
•
Monitoring SOAP applications
•
Configuring enterprise-wide service levels

Integrating with CA SiteMinder

CA SiteMinder is a centralized web access management system that enables:

•
user authentication and single sign-on
•
policy-based authorization
•
identity federation
•
auditing of access to web applications and portals.

The SiteMinder Policy Server is a SiteMinder component that provides authorization and authentication services to applications. To monitor applications that utilize SiteMinder, you need to configure Foglight Experience Monitor so that it performs the same type of user authentication with CA SiteMinder that your applications currently perform with SiteMinder.

Applications that utilize SiteMinder identify user sessions through the SMSESSION cookie (at some sites, a different cookie name may be used). If your application relies solely on this cookie to identify user sessions, you need to configure the appliance to work with your SiteMinder installation. Failure to setup the configuration means that your appliance cannot correctly identify user sessions resulting in inaccurate metrics. If your application has other means of identifying user sessions, such as using the JSESSION cookie variable, that are independent of SiteMinder, you should not configure the appliance to access SiteMinder.

 
* 
NOTE: Foglight Experience Monitor supports SiteMinder version 6.0 with Service Pack 5.

For more information, see Communicating with SiteMinder.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating