Hi,
I've got a Java application that I want to monitor. I've added the API MonitorFactory.start("nameofmethod") and stop() to all methods. When I open the Jamon interface, I see different calls and not the ones I was expecting (the ones with the name of my methods). Am I missing some configuration?
Is the screen snapshot from your running instance? If so , it looks like jamon is wired up correctly. I see SQL stats, and garbage collection stats so that is good.
Your problem is probably the most common one that I see (almost 100%). If your code is executing and not throwing exceptions that means it is finding the jamon jar, but you probably have the jamon jar deployed twice
Your application is writing to one jamon jar (yourapp->jamonjar1)
The jamon web app is reading from a different jamon jar and so can't see your data. (webconsole<-jamonjar2)
Typically this is caused when you install the jamon jar both in the web app (usually the jamon.war web app) as well as at the server level. You just want to deploy it at the server level.
Search your application classpath and see if you have multiple jamon jar files. If in your application you log (something like System.out.println(MonitorFactory.getReport()) after you have populated you should see all of your data.
Steve
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I've got a Java application that I want to monitor. I've added the API MonitorFactory.start("nameofmethod") and stop() to all methods. When I open the Jamon interface, I see different calls and not the ones I was expecting (the ones with the name of my methods). Am I missing some configuration?
Is the screen snapshot from your running instance? If so , it looks like jamon is wired up correctly. I see SQL stats, and garbage collection stats so that is good.
Your problem is probably the most common one that I see (almost 100%). If your code is executing and not throwing exceptions that means it is finding the jamon jar, but you probably have the jamon jar deployed twice
Typically this is caused when you install the jamon jar both in the web app (usually the jamon.war web app) as well as at the server level. You just want to deploy it at the server level.
Search your application classpath and see if you have multiple jamon jar files. If in your application you log (something like System.out.println(MonitorFactory.getReport()) after you have populated you should see all of your data.
Steve