(Reviews written by the users after using the tool)
Very useful and nice reports!
This is Awesome...!
|By n.van.klaveren, topdesk|
Hi guys, just trying to see if a Json heapdump generated through the Jolokia JMX over REST agent would work, but it seems it tries to interpret it by a (very forgiving) JvisualVM text based dump. While your program claims to have found "no problems" during parsing, the outcome (except for totals of thread states) is completely useless. A shame, since for a lot of cloud based applications JMX over REST is the only way to get heapdumps. Correct parsing should be relatively trivial to implement as well.
This is what i was looking for. Nicely done. PS: I hope the data shared is kept confidential.
Useful report for developer
|By gerald.cussen, alfresco|
I'm looking at a problem where a thread dump is captured every minute over a 24 hour period. Therefore it's important to have the report display the time and date each thread dump was captured. For example, a source thread dump file contains this information on line 1: Thread dump triggered at 2017-07-26 09:39:01 but this information is not displayed in the report