What's New in Intercept uX

All AVIcode products are rigorously tested under production conditions for quality, consistency, usability and reliability. AVIcode quality standards and testing are designed to ensure optimal solution use. To that end, AVIcode has also developed a Scalability Assessment Tool to assist in large environment installations. For further information on this tool and AVIcode scalability tests, please contact your AVIcode representative.

Please see the Intercept Studio release notes to learn about other system changes

Version 5.7.491 (5.7 RTM)

Intercept uX Agent and Collector 5.7 can be seamlessly installed upon 5.6 versions of Intercept uX Agent and Collector respectively. Upgrade of Agent and Collector involves partial uX configuration merging that covers the most important settings.

Intercept uX Agent used to add all Server Applications added to p-monitor monitoring as specific applications. In uX 5.7 it was decided to get rid of this automatic configuration update and ability to manually add application in uX Configuration has been added. Then “Add Application” feature was augmented by “Remove Application” option.

The process of adding a new application has been augmented by passing the uX monitoring compatibility check through a special utility – ACS (Application compatibility scan). Once a user adds a new application to uX monitoring, the application is being added into uX configuration in silent mode (monitoring is “on”, but there is a Request “Deny” filter group based on filtering all IP addresses, that disables monitoring of the application requests), and then ACS utility is automatically launched for scanning the application. There are a set of compatibility check rules of different severities (error/warning/information) that are managing how to find incompatibility issues, what to find and how to provide actionable steps for mitigation/resolution (knowledgebase). There is ability to run ACS utility any time afterward an application adding, the command is called via pop-up menu item “Analyze” in Applications Tree View in uX MMC or via “Button “Analyze” in properties window of the application.

Intercept uX Agent 5.7 RC does not allow monitoring of web applications not added to uX configuration specifically.

It is possible to create either “Deny” or “Settings” filter group in uX Agent 5.7.

Filter group of any class (“Deny” or “Settings”) may have conjunctive or disjunctive logic that union filters in the group.

If a monitored page addresses filters defined in a “Deny” filters group, uX monitoring of such a page will be prevented, page will not be instrumented by uX JavaScript code.

If a monitored page addresses filters defined in a “Settings” filters group, uX will apply separately specified monitoring settings for such a page. Monitoring settings are to be changed during passing of all filter groups and result settings to be applied are the settings combined from settings associated with each applied “Settings” filter group.

Filter groups of both classes can be of 3 filter group types: Request, Response or Stream. Group Type defines its own set of possible filters for groups, i.e.: Request Filter Group can contains filters by page name, Response Filter Group can contains filters by user name and Stream Filter Group can contains filters by buffer characters only.

Intercept uX Agent 5.7 monitors MVC-designed pages and extracts MVC Controller and MVC Action parameters for such pages. Also there is an ability to build request filter based on IsMvcRequest flag (means whether page was designed as MVC pattern or not) or specific MVC Controller or MVC Action values.

There is an introduced possibility to specify alerting threshold for asynchronous AJAX calls separately from alerting threshold for monitored page loads. Now Intercept uX Agent 5.7 has UI for setting the threshold. Also there is an option to manage the threshold by means of Intercept uX Scripting Library commands.

uX 5.7 supports operating with criteria that reflects the complexity of monitored page. There are: page size (in bytes), number of defined document images, scripts, style sheets, IE-specific HTC behaviors, global variables. There is ability for user to set quantitative metric - complexity criteria limit per each mentioned metric in order to decide whether monitored page is complex or non-complex in terms of uX. For complex pages uX dramatically decreases possible caused noise and prevents instrumented code from collecting part of data. The most important information still will be collected for such a complex pages. The information that is not collected for complex pages:

- Images list

- Scripts list

- Style sheets list

- HTC behaviors list (applicable for IE browsers only)

- Details of AJAX calls took place while page loading

- Global Variables list

- Call Stack

User is able to choose what type of content/troubleshooting information is required to be collected. Now Intercept uX Agent 5.7 has UI for specifying type(s) of data for collection information about. There are the following data types: defined document images, scripts, style sheets, IE-specific HTC behaviors, global variables, exception call stack.

Also there is an introduced possibility to limit collecting of each kind of mentioned data type by some number (that bounds the count of items (images, scripts, style sheets, IE-specific HTC behaviors, global variables, exception call stack points) passed in cycles along corresponding arrays). The limit settings are configurable and do not have UI for modifying, because considered to be service options.

There is one more configurable options set that is introduced in Intercept uX Agent 5.7 for manageability of produced uX noise and payload on browser side. User is able to define number of characters collected in long strings/texts, number of collected array elements, etc. The settings are configurable and do not have UI for modifying, because considered to be service options.

Intercept uX Agent 5.7 has several issues connected with wrong place of prefix injection fixed. Formerly wrong injection used to cause page to behave incorrectly or even to fail. uX Injector 5.7 has improved logic of tags skippers allows to correctly resolve injection moment questions.

Intercept uX Agent used to have ability of tracing log information in diagnostic mode. In order to manage noise and file operations overhead, we implemented filtering of trace information based on specific client IP/Subnet. Now, only requests come from specific IP or subnet are taken into account for tracing.

Intercept uX Agent has client diagnostic mode with tracing calls of overridden client objects/functions/events (like window.onload, window.showModalDialog, new ActiveXObject(), new XmlHttpRequest(), methods ofXmlHttpRequest and others). Trace entries depending on trace mode are put into either Event Log of uX Collector or Tracing Alert message content. Also there is a tracing into Firebug console add-on of Mozilla Firefox browser.

The client tracing is working only if uX Agent Diagnostics is turned on and is also IP/subnet specific, so only requests that come from specific IP or subnet are taken into account for tracing.

Intercept uX Agent 5.7 RC can collect source code of anonymous stack points on call stack of client JavaScript exception.

Version 5.7.399

Intercept uX Agent and Collector 5.7 can be seamlessly installed upon 5.6 versions of Intercept uX Agent and Collector respectively. Upgrade of Agent and Collector involves partial uX configuration merging that covers the most important settings.

Intercept uX Agent used to add all Server Applications added to p-monitor monitoring as specific applications. In uX 5.7 it was decided to get rid of this automatic configuration update and ability to manually add application in uX Configuration has been added. Then “Add Application” feature was augmented by “Remove Application” option.

Intercept uX Agent 5.7 RC version does not allow monitoring of web applications not added to uX configuration specifically.

It is possible to create either “Deny” or “Settings” filter group in uX Agent 5.7.

Filter group of any class (“Deny” or “Settings”) may have conjunctive or disjunctive logic that union filters in the group.

If a monitored page addresses filters defined in a “Deny” filters group, uX monitoring of such a page will be prevented, page will not be instrumented by uX JavaScript code.

If a monitored page addresses filters defined in a “Settings” filters group, uX will apply separately specified monitoring settings for such a page. Monitoring settings are to be changed during passing of all filter groups and result settings to be applied are the settings combined from settings associated with each applied “Settings” filter group.

Filter groups of both classes can be of 3 filter group types: Request, Response or Stream. Group Type defines its own set of possible filters for groups, i.e.: Request Filter Group can contains filters by page name, Response Filter Group can contains filters by user name and Stream Filter Group can contains filters by buffer characters only.

Intercept uX Agent 5.7 monitors MVC-designed pages and extracts MVC Controller and MVC Action parameters for such pages. Also there is an ability to build request filter based on IsMvcRequest flag (means whether page was designed as MVC pattern or not) or specific MVC Controller or MVC Action values.

There is an introduced possibility to specify alerting threshold for asynchronous AJAX calls separately from alerting threshold for monitored page loads. Now Intercept uX Agent 5.7 has UI for setting the threshold. Also there is an option to manage the threshold by means of Intercept uX Scripting Library commands.

uX 5.7 supports operating with criteria that reflects the complexity of monitored page. There are: page size (in bytes), number of defined document images, scripts, style sheets, IE-specific HTC behaviors, global variables. There is ability for user to set quantitative metric - complexity criteria limit per each mentioned metric in order to decide whether monitored page is complex or non-complex in terms of uX. For complex pages uX dramatically decreases possible caused noise and prevents instrumented code from collecting part of data. The most important information still will be collected for such a complex pages. The information that is not collected for complex pages:

User is able to choose what type of content/troubleshooting information is required to be collected. Now Intercept uX Agent 5.7 has UI for specifying type(s) of data for collection information about. There are the following data types: defined document images, scripts, style sheets, IE-specific HTC behaviors, global variables, exception call stack.

Also there is an introduced possibility to limit collecting of each kind of mentioned data type by some number (that bounds the count of items (images, scripts, style sheets, IE-specific HTC behaviors, global variables, exception call stack points) passed in cycles along corresponding arrays). The limit settings are configurable and do not have UI for modifying, because considered to be service options.

There is one more configurable options set that is introduced in Intercept uX Agent 5.7 for manageability of produced uX noise and payload on browser side. User is able to define number of characters collected in long strings/texts, number of collected array elements, etc. The settings are configurable and do not have UI for modifying, because considered to be service options.

Intercept uX Agent 5.7 has several issues connected with wrong place of prefix injection fixed. Formerly wrong injection used to cause page to behave incorrectly or even to fail. uX Injector 5.7 has improved logic of tags skippers allows to correctly resolve injection moment questions.

Intercept uX Agent used to have ability of tracing log information in diagnostic mode. In order to manage noise and file operations overhead, we implemented filtering of trace information based on specific client IP/Subnet. Now, only requests come from specific IP or subnet are taken into account for tracing.

Intercept uX Agent has client diagnostic mode with tracing calls of overridden client objects/functions/events (like window.onload, window.showModalDialog, new ActiveXObject(), new XmlHttpRequest(), methods ofXmlHttpRequest and others). Trace entries depending on trace mode are put into either Event Log of uX Collector or Tracing Alert message content. Also there is a tracing into Firebug console add-on of Mozilla Firefox browser.

The client tracing is working only if uX Agent Diagnostics is turned on and is also IP/subnet specific, so only requests that come from specific IP or subnet are taken into account for tracing.

Intercept uX Agent 5.7 RC can collect source code of anonymous stack points on call stack of client JavaScript exception.

Version 5.6.515

This release is a refresh of Intercept uX Version 5.6.513. Please see the 5.6.513 notes for details.

Version 5.6.513

What's New

- Close the Intercept MMC;

- Navigate to [drive]:\Program files\AVIcode\Intercept\Agent\vX.X.XX\Configuration\Standard;

- Open PMonitor.config for editing;

- Change the "supportedFramework" to <ss:supportedFramework max="4.0.99999.9999"/>

- Save the file and restart application monitoring;

- Do the same with other Agents installations.

Version 5.6.264

What's New

Version 5.6.248

What's New

 

If the click occurred on an Image, where: the element is defined with the tag <img> or the element is defined with the tag <input> with the specified attribute Type = "image", then the set of the element’s properties is:

The following information is collected for Asynchronous AJAX Calls that occurred during page loading:

Pop-ups whose duration is excluded from the monitored scope in default configuration:

Version 5.5.75 Hotfix

What's Fixed

Version 5.5.61

What's New

Last update: Friday, December 10, 2010 12:02:26 PM