Alexander Wert

> @AlexanderWert has that been discussed already? Yes, those will stay `trace_id`, `span_id` in non-OTLP log formats: - https://github.com/open-telemetry/opentelemetry-specification/pull/3469 - https://github.com/open-telemetry/opentelemetry-specification/issues/3518

To provide some input from the [ECS](https://www.elastic.co/guide/en/ecs/current/ecs-url.html) perspective to this: Being more explicit about all the URL-related aspects and group them under a common namespace would allow to address the...

Hi Jürgen 👋 , the profiling agent / donation is currently under review by a group of volunteers from the Profiling SIG. Once that is done, there will be a...

A new PR has been created for this proposal in https://github.com/open-telemetry/oteps/pull/222. We would appreciate the discussion to continue there and see the approvals from this PR to be "transferred" to...

@open-telemetry/specs-approvers Is anything missing in this proposal to get approvals / reviews? There seems to be quite some interest for this and also https://github.com/open-telemetry/opentelemetry-proto/pull/384 seems to be waiting on this.

- With https://github.com/open-telemetry/opentelemetry-specification/pull/3257 being merged, the parent SpanContext (including the parent's `IsRemote` information) is specified as something that must be exposed on the `ReadableSpan`. So, [this comment](https://github.com/open-telemetry/oteps/pull/182#discussion_r969725628) should be resolved....

> I think all the `faas.*` fields should be on transaction metrics only. @AlexanderWert would you agree with that? Yes, that's true.

> I remember there were some oddities with FAAS data where some of it was handled differently than regular transactions. I don't immediately remember what it was, but maybe @AlexanderWert...

@Oberon00 Aren't we mixing up two things here? The flags [defined on a span (or a link) in opentelemetry-proto](https://github.com/open-telemetry/opentelemetry-proto/blob/ac3242b03157295e4ee9e616af53b81517b06559/opentelemetry/proto/trace/v1/trace.proto#L126) is a 32 bit field that conveys information about that span...

@open-telemetry/specs-semconv-approvers @open-telemetry/specs-semconv-maintainers would love your thoughts on the above!