Method and apparatus for providing instrumentation data to an instrumentation data source from within a managed code environment
First Claim
1. A method for exposing instrumentation data available within a managed code environment to an instrumentation data source executing outside said managed code environment, comprising:
- 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 Assignments
0 Petitions
Accused Products
Abstract
A method and apparatus for providing instrumentation data to an instrumentation data source from within a managed code environment is provided. A decoupled provider is provided that executes partially in managed code and partially in unmanaged code. The decoupled provider facilitates communication with an instrumentation data source. The decoupled provider also dynamically registers schema for managed code objects to be instrumented at run-time. The decoupled provider also receives and processes requests from the instrumentation data source to retrieve instance data for managed code objects, to write properties on managed code objects, and to execute methods on managed code objects.
-
Citations
31 Claims
-
1. A method for exposing instrumentation data available within a managed code environment to an instrumentation data source executing outside said managed code environment, comprising:
-
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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A method for exposing instrumentation data available within a managed code environment to an instrumentation data source executing outside said managed code environment, comprising:
-
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 proxy; 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. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A method for exposing instrumentation data available within a managed code environment to an instrumentation data source executing outside said managed code environment, comprising:
-
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, querying one or more providers from 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. - View Dependent Claims (20, 21, 22, 23, 24)
-
-
25. A method for exposing instrumentation data available within a managed code environment to an instrumentation data source executing outside said managed code environment, comprising:
-
receiving a request to fire an event relating to said instrumentation data into said instrumentation data source;
in response to receiving said request, 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;
determining at said decoupled provider whether said event should be fired; and
in response to determining that said event should be fired, converting said instrumentation data from a format compatible with said managed code environment to a format compatible with said instrumentation data source, and firing said converted instrumentation data from said decoupled provider to said instrumentation data source as an event. - View Dependent Claims (26, 27, 28, 29, 30, 31)
-
Specification