DYNAMIC GENERATION OF INSTRUMENTATION LOCATORS FROM A DOCUMENT OBJECT MODEL

• US 20170132181A1
• Filed: 11/11/2015
• Published: 05/11/2017
• Est. Priority Date: 11/11/2015
• Status: Active Grant

• Current Assignee: Box Incorporated
• Original Assignee: Box Incorporated
• Inventors: Batraski, Ethan, Van As, Tarrence, Basta, Matthew
• Granted Patent: US 11,580,001 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/30 Monitoring
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 16/957 Browsing optimisation, e.g. caching or content distillation
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]

Abstract

Systems for web page or web application instrumentation. Embodiments commence upon identification of a computer-readable user interface description comprising at least some markup language conforming to a respective document object model that is codified in a computer-readable language. An injector process modifies the user interface description by inserting markup text and code into the user interface description, where the inserted code includes instrumentation code to invoke dynamic generation of instrumentation locator IDs using the hierarchical elements found in the document object model. The modified computer-readable interface description is transmitted to a user device. Log messages are emitted upon user actions taken while using the user device. The log messages comprise the instrumentation locator IDs that are formed using hierarchical elements found in the document object model.

Claims

1. A method comprising:

receiving a user request for an action to be performed on a web page;

preparing, a first portion of a markup language user interface description that conforms to a respective document object model;

injecting, into the first portion of the markup language user interface description, a first markup language instrumentation code comprising at least one first key-value pair that is used to generate one or more first instrumentation locator IDs by using the respective document object model;

generating a second portion of the user interface description wherein the second portion of the user interface description is generated in response to the user request;

injecting, into the second portion of the user interface description markup language, markup language instrumentation code that conforms to an instrumentation format template having at least one second key-value pair that is used to generate one or more second instrumentation locator IDs, wherein the second portion of the user interface description is generated in response to the user request; and

transmitting, to a user device, at least some of the first portion of the markup language instrumentation code and at least some of the second portion of the markup language instrumentation code.

2. The method of claim 1, further comprising receiving at least one log message wherein the log message comprises at least one of the instrumentation locator IDs.

3. The method of claim 1, wherein at least one of the instrumentation locator IDs is formed as an assembly of hierarchical element names.

4. The method of claim 3, wherein at least one of the instrumentation locator IDs is formed as an assembly of an order of a hierarchical path rather than on names of classes in the hierarchical path.

5. The method of claim 1, further comprising identifying a server in a cloud-based environment, wherein the server is configured to interface with one or more storage facilities that store the user interface description for access by one or more users.

6. The method of claim 5, further comprising identifying at least one user characteristic pertaining to at least the one or more users wherein at least one of the instrumentation locator IDs comprises the user characteristic.

7. The method of claim 1, wherein the log message that is emitted responsive to a user action comprises an occurrence ID.

8. The method of claim 7, wherein the occurrence ID is formed using at least one of, an occurrence ID, or a unique sequencing number, or a random number, or any combination thereto.

9. The method of claim 1, further comprising packaging a document object model parser together with the user interface description.

10. The method of claim 1, wherein the document object model is at least one of, an XML DTD, or an XML schema, or an HTML schema, or an XHTML schema, or any combination thereof.

11. A computer program product, embodied in a non-transitory computer readable medium, the non-transitory computer readable medium having stored thereon a sequence of instructions which, when stored in memory and executed by a processor causes the processor to perform a set of acts, the acts comprising:

receiving a user request for an action to be performed on a web page;

preparing, a first portion of a markup language user interface description that conforms to a respective document object model;

injecting, into the first portion of the markup language user interface description, a first markup language instrumentation code comprising at least one first key-value pair that is used to generate one or more first instrumentation locator IDs by using the respective document object model;

generating a second portion of the user interface description wherein the second portion of the user interface description is generated in response to the user request;

injecting, into the second portion of the user interface description markup language, instrumentation code that conforms to an instrumentation format template having at least one second key-value pair that is used to generate one or more second instrumentation locator IDs, wherein the second portion of the user interface description is generated in response to the user request; and

transmitting, to a user device, at least some of the first portion of the markup language instrumentation code and at least some of the second portion of the markup language instrumentation code.

12. The computer program product of claim 11, further comprising instructions which, when stored in memory and executed by a processor causes the processor to perform a set of acts for receiving at least one log message wherein the log message comprises at least one of the instrumentation locator IDs.

13. The computer program product of claim 11, wherein at least one of the instrumentation locator IDs is formed as an assembly of hierarchical element names.

14. The computer program product of claim 13, wherein at least one of the instrumentation locator IDs is formed as an assembly of an order of a hierarchical path rather than on names of classes in the hierarchical path.

15. The computer program product of claim 11, further comprising identifying a server in a cloud-based environment, wherein the server is configured to interface with one or more storage facilities that store the user interface description for access by one or more users.

16. The computer program product of claim 15, further comprising instructions which, when stored in memory and executed by a processor causes the processor to perform a set of acts for identifying at least one user characteristic pertaining to at least the one or more users wherein at least one of the instrumentation locator IDs comprises the user characteristic.

17. The computer program product of claim 11, wherein the log message that is emitted responsive to a user action comprises an occurrence ID.

18. The computer program product of claim 11, wherein the document object model is at least one of, an XML DTD, or an XML schema, or an HTML schema, or an XHTML schema, or any combination thereof.

19. A system comprising:

a network port to receive a user request for an action to be performed on a web page; and

a server or a plurality of servers that perform acts of,

preparing, a first portion of a markup language user interface description that conforms to a respective document object model;

injecting, into the first portion of the markup language user interface description, a first markup language instrumentation code comprising at least one first key-value pair that is used to generate one or more first instrumentation locator IDs by using the respective document object model;

generating a second portion of the user interface description wherein the second portion of the user interface description is generated in response to the user request;

injecting, into the second portion of the user interface description markup language, instrumentation code that conforms to an instrumentation format template having at least one second key-value pair that is used to generate one or more second instrumentation locator IDs, wherein the second portion of the user interface description is generated in response to the user request; and

transmitting, to a user device, at least some of the first portion of the markup language instrumentation code and at least some of the second portion of the markup language instrumentation code.

20. The system of claim 19, further comprising a processor to perform a set of acts for receiving at least one log message wherein the log message comprises at least one of the instrumentation locator IDs.