-
Notifications
You must be signed in to change notification settings - Fork 117
PostgreSQL instrumentation #415
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
PostgreSQL instrumentation #415
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #415 +/- ##
============================================
+ Coverage 83.07% 83.90% +0.83%
- Complexity 1530 1662 +132
============================================
Files 97 99 +2
Lines 6115 6642 +527
============================================
+ Hits 5080 5573 +493
- Misses 1035 1069 +34 Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Looks good to me, it needs a gitsplit entry so we can publish |
The |
My fault, fixed. |
I've just added it. It is ready to go. Should I add myself as a maintainer in the README.md? I saw that kind of info in some java isntrumentations. |
https://packagist.org/packages/open-telemetry/opentelemetry-auto-postgresql - I think packagist is complaining about "version" in composer.json: https://github.com/opentelemetry-php/contrib-auto-postgresql/blob/main/composer.json#L3 |
Please take a look into README for instrumented functions set