Skip to content

Need better OpenSearch transport instrumentation after 3.0 #14652

@mznet

Description

@mznet

Is your feature request related to a problem? Please describe.

OpenSearch Client uses the Transport interface to send requests. Before 3.0, only RestClientTransport existed and it is well covered and fully traced by opensearch-rest-client instrumentation.

Starting from 3.0, new transports were added: ApacheHttpClient5 as default and AwsSdk2. ApacheHttpClient5 can be traced with apache-httpclient instrumentation but it does not include database attributes, which means not fully covered and the same goes for AwsSdk2.

Describe the solution you'd like

If instrumentation is added on the Transport interface itself, database attributes could be captured for all transports.

Describe alternatives you've considered

No response

Additional context

[RestClient transport]
Image

[ApacheHttpClient5 transport]

Image

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.

Metadata

Metadata

Assignees

Labels

contribution welcomeRequest makes sense, maintainers probably won't have time, contribution would be welcomeenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions