Advanced agent instrumentation for opentelemetry implementations
In one embodiment, a method herein comprises: intercepting runtime calls from a telemetry invocation for method entry to discover loaders; determining whether an implementation tenant is already allocated for a particular discovered loader; allocating, in response to no implementation tenant being already allocated for the particular discovered loader, a particular implementation tenant from a plurality of available implementation tenants, wherein a corresponding loader for the particular implementation tenant is set to delegate from the particular discovered loader; and calling, in response to the particular implementation tenant being allocated or being already allocated for the particular discovered loader, a method entry for the particular implementation tenant to perform an associated interception operation while using direct telemetry class and/or method calls.
1 . A method, comprising:
intercepting, by a process comprising a proxy tenant handler, runtime calls from a telemetry invocation for method entry to discover loaders;
determining, by the process, whether an implementation tenant is already allocated for a particular discovered loader;
allocating, by the process and in response to no implementation tenant being already allocated for the particular discovered loader, a particular implementation tenant from a plurality of available implementation tenants, wherein a corresponding loader for the particular implementation tenant is set to delegate from the particular discovered loader to a proxy class loader; and
calling, by the process in response to the particular implementation tenant being allocated for the particular discovered loader, a method entry for the particular implementation tenant to perform an associated interception operation while using direct telemetry class and/or method calls.
2 . The method as in claim 1 , further comprising:
creating the plurality of available implementation tenants during a proxy initialization for the telemetry invocation.
3 . The method as in claim 2 , wherein creating the plurality of available implementation tenants comprises:
loading specific handler bytes that will make direct telemetry calls from a jar file into a javassist class;
renaming the javassist class to match a specific implementation tenant; and
associating the specific handler bytes with the specific implementation tenant.
4 . The method as in claim 1 , wherein allocating the particular implementation tenant comprises:
determining, for the particular implementation tenant, an associated tenant class loader and associated handler bytes; and
calling, for the associated tenant class loader, a method defineClass with the associated handler bytes.
5 . The method as in claim 1 , wherein the telemetry invocation is an invocation according to a standardized application performance monitoring solution.
6 . The method as in claim 1 , wherein the associated interception operation comprises instrumenting telemetry calls.
7 . The method as in claim 1 , wherein determining whether the implementation tenant is already allocated for the particular discovered loader comprises:
checking an implementation map that maps discovered loaders to implementation tenants.
8 . The method as in claim 1 , wherein allocating the particular implementation tenant comprises:
updating an implementation map that maps loaders to implementation tenants with a loader key pointing to the particular implementation tenant.
9 . The method as in claim 1 , wherein allocating the particular implementation tenant comprises:
verifying a class loaded in a class loader of the particular implementation tenant.
10 . The method as in claim 1 , wherein the plurality of available implementation tenants have no instrumentation.
11 . The method as in claim 1 , further comprising:
loading multiple tenants by creating corresponding tenant folders and setting a corresponding configuration to have no instrumentation.
12 . The method as in claim 1 , wherein the telemetry invocation is one of either an application programming interface or a software developer kit.
13 . The method as in claim 1 , wherein using direct telemetry class and/or method calls comprises:
loading telemetry classes and any classes loaded by the telemetry classes.
14 . A tangible, non-transitory, computer-readable medium having computer-executable instructions stored thereon that, when executed by a processor on a computer, cause the computer to perform a method comprising:
intercepting, by a proxy tenant handler, runtime calls from a telemetry invocation for method entry to discover loaders;
determining whether an implementation tenant is already allocated for a particular discovered loader;
allocating, in response to no implementation tenant being already allocated for the particular discovered loader, a particular implementation tenant from a plurality of available implementation tenants, wherein a corresponding loader for the particular implementation tenant is set to delegate from the particular discovered loader to a proxy class loader; and
calling, in response to the particular implementation tenant being allocated for the particular discovered loader, a method entry for the particular implementation tenant to perform an associated interception operation while using direct telemetry class and/or method calls.
15 . The tangible, non-transitory, computer-readable medium as in claim 14 , wherein the method further comprises:
creating the plurality of available implementation tenants during a proxy initialization for the telemetry invocation.
16 . The tangible, non-transitory, computer-readable medium as in claim 15 , wherein creating the plurality of available implementation tenants comprises:
loading specific handler bytes that will make direct telemetry calls from a jar file into a javassist class;
renaming the javassist class to match a specific implementation tenant; and
associating the specific handler bytes with the specific implementation tenant.
17 . The tangible, non-transitory, computer-readable medium as in claim 14 , wherein allocating the particular implementation tenant comprises:
determining, for the particular implementation tenant, an associated tenant class loader and associated handler bytes; and
calling, for the associated tenant class loader, a method defineClass with the associated handler bytes.
18 . The tangible, non-transitory, computer-readable medium as in claim 14 , wherein the telemetry invocation is an invocation according to a standardized application performance monitoring solution.
19 . An apparatus, comprising:
one or more network interfaces to communicate with a network;
a processor coupled to the one or more network interfaces and configured to execute one or more processes; and
a memory storing a process that is executable by the processor, the process, when executed, configured to:
intercept, by a proxy tenant handler, runtime calls from a telemetry invocation for method entry to discover loaders;
determine whether an implementation tenant is already allocated for a particular discovered loader;
allocate, in response to no implementation tenant being already allocated for the particular discovered loader, a particular implementation tenant from a plurality of available implementation tenants, wherein a corresponding loader for the particular implementation tenant is set to delegate from the particular discovered loader to a proxy class loader; and
call, in response to the particular implementation tenant being allocated for the particular discovered loader, a method entry for the particular implementation tenant to perform an associated interception operation while using direct telemetry class and/or method calls.