# US 2017/0286191 A1 · Application event tracing > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2017/0286191 A1 - Document ID: US20170286191A1 - Status: Published application - Kind: A1 - Application number: 15/507,404 - Filed: 2015-02-27 - Published: 2017-10-05 - Earliest claimed: 2015-02-27 - Assignees: Hewlett Packard Enterprise Development LP - Applicants: Hewlett Packard Enterprise Development LP - Inventors: Aviad Israeli; Olga Shershevsky; Oded Gazit - Web page: https://patentgrep.com/patent/US20170286191A1 ## CPC - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F 11/3452: {Performance evaluation by statistical analysis} - G06F 11/3466: {Performance evaluation by tracing or monitoring} - G06F 11/3636: {by tracing the execution of the program} - G06F 2201/865: Monitoring of software - H04L 43/0876: Network utilisation, e.g. volume of load or congestion level - H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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 ### Claim 1 A system for application event acing comprising: an application 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 comprises the at least one event listener associated with the significant event; and a metric engine to: in response to the application engine determining that the composite event sequence comprises the at least one event listener associated with the significant event: measure a performance metric associated with the received action, and create a log record according to the composite event sequence, the log record comprising the performance metric. ### Claim 2 (depends on 1) The system of claim 1, wherein the application engine is to identify the significant event based on whether a non-dummy action handler has been added to the at least one event listener. ### Claim 3 (depends on 1) The system of claim 1, wherein the application engine is to generate the composite event sequence based on an initial event of the action. ### Claim 4 (depends on 3) The system of claim 3, wherein the application engine is to generate the composite event sequence further based on an end event of the action. ### Claim 5 (depends on 3) The system of claim 3, wherein the application engine is to generate the composite event sequence further based on an expiration of an idle timer. ### Claim 6 (depends on 1) The system of claim 1, wherein the application engine is to add a dummy action handler to an event listener associated with at least one non-significant event. ### Claim 7 (depends on 6) The system of claim 6, wherein the at least one non-significant event is associated with at least one of the plurality of event listeners comprising the composite event sequence. ### Claim 8 (depends on 1) The system of claim 1, wherein action associated with the element of the application comprises an interaction between a user and an interface of application on a display device. ### Claim 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 listener of the plurality of event listeners wherein the second event listener of the plurality of event listeners comprises a non-significant event listener; receive an 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. ### Claim 10 (depends on 9) 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. ### Claim 11 (depends on 9) 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. ### Claim 12 (depends on 11) 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. ### Claim 13 (depends on 9) 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, wherein the second log record; and associate the second log record to the log record associated with the composite event sequence. ### Claim 14 (depends on 9) 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. ### Claim 15 A computer-implemented method comprising: adding a dummy action handler to each of a plurality of event listeners associated with an application; generating a composite event sequence comprising at least one first event listener in response to receiving a first user action associated with the application, wherein the first user action triggers at least one predefined start event associated with the at least one first event listener of the plurality of event listeners; adding at least one second event listener of the plurality of event listeners to the composite event sequence based on the dummy action handler of the at least one second event listener; measuring a respective performance metric for the at least one first event listener and the at least one second event listener, wherein the respective performance metric comprises a time to complete the at least one first event listener and the at least one second event listener; closing the composite event sequence in response to at least one of the following: an expiration of an idle timer and a receiving of a second user action triggering the at least one predefined start event; 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, wherein the final performance metric comprises a total time to complete the user action according to the respective performance metrics for the at least one first event listener and the at least one second event listener, and creating a log record comprising the final performance metric, wherein the log record is 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.