Christian Neumüller

> Like what the heck are they....a file, a GRPC operation, a HTTP request, a DB query, something else? > > Not at all obvious. The details are specified in...

> Because I don't see how Otel is going to work with Datadog using the it can intelligently produce an operation and resource ("type" and "name"). All semantic conventions should...

Since that would be quite coarse-grained (there is a network-request in-between) I guess it cannot really be used to improve accuracy, but at least it could be used to catch...

The way protobuf works is that fields are not sent over the wire if they are not set (or set to the default/zero). So for OTLP this would not be...

Exactly. The difficult to get right (but specified!) order (exporting may happen before the other OnEnd processor) is another problem, but the main problem is that spans are already ended,...

No, the main issue is that in OnEnd the span is already ended, and for an ended span, SetAttribute should be a no-op. Changing that seems liable to opening a...

Maybe we would even need a special state where the span is semi-ended, i.e. it has IsEnded==true and has an end timestamp, but is still recording.

Agree with @bogdandrutu. I'm not sure which implemenation language you are using but in Java there is https://github.com/open-telemetry/opentelemetry-java/blob/v0.9.1/sdk_extensions/tracing_incubator/src/main/java/io/opentelemetry/sdk/extensions/incubator/trace/data/SpanDataBuilder.java Unfortunately, #158 is not resolved so this is all a bit vague...

@tsloughter > Where is there a pluggable place to modify SpanData before export? The exporter interface. You can make your own exporter that wraps an existing one and does the...

@iNikem > Processor can certainly modify SpanData True, but in order for the "modification" (SpanData is immutable at least in Java, so it actually creates an updated copy) to be...