ADF Performance Monitor New Version 9.5

Frank Houweling
0 0
Read Time:1 Minute, 39 Second

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 warnings. The monitor will automatically interpret the metrics and will show warnings if the ADF application is not meeting the configured SLA thresholds. 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. 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 SLA critical warnings are configurable:

  • AVG Total Response time (average total response time; including time in database, webservices, application server, network to the client and browser load time)
  • AVG Server Response Time  (average application server process time – including time in database, and webservices)
  • Slow Request % (it is configurable what is SLOW, for example between 1 and 2 seconds)
  • Very Slow Request % (it is configurable what is VERY SLOW, for example everything slower than 1.5 seconds)
  • Error %

Read the whole article on our ADF Performance Monitor website

About Post Author

Frank Houweling

Frank Houweling is an Oracle ADF, Java and performance specialist. During the past years he has been requested several times as troubleshooter of ADF projects with bad performance. As such he has been performing performance analysis, bottleneck detection and developing mitigating solutions based on these analysis. He is also the creator of the ADF Performance Monitor, an advanced monitor that can identify, report and help solve performance bottlenecks in ADF applications.
Happy
Happy
0 %
Sad
Sad
0 %
Excited
Excited
0 %
Sleepy
Sleepy
0 %
Angry
Angry
0 %
Surprise
Surprise
0 %

Average Rating

5 Star
0%
4 Star
0%
3 Star
0%
2 Star
0%
1 Star
0%

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Next Post

Azure Pipeline: Build Angular and Node.js webapp (part 2)

In the previous article, we discussed how we can set up a pipeline with multiple stages in Azure Pipelines. In this article we will discuss how we can build the Angular and Node.js apps in the pipeline itself. I usually put all the build processes in one stage. In that […]
Azure Pipelines: How to build and test an Angular and Node.js webapp
%d bloggers like this: