Semantic conventions catch up

[pollosp]

Hello,

I hope everything is going well on your side.

Currently in our organisation, we use multiple programming languages, including Ruby and Java. We've noticed that the Ruby semantic conventions are not as up-to-date as those for Java. This discrepancy impacts us because certain attributes are named differently, complicating our data queries and mining.

We have reviewed the SIG meeting logs from April 9th, which mention:

We're stuck with the values we have today until we can come up with a solution to change these things, with the caveat that we
 need to check the spec on this stuff to see if it's true 
(it's true for HTTP because it's gone stable, but for things that aren't stable, break things)

Given this context, we're unsure if there is active work being done to address this issue or if there is a way we can help here.

Currently, we are considering a few potential solutions on our end, such as monkey patching in our OTEL wrapper, forking the repo and modifying the attributes ourselves, or replacing these attributes in the collector until you catch up with the semantic conventions.

Before proceeding, we wanted to reach out to your team to understand the current state of this issue and to seek your advice on the best course of action. Any guidance or updates you can provide would be greatly appreciated.

Thank you for your time and assistance.

Best regards,

[arielvalentin]

We need all the help we can get. @robbkidd had been experimenting with dynamic comparability between schema versions in the semconv gem.

We're looking for help from folks willing to update instrumentations to support the environment variable opt-in options and maintain comparability with pre-1.0 schemas

Please file an issue in the contrib repo and build out a task list to help us keep track of your work. We'll start reviewing PRs as soon as we can.

Thanks again for your willingness to help!