Christian Neumüller

I would simply feel more comfortable if I know that most likely the recording will not be publicly available forever. If that is counts as an argument. 😃

hostName should be supported by host.name (https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/resource/semantic_conventions/host.md) and containerName by container.name (https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/resource/semantic_conventions/container.md)

Note that in the case I observed, I even got a null activity despite there being no current span (the parent context was extracted from HTTP headers, having IsRemote=true, TraceFlags=None)

@open-telemetry/dotnet-contrib-maintainers I'm an "owner" of the component changed here, but not an approver on the repository. What can I do to get this PR merged? I would like to have...

I think nobody we know of has tried it & reported back so far. Did you try it and hit any roadblocks?

This was very useful for unit tests, etc. where using a lambda to implement the single-method interface worked nicely. Now that it no longer is one, I think we can...

CC @carlosalberto

Thanks for the reminder, this requires ~~https://github.com/open-telemetry/build-tools/pull/100~~ https://github.com/open-telemetry/build-tools/pull/79

Sorry, I meant to link to https://github.com/open-telemetry/build-tools/pull/79, so I'm not sure what you meant by toolchain, but only the actual tool needs to be updated, nothing further down the stack.

To fully capture all (or at least more) of the possible relationships between Spans, in addition to the `create(parent)` API, we would need APIs that signal that a span begins/ends...