JavaMelody Overhead instead of JMX

Question

I am looking for a Monitoring tool for tomcat. I found the thread here: https://stackoverflow.com/questions/242958/best-tools-to-monitor-tomcat

I noticed JavaMelody and installing it took only 10 minutes. However, I have the following question which results from having added JavaMelody as a filter in web.xml,

Doesn't this mean that all requests go through JavaMelody before reaching my servlet? So this adds an additional overhead to process every request.

This seems at first to me to be a deal breaker for production servers handling large numbers of requests. Comments?

Answer 1

I really think that javamelody users can write and give their own answer(s).

Meanwhile, some information is available about javamelody overhead in production.

It seems to me that javamelody overhead is not a deal breaker. (I am the author of javamelody)