elasticsearch: don't produce spans if native elasticsearch support is enabled

[xrmx]

Description

If elasticsearch is found with native OTel support enabled just call the wrapped function without creating our own spans.

Fixes #2393

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• tox -e py310-test-instrumentation-elasticsearch-2

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[xrmx]

cc @pquentin

[pquentin]

Thanks for this Riccardo! I wonder, though, should we add a warning in that case?

The native instrumentation is more correct, following the semantic conventions, but also very different. If you install this package and elasticsearch-py 8.13+, you're going to be very surprised. So a warning saying to uninstall opentelemetry-instrumentation-elasticsearch because it does not cover elasticsearch-py 8.13+ would be useful IMO.

[xrmx]

Thanks for this Riccardo! I wonder, though, should we add a warning in that case?

I can add that only if we have a rate limited logger because we are still checking the span at each perform request call

The native instrumentation is more correct, following the semantic conventions, but also very different. If you install this package and elasticsearch-py 8.13+, you're going to be very surprised. So a warning saying to uninstall opentelemetry-instrumentation-elasticsearch because it does not cover elasticsearch-py 8.13+ would be useful IMO.

Will add something to the documentation

[pquentin]

I can add that only if we have a rate limited logger because we are still checking the span at each perform request call

Warnings are deduplicated already, you can run this example to see for yourself:

import warnings

def deprecated_api(message):
    warnings.warn(message, Warning, stacklevel=2)

for i in range(10):
    deprecated_api("test")

[xrmx]

Updated PR: fixed typo in env variables, added warning to the docs and code, limited tests with native Otel to elasticsearch > 8.13

[pquentin]

Thanks! LGTM.

[tammy-baylis-swi]

Thanks for comments as well