Generate semconv package for 1.4.0

[tigrannajaryan]

Now that spec 1.4.0 is release we need to generate semconv 1.4.0 and update SDK's resource detectors to use it.

I can generate semconv/trace.go and semconv/resources.go using the generator but I don't know how to generate semconv/http.go, exception.go, etc.

@MrAlias @Aneurysm9 can you help?

[MrAlias]

We should also document this process and decide on open-telemetry/opentelemetry-collector#2600

[tigrannajaryan]

It is partially documented here https://github.com/open-telemetry/opentelemetry-go/blob/main/RELEASING.md#semantic-convention-generation but only says how to generate trace.go and resource.go.

[MrAlias]

It is partially documented here https://github.com/open-telemetry/opentelemetry-go/blob/main/RELEASING.md#semantic-convention-generation but only says how to generate trace.go and resource.go.

Ah, gotcha. I missed that 👍

[MrAlias]

@tigrannajaryan I think the http.go and exception.go are hand crafted and not generated because they do not have yaml definitions. I think if you run the generator based on the docs you shared that you should accomplish all that we can with the generation.

[tigrannajaryan]

they do not have yaml definitions.

I see some yamls: https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/trace/http.yaml and https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/trace/exception.yaml

[MrAlias]

I see some yamls: https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/trace/http.yaml and https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/trace/exception.yaml

Interesting, I must have misunderstood the generation gap for these files then. @Aneurysm9 is going to have a lot more context here.

[Aneurysm9]

they do not have yaml definitions.

I see some yamls: https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/trace/http.yaml and https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/trace/exception.yaml

Those are generated into trace.go. http.go contains two values we've used commonly in instrumentation that aren't in the conventions as an enumeration and some helper functions that can probably just be copied wholesale. exception.go includes a constant for the event name used with exceptions that could probably move closer to where it is used if it isn't going to be included in the conventions.

[tigrannajaryan]

So do we just copy existing http.go and exeception.go and we should be good?

[Aneurysm9]

Yeah, that's what I'm going to do. I'll have a PR up shortly.