As the subject says, I'm wondering what other benefits java-monitor has over what visualvm?
One thing I can think of is online/web-based monitoring, while visualvm can do remote monitoring but not through web...but on the other hand, visualvm offers benefits like taking thread/heap dump and analysing them later.
You nailed it. Heap dumps are impractical because of their size and file format nastiness between JVM versions.
Java-monitor lets you look at what happened in a JVM while it is no longer running. You can restart a JVM that has died without worrying about destroying evidence that may lead to resolving the root cause of a crash.
So there is a tradeoff you can make. One has the benefit of being closer to the JVM, while the other has the benefit of being farther away. In fact, I use both tools. ;)
Thanks for the chart Ulf. My follow up question was how java-monitor allows viewing of not-running JVM session? Does java-monitor has list of previous JVM sessions to view? Because those chart can be just showing current live session which has been alive for past 2-days or 1-week.
Kees Jan Koster
posted 7 years ago
Ah, now I understand the question: Java-monitor does not make new 'sessions' for each restart. We just collect data over time and graph it. If you switch off a JVM for a few hours and then start it back up, that will show in the graphs as a section where no data is available.
PS. And each Tuesday you get an email with the overview of the availability and number of restarts over the past week.