Advanced Configuration

AJAX Calls in Statistical Mode

By default, when Intercept uX is configured for monitoring in Full Mode, AJAX calls will be distinguished from other calls on the server side. If uX monitoring is disabled or configured for Statistical Mode however, is still possible to distinguish AJAX calls on the server side. Please see please see AVIcode Intercept Studio User Manual Advanced ConfigurationOperations Monitor 2.0 Default Configuration File (PMonitor2_0.default.config)

Disabled Content

For this section you may either use the Intercept uX Management Console, and edit the Data Collecting properties, or manually edit the uX configuration file. To access the file:

Access the server with the monitored applications and monitoring agent
Close all instances of the Intercept uX Management Console
Navigate to [drive]\Program Files\AVIcode\Intercept\Agent\[version-number]\Configuration\Standard\CSM.action.config Please note that on x64 installation, the server agent and its associated configuration files may be found under "Program Files ", while other components will be under "Program Files (x86)"

The disabledContent flag determines which content is disabled from collection. Default value = 63 (means that all are disabled). The flag's values may be set to:

0 - all content is collected
1 - images are disabled
2 - scripts are disabled
4 - CSS are disabled (this is the default value)
8 - htc are disabled
16 - global variables are disabled
32 - exception stack is disabled

Bitwise combination of these flags is also supported. For example:

To disable collecting both images and CSS use value 5 (= 1+4)
To disable collecting images, scripts and CSS use value 7 (= 1+2+4)

In order to collect CSS, images and scripts, edit the file as in the following example:

Before:

<ss:appdomains

minorPageLoadTime="1000"

majorPageLoadTime="10000"

calcLinkedContentUsingAjax="true"

collectHtc="false"

include="false"

includeStatistic="false"

includeProblem="false"

statisticsSampling="10"

samplingMode="Statistics"

scriptsVersion=""

disabledContent="4">

...

After:

<ss:appdomains

minorPageLoadTime="1000"

majorPageLoadTime="10000"

calcLinkedContentUsingAjax="true"

collectHtc="false"

include="false"

includeStatistic="false"

includeProblem="false"

statisticsSampling="10"

samplingMode="Statistics"

scriptsVersion=""

disabledContent="0">

...

Collecting Tenant Information

For this section you must manually edit the uX configuration file. To access the file:

Access the server with the monitored applications and monitoring agent
Close all instances of the Intercept uX Management Console
Navigate to [drive]\Program Files\AVIcode\Intercept\Agent\[version-number]\Configuration\Standard\CSM.action.config Please note that on x64 installation, the server agent and its associated configuration files may be found under "Program Files ", while other components will be under "Program Files (x86)"

By configuring the path to tenant variable in the HttpContext, Intercept uX will extract it while monitoring, and pass the internal business context to both the uX and server agent events.

When updating the configuration file to include tenant information, be sure to set the value of "tenantPathCount" to the number of tenant paths being added as in this example:

<ss:dataProviderSettings>

...

<ss:add name="tenantPathCount" alias="tenantPathCount" value="2" include="true" />

<ss:add name="tenantPath1" alias="test" value="1/System.Web.HttpContext::Request/System.Web.HttpRequest::Headers/System.Collections.Specialized.NameValueCollection" include="true" />

<ss:add name="tenantPath2" alias="test" value="1[Tenant_Header]/System.String " include="true" />

...

</ss:dataProviderSettings>

Also note that the alias does not have to be unique, but the name of the tenant path does need to be unique:

<ss:dataProviderSettings>

...

<ss:add name="tenantPathCount" alias="tenantPathCount" value="2" include="true" />

<ss:add name="tenantPath1" alias="test" value="1/System.Web.HttpContext::Request/System.Web.HttpRequest::Headers/System.Collections.Specialized.NameValueCollection" include="true" />

<ss:add name="tenantPath2" alias="test" value="1[Tenant_Header]/System.String " include="true" />

...

</ss:dataProviderSettings>

Follow the appropriate sections below for examples of extracting tenant information from request headers, session variables or form variables.

Tenant Extraction from Request Headers

In order to collect tenant information from the HTTP Request Header, edit the file as in the following example (assuming that Tenant is stored in the Request Header called “Tenant_Header”)

<ss:dataProviderSettings>

...

<ss:add name="tenantPathCount" alias="tenantPathCount" value="2" include="true" />

<ss:add name="tenantPath1" alias="test" value="1/System.Web.HttpContext::Request/System.Web.HttpRequest::Headers/System.Collections.Specialized.NameValueCollection" include="true" />

<ss:add name="tenantPath2" alias="test" value="1[Tenant_Header]/System.String " include="true" />

...

</ss:dataProviderSettings>

Tenant Extraction from Session Variables

In order to collect tenant information from the HTTP SessionVariable, edit the file as in the following example (assuming that Tenant is stored as an element value (accepted by the key “current_network_id”) of a Hashtable located in a session variable called “Enterprise.ApplicationState” as a value (accepted by key “MemberContext.MEMBER_CONTEXT”)

<ss:dataProviderSettings>

...

<ss:add name="tenantPathCount" alias="tenantPathCount" value="3" include="true" />

<ss:add name="tenantPath1" alias="test" value="1/System.Web.HttpContext::Session[Enterprise.ApplicationState]/System.Collections.Hashtable" include="true" />

<ss:add name="tenantPath2" alias="test" value="1[MemberContext.MEMBER_CONTEXT]/System.Collections.Hashtable" include="true" />

<ss:add name="tenantPath3" alias="test" value="1[current_network_id]/System.Object" include="true" />

...

</ss:dataProviderSettings>

Tenant Extraction from Request Form Variables

In order to collect tenant information from the HTTP Request Form Variable, edit the file as in the following example (assuming that Tenant is stored in a Request Form Variable called “Tenant_Form”)

<ss:dataProviderSettings>

...

<ss:add name="tenantPathCount" alias="tenantPathCount" value="2" include="true" />

<ss:add name="tenantPath1" alias="test" value="1/System.Web.HttpContext::Request/System.Web.HttpRequest::Form/System.Collections.Specialized.NameValueCollection" include="true" />

<ss:add name="tenantPath2" alias="test" value="1[Tenant_Form]/System.String " include="true" />

...

</ss:dataProviderSettings>

Excluding Functions from Runtime Duration Monitoring

For this section you must manually edit the uX configuration file. To access the file:

Access the server with the monitored applications and monitoring agent
Close all instances of the Intercept uX Management Console
Navigate to [drive]\Program Files\AVIcode\Intercept\Agent\[version-number]\Configuration\Standard\CSM.action.config Please note that on x64 installation, the server agent and its associated configuration files may be found under "Program Files ", while other components will be under "Program Files (x86)"

Intercept uX provides ability to define the signatures of JavaScript functions whose runtime duration will be excluded from the duration of the monitored bounding (outer function) scope.

Edit the file as follows:

<ss:excludes>

<ss:exclude name="window.alert" paramCount="1" isSystem="true" />

<ss:exclude name="window.prompt" paramCount="2" isSystem="true" />

<ss:exclude name="window.confirm" paramCount="1" isSystem="true" />

<ss:exclude name="your_function" paramCount="num" isSystem="false" />

</ss:excludes>

Where:

your_function = your custom function name

num = the number of function parameters in your custom function

isSystem = a Boolean flag that should always be set to false for custom functions

Collecting User Clicks on Page Controls

For this section you must manually edit the uX configuration file. To access the file:

Access the server with the monitored applications and monitoring agent
Close all instances of the Intercept uX Management Console
Navigate to [drive]\Program Files\AVIcode\Intercept\Agent\[version-number]\Configuration\Standard\CSM.action.config Please note that on x64 installation, the server agent and its associated configuration files may be found under "Program Files ", while other components will be under "Program Files (x86)"

To Enable Click Events uncomment the following section

<!--

<ss:add controlTagName="input" eventName="onclick" eventAliasName=".OnClick()"/>

<ss:add controlTagName="img" eventName="onclick" eventAliasName=".OnClick()"/>

<ss:add controlTagName="a" eventName="onclick" eventAliasName=".OnClick()"/>

<ss:add controlTagName="a" eventName="href" eventAliasName=".href-javascript:(...)"/>

<ss:add controlTagName="td" eventName="onclick" eventAliasName=".OnClick()"/>

<ss:add controlTagName="span" eventName="onclick" eventAliasName=".OnClick()"/>

-->

Enabling Multiple Subnets

To enable two separate subnets for monitoring, add only one filter group that disables monitoring for everything except these two subnets. Therefore the system will check the condition “If User’s IP is not in subnet1 and User’s IP is not in subnet2" then disable monitoring.

Go to:

Start

Programs

AVIcode Intercept Studio

Intercept Configuration

Intercept uX Management Console

Create the filter group
Add an IP Address filter with Compare Type = Not in Subnet for the first subnet
Add an IP Address filter with Compare Type = Not in Subnet for the second subnet
Set filter group settings under the Monitoring Status group box to disable monitoring (disable the "Enable Monitoring" checkbox)

Move this new filter group to the top of Filter Group list.

uX IP Filtering

This section describes how to filter for particular client IP addresses in Intercept uX.

Adding IP 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 a request/response satisfies all filters in the group.

Each filter has “action”, either "allow" or "deny" (Allow/Deny) attribute, meaning that settings are applied either to pages/requests whose parameters (page names, IP addresses, User name, tenant or other request and response parameters) match the filter (Allow), or to pages/requests whose parameters do not match the filter (Deny).

Using the Intercept uX Management Console

To add IP Filter Groups using the Intercept uX Management Console:

Go to:

Start

Programs

AVIcode Intercept Studio

Intercept Configuration

Intercept uX Management Console

Right-click either the Web Applications node or a particular Web Application and select the "Properties" menu option.
Go to the "Filters" tab
Click "Add…"
Click "Add Filter…", and select "IP Address…" from the submenu
In the "Value" field, set the value of the IP address and the subnet mask that you want to use separated by a forward slash. For example, 192.168.0.123/255.255.255.0 [Note that this value must be formatted based on whether or not you have selected the "Use IPv6" checkbox].
In the "Compare Type" field, select whether the configuration override settings will apply to IP addresses which meet fall within this IP range (Compare Type = "In Subnet") or IP addresses which fall outside of this IP range (Compare Type = Not in Subnet).
Click "OK"
Set the override values using the options described under "Setting Override Values for IP Filtering"
Click "OK"

Setting Override Values for IP Filtering

Please note that the annotations on the screenshots refer to parameters in the CSM.action.config file.

Go to:

Start

Programs

AVIcode Intercept Studio

Intercept Configuration

Intercept uX Management Console

Monitoring Mode Properties

"Statistic Mode" [includeStatistic true/false to enable statistics monitoring (applied only if 'include' = true)]: 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 Mode" [includeProblem true/false to enable both exception and performance monitoring (applied only if 'include' = true)]: 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.

Performance Settings Overrides

"Page Load Threshold (ms)" [majorPageLoadTime]: The Monitor sends a performance alert when a Page Load time exceeds the 'Alerting Threshold'. [default = 10000 ms]
"Sensitivity Threshold (ms)" [minorPageLoadTime]: Client side JavaScript function details are collected when a function's execution time exceeds the 'Sensitivity Threshold (ms)'. [default = 1000 ms]
"Ajax/WCF Threshold (ms)": The Monitor sends a performance alert when an AJAX call time exceeds the 'Ajax/WCF Threshold'.

Last update: Thursday, December 09, 2010 12:46:40 PM