Configurable collection of computer related metric data

• US 7,441,246 B2
• Filed: 03/19/2004
• Issued: 10/21/2008
• Est. Priority Date: 03/19/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Murphy, Shawn M., Auerbach, Alan B., Smith, Walter R
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): To; Jennifer N
• Application Number:
  US10/804,367
• Publication Number:
  US 20050210477A1
• Time in Patent Office: 1,677 Days
• Field of Search: 719315-316, 719/310, 719/331, 709201-224, 707100-102
• US Class Current: 719/310
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

The present invention relates it directed to configurable collection of computer related metric data. A computer system generates computer related metric data related to an application. The application accesses a manifest that indicates a portion of the generated computer related metric data (e.g., a subset) is to be packaged for delivery. The application sends schema-based package start data to cause the portion of generated computer related metric data to be packaged. A quality metric module receives the schema-based package start data and accesses the indicated portion of computer related metric data. The quality metric module packages the portion of computer related metric data according to a packaging schema. The application sends a package send command to cause the packaged portion of computer related metric data to be delivered. The quality metric module receives the package send command and sends the packaged portion of computer related metric data in response to the package send command.

Claims

1. A method for specifying computer related metric data that is generated by a computer system to be delivered to a server, the method comprising:

executing an application at the computer system;

generating metric data related to functionality of the application monitored during execution of the application, the generated metric data including at least one of performance monitoring data and event log data for the application;

storing the metric data related to the monitored functionality of the application at the computer system;

accessing a separately defined manifest including instructions that indicates a subset of the generated metric data related to the monitored functionality of the application is to be packaged for delivery to a server subsequent to storing the generated metric data, the separately defined manifest being separate from the generated metric data and separate from the application, the extent of the subset of the generated metric data relative to the total generated metric data configured in accordance with a desire of a user of the computer system;

converting the instructions included in the separately defined manifest to a schema-based package start command, the schema-based package start command including elements and attributes of a vocabulary defined in a selection schema, the selection schema defining how subsets of performance monitoring data and subsets of event log data are to be packaged;

automatically sending the schema-based package start command to a quality metric module to cause the subset of the generated metric data indicated in the separately defined manifest to be packaged for delivery to the server; and

sending a package send command to the quality metric module to cause the packaged subset of generated metric data related to the monitored functionality of the application to be delivered to the server.

2. The method as recited in claim 1, wherein generating metric data comprises an operating system generating metric data related to the functionality of the application.

3. The method as recited in claim 1, wherein generating metric data comprises the application generating metric data related to the functionality of the application.

4. The method as recited in claim 1, wherein accessing a separately defined manifest comprises the application accessing a dynamic link library.

5. The method as recited in claim 1, wherein accessing a separately defined manifest comprises accessing a manifest that indicates a portion of performance monitoring data related to the functionality of the application is to be packaged for delivery.

6. The method as recited in claim 1, wherein accessing a separately defined manifest comprises accessing a manifest that indicates a portion of event log data related to the functionality of the application is to be packaged for delivery.

7. The method as recited in claim 1, wherein accessing a separately defined manifest comprises accessing a manifest that indicates statistical operations that are to be performed on generated metric data related to the functionality of the application.

8. The method as recited in claim 1, wherein converting instructions included in the separately defined manifest to the schema-based package start command comprises converting the instructions included in the separately defined manifest into XML instructions.

9. The method as recited in claim 1, wherein sending the schema-based package start command comprises sending XML instructions to the quality metric module to indicate to the quality metric module that a subset of the generated metric data related to the functionality of the application is to be packaged for delivery.

10. The method as recited in claim 1, further comprising:

sending a sample command to the quality metric module, the sample command indicating that—

the quality metric module is to sample at least one item or event represented in the separately defined manifest.

11. The method as recited in claim 10, wherein sending a sample command comprises sending a sample command that indicates that the metric data represented in the separately defined manifest is to be sampled.

12. The method as recited in claim 1, wherein sending a package send command comprises sending a dispose flag that indicates whether or not a corresponding package is to be retained after the package is queued for delivery.

13. The method as recited in claim 1, wherein accessing a separately defined manifest that indicates a subset of the generated metric data related to the monitored functionality of the application is to be packaged comprises accessing a separately defined manifest specifically selected by a developer to configure the subset of generated metric data for use in studying the monitored functionality of the application.

14. A computer system that includes a quality metric module, the quality metric module configured to package computer related metric data for delivery, a method for packaging specified computer related metric data, the method comprising:

receiving a schema-based package start command from an application, the schema-based package start command indicating that a subset of previously stored metric data related to monitored functionality of the application is to be packaged for delivery to a server, the schema-based package start command including XML instructions that indicate a subset of generated metric data related to the monitored functionality of the application is to be packaged for delivery, the generated metric data including at least one of performance monitoring data and event log data for the application, the subset of the previously stored metric data indicated in a separately defined manifest that is separate from the application and separate from the generated metric data, the extent of the subset of the previously stored metric data relative to the total generated metric data configured in accordance with the desire of a user of the computer system, the schema-based package start command and XML instructions including elements and attributes of a vocabulary defined in a selection schema, the selection schema defining how to indicate that subsets of performance monitoring data and subsets of event log data are to be packaged;

accessing the indicated subset of generated metric data related to the monitored functionality of the application from computer system storage;

packaging the subset of generated metric data related to the functionality of the application according to a packaging schema defining elements and attributes used at the server;

receiving a package send command from the application; and

sending the packaged subset of metric data related to the functionality of the application to the server in response to the package send command.

15. The method as recited in claim 14, further comprising:

receiving a sample command;

retrieving at least one item or event related to the monitored functionality of the application from system memory; and

storing the at least one item or event —

in a data point store.

16. The method as recited in claim 15, wherein retrieving at least one item or event from system memory comprises retrieving all the metric data indicated in the XML instructions.

17. The method as recited in claim 14, wherein accessing the -subset of generated metric data related to the monitored functionality of the application comprises accessing the subset of generated —

metric data related to the monitored functionality of the application from a data point store.

18. The method as recited in claim 17, further comprising:

performing a statistical operation based on the accessed subset of metric data related to the monitored functionality of the application.

19. The method as recited in claim 14, wherein packaging the subset of generated metric data related to the monitored functionality of the application according to a packaging schema comprises converting the subset of generated metric data related to the monitored functionality of the application into second XML instructions in accordance with an XML schema.

20. The method as recited in claim 14, wherein packaging the subset of generated metric data related to the monitored functionality of the application according to a packaging schema comprises packing —

metric data related to the monitored functionality of the application in an array.

21. The method as recited in claim 14, wherein receiving a package send command comprises receiving a dispose flag that indicates whether or not a corresponding package is to be retained after the package is queued for delivery.

22. The method as recited in claim 14, wherein sending the packaged subset of —

metric data related to the monitored functionality of the application to the server comprises sending the packaged subset of —

metric data related to the functionality of the application to a server that collects computer related metric data for an application developer of the application.

23. The method as recited in claim 14, wherein receiving a schema-based package start-command in the form of XML instructions from an application comprises receiving a schema-based package start command based on a separately defined manifest specifically selected by a developer to configure the subset of generated metric data for use in studying the monitored functionality of the application.

24. A computer program product for use at a computer system that is configured to generate computer related metric data associated with the application, the computer program product for implementing a method for specifying computer related metric data that is to be delivered to a server, the computer program product stored on one or more computer-readable media having computer-executable instructions that, when executed by a processor, cause the computer system to perform the following:

execute an application at the computer system;

generate metric data related to functionality of the application monitored during execution of the application, the generated metric data including at least one of performance monitoring data and event log data for the application;

store the metric data related to the monitored functionality of the application at the computer system;

access a separately defined manifest including instructions that indicates a subset of the generated metric data related to the monitored functionality of the application is to be packaged for delivery to a server subsequent to storing the generated metric data, the separately defined manifest being separate from the generated metric data and separate from the application, the extent of the subset of the generated metric relative to the total generated metric data configured in accordance with a desire of a user of the computer system;

convert the instructions included in the separately defined manifest to a schema-based package start command, the schema-based package start command including elements and attributes of a vocabulary defined in a selection schema, the selection schema defining how subsets of performance monitoring data and subsets of event log data are to be packaged;

s

send the schema-based package start command to a quality metric module to cause the subset of the generated metric data indicated in the separately defined manifest to be packaged for delivery to the server; and

send a package send command to the quality metric module to cause the packaged subset of generated metric data related to the monitored functionality of the application to be delivered to the server.

25. A computer program product for use at a computer system that includes a quality metric module, the quality metric module configured to package computer related metric data for delivery, the computer program product for implementing a method for packaging specified computer related metric data, the computer program product stored on one or more computer-readable media having computer-executable instructions that, when executed by a processor, cause the computer system to perform the following:

receive a schema-based package start command from an application, the schema-based package start command indicating that a subset of previously stored metric data related to monitored functionality of the application is to be packaged for delivery to a server, the schema-based package start command including XML instructions that indicate a subset of generated metric data related to the monitored functionality of the application is to be packaged for delivery, the generated metric data including at least one of performance monitoring data and event log data for the application, the subset of the previously stored metric data indicated in a separately defined manifest that is separate from the application and separate from the generated metric data, the extent of the subset of the previously stored metric data relative to the total generated metric data configured in accordance with the desire of a user of the computer system, the schema-based package start command and XML instructions including elements and attributes of a vocabulary defined in a selection schema, the selection schema defining how subsets of performance monitoring data and subsets of event log data are to be packaged;

access the indicated subset of generated metric data related to the monitored functionality of the application from computer system storage;

package the subset of generated metric data related to the functionality of the application according to a packaging schema defining elements and attributes used at the server;

receive a package send command from the application; and

send the packaged subset of metric data related to the functionality of the application to the server in response to the package send command.