Enable debugging tracing of SQL queries #2467
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2467 +/- ##
===========================================
- Coverage 64.69% 26.53% -38.16%
===========================================
Files 398 399 +1
Lines 19681 19714 +33
===========================================
- Hits 12733 5232 -7501
- Misses 6033 13925 +7892
+ Partials 915 557 -358
... and 128 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Thank you very much for sending the PR!
Yes, this approach is something we want to start from. Of course, we want to add an ability to trace requests, so those pgdb spans will become parts of some other spans. But it's for a separate issue. For now, we just want to start seeing at least some data :)
I added a couple of comments about TraceQueryStart and TraceQueryEnd implementation - let's add some data as span attributes, so we can see some actual info about the queries in Jaeger.
Head branch was pushed to by a user without write access
Description
Closes #2389.
I had a quick go at trying to resolve #2389. Is this the approach you would like to take? I can see the spans in Jaeger, but, afaict, they are not part of anything else.
Readiness checklist
task all, and it passed.@FerretDB/core), Labels, Project and project's Sprint fields.