Thank you! We will contact you to schedule your trial.

New Version 9.5


We have again a major new version of the ADF Performance Monitor available – version 9.5 ! We have added many new valuable features and improvements. Many overview screens have got a facelift and new charts. In several blogs I will write on them.

This blog is on one of those new features, automatic SLA and health KPI warnings. The monitor will automatically interpret the metrics and will show warnings if the ADF application is not meeting the configured SLA thresholds (KPIs). Or if configured JVM and system health thresholds are not met – like JVM garbage collection, JVM CPU load, system CPU load, OS memory, database, webservice, application server, network, and browser. From now on it will be even more fast and simple to interpret the metrics. You do not have to be a performance expert/engineer, the monitor will already show the (type of) problems!

SLA Monitoring

A service-level agreement (SLA) is a commitment between a service provider and a client. Aspects of the service – quality, availability, responsibilities – are agreed between the service provider and the service user in a contract. In the world of web applications, frequently part of such a contract are the HTTP response times – to make performance guarantees. It is important to evaluate the success. For example, one company could have in an SLA contract: 80% of the requests must be processed within 1 second, 95% within 2 seconds, and 5% or less is allowed to be slower than 2 seconds.

In this new release the following KPIs are configurable:

Here the configuration screen is shown:

Application Layer Health

Application layer ‘healthKPIs can be set as well: This is the AVG Process Time spent in these layers per request:

Warnings are shown when the AVG time per HTTP request is longer than the configured thresholds:

In this example during some hours (from 00:00 to 01:00, and from 20:00 to 21:00) there were too long browser load times on average (grey color), longer than the configured threshold of 500 milliseconds. By the way see more information here on long browser load times. We can also see too long application server response times on average (blue), longer than the configured 0.50 seconds per request.

JVM and Operating System Health

The following JVM and system health KPIs can be set:

In the following paragraphs examples will be shown.

Long running JVM Garbage Collections

Garbage Collections longer than the default 10 second threshold will show like:

High System CPU Load

The system CPU load percentage depends on all the processes going on in the whole operating system, this is the total CPU load. When there are other big background processes executed on the same machine, and the load passes the threshold (default 70%), a warning will be shown. The performance of the ADF application will likely be influenced.

High JVM CPU Load

If during the peak hours (because of the load of the ADF application), the JVM process load is more than 50%, the monitor gives a warning. This should be a trigger to investigate this, and to try to bring it down:

Low Free OS Memory

When an operating system is running out, it will go swapping memory in and out – this is expensive and resource consuming. A warning will be shown if the free memory is under the threshold (configurable, in this case 4%):

Good Health

The goal is of course be alerted when something threatens the performance goals. And to act proactively to prevent performance problems.

Free 7 Day Trial

We have also a free 7-day trial, you can request it on this website at our main page (


You can purchase a license of the ADF Performance Monitor at our order page.

Share this article on social media!