support native otel (vs. contributing to OTel Python Contrib)

[KimSoungRyoul]

hi, I have been developing opentelemetry-instrumentation-aerospike and use it last year It has been working well in my project

current:

• kimsoungryoul/opentelemetry-instrumentation-aerospike

pip install opentelemetry-instrumentation-aerospike==0.2.4 

recently, I try to contribute this library to the official opentelemetry-python-contrib repository (opentelemetry-python-contrib/#4154) to ensure better long-term maintenance. However, during the review, the OTel maintainers suggested that I reach out to you first regarding native instrumentation.

suggestion to otel-python

• feat: add opentelemetry-instrumentation-aerospike open-telemetry/opentelemetry-python-contrib#4154

pip install "opentelemetry-instrumentation-aerospike==0.61b0.dev"

I think native instrumentation is the best approach. native otel support ensures that telemetry stays perfectly in sync with client updates and offers the best "out-of-the-box" experience for developers, rather than relying on external patches or wrappers.

Here is my proposal:

I would love to contribute (opentelemetry-instrumentation-aerospike) to enable native OTel support in aerospike-client-python. If I prepare a PR, would the team have the bandwidth to review it?

suggestion for best

pip install "aerospike[otel]"

I wanted to check your preference. I am happy to adapt to whichever direction fits your team roadmap best.

Looking forward to your thoughts!

Best regards,