Use DiagnosticSource to collect RDD telemetry from 3rd-party SDKs/libraries. This requires defining the "contract" for dependency collection which later can be implemented directly in particular libraries
The approach we want to use is based on DiagnosticSource Activities - AI DependencyTrackingTelemetryModule will implement a DiagnosticSource subscriber which will subscribe to all activities following given naming convention (TBD) with possible support of config-based white/blacklists. All of those activities are expected to follow the OpenTracing tag naming convention (https://github.com/opentracing/specification/blob/master/semantic_conventions.md) which will allow the listener to construct meaningful RDD telemetry.
The next steps are to contribute to selected 3rd-party projects in order to add corresponding Activities relevant to given technology
Use DiagnosticSource to collect RDD telemetry from 3rd-party SDKs/libraries. This requires defining the "contract" for dependency collection which later can be implemented directly in particular libraries
The approach we want to use is based on DiagnosticSource Activities - AI
DependencyTrackingTelemetryModulewill implement a DiagnosticSource subscriber which will subscribe to all activities following given naming convention (TBD) with possible support of config-based white/blacklists. All of those activities are expected to follow the OpenTracing tag naming convention (https://github.com/opentracing/specification/blob/master/semantic_conventions.md) which will allow the listener to construct meaningful RDD telemetry.The next steps are to contribute to selected 3rd-party projects in order to add corresponding Activities relevant to given technology