Distributed capture and aggregation of dynamic application usage information

• US 8,135,827 B2
• Filed: 04/07/2008
• Issued: 03/13/2012
• Est. Priority Date: 07/12/2005
• Status: Active Grant

• Current Assignee: Acuityads
• Original Assignee: Visible Measures Corp. (AcuityAds Holdings, Inc.)
• Inventors: Wilson, Andrew S., Shin, Brian J., Angel, David
• Primary Examiner(s): Patel, Haresh N
• Application Number:
  US12/098,579
• Publication Number:
  US 20100030785A1
• Time in Patent Office: 1,436 Days
• Field of Search: 709217-228, 709200-203, 719/311, 719/328, 714/2, 714/25
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

A web-based hosted solution through which application developers create, manage and monitor application usage analytics in an online manner. Preferably, an application under test is one of: application software, a script-enabled web application, or a rich Internet application (RIA). During the development process, a usage monitoring API is integrated into the application and the application is deployed. As users interact with the application, a log file is generated, typically in one of two ways. If the application is able to write to a local file system (in the user'"'"'s machine), usage information is gathered in a log file local to the deployed application and then dispatched to an upload server for processing in a batch manner. If the application is not able to write to the user machine'"'"'s local file system, the usage information is sent to a remote logging server, preferably on a just-in-time basis, and then the log file is generated on the logging server. In either case, preferably the usage information that is tracked comprises “features,” “faults” and “failures” of the application, independent of platform, location, and number of deployed application instances.

Claims

1. A method of tracking an application that is deployed as a set of application instances, where the application is instrumented with a usage monitoring application programming interface (API) that generates a log file when the application is executed, the log file comprising data associated with a set of application feature executions, failures or faults, wherein the log file data comprises a set of messages associated with the application feature executions, failures and faults, wherein the set of messages are written in a sequential order of the application feature executions, failures and faults, comprising:

operating, at a service provider domain, an Internet-accessible infrastructure, the Internet-accessible infrastructure comprising a web server, an application server, and a database;

receiving, by the web server, log files generated by the instrumented applications, wherein information in at least one log file is encoded in a compact data structure, and wherein at least first and second messages of the set of messages each have timestamps, and wherein the timestamp of the second message is a function of the timestamp in the first message;

processing, by the application server, data aggregated from the received log files; and

storing, in the database, aggregated log data;

exporting, from the database and to a permitted entity, aggregated log data;

where the application is one of;

a server-based application, a web-based application, and a rich Internet application.

2. The method as described in claim 1 wherein the log files are received at the web server via http transport.

3. The method as described in claim 1 wherein the permitted entity is a provider of the application.

4. The method as described in claim 1 wherein the application instances are deployed across a public network and the log files are received from a set of end users that are located throughout the public network.

5. The method as described in claim 1 wherein a log file is generated at an end user machine.

6. The method as described in claim 1 wherein a log file is generated at a gateway server of the Internet-accessible infrastructure.

7. A non-transitory computer storage medium having computer-executable instructions for performing the method steps of claim 1.

8. Apparatus for tracking a web application deployed across a wide area network as the web application is used within local end user web browser environments, where the web application is instrumented with a web application usage monitoring application programming interface (API) that generates a log file when the web application is executed, the log file comprising a set of messages associated with application feature executions, failures and faults, wherein the set of messages are written in a sequential order of the application feature executions, failures and faults, the apparatus comprising:

an Internet-accessible infrastructure operating at a service provider domain, the Internet-accessible infrastructure comprising at least one web server, an application server, and a database, the Internet-accessible infrastructure comprising at least one hardware element;

the web server operative to receive log files generated by the instrumented web applications, wherein information in at least one log file comprises a set of messages encoded in a compact data structure, and wherein at least first and second messages of the set of messages each have timestamps, and wherein the timestamp of the second message is a function of the timestamp in the first message;

the application server operative to process data aggregated from the received log files;

the database operative to store aggregated log data; and

the web server further operative to export, from the database and to a permitted entity, at least a portion of the aggregated log data;

where the web application is one of;

a web page having a browser-enabled script, and a rich Internet application.

9. The apparatus as described in claim 8 wherein the application feature execution data is one of:

a feature failure, and a feature fault.

10. The apparatus as described in claim 8 wherein the Internet-accessible infrastructure includes a login server to authenticate one or more users associated with the permitted entity.

11. The apparatus as described in claim 8 wherein the Internet-accessible infrastructure includes an administrative server to provide an accounting function associated with the web application tracking.

12. The apparatus as described in claim 8 wherein the Internet-accessible infrastructure includes a reporting server to provide a reporting function associated with the web application tracking.

13. The apparatus as described in claim 8 wherein at least a portion of the Internet-accessible infrastructure operates behind a firewall.