Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Our First Steps Towards the Monitoring Solution

DZone's Guide to

Our First Steps Towards the Monitoring Solution

· Java Zone ·
Free Resource

Verify, standardize, and correct the Big 4 + more– name, email, phone and global addresses – try our Data Quality APIs now at Melissa Developer Portal!

Last Friday we rolled out an update to our services. This update, labeled 3.8, is most likely the biggest change we have made in our product. In this post I will guide you through the changes. If you have three minutes, stay with me, there are some truly interesting additions and changes to brag about.

As one picture is worth a thousand words, I thought to illustrate our progress with a screenshot from the 3.8 Plumbr in action.

java memory leak monitoring

On this screenshot, there are two changes I wish to talk about. First of those is the significantly improved value proposition on memory leak detection. Until version 3.7 Plumbr was only able to communicate the presence of a memory leak. When the application did not contain one, Plumbr was completely silent.

From Plumbr 3.8 we communicate the lack of problems as well – when you monitor your services with Plumbr agent attached the green lights on memory and permgen leak sections give you the confidence that the application does not leak memory neither in heap or permgen.

Second major change is addition of new type of problem being monitored. Asides memory leaks, Plumbr can now detect long GC pauses and, as with memory leaks – give you guidelines how to alter your application in order to reduce the pause times. Following is an example of long GC pause being detected and a solution being offered:

GC latency issues java

As seen from above – the JVM is deployed on a machine with four cores but is configured to run on Serial GC. Serial GC uses only  one core, thus the first significant win is to migrate to Parallel GC, shortening the individual pause times significantly.

We have kept the GC pause detection in closed beta for two months and have detected thousands of long GC pauses during the period. But we admit that our solution algorithms are not yet mature, so we are releasing this functionality in Beta mode. In case you face unexpected behaviour, let us know and one of our core engineers will contact you soon.

We continue to work towards expanding the set of performance problems Plumbr is able to safeguard your application against, so stay tuned for updates already in following months. Or, better yet, go and get rid of your performance problems with the help of the latest Plumbr release.

Developers! Quickly and easily gain access to the tools and information you need! Explore, test and combine our data quality APIs at Melissa Developer Portal – home to tools that save time and boost revenue. Our APIs verify, standardize, and correct the Big 4 + more – name, email, phone and global addresses – to ensure accurate delivery, prevent blacklisting and identify risks in real-time.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}