otelconv only generates synchronous instruments

[dashpole]

Description

In #6393, I need to define an asynchronous UpDown counter for the "otel.sdk.processor.span.queue.size" and , "otel.sdk.processor.span.queue.capacity" metrics.

However, these are hard-coded as an Int64UpDownCounter:

opentelemetry-go/semconv/v1.34.0/otelconv/metric.go

Lines 1598 to 1600 in 291140b

	type SDKProcessorSpanQueueSize struct {
	metric.Int64UpDownCounter
	}

Expected behavior

I expected to be able to get an asynchronous version of the metric.

@MrAlias @pellared

[MrAlias]

This can be configured here:

opentelemetry-go/semconv/weaver.yaml

Lines 71 to 83 in 826a8ec

	cpu.time: Float64ObservableCounter
	go.config.gogc: Int64ObservableUpDownCounter
	go.goroutine.count: Int64ObservableUpDownCounter
	go.memory.allocated: Int64ObservableCounter
	go.memory.allocations: Int64ObservableCounter
	go.memory.gc.goal: Int64ObservableUpDownCounter
	go.memory.limit: Int64ObservableUpDownCounter
	go.memory.used: Int64ObservableUpDownCounter
	go.processor.limit: Int64ObservableUpDownCounter
	process.cpu.time: Float64ObservableCounter
	system.memory.usage: Int64ObservableUpDownCounter
	system.memory.utilization: Float64ObservableGauge
	system.network.io: Int64ObservableCounter

[dashpole]

I assume that will only apply to the next version of semconv? Or is otelconv not stable?

[MrAlias]

Correct. Which seems fine since v1.36.0 needs to be generated and included in the next release.

[MrAlias]

[...] since v1.36.0 needs to be generated and included in the next release.

#7030

[MrAlias]

@dashpole I can get a PR up to resolve #7030 and after that is merged you can make a PR to change the instrument type and regenerate? Or, would you be interested in addressing #7030 and this issue all in one PR?

[dashpole]

Don't block on me. I'll update and fix after you generate it.

[MrAlias]

#7032