Benefits of Stagemonitor over JMX monitoring

Question

How does Stagemonitor compare over simple JMX metrics?

Unlike java-native JMX MBeans, Stagemonitor includes an agent that sits in your Java application, sending metrics and request traces at the central database, which can be Elasticsearch.

Since both ways can serve as input for an ELK Monitoring Stack (JMX see this blog post ) what are the benefits of Stagemonitor?

Answer 1

Most of the metrics stagemonitor collects are not available via JMX. For example, response time statistics grouped by the endpoint of your application.

Also, stagemonitor is much more than just metrics. It is also a profiler, you can use to see which methods caused a request to be slow. Further more, it can (soon) do distributed tracing which helps you to analyze and debug latency problems in a microservice environment by correlating related requests. It also offers you a Kibana dashboard you can use to drill into the requests your application serves to find out about causes of errors or latency. Another use case is lightweight web analytics to identify which devices and operating systems your customers use to access your site.