Skip to content

SQLAlchemy instrumentation sets otel.library.name as the vendor, not the library name #922

@simondale00

Description

@simondale00

Describe your environment

  • Python 3.9.6
  • opentelemetry.instrumentation.sqlalchemy==0.28b1

Steps to reproduce

Create an application that leverages SQLAlchemy and MySQL (or any vendor; I just used MySQL)
Install opentelemetry.instrumentation.sqlalchemy==0.28b1
Make a request to your backend application.
Observe the resulting spans.

What is the expected behavior?

The otel.library.name should report as opentelemetry.instrumentation.sqlalchemy.

What is the actual behavior?

The otel.library.name is the DB vendor. In my case, it's mysql:

Screen Shot 2022-02-14 at 4 30 49 PM

This is super confusing when there is a separate opentelemetry.instrumentation.mysql package that I'm not using.

Additional context

Nope!

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomershelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions