Re: Tracing queries within DB transactions with dbslower
Dave M
Hi Kevin,
toggle quoted message
Show quoted text
I see you've made a Github issue as well (https://github.com/iovisor/bcc/issues/4256). That's good, as I would've recommended making one since the mailing list isn't frequently used these days. I will respond in the issue as well and we can continue conversation wherever you'd prefer. The folks who did most of the implementation of `dbslower` (https://github.com/iovisor/bcc/pulls?q=is%3Apr+dbslower+is%3Aclosed) aren't particularly active in this repo these days. They might have the mysql expertise necessary to answer your question. Unfortunately I'm not sure if any of the current maintainers have experience tracing MySQL - myself included. Regardless, if you're willing to dig around in the MySQL source I do think your suggested approach of modifying which functions are uprobe'd is likely to work. If current tracing of 'dispatch_command' isn't catching the actual statements in the transaction, presumably there's some other function that is processing the text of those statements that should be fine to trace in lieu of / in addition to what's currently being traced. If you do get this working we'd certainly appreciate a PR! -Dave On Tue, Oct 4, 2022 at 3:56 AM Kevin Maier <kevin.maier@...> wrote:
|
|