5 ms·

Database-backed debugging is great! It means that debugging can be done as a data science exercise, which is very useful when, for example, a rare confluence of

Database-backed debugging is great! It means that debugging can be done as a data science exercise, which is very useful when, for example, a rare confluence of external factors make the program behave badly. Earlier examples: "Debugging in the (very) large", which describes how Microsoft used Windows telemetry, especially for debugging weird slow-down glitches. In the networking domain, where there is AppDynamics for trying to debug the interactions between network and distributed services. I'd love to see data-science style debugging much more accessible (especially in Python). And it's great to see that you're making a serious effort to get the user experience right -- though I hope that the underlying data will also be accessible from more capable data science platforms.

HenriNext 7y ago
BugJail writes its data files in open source format, Apache ORC. You can load the data files directly to Spark, Hive or anything else that reads ORC, and then use Python to query, visualize or get statistics from the captured program execution. Give it a try and let me know how it goes?
- rmetzler 7y ago
  I think it might be really useful to run BugJail as an (optional) CI step and offer the user to download, integrate with the IDE, or have historical data. But I didn't fully understand the license regarding such usecases.
  - HenriNext 7y ago
    Absolutely. The long term plan is to do separate edition "BugJail for CI/QA/SIT/UAT/PreProd/etc", so that when things-are-not-fine on server, you don't need to repro but just load the capture in BugJail and see what happened [edit: that in addition to your "post CI build step" use case; both uses seem compelling]. But the current beta version is not robust enough and doesn't handle long captures well enough. I want to make sure that BugJail doesn't waste people's time, hence the license allows only capturing from local workstation.

HenriNext 7y ago

BugJail writes its data files in open source format, Apache ORC. You can load the data files directly to Spark, Hive or anything else that reads ORC, and then use Python to query, visualize or get statistics from the captured program execution. Give it a try and let me know how it goes?

rmetzler 7y ago
I think it might be really useful to run BugJail as an (optional) CI step and offer the user to download, integrate with the IDE, or have historical data. But I didn't fully understand the license regarding such usecases.
- HenriNext 7y ago
  Absolutely. The long term plan is to do separate edition "BugJail for CI/QA/SIT/UAT/PreProd/etc", so that when things-are-not-fine on server, you don't need to repro but just load the capture in BugJail and see what happened [edit: that in addition to your "post CI build step" use case; both uses seem compelling]. But the current beta version is not robust enough and doesn't handle long captures well enough. I want to make sure that BugJail doesn't waste people's time, hence the license allows only capturing from local workstation.