Now you can see detailed data for individual Pods, Containers and Nodes in your Kubernetes
We started off a few months ago as a JVM monitoring service. We have continued adding features to our service ever since in our commitment to make the best possible Java performance monitoring service.
With the addition of today’s features, we have graduated from a JVM monitoring service to an APM!
Lets walk through them:
A new interface
This is the first thing you will notice. The interface has been fully reworked to support all the new features.
This shows you an overview of your entire application, across all the transactions and all the JVMs. Right at a glance you can see whether you are spending most of your time in your own code or some external REST service or MongoDB.
Lists all the transactions in your code and their performance. Now each transaction will have a code level breakdown of where the time is being spent most.
Shows any service you are communicating through REST, be it a third party service or some node internal in your application. Alongside the response time and throughput, you can even see exactly which transaction is spending the most time in each service, allowing you to know exactly where to optimize.
Just like REST services above, this view shows how MongoDB affects your application performance.
See the exact versions of each dependency of your application and your app server, jvm etc. Very useful when you want to answer questions like ‘whats the version of spring that is running?’
JVM Stats and Alerts
And of course, the JVM level stats and the High GC and High Memory usage alerts continue to stay and serve :-)
Upgraded DripStat Agent
You will need to update to the latest version of DripStat agent, version 3.5.0 to see all these features in your own application.
We have taken 1 jvm from our cluster and exposed it publicly to you to see a live demo of all the above features.