Hacker News Reader

Comment by aarbor989 | Hacker News Reader

I tried using it and my first impression is that it's pretty difficult to use for a webapp (or maybe just specifically a Spring application since there are a ton of added proxy classes) without the ability to search. You need to know exactly which thread accepted your http request and then dig your way down the call stack to find your method invocation. You should be able to search for your method invocation and then go back up the call stack from there.

Other than that, seeing exactly how long every single method call took is awesome. I think there's a lot of potential, but without the ability to search I can't see myself reaching for this again

View on HN

I totally understand your point.

The search functionality is currently under development, and it's by far the most critical 'missing' feature.

As a workaround for webapps: using the 'Capturing Assistant' and configuring BugJail to capture only your own packages helps a lot. That way you usually see clearly which thread handled the request, and also have less app-server / framework level crap that you need to expand through before you get to your own code.

If you'd like to get notified when the search functionality is available, just shoot me an email (my email is in the contact page).

Thanks for providing the feedback, and sorry that the initial experience wasn't better.

Thanks for your reply. I actually did specify my packages in the agent -javaagent:/Users/aa/.BugJail/agent.jar=--snapshot:.--primary:io.mycompany. but it didn't seem to help too much. I'll shoot you an email to get notified - is there an estimated timeline?

Hmm, if setting --primary didn't help, then it might not have worked (aka Bug in BugJail..). I'd love to check that further tomorrow, if you have couple of minutes?

As for the search/query timeline, I'm afraid to say anything more exact than "month or two". The core search/query is working on dev version, but it needs a lot of work.

Reply on news.ycombinator.com