Need guidance with production monitoring?
Book FREE office hours and we'll help you out
Not sure how to approach production monitoring? Book FREE office hours and we'll help you out
Kamon APM/Using Kamon APM

JVM Integration #

Services running on the JVM and collecting the JVM metrics will have a JVM integration tab, displaying charts with information collected about the Java virtual machine your service is running on. They can be split into three main categories:

The top half of the page displays garbage collection metrics - the duration and number of garbage collection intervals, with an additional split between young and old GC generations. The second section is dedicated to heap and memory usage. Here you can see the memory usage, both in heap and outside of the heap, as well as additional memory allocations in your code and promotions of memory chunks to the old generation. Finally, the third section shows durations of JVM hiccups, as well as their distribution in a percentile chart.

One particular correlation that can be of interest is that between hiccups and garbage collection time. If you have many, or very long, hiccups that do not correlate very well to the garbage collection times, it might mean that there are issues in your host setup, or that other processes are taking up resources that your service running on JVM might make better use of instead.

The JDBC integration can be access from the service overview page, where a JVM tab will appear on the top of the page if the integration is detected.

JVM integration dashboards are a feature exclusive to Kamon Telemetry. If you use OpenTelemetry with a service running on the JVM, you will not have access to this dashboard.

On this article
Kamon APM Logo
Monitor and fix issues in production without being an expert
Learn about APM
Try Kamon APM I know how Kamon APM can help with monitoring. Don't show this again.