-
Notifications
You must be signed in to change notification settings - Fork 477
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
SNOW-1177361: opentelemetry autoinstrumentation #1891
Comments
hi and thank you for raising this request with us ! can you please take a look at the Emitting Trace Events in Python to see if it is at least partially what can help you move forward ? |
I did not feel this documentation was very helpful for this issue for two main reasons:
|
thanks for checking still, and for providing further insight into the use-case. we'll consider this requirement for enhancement for the future. |
What is the current behavior?
None, seemingly. Using opentelemetry autoinstrumentation along with included related packages (see https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation ) a python application can get tracing data and timing for most network-related actions: http requests, database access, aws operations, etc. but snowflake is invisible.
What is the desired behavior?
Provide common database opentelemetry information if there's an active trace such that the query and timing (and calls) appear in auto-instrumented opentelemetry traces.
Barring that, documentation on how to manually collect trace information for snowflake-connector while otherwise utilizing automatic instrumentation would be helpful.
How would this improve
snowflake-connector-python
?Improved observability of any python application utilizing snowflake
References and other background
No response
The text was updated successfully, but these errors were encountered: