snowflakedb / snowflakedb/snowflake-connector-python

SNOW-1177361: opentelemetry autoinstrumentation

Open
#1,891 4 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature status-triage_done v5.0.0
Dominant language
Python
Stars
730
Forks
574
Avg merge
5h 45m
Merged PRs (30d)
16

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked opentelemetry-python-contrib instrumentation packages and review how snowflake-connector-python currently exposes query execution and documentation. Determine whether the intended result is automatic tracing or guidance for manual collection; done means Snowflake queries and timing appear in an active trace, or the manual setup is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
databases, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.