Amir Blum

> What would be the issue with having **only sync detectors**? > > * Slow down of application startup? How significant is this impact, are we talking about tens of...

> What about packing the resource into a Promise/Future? This one can be created sync and it's immutable. Whoever needs resource has to await it. As far as I know...

Hi @punya Thank you for your interest. I too think it could be great to add this information to the README. Would you be interested in contributing a PR that...

upstream the instrumentation to contrib repo, with `test-all-version`, support for v6 and documentation in README https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1131 Thanks for bringing it up :)

Thanks eric, > .create and .save in active record are not alias methods. While .save makes up a percentage of work within create, their performance profiles would be different, I...

Great iterating over this with you guys, like the brainstorming :) > I think it's dangerous to begin to write instrumentation that is overly worried about "their cost and visual...

Thanks very much @ericmustin At first I planned on adding configuration per noisy instrumentation in order to reduce verbosity. This is what we've done so far in node's instrumentations. The...

> Thanks for opening this issue and providing us with details. > > Do you have a hypothesis as to why this is happening? I am new to ruby so...

Thanks @arielvalentin :) I appreciate the warm welcome and the time you put into pointing me to the relevant part of the code. Lot's of new info - I'll need...

> Part of the issue here is the incorrect RequestOptions parameter for the http.get() function call. The host '::1' is actually just the hostname, changing the get request to :...