At the end of November, we’ll be migrating the Sematext Logs backend from Elasticsearch to OpenSearch

Introducing JVM logs integration

September 30, 2021

If you run applications on top of the JVM you know how critical garbage collection is for application performance. Some of the information about JVM performance can be collected from JMX, which is what our JVM monitoring integration exposes in a set of out-of-the-box dashboards. But the JVM also logs a bunch of useful information. Unfortunately, these logs are not designed for humans. They are not easy to interpret quickly. That’s why we are happy to announce a new integration – the JVM Logs Integration. It gleans insights about the JVM garbage collection performance from the JVM logs and presents them in a set of easy-to-understand dashboards. Using the Split Screen you can also correlate other JVM performance metrics with JVM GC data extracted from logs.

Here are some insights this new integration provides:

  • Details about your JVM garbage collector runs including new and tenured generations’ statistics
  • Region information, such as survivor region size after garbage collection and new generation region size after garbage collection.
  • Time your application threads were stopped because of garbage collection, and much more.

JVM GC Overview

The easiest way to get started is using the Logs Discovery that, if you are running a recent version of Sematext Agent, will let you select the JVM logs you want to ship to Sematext, so you can set up log shipping in about a minute just through the Discovery screen (EU). Learn more about this JVM Garbage Collection logs integration. Enjoy!