[enrichment/trace] Update to latest semconv

[lahsivjar]

A lot of the deprecated semconv has been removed in the newer version v1.26.0. For example: net.* -> network.*.

• Decide on a support policy and backward compatibility matrix for older semconv versions
• Update to use the latest semconv.

CC: @AlexanderWert @gregkalapos

[felixbarny]

Does that break something in the trace enrichment, or are we handling both the old and the new semconv at the moment?

[lahsivjar]

We are only handling the older semconv as of now (net.*), so, any implementation with the newer semconv will not work as expected.

[gregkalapos]

I think for enrichment we'd need backwards compatibility. If we start dropping handling of those old attributes, then SDKs that still send data with it, suddenly will miss very significant things. I think we already saw that with HTTP in combination with the Node.js SDK.

Unfortunately reality is that some SDKs can still send old SemConv versions. If we'd drop handling for those, it'd not be good user experience.

Since the logic in the enrichment relies only on a small set of fields, I'd try to only add incremental changes there (and keep handling of old fields). The downside is that we can't just bump the version.

(and sorry to close with a rant: this whole thing so strange. From what I remember, the JS code that they generate contains all the deprecated fields - and then now it seems Go doesn't? Also, the SemConv repo forces people to still keep all the deprecated fields and they enforce a bunch of rules on those. Why don't they just generate those fields, e.g. under deprecated or something like that? 🤷 )