Problem Statement
Instead of hard-coding bucket boundary options in instrumentation code like open-telemetry/opentelemetry-go-contrib#8642, do it in the generated code to make it cleaner.
Proposed Solution
Similar to how we choose between observable and synchronous instruments, we could list all of the custom bucket boundaries in https://github.com/open-telemetry/opentelemetry-go/blob/main/semconv/templates/registry/go/weaver.yaml, and generate the option. For example, we have the same bucket boundaries provided for a bunch of http instrumentation libraries.
Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.