Kees Jan Koster

Thanks Jeanne, for organising this event. It was good fun.

Congratulations to all the winners!

Kees Jan

Dear Carol,

Yeah. Over time I learned that different people use Java-monitor in very different ways. Now I tend to opt for simplicity instead.

Kees Jan

Dear Carol,

You found the correct kick-start and the correct code to boot.

Kick-start is a one-hour, shared-screen Skype session that I do for customers. Generally they start with a Java-monitor tour and JVM intro, but after 30 minutes or so we usually switch to focus on the code and systems of the customer. What happens then is up to the customer, really. Some want to go really deep into an aspect of the JVM or their code, others prefer to talk about design aspects like fail-over and scalability or design for zero down-time deployment.

And yes, for this promo one of the give-aways is the one-on-one Kick-start. They tend to be the most fun and fruitful, because you get *your* questions answers and nothing else. ;-)

The probe is a JMX bridge that sends JMX data to the Java-monitor collector server. It does some thread handling and tries to identify what app server you are using, but not much else. The code is Open Source to allow you to inspect the code you are loading into your server. After all, you are downloading something that goes into machines you are responsible for. The code is also in the WAR, so you can see what you are getting.

I hope that answers your questions?

Kees Jan

Dear Carol,

I see you discovered the "post on forum" button too. :-)

The staging types were designed to help ordering once you have a few servers. I actually never thought to mix it with notifications. What was your expectation when you looked at the staging?

By all means put more load on your server and see what the graphs tell you.

Kees Jan

Dear Carol,

Great. Let us know what you think of Java-monitor.

Kees Jan

Dear All,

I fixed an issue with the SMS configuration page not showing up. You can now go to https://coderanch.com/forums/jmapi/phone and enter your phone number if you would like to receive SMS messages from Java-monitor.

Kees Jan

Dear Carol,

Hmm. You managed to unearth a bug in the Java-monitor Java Ranch integration. Thank you for taking the time to report this issue. So far we have not managed to reproduce it, but that is underway.

I have manually added your account to the database, can you please redeploy the probe to try again?

Kees Jan

Dear Venkata,

It goes further than that. If you have a JVM that is not a servlet container, you can also enable monitoring from code. Just unzip the WAR file and add the code to your own project.

final JavaMonitorCollector collector = new JavaMonitorCollector("1234"); collector.start();

There's more talk about that here: http://java-monitor.com/forum/showthread.php?t=2879#4

Kees Jan

Dear Meena,

Good to hear.

Kees Jan

Dear Wirianto,

It is case #1. MaaS offering (Monitoring as a Service).

Kees Jan

Dear Wirianto,

No problem.

Kees Jan

Dear Wirianto,

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.

Kees Jan

PS. And each Tuesday you get an email with the overview of the availability and number of restarts over the past week.

Thanks Ulf.

Wirianto: if you look at the top graph you can see that that JVM was restarted once or twice. You can see the data across restarts easily.

Dear Wirianto,

Woops. What gave you that idea? You can use the Java-monitor widget on JavaRanch to view statistics of your own application servers. You can't see the JavaRanch server stats, that would not be useful to you, would it?

Try the widget and see. That will make it clear I hope.

Kees Jan

Dear Wirianto,

Then Java-monitor should work just fine for all of those.

Kees Jan