Performance overview

Automatic SLA and Health KPI Warnings

Automatic SLA and health KPI warnings. Error Percentage, Very Slow Requests Percentage, AVG Server Process Time, JVM garbage collection, jvm and system CPU load, OS memory, database, webservice, application server, network, and browser. Read more in this blog article.

24/7 Performance Overview

The dashboard gives a 24/7 overview of the performance in a selected time range. It shows real-time critical information about the ADF application’s performance. Monitor your service level agreement (SLA): What is the end-user experience? Are response times within SLA boundaries? Or are they well outside SLA boundaries and is it seriously problematic? What is the error rate? What is the health of the JVM memory? Is immediate action required?

Summary of Response Times

In the top left section of the dashboard a summary of HTTP requests response times is shown for the selected time range. It shows 4 categories:

• Normal (well within the SLA range)
• Slow (somewhat outside the specified SLA response time)
• Very slow (well outside the SLA boundaries, considered seriously problematic)
• Errors (Number of Errors/Exceptions)

Details Response Times

HTTP response times can be analyzed over the selected time range. This makes visible when the load is high (and how high), how the response times are distributed over the categories (very slow, slow and normal) and when there are performance problems (more red and yellow colored parts of the bars). When there is more red (and yellow) colored parts in the bar chart (top right) this should be a trigger to drill down to this hour for further analysis in order to find the root cause.

Network Time to and from the Browser

Troubleshoot network problems. Network time is the time that it takes to send a HTTP request from a browser (http request network time) to the application server and from the application server back to the browser (http response network time). Read more here.

Time spent in Layer

The dashboard shows several overview and detail graphs that shows the layer (database, webservice, application server, network/browser loadtime) where process time is spent of your ADF application. It traces key ADF actions across tiers and services to provide end-to-end visibility and automatically maps each tier to easily visualize the relationship between them.

JVM CPU Load and System CPU Load

The CPU load percentage of the JVM, and the total CPU load percentage of the whole underlying operating system. A high CPU usage rate and memory usage may indicate a poorly tuned or designed application. Read more in this blog article.

JVM Heap and Garbage Collection

An important aspect of performance management is a healthy JVM. The ADF Performance Monitor shows realtime or historic JVM heap usage and JVM garbage collection times. If garbage collections are running longer than a configurable threshold (for example 20 seconds) a warning sign is shown. This is often an indication of a problem – such as a freeze of all current requests because the JVM cannot clear enough memory. This should be a trigger to drill down to for further analysis in order to find the root cause.

Errors/Faults Overview

Insight in the number, type and severity of errors that happen in a test or production environment is crucial to resolve them, and to make a stable ADF application that is less error-prone. Application errors (and their stack traces) are often hard to retrieve or take a lot of time to find. Project teams commonly depend on the reports of end-users and testers, and they typically do not report all errors or provide insufficient information about them. Development, QA and operational teams can drill down to the error messages, their type, severity, and their stack traces to quickly troubleshoot errors and make the application more stable. Read more here.

Time Range

There is common functionality; in every page a time range can be selected (5 minute, hour, day, week, month). You can drill down or roll up to any time range, or navigate to next or previous time range. There is also an option for a custom time range; this is useful to evaluate load tests.