Asset Vision®Asset Vision® OptimizeAgent ConfigurationHow to Configure Agent Web Application Tracking

How to Configure Agent Web Application Tracking

Web Application (Web App) Tracking allows for usage tracking by minutes and keystrokes for all defined Web Applications.  WebApp tracking differs from Web Domain discovery as the former tracks actual usage and the latter only tracks URL hit counts. Note: In order for a Web App to be tracked on a device, the device must have an Asset Vision agent installed and an Asset Vision web browser extension installed.

Web App Tracking

The Web App Tracking page above controls the enabling and disabling of the Web App tracking feature.

Usage will only be tracked for Web Apps that have been defined using an old-style pattern (ex: *.domain) or a regular expression.

Web App Definitions

Users may choose to manually create a Web App definition by clicking on the New button above. Users may also create a Web App from a URL/domain name that has already been discovered by Web Domain Discovery. To do this, by click on the Discovered button. A "Pick up domain to track" window will appear like below. Users will see a list of domain names that have been discovered as being used in their environment. Select one to automatically create a web application based on that domain name.

Furthermore, users may choose to create a Web App or from a library of pre-defined Web Apps available from Scalable Software's Chaklun database. Selecting one or more of these example entries below allows a Web App definition to be created and tracked.

Pressing the Update from Library button, as seen below from the Web App Definitions page, will manually update existing Chaklun-derived web application definitions with any updates available.

Patterns for Web Apps

Users can define a Web App from patterns in the URL and also optionally from text in the browser tab name and even the URL icon (referred to as a favicon) delivered to a browser tab.

Multiple Patterns for Web App

Multiple URL Patterns per Application

Multiple URL Patterns per Application

Multiple URL patterns can be defined for a given Web App to account for variations.  Click the plus (+) button located to the right of the text input box to add additional values. To delete a pre-existing line, click the minus (-) button next to it.

An Example of a Web App's Properties

This is an example of a filled form for a Web App's properties. The optional fields in the advanced section allow the user to create even more specific patterns that can match a document used by Office 365.

In this way complex patterns can be constructed to accurately identify specific aspects of a Web App. 

The fields where the regex can be entered include:

  • URL Patterns: Pattern found in the URL in the web browser.
  • Tab Caption Patterns: Pattern found in the caption of the web browser tab.
  • Favicon Patterns: Pattern found in the icon name located on the tab.

If the user wants to track a specific document made with Office 365 or Google Apps they can fill out the optional advanced section of the Web App Properties.

NOTE: Once a Web App is created, it cannot be deleted. The URLs associated with each Web App maybe modified and/or deleted as desired. Deleting all associated URLs defined in a Web App will render the Web App useless, thus no usage tracking for it will be done.

In addition, Asset Vision contains predefined definitions for the key elements of both Office365 and Google Docs. Asset Vision DOES NOT install the Office365 and Google Docs definitions by default. If you would like to install these Web App definitions, check the Enable Advanced Tracking checkbox and click Save at the bottom.

NOTE: As with any Web App, once they are installed/created, they cannot be deleted.

Advanced Web App Properties

Advanced Properties

The advanced section in the Web App definition optionally allows further patterns to be defined to extract information about the URL or tab relating to a document being worked on.

The patterns defined allow a document to be identified from any combination of Document name, GUID and the domain of the document provider, searched for in either the page URL or document tab name.

The data collected by these patterns, if defined, is stored in the cmdb_webapp_document and cmdb_window_audit tables in Asset Vision.

A user can easily add their own definitions for other web applications using these features.