Persistent instrumentation for Java

Question

We have an application at work that we'd like to monitor for performance. Actually, what we want to monitor is not our app's performance, but things like response time for external web services we invoke.

Years ago, using ATG Dynamo, you could instrument your code with something like...

Performance.monitorStart("my.operation");
try {
  // code goes here
}
finally {
  Performance.monitorEnd("my.operation");
}

; this generated a nice report of the time spent in diverse operations, in a friendlier way than hprof. Ideally, the time should be persisted (db or otherwise).

I recall seeing somewhere (here? Dzone? TSS?) about a new library that does this, but googling reveals nothing.

Thoughts?

Alex

score 2 · Accepted Answer · answered Feb 22 '11 at 11:39

2

What you're describing sounds a lot like Perf4J.

answered Feb 22 '11 at 11:39

Michael Borgwardt

342,105
78
482
720

score 0 · Answer 2 · answered Feb 22 '11 at 11:38

0

Springsource TC Server (which is a Tomcat++) with Insight enabled has been helpful to me

It will time your entire call-stack and give you nice reports. Here's a screencast http://www.youtube.com/watch?v=nBqSh7nVNzc

answered Feb 22 '11 at 11:38

Hans Westerbeek

5,645
3
34
35

score 0 · Answer 3 · answered Feb 22 '11 at 13:41

Since you are already showing an example where code changes are involved, you could simply roll your own using your probably existing logging facility.

Another option would be JMX beans for live statistics - this option is often used together with a 'professional' monitoring facility which aggregates these statistics.

Persistent instrumentation for Java

3 Answers3