open-telemetry/opentelemetry-python-contrib issues and pull requests

#1648 - Document how to instrument SQLAlchemy manually for PostgreSQL

Issue - State: open - Opened by AkselAllas almost 2 years ago - 3 comments
Labels: bug

#1644 - Make sure remoulade instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1644 - Make sure remoulade instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1644 - Make sure remoulade instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1643 - Make sure pika instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1642 - Make sure kafka-python instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1641 - Make sure confluent-kafka instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 2 comments
Labels: good first issue, help wanted, instrumentation

#1640 - Make sure celery instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1640 - Make sure celery instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1640 - Make sure celery instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1640 - Make sure celery instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1639 - Make sure boto3sqs instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1639 - Make sure boto3sqs instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1638 - Make sure aio-pika instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 2 comments
Labels: good first issue, help wanted, instrumentation

#1637 - Make sure messaging instrumentations follow semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 6 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 4 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1634 - Make sure dbapi instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 3 comments
Labels: good first issue, help wanted, instrumentation

#1632 - Make sure mysql instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 2 comments
Labels: good first issue, help wanted, instrumentation

#1630 - Make sure pymemcache instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1630 - Make sure pymemcache instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1628 - Make sure pymysql instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 4 comments
Labels: good first issue, help wanted, instrumentation

#1627 - Make sure redis instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 7 comments
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1626 - Make sure sqlalchemy instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1625 - Make sure sqlite3 instrumentation follows semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: good first issue, help wanted, instrumentation

#1624 - Make sure database instrumentations follow semantic conventions

Issue - State: open - Opened by srikanthccv almost 2 years ago - 1 comment
Labels: bug, good first issue, help wanted, instrumentation

#1600 - Update http instrumentations to spec v1.17 for semantic conventions

Issue - State: closed - Opened by lzchen almost 2 years ago - 1 comment
Labels: instrumentation, specification

#1598 - add elasticsearch db.statement sanitization

Pull Request - State: closed - Opened by nemoshlag almost 2 years ago - 4 comments

#1598 - add elasticsearch db.statement sanitization

Pull Request - State: closed - Opened by nemoshlag almost 2 years ago - 4 comments

#1598 - add elasticsearch db.statement sanitization

Pull Request - State: closed - Opened by nemoshlag almost 2 years ago - 4 comments

#1598 - add elasticsearch db.statement sanitization

Pull Request - State: closed - Opened by nemoshlag almost 2 years ago - 4 comments

#1598 - add elasticsearch db.statement sanitization

Pull Request - State: closed - Opened by nemoshlag almost 2 years ago - 4 comments

#1598 - add elasticsearch db.statement sanitization

Pull Request - State: closed - Opened by nemoshlag almost 2 years ago - 4 comments

#1598 - add elasticsearch db.statement sanitization

Pull Request - State: closed - Opened by nemoshlag almost 2 years ago - 4 comments

#1595 - opentelemetry-bootstrap too many false positives

Issue - State: open - Opened by dimaqq almost 2 years ago - 2 comments
Labels: bug

#1595 - opentelemetry-bootstrap too many false positives

Issue - State: open - Opened by dimaqq almost 2 years ago - 2 comments
Labels: bug

#1584 - Resource detector for container properties

Pull Request - State: closed - Opened by sanketmehta28 almost 2 years ago - 12 comments
Labels: enhancement

#1583 - Conformity of client intereptor(s) with the official `grpc.*ClientInterceptor`-interfaces

Pull Request - State: open - Opened by CoLa5 almost 2 years ago - 1 comment

#1582 - Add instrumentation for threading module

Pull Request - State: closed - Opened by pridhi-arora almost 2 years ago - 18 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1564 - Fix UnboundLocalError in asgi handler

Pull Request - State: open - Opened by mike-baker-on almost 2 years ago - 2 comments

#1554 - Django with sql commentor functionality duplicates SQL queries in debug mode and CaptureQueriesContext

Issue - State: open - Opened by phillipuniverse almost 2 years ago - 3 comments
Labels: bug

#1543 - Missing db.statement / db.operation sensitive data sanitization option

Issue - State: open - Opened by nemoshlag almost 2 years ago - 7 comments
Labels: help wanted, instrumentation, feature-request

#1543 - Missing db.statement / db.operation sensitive data sanitization option

Issue - State: open - Opened by nemoshlag almost 2 years ago - 7 comments
Labels: help wanted, instrumentation, feature-request

#1543 - Missing db.statement / db.operation sensitive data sanitization option

Issue - State: open - Opened by nemoshlag almost 2 years ago - 7 comments
Labels: help wanted, instrumentation, feature-request

#1543 - Missing db.statement / db.operation sensitive data sanitization option

Issue - State: open - Opened by nemoshlag almost 2 years ago - 8 comments
Labels: help wanted, instrumentation, feature-request

#1543 - Missing db.statement / db.operation sensitive data sanitization option

Issue - State: open - Opened by nemoshlag almost 2 years ago - 8 comments
Labels: help wanted, instrumentation, feature-request

#1532 - Falcon exceptions should not always be masked as 500 and marked as error

Issue - State: open - Opened by andre-meneses-fivestars almost 2 years ago - 4 comments
Labels: feature-request

#1532 - Falcon exceptions should not always be masked as 500 and marked as error

Issue - State: open - Opened by andre-meneses-fivestars almost 2 years ago - 3 comments
Labels: feature-request

#1532 - Falcon exceptions should not always be masked as 500 and marked as error

Issue - State: open - Opened by andre-meneses-fivestars almost 2 years ago - 4 comments
Labels: feature-request

#1514 - Add link validation check

Issue - State: open - Opened by codeboten almost 2 years ago - 3 comments
Labels: good first issue, help wanted

#1514 - Add link validation check

Issue - State: open - Opened by codeboten almost 2 years ago - 1 comment
Labels: good first issue, help wanted

#1514 - Add link validation check

Issue - State: open - Opened by codeboten almost 2 years ago - 3 comments
Labels: good first issue, help wanted

#1478 - Instrumentation raises uncaught exception on non utf-8 request header sequences

Issue - State: closed - Opened by marianogappa almost 2 years ago - 19 comments
Labels: bug, help wanted, instrumentation

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: closed - Opened by nozik almost 2 years ago - 11 comments

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: closed - Opened by nozik almost 2 years ago - 11 comments

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: closed - Opened by nozik almost 2 years ago - 11 comments

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: open - Opened by nozik almost 2 years ago - 6 comments

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: open - Opened by nozik almost 2 years ago - 7 comments

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: open - Opened by nozik almost 2 years ago - 6 comments

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: open - Opened by nozik almost 2 years ago - 6 comments

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: open - Opened by nozik almost 2 years ago - 6 comments

#1476 - Add aws lambda instrumentation hooks

Pull Request - State: open - Opened by nozik almost 2 years ago - 6 comments

#1475 - grpc aioserver context the code getting

Issue - State: open - Opened by ezinall almost 2 years ago - 2 comments
Labels: bug, help wanted, instrumentation

GitHub / open-telemetry/opentelemetry-python-contrib issues and pull requests