Configuration

Intercept uX Management Console

The Intercept uX Management Console resides on the monitored web application server(s). It is used to add applications for client-side monitoring, configure data collection and provide access to the Application Code Scan utility to ensure that applications can be properly monitored.

The Intercept uX Management Console is not applicable for executable applications and windows services, because they have no client side component.

To open the Configuration Utility, go to:

Overview

The Intercept uX Management Console is not applicable for executable applications and windows services, because they have no client side component.

Main window tree view

The left pane is the console tree and contains the list of web applications configured for uX monitoring.

Main window Properties and Values

Display name: The 'Display Name' serves as an alias for the application name that uniquely identifies an application in all phases of monitoring, from configuration to monitoring, viewing and reporting in SEViewer. The default display name is the IIS property 'Application name' for web applications. This value is the same as displayed in the Intercept MMC.
Application path (Collector node only): This value is the same as displayed in the Intercept MMC.
Server Side Monitoring:

Server-side monitoring is configured in the Intercept MMC:

ON when server monitoring is enabled

OFF when server monitoring is disabled for w3wp

Client Side Monitoring:

The client-side monitoring status is configured in the Intercept uX MMC:

ON when client side monitoring is enabled

Off when client side monitoring is disabled for w3wp

Monitoring Mode:

This value only appears when monitoring is switched on.

Statistic when Intercept uX collects performance counters for the client portion of the monitored application.

Full when Intercept uX collects client side performance counters and report on performance events and exception events for the client portion of the monitored application

Event collection:

Event collection is dependent on whether or not server side monitoring is enabled. Intercept uX events (AJAX, OnClick, etc.) will be collected only if monitoring is enabled both on server side from the Intercept MMC (the current setting is viewable on this screen under 'Server Side Monitoring') and on the client side (the current setting is viewable on this screen under 'Client Side Monitoring'). When both the server and client sides are enabled, the 'Event Collection' field will display 'ON'.

For Statistics (performance counters), since the agent and collector are on the same computer (see "Deployment"), both client side and server side monitoring must be enabled to collect performance counters.

Enabled when Intercept uX monitoring collects and sends events because monitoring is turned off for both the server and Intercept uX

Disabled when Intercept uX monitoring does not collect or send events because monitoring is turned on for both the server and Intercept uX

General Properties

Monitoring Status

Enable Monitoring: Selecting this checkbox will enable client side collection of performance counters, exception events, performance events and statistic events. Checking this field will allow you to set specific monitoring parameters for specific application.. Please read the "Event Collection" description under "Main window Properties and Values" to understand how server side monitoring and deployment affect counter and event reporting. [default = unchecked]
Monitoring Mode: This value can be:

Statistic: Intercept uX collects and reports statistical counters for the monitored application and reports on performance problems and exceptions events. These problems are counted as part of the statistics reporting, and are not sent to SE-Viewer with details as they are in full monitoring mode.

Full: Intercept uX collects and reports statistical counters for the monitored application, and reports on performance events and exception events for the client portion of the monitored application. In full monitoring mode, the performance and exception events provide extensive details about the problem that occurred including the full call stack, global variables, nested AJAX calls, etc.

None: Client side monitoring is disabled (i.e., when the 'Enable Monitoring' box is not checked)

[default = NONE]

Change Mode...: This button opens a dialog for selecting either Statistic Mode or Full Mode

Change Mode dialog

Statistic Mode: In Statistic Mode the agent will collect performance characteristics for the client-side portion of the monitored application.

Full Mode: In Full Mode the agent will collect client side performance characteristics and report on performance degradation and exception events for the client-side portion of the monitored application.

Collector Settings

Use Specified Collector: This checkbox allows you to override the settings inherited from the level above. [default = unchecked]
Address Field: Defines the path to event collector service. Note that this URL may be modified to use a non-default port number or https, but it must always point to the CsmCollectorService.asmx web service with an address that is formatted as an absolute path:

http[s]://servername.domainname[:port]/CsmCollectorService.asmx

or as a relative path (relative to the monitored application)

[..]/[folder path]/CsmCollectorService.asmx

[default = http://localhost/CsmCollector/CsmCollectorService.asmx]

The default URL is where the Collector Configuration Utility has deployed the CSM Collector application (CSMCollectorService.asmx) under the website.

Test Connectivity...: Connectivity to the Collector service may be manually checked by clicking on Test Connectivity. this functionality is only available for absolute paths.

Monitoring Resource Settings

Use Specified Monitoring Resources: This checkbox allows you to override the settings inherited from the level above. [default = unchecked]
Address Field: Intercept uX has resource files (scripts, images, etc.) used by the Collector that are installed by default to:

[drive]: \Program Files\AVIcode\CSMCollector\[version-number]\Web

If this folder is not accessible or there is a need to host the included files in another location (separate server, site, virtual directory, etc.), a new location may be specified via the address field.

To set up a new virtual directory:

Copy the [drive]: \Program Files\AVIcode\CSMCollector\[version-number]\Web folder to the new location
Create a virtual directory in IIS, and point it to the new location
Set the address field to http://[servername]' .[domainname]' :[portnumber]' /[virtual-dir-name]

Performance Settings Properties

Thresholds define if client side performance events will be sent and what information they will contain.

Performance Monitoring

Page Load Threshold (ms): The Monitor sends a performance event when a page load time exceeds the 'Page Load Threshold'. [default = 30000 ms for the uX Management Pack, 15000 ms for the uX Cartridge]
Sensitivity Threshold (ms): Synchronous Ajax call details will be collected when an AJAX total time exceeds the Sensitivity Threshold (ms)'. [default = 3000 ms for the uX Management Pack, 3000 ms for the uX Cartridge]
Ajax/WCF Threshold (ms): The Monitor sends a performance event when an AJAX call time exceeds the 'Ajax/WCF Threshold (ms)' [default = 5000 ms for the uX Management Pack and uX Cartridge]

Filters Properties

This tab contains the list of configured filter groups. Filter groups allows configuring specific monitoring settings for specific types of pages and requests (based on selected parameters). Each filter group is comprised of several filters. Monitoring settings (thresholds, mode, etc.) are applied if an event satisfies all filters in the group.

Filter Group Class Type Icon: This column indicates whether a Filter Group is "Settings" Group ( ) or a "Deny" Group ()
Type: This column indicates Request filter (check properties of request), Response filter (check properties of response), or Stream filter (check response stream)
Filter Group Name: The user-defined name of a filter group.
Add "Deny" Group...: "Deny Group" filters omit client-side monitoring for clients that meet the filter group criteria
Add "Settings" Group...: "Settings Group" filters apply monitoring settings to clients that meet the filter group criteria
Edit...: These buttons open a dialog for modifying filter groups
Remove: Remove the selected Filter group from the list.
Arrow buttons: Filter groups are applied from top of the list to the bottom. To move filter groups, buttons with arrows are used.
Clear All: This button removes all filter groups.

Adding or Editing "Deny" Groups

"Deny Group" filters omit client-side monitoring for clients that meet the filter group criteria

Clicking the Add "Deny" Group... button, or selecting the Edit... button for a "Deny" filter, will open the Deny Filter Group dialog. The dialog displays:

Name: A user-defined name for the Deny group
Operator dropdown: Whether to "AND" all filters in group or "OR" all filters in group
Filter List: The list of all filters included in the group. The columns display the Argument (what to compare), Compare Type (how to compare), and Value (compare to what)
Remove: Remove the selected Filter from the filter group.
Arrow buttons: Filters are applied from top of the list to the bottom. To move filter s, buttons with arrows are used.
Clear All: This button removes all filters in the group.
Add Filter...: This buttons opens a dialog to add filters of the following types:

IP Mask
Page name
Request Header
Request Form,
Query String
Http Method (Get or Post)
MVC Check
MVC Route Data
User Name
Tenant
Content Type
Content Encoding
Status Code
Buffer (stream)

Filters are constructed from differing fields, depending on what filter is being constructed. Users can configure unique monitoring parameters for cases when a particular user name (or request form, query string, etc.) equals (doesn't equal, starts with, matches regular expression, etc.) a selected value. Most filter dialogs will contain these fields:

Argument: What to compare.
Compare Type: How to compare
Value: Compare to what

Adding or Editing "Settings" Groups

"Settings Group" filters apply monitoring settings to clients that meet the filter group criteria

Clicking the Add "Settings" Group... button, or selecting the Edit... button for a "Settings" filter, will open the Settings Filter Group dialog. The dialog displays:

Name: A user-defined name for the Deny group
Operator dropdown: Whether to "AND" all filters in group or "OR" all filters in group
Filter List: The list of all filters included in the group. The columns display the Argument (what to compare), Compare Type (how to compare), and Value (compare to what)
Remove: Remove the selected Filter from the filter group.
Arrow buttons: Filters are applied from top of the list to the bottom. To move filter s, buttons with arrows are used.
Clear All: This button removes all filters in the group.
Monitoring Mode...: This option allows you to set the monitoring mode for any clients that meet the filter criteria. Client's may be set to either Statistic Mode(uX will send information about images, scripts, HTC files etc., and the agent will collect performance counters for the client portion of the monitored application), or Full Mode (uX will send information about application performance and exceptions, and the agent will collect client side performance counters and report on performance events and exception events for the client portion of the monitored application)
Performance Settings...: This button opens the 'Performance Settings' dialog (see 'Performance Settings Properties' above)
Add Filter...: This buttons opens a dialog to add filters of the following types:

IP Mask
Page name
Request Header
Request Form,
Query String
Http Method (Get or Post)
MVC Check
MVC Route Data
User Name
Tenant
Content Type
Content Encoding
Status Code
Buffer (stream)

Argument: What to compare.
Compare Type: How to compare
Value: Compare to what

Data Collecting Properties

This tab allows you to configure additional data that should be collected in events. Use the "On/Off" column to select items to be collected:

Images
Scripts
CSS
HTC (Note that HTC behaviors will be collected only if CSS collection is enabled)
Global variables
Exception stack

Client IP Properties

This tab is used to configure collecting the correct IP address from the host from the header when it has been modified by a proxy or firewalls. By default, all filters on this tab are disabled.

Name: A user-defined name for the property

The default values are:

"AKAMAI" , "True-Client-IP", not enabled

"RFC" , "X_FORWARDED_FOR", not enabled

"Netscape/iPlanet", "X-Client-IP", not enabled

"Cisco/NAT", "x-forward", not enabled

Argument: The header name/key where the address is hidden
Add/Edit...: These buttons open a dialog for creating and modifying IP Client properties

Add/Edit Settings Dialog

Name: A user-defined name for the property

Argument: The header name/key where the address is hidden

Enable: This field allows you to enable one of the predefined arguments or enable a custom argument

Clear All: This button removes all Client IP settings

Sampling Properties

This tab is used to configure the collection frequency for statistics, performance violations and exception events. Note that decreasing the frequency N will increase the amount of network traffic.

When sampling is enabled, Network and Server times might not be collected.

Limit statistics collection to every N-th page: Select to collect all exception and performance events, but to decrease statistics collection to every N-th page. This is the default mode.
Limit statistics, exception event, and performance violation collection to every N-th page: Select to decrease statistics, exception event and performance event collection to every N-th page.where N:: Set N to be the sampling frequency. Setting N=1 effectively disables sampling and will cause data to be collected for every page. [default = 10]

Collector Configuration Utility

The Collector Configuration Utility allows managing the uX Collector IIS Virtual Directory (“CSMCollector”) installation across Web Sites on the Web Server. The primary scenario for uX Monitoring is specifying a relative path to uX Collector on the Application Web Server, and deployment IIS structure of the uX Collector under the Web Sites selected for uX monitoring. The utility provides a list of Web Sites detected on the Application Web server and the ability to install the uX Collector IIS structure under the selected sites.

Web Sites Tab

Web Site Management

On / Off: Choosing the web site(s), the uX Collector is to be installed under. [default = unchecked]

Check all: Choosing all the web sites for installing the uX Collector under.

Uncheck all: Choosing all the web sites to remove the uX Collector from.

Web Site Information

Web Site: Shows the site properties for:

Root Application Pool
Collector Application Pool
Collector Physical Path

Last update: Thursday, December 09, 2010 02:42:42 PM