-
Notifications
You must be signed in to change notification settings - Fork 664
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
Add trace integration with PostgreSQL #265
Comments
I would like to work on this integration, please assign to me to avoid work duplication |
You're going crazy with the integrations! Keep it up! |
Is there any way to write a more general integration or integration base layer based on https://www.python.org/dev/peps/pep-0249/ Python Database API Specification v2.0 "DBAPI"? |
@Oberon00 I have seen a couple of different DB libraries and usually follow the DBAPI in some way or another, we can have some shared code when possible, at the end we will need the specific library integration because the patching or hook if provided would be different, in the case of psycopg plenty of the code is written on C and they have a Python wrapper on top, so patching would be entirely different to other libraries, what would be a good way to share code for DB integrations?, creating another ext package like OpenCensus? |
Yes, I think something like a |
Closing this as we now have dbapi and pyscopg2. |
OpenCensus currently supports trace integration with Psycopg library, being one of most popular for PostgreSQL
http://initd.org/psycopg/
Other popular libraries could be also considered in the future
https://wiki.postgresql.org/wiki/Python
The text was updated successfully, but these errors were encountered: