Matt Hensley

@ranjanmadhu The first node in `$componentTemplateNodes` is the node you're searching for, and jQuery is only searching descendants. The following works, but is ugly: ```javascript $($componentTemplateNodes).find('header').addBack('header') ```

This would be a nice addition for distribution authors and simplify documenting proper SDK setup, especially for .NET Framework applications.

@RohitRanjanMS is there a publicly available roadmap for the on-going work? I'm getting questions weekly on instrumenting Azure Functions. This new OTel support is a hot topic, so any information...

> Detectors always have a parameter-less constructor until now. Any suggestion? `HostDetector` [has an internal constructor to facilitate testing](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Resources.Host/HostDetector.cs#L44)

Available from [1.11.0-beta.1](https://github.com/open-telemetry/opentelemetry-dotnet--contrib/blob/main/src/OpenTelemetry.Instrumentation.SqlClient/CHANGELOG.md)

+1 for extensions methods against `ResourceBuilder` like we see with instrumentation and other components. The style is pretty natural and helps with ergonomics IMO.

Going to pick up a few of these as I have time. Reasonably straightforward after applying the changes to #1691.

FYI @alanwest @gregkalapos

Thanks for the code sample, made this quick to investigate. I went through the instrumentation code and do not see a quick fix. Is this something you'd like to work...

Agree with @Kielek, dynamic ActivitySource naming is unusual. I believe the use case can be handled by named configurations /connections.