Paulo Janotti

Thinking back to https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/28587#discussion_r1370863850 I opted to go with maps to keep it compact, ie.: avoiding naming the element fields, but, if we were to follow the actual XML event...

One idea regarding a configuration option: a versioned data struct option seems a good choice in this case. It allows users to stay on a desired format while allowing possible...

@strawgate sorry, I don't know one from the top of my mind. @djaglowski may know some component doing that.

I took a look at this and it seems a frequent issue when running tests on Windows: timing and synchronization. From my debugging the test code is relying on the...

@dyladan I completely missed the initial notification for this issue. I hitting the [same issue](https://github.com/open-telemetry/community/issues/1147#issuecomment-1234764332) reported by Tigran - I guess it needs the creation of a new document. Could...

Thanks @trask @dyladan you can mark [.NET: Automatic Instrumentation Doc](https://docs.google.com/document/d/1XedN2D8_PH4YLej-maT8sp4RKogfuhFpccRi3QpUcoI/edit?usp=sharing) owned by @pjanotti as done.

I suggest closing this one and follow-up on the releaser repo via https://github.com/open-telemetry/opentelemetry-collector-releases/issues/339 cc @open-telemetry/collector-triagers

SIG meeting: - Needs to be configurable similar to what is done for instrumentations (fine and coarse level control) - Short run: add "low dependencies" detector: docker first and AZ...

SIG: we will evaluate post-GA if we want to provide this out-of-the-box or not.

Relevant comment from #2003: https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/2003#issuecomment-1396716474