-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Add OpenTelemetry support #818
Labels
enhancement
New feature or request
Comments
Also, semantic conventions can look like Elasticsearch for third party support. |
Would love this! Does anyone care to contribute? We can go the elastic route, but as always please make sure not to be copying/looking at any non-APLv2 compatible code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
Currently there is no OpenTelemetry instrumentation for the OpenSearch python client.
A good telemetry setup can aid developers to better monitor and diagnose issues with the requests being performed from their apps against an OpenSearch instance.
What solution would you like?
Something similar to elastic/elasticsearch-py#2435
What alternatives have you considered?
There was a proposal to handle this by the community via monkeypatching open-telemetry/opentelemetry-python-contrib#1131 but has not gained any traction.
Official support has the advantage of having the telemetry instrumentation evolve with the code of the client itself.
The text was updated successfully, but these errors were encountered: