-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support collecting non-HTTP dependency calls from 3rd party libraries #1595
Comments
I would like to help with this as I've been reviewing how to do it with MongoDB |
@TomMilos Can we close this and create separate items for 3rd party? |
@TomMilos please update |
Is there any update on this? I saw Redis showing up as a dependency at Build. It would be great if this was coming soon. |
@andymac4182 could you please point me to the slides/video with Redis dependency? This is something we discussing with Redis StackExchange team now, but have not got any agreement yet. |
@lmolkova https://youtu.be/vPZiwi-15_U?list=PLlrxD0HtieHg7uB3_amVXvaRgxIcXLtYD&t=2558 Here is the video that I was referring to. |
Any progress? I'm interested in Mongo dependency calls. |
It would be great if MongoDB could be supported especially since this is already officially supported in the Official Application Insights NodeJs Npm Package. |
@milkshakeuk There are no additional dependency collection planned for application insights SDK this year. We are investing into OpenTelemetry and any new dependency collection will come through open telemetry integration - The details about the same would be shared in the coming months. (most likely all that users need to do is to simply upgrade to newer version of SDK, and underneath it could use OpenTelemetry.. but these details are not yet designed and hence not shared) |
This issue is stale because it has been open 300 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
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
The text was updated successfully, but these errors were encountered: