Robert Pająk

> Logging the exception instead could also work in this case, although a span has the slight benefit that it also records the duration of the actual endpoint function separate...

> @pellared Span.RecordException(ex) already couples trace api with semconv ~~@lmolkova, I am aware and I do not like this design. In my opinion, API should not be coupled to to...

Related OTel Go "hanging" PR: - https://github.com/open-telemetry/opentelemetry-go/pull/5762 I think it is safe to start with Semantic Conventions to allow using `exception.*` attributes directly on the span and consider enhancing the...

I can say that such setup is possible. I can create prototype in Go if necessary. Otherwise, I plan to close it next week. But maybe you want to make...

> If this concept is useful for other languages, we could reserve one of the bits in [LogRecord.flags](https://github.com/open-telemetry/opentelemetry-proto/blob/049d4332834935792fd4dbd392ecd31904f99ba2/opentelemetry/proto/logs/v1/logs.proto#L186). This could be useful for standardizing the prevention of double recording logs...

> [AnyValue](https://github.com/open-telemetry/opentelemetry-proto/blob/342e1d4c3a1fe43312823ffb53bd38327f263059/opentelemetry/proto/common/v1/common.proto#L28-L67) is a recursive data structure, and the common attribute limits were designed for a flat list of key value pairs. Here's how we might apply the rules to...

@AndrewWPhillips, I guess you have not configured the endpoint for the exporter correctly. Not that the default value is `https://localhost:4318/v1/traces` (HTTPS) and not `http://localhost:4318/v1/traces`. Can you please double-check?