Johannes Tax

The change itself looks good, however, we're currently actively working on stabilizing semantic conventions for messaging, and other breaking changes might come up. That's why we have this [disclaimer](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/messaging/messaging-spans.md) on...

Looks good, @danielgblanco could you please do a final review?

@lmolkova Do you see this resolved with the integration of https://github.com/open-telemetry/semantic-conventions/pull/284? We introduced a requirement for attributes and links and we went with option 1 from your initial proposal (one...

> Isn't Grafana Agent capable of accepting OTLP directly? Yes, it is: https://grafana.com/docs/agent/latest/flow/getting-started/collect-opentelemetry-data/ Nevertheless, I get @lindeberg's point about wanting to log to stdout, it's the [most common practice for...

Hi Guilherme! Great to see Rust apps reporting to New Relic. Unfortunately, the C SDK doesn't currently provide the possibility to use custom stack traces. At the moment the only...

Hi Guilherme, Yes, a PR with this change would be much appreciated! I already have an internal issue filed, I will link it to your PR and we'll evaluate your...

> Semantic convention is in the way to be stable. Especially there were few changes after releasing latest 1.24.0 which are not reflected in this PR (see suggestions). We're planning...

Also, besides some attributes names, also operation names and their semantics changed. There's now "publish" and "create" for producer operations, "receive" for pull-based consumption and "deliver" for push-based consumption. However,...

It seems to me the [spec is deliberately unclear](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#specifying-links) in that regard: > Implementations MAY ignore links with an invalid SpanContext. The use case is a valid one, but I'm...

> Creation context is used as a parent, in addition to being added as a link. This scenario is described in [OTEP](https://github.com/open-telemetry/oteps/blob/dc619dfc70f174ef31caf90f14e8b00600da4049/text/trace/0220-messaging-semantic-conventions-span-structure.md?plain=1#L200) and was discussed when working on the https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/pull/3055#discussion_r1399074286....