DYNAMIC EVENT COLLECTION AND STRUCTURED STORAGE

• US 20100299678A1
• Filed: 05/20/2009
• Published: 11/25/2010
• Est. Priority Date: 05/20/2009
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: MacNary, Timothy Glenn, Zunino, Gilles C.J.A, Taylor, John Anthony, Mohanty, Sumit, Kulkarni, Amol Sudhakar, Wolf, Kenneth D., Wu, Haoran Andy, Sedukhin, Igor, Krejcik, Michael Josef
• Granted Patent: US 8,689,239 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

In one embodiment, a computer system accesses an event associated with an activity, where the activity has been executed by a runtime as part of a software application. The runtime includes a software hook configured to listen for event stream operation indications from the user. The computer system tags the accessed event with an additional portion of identification information that uniquely identifies the executed activity. The computer system receives an event stream operation indication from the user indicating that event transmission for an identified event stream is to be dynamically enabled or disabled and identifies the user-indicated event stream using the tagged identification information. The computer system also dynamically performs the indicated event stream operation on the identified event stream according to the user'"'"'s indication.

Claims

1. At a computer system including a processor and a memory, in a computer networking environment including a plurality of computing systems, a computer-implemented method for performing operations based on applied event tags, the method comprising:

an act of accessing an event associated with an activity, wherein the activity has been executed by a runtime as part of a software application, the runtime including a software hook configured to listen for event stream operation indications from the user;

an act of tagging the accessed event with an additional portion of identification information that uniquely identifies the executed activity;

an act of receiving an event stream operation indication from the user indicating that event transmission for an identified event stream is to be dynamically enabled or disabled;

an act of identifying the user-indicated event stream using the tagged identification information; and

an act of dynamically performing the indicated event stream operation on the identified event stream according to the user'"'"'s indication.

2. The method of claim 1, wherein events are continually and automatically accessed as the runtime executes by a publisher-subscriber event collection system.

3. The method of claim 2, wherein the publisher-subscriber event collection system comprises an event collection agent and a lossy, low-latency, low-overhead channel.

4. The method of claim 1, further comprising an act of storing one or more of the tagged events in a persistent store in a structured manner, such that the stored events form a relational model of the runtime execution of the application.

5. The method of claim 4, further comprising an act of troubleshooting the software application using one or more of the tagged events stored in the persistent store, each event indicating what the event'"'"'s corresponding activity was doing at a given point in time.

6. The method of claim 4, wherein the relational model is different for each different application type.

7. The method of claim 1, wherein the added identification information includes at least one of the following identification items:

application ID, virtual path, web site name, application domain ID and process ID.

8. The method of claim 7, wherein the user indicates that a particular event stream is to be dynamically enabled or disabled by identifying the event stream'"'"'s corresponding identification item, such that the runtime hook is made aware that the user intends to subscribe or unsubscribe from the event stream.

9. The method of claim 2, wherein a plurality of users are subscribed to the same event stream.

10. The method of claim 1, wherein events from a plurality of applications are sent to a user upon determining that the user has indicated that the user desires to receive corresponding events for each of the plurality of applications.

11. The method of claim 1, further comprising an act of monitoring an activity stream to determine from the stream how the activity stream'"'"'s associated application is behaving.

12. The method of claim 7, wherein at least one of the identification items identifies which sub-component of the application emitted the event.

13. The method of claim 1, wherein the emitted event is discarded upon determining that no user is subscribed to the event'"'"'s corresponding event stream.

14. The method of claim 2, further comprising an act of automatically subscribing a user to an event stream upon determining that the event stream is being emitted from an application that provides substantially similar functionality to an application to whose event stream the user is currently subscribed.

15. A computer program product for implementing a method for storing received events such that the stored events form a relational model contextually representing how each of the activities of the application was executed, the computer program product comprising one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by one or more processors of the computing system, cause the computing system to perform the method, the method comprising:

an act of accessing an event associated with an activity, wherein the activity has been executed by a runtime as part of a software application, the runtime including a software hook configured to listen for event stream operation indications from the user;

an act of tagging the accessed event with an additional portion of identification information that uniquely identifies the executed activity; and

an act of storing each received event in a structured manner, such that the stored events form a relational model contextually representing how each of the activities of the application was executed.

16. The computer program product of claim 15, wherein the events are stored in a persistent store which is further configured to store application models.

17. The computer program product of claim 16, wherein each application model is configured to store events in a manner corresponding to the application being executed by the runtime.

18. The computer program product of claim 15, further comprising accessing one or more of the stored events to perform a user-initiated action using the stored events.

19. The computer program product of claim 15, wherein the tagged information is stored with the event.

20. A computer system comprising the following:

one or more processors;

system memory;

one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by the one or more processors, causes the computing system to perform a method for performing operations based on applied event tags, the method comprising the following;

an act of accessing an event associated with an activity, wherein the activity has been executed by a runtime as part of a software application, the runtime including a software hook configured to listen for event stream operation indications from the user;

an act of tagging the accessed event with an additional portion of identification information that uniquely identifies the executed activity;

an act of receiving an event stream operation indication from the user indicating that event transmission is to be dynamically enabled or disabled;

an act of dynamically performing the indicated event stream operation according to the user'"'"'s indication, using the identification information tagged to the activity; and

an act of storing each received event in a structured manner, such that the stored events form a relational model contextually representing how each of the activities of the application was executed.