Application event tracing

• US 10,241,845 B2
• Filed: 02/27/2015
• Issued: 03/26/2019
• Est. Priority Date: 02/27/2015
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: entIT Software LLC (Open Text Corporation)
• Inventors: Israeli, Aviad, Shershevsky, Olga, Gazit, Oded
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US15/507,404
• Publication Number:
  US 20170286191A1
• Time in Patent Office: 1,488 Days
• CPC Class Codes: G06F 11/3452 Performance evaluation by statistical analysis
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

Examples disclosed herein relate to a system for generating an element identifier comprising an action engine to identify at least one event listener associated with a significant event in an application, receive an action associated with an element of the application, generate a composite event sequence comprising a plurality of event listeners associated with the action, and determine whether the composite event sequence is associated with the at least one significant event. The system may further comprise a metric engine to measure a performance metric associated with the received action and create a log record according to the composite event sequence comprising the performance metric.

Claims

1. A system for application event tracing comprising:

a processor; and

a memory storing instructions that when executed cause the processor to;

identify a first event listener associated with a significant event in an application,

insert a dummy action handler to a second event listener associated with the application to cause the second event listener to be called by the application when an action associated with the first event listener is received,

receive the action associated with the first event listener,

in response to receiving the action associated with the first listener, generate a composite event sequence comprising the first and second event listeners associated with the action, and

determine whether the composite event sequence comprises the first event listener associated with the significant event; and

in response to determining that the composite event sequence comprises the first event listener associated with the significant event;

measure a performance metric associated with the action, and

create a log record according to the composite event sequence, the log record comprising the performance metric.

2. The system of claim 1, wherein the processor is to identify that the first event listener is associated with the significant event based on whether the first event listener includes a non-default action handler.

3. The system of claim 1, wherein the processor is to generate the composite event sequence based on an initial event of the action.

4. The system of claim 3, wherein the processor is to generate the composite event sequence further based on an end event of the action.

5. The system of claim 3, wherein the processor is to generate the composite event sequence further based on an expiration of an idle timer.

6. The system of claim 1, wherein the processor is to add the dummy action handler to the second event listener after identifying that the second event listener is associated with a non-significant event.

7. The system of claim 6, wherein the processor is to identify that the second event listen is associated with the non-significant event based on a determination that the second listener includes a default action handler.

8. The system of claim 1, wherein the action associated with the element of the application comprises an interaction between a user and an interface of the application on a display device.

9. A non-transitory machine-readable storage medium including instructions which, when executed by a processor, cause the processor to:

identify a first event listener of a plurality of event listeners as a significant event listener associated with an application;

add a dummy action handler to a second event listener of the plurality of event listeners to cause the second event listener to be called by the application when an action associated with the first event listener is received, wherein the second event listener of the plurality of event listeners is a non-significant event listener;

receive the action associated with the first event listener;

in response to receiving the action associated with the first event listener, generate a composite event sequence comprising the first event listener and the second event listener;

measure a performance metric associated with the action; and

create a log record comprising the performance metric, wherein the log record is associated with the composite event sequence.

10. The non-transitory machine-readable storage medium of claim 9, wherein the measured performance metric associated with the action comprises an amount of time taken to complete the action.

11. The non-transitory machine-readable storage medium of claim 9, wherein the instructions to identify the first event listener as the significant event listener associated with the application comprise instructions to determine whether each of the plurality of event listeners comprises a non-default action handler.

12. The non-transitory machine-readable storage medium of claim 11, wherein the non-default action handler comprises an application function override of a default action handler.

13. The non-transitory machine-readable storage medium of claim 9, further comprising instructions to:

receive a second action associated with the second event listener of the plurality of event listeners;

measure a second performance metric associated with the second action,

create a second log record associated with the composite event sequence comprising the second performance metric; and

associate the second log record to the log record associated with the composite event sequence.

14. The non-transitory machine-readable storage medium of claim 9, further comprising instructions to generate a performance report associated with the application, wherein the performance report consolidates a plurality of log records each associated with the composite event sequence.

15. A computer-implemented method comprising:

identifying, by a processor, a first event listener of a plurality of event listeners associated with an application;

adding, by the processor, a dummy action handler to a second event listener of a plurality of event listeners associated with the application to cause the second event listener to be called by the application when an action associated with the first event listener is received;

receiving a first user action associated with the first event listener;

generating, by the processor, a composite event sequence comprising the first event listener in response to receiving the first user action associated with the first event listener, wherein the first user action triggers a predefined start event;

adding the second event listener of the plurality of event listeners to the composite event sequence based on the dummy action handler of the second event listener;

measuring a respective performance metric for the first event listener and the second event listener, wherein the respective performance metric comprises a time to complete the first event listener and the second event listener; and

creating, by the processor, a log record comprising the respective performance metric, wherein the log record is associated with the composite event sequence.

16. The method of claim 15, further comprising:

closing the composite event sequence in response to one of the following;

an expiration of an idle timer and a receiving of a second user action triggering the predefined start event.

17. The method of claim 15, further comprising:

determining whether the composite event sequence comprises a significant event listener, wherein the significant event listener comprises a non-default and non-dummy action handler;

in response to determining that the composite event sequence comprises the significant event listener, computing a final performance metric comprising a total time to complete the user action based on the respective performance metrics for the first event listener and the second event listener, and adding the final performance metric to the log record associated with the composite event sequence; and

in response to determining that the composite event sequence does not comprise the significant event listener, discarding the respective performance metrics.