Search

GC easy – Universal Java GC Log Analyser

Category

Features

Health Check Status Page

Debug/Diagnostic information about the application and JVM instance is published in the health check status page. In the health check status page, the following information is printed in the JSON format:

Continue reading “Health Check Status Page”

GCeasy API – Remote Location

In Garbage collection log analysis API we have introduced a new feature called Remote Location. Using this feature now you can pass the http(s) URL location of your GC log in the request.

Continue reading “GCeasy API – Remote Location”

jstat – Analysis

jstat is a simple utility tool, that is present in JDK to provide JVM performance-related statistics like garbage collection, compilation activities. The major strength of jstat is its ability to capture these metrics dynamically when JVM is running without any pre-requisite instrumentation. What do we mean by it? Say for example if you want to capture garbage collection related statistics, you need to pass below arguments before you start the JVM:

Continue reading “jstat – Analysis”

HOW TO INVOKE GC LOGS ANALYSIS API THROUGH POSTMAN

GCeasy provides powerful REST API to analyze Java GC logs. This API can be used for application monitoring, analyzing code quality during CI/CD pipeline, proactive production monitoring, and several other purposes. This document walks through the steps involved in invoking this REST API through the Postman tool.

Continue reading “HOW TO INVOKE GC LOGS ANALYSIS API THROUGH POSTMAN”

KEY ELEMENTS IN API RESPONSE

GCeasy’s JSON APIs are used for application monitoring, analyzing code quality during CI/CD pipeline and several other purposes. API response contains rich set of information (i.e. lot of elements). In this article, we intend to highlight to few key elements in the API response. If values of these elements exceed or drops below the certain threshold, then you might consider raising alerts/warnings.

Continue reading “KEY ELEMENTS IN API RESPONSE”

GC LOG STANDARDIZATION API

Based on the JVM version (1.4, 5, 6, 7, 8, 9), JVM vendor (Oracle, IBM, HP, Azul, Android), GC algorithm (Serial, Parallel, CMS, G1, Shenandoah) and few other settings, GC log format changes. Thus, today the world has ended up with several GC log formats.

Continue reading “GC LOG STANDARDIZATION API”

Powered by WordPress.com.

Up ↑