Providing instrumentation data to an instrumentation data source from within a managed code

• US 20060015854A1
• Filed: 08/31/2005
• Published: 01/19/2006
• Est. Priority Date: 07/10/2000
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Muhlestein, Travis J., Feuerstein, Corina E., Cooperstein, Jeffrey M.
• Granted Patent: US 7,631,300 B2
• Time in Patent Office: Days
• US Class Current: 717/130
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements

Abstract

A computer-implemented method for exposing instrumentation data available from within a managed code environment to an instrumentation data source executing outside of said managed code environment is presented. The method comprises each of the following. An indication is received that said instrumentation data should be exposed to said instrumentation data source. In response to receiving said indication, a decoupled provider is loaded. The decoupled provider facilitates communication between said managed code environment and said instrumentation data source. A determination is made as to whether schema describing said instrumentation data has been previously registered with said instrumentation data source. In response to determining that said schema has not been previously registered with said instrumentation data source, said schema is registered with said instrumentation data source through said decoupled provider.

Claims

1. A computer-implemented method for exposing instrumentation data available within a managed code environment to an instrumentation data source executing outside of said managed code environment, comprising each of the following:

receiving an indication that said instrumentation data should be exposed to said instrumentation data source;

in response to receiving said indication, loading a decoupled provider for facilitating communication between said managed code environment and said instrumentation data source;

determining whether schema describing said instrumentation data has been previously registered with said instrumentation data source;

in response to determining that said schema has not been previously registered with said instrumentation data source, registering said schema with said instrumentation data source through said decoupled provider.

2. The method of claim 1, further comprising:

registering an application program associated with said instrumentation data with said instrumentation data source as a provider of instances of said instrumentation data.

3. The method of claim 2, further comprising:

notifying said decoupled provider that said instrumentation data is available.

4. The method of claim 3, wherein said instrumentation data comprises an object and wherein said schema describes the properties and methods exposed by said object.

5. The method of claim 4, wherein said indication that said instrumentation data should be exposed to said instrumentation data source comprises an attribute.

6. The method of claim 4, wherein said indication that said instrumentation data should be exposed to said instrumentation data source comprises a call to an application programming interface.

7. The method of claim 1, wherein the managed code environment is Microsoft Corporation'"'"'s .NET framework.

8. The method of claim 7, wherein the instrumentation data source is a Windows Management Instrumentation (WMI) service.

9. The method of claim 1, wherein the managed code environment is a JAVA virtual machine.

10. A computer-implemented method for exposing instrumentation data available within a managed code environment to an instrumentation data source executing outside said managed code environment, comprising each of the following:

receiving an indication that said instrumentation data should be exposed to said instrumentation data source;

in response to receiving said indication, loading a decoupled provider for facilitating communication between said managed code environment and said instrumentation data source;

determining whether schema describing said instrumentation data has been previously registered with said instrumentation data source;

in response to determining that schema has not been previously registered with said instrumentation data source, registering said schema with said instrumentation data source through said decoupled provider;

receiving a request for said instrumentation data from said instrumentation data source at said decoupled provider; and

in response to said request, converting said instrumentation data from a format compatible with said managed code environment to a format compatible with said instrumentation data source, and transmitting said converted instrumentation data to said instrumentation data source.

11. The method of claim 10, wherein said instrumentation data comprises an object and wherein said schema describes the properties and methods exposed by said object.

12. The method of claim 11, wherein said request for said instrumentation data comprises a request for instances of said object,

13. The method of claim 12, wherein said request for said instrumentation data is received at said decoupled provider, and the method further comprising querying one or more providers for instances satisfying said request.

14. The method of claim 13, wherein said one or more providers are queried by said decoupled provider in a round-robin fashion to identify instances satisfying said request.

15. The method of claim 14, wherein said indication that said instrumentation data should be exposed to said instrumentation data source comprises an attribute.

16. The method of claim 14, wherein said indication that said instrumentation data should be exposed to said instrumentation data source comprises a call to an application programming interface.

17. A computer-implemented method for exposing instrumentation data available within a managed code environment to an instrumentation data source executing outside said managed code environment, comprising each of the following:

receiving a request for said instrumentation data at a decoupled provider;

determining whether said request comprises a request for one or more instances of said instrumentation data;

in response to determining that said request comprises a request for instances of said instrumentation data, querying said decoupled provider to determine if instances of said instrumentation data are available; and

in response to determining that said instances of said instrumentation data are available that satisfying said request, converting said instances of said instrumentation data satisfying said request from a format compatible with said managed code environment to a format compatible with said instrumentation data source, and transmitting said converted instances of said instrumentation data satisfying said request to said instrumentation data source.

18. The method of claim 17 wherein said providers are queried by said decoupled provider in a round-robin fashion to determine if instances of said instrumentation data are available that satisfy said request.

19. The method of claim 17, further comprising:

determining whether said request comprises a request to write a property on an instance of said instrumentation data;

in response to determining that said request comprises a request to write a property, identifying said instance of said instrumentation data and writing said property on said instance; and

providing a confirmation from said decoupled provider to said instrumentation data source that said property was written.

20. The method of claim 17, wherein the managed code environment is Microsoft Corporation'"'"'s .NET framework.