open-telemetry / open-telemetry/opentelemetry-python-contrib

Feature request: support mssql instrumentation

Open
#1,992 5 comments 1 reaction 1 assignee View on GitHub

@rahulhacker is already working on this.

Since Sep 9, 2024.

feature-request
Dominant language
Python
Stars
1.1k
Forks
1.1k
Avg merge
4d 15h
Merged PRs (30d)
16

Description

Describe your environment Describe any aspect of your environment relevant to the problem, including your Python version, platform, version numbers of installed dependencies, information about your cloud hosting provider, etc. If you're reporting a problem with a specific version of a library in this repo, please check whether the problem has been fixed on main.

I have an python flask application connected to mssql server using pyodbc driver.
I am instrumenting my application following this guide: https://opentelemetry.io/docs/instrumentation/python/automatic/
I realized that no traces or metrics are being generated for my mssql server queries.

I have tested the same application and the same installation of open telemetry, but connecting to mysql and postgres database and the traces and metrics are generated correctly.

Does Open Telemetry support pyodbc? (for automatic instrumentation)

Steps to reproduce
Describe exactly how to reproduce the error. Include a code sample if applicable.

Configure pyodbc driver: https://learn.microsoft.com/es-es/sql/connect/python/pyodbc/step-3-proof-of-concept-connecting-to-sql-using-pyodbc?view=sql-server-ver16
Configure open telemetry automatic instrumentation: https://opentelemetry.io/docs/instrumentation/python/automatic/

What is the expected behavior?
What did you expect to see?

I expect to see traces of my mssql queries, just as I see traces when the queries are on mysql or postgres.

What is the actual behavior?
What did you see instead?

Mssql related traces are not generated.

Additional context
Add any other context about the problem here.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.