About Our Solution

One of the most important steps in analyzing Composite and Complex Business Applications is to make the topology of the Application real and accurate. When we begin to analyze the application within the scope of the service, we first want to know which components of the Application operate on which Servers, how these components communicate with each other, and which protocols they use.

Topology of the Application

Topology of the Application

Obtaining the topology reveals each of the components to be analyzed. So if there is a performance or avalability complaint from the end users, soruce cause of the problem is one or at least one of the components in the picture. The utilization of hardware resources of the application is the first part to be looked at. And these are easiest & quickest the problems to be detected.

CPU usage problem sample

CPU usage problem sample

Problems arising from CPU usage can be solved easily by increasing the CPU or optimizing the code. Similar logic applies in Memory. The Memory Leak in applications is a programming error and after a certain time it will increase the resources used by the Application causing the hardware to become insufficient.

Detecting the CPU Usage and Peak Points of the Application

Detecting the CPU Usage and Peak Points of the Application

Basically, to understand how an application interacts with hardware, analyzing the CPU, Memory Metrics to know if the is working on a correct and sufficient configuration.

Memory Based Problems

Memory Based Problems

If the problem is not caused by optimization but by the code itself, then it is necessary to start analyzing all code fragments that the code interacts with, starting with the problematic code fragment, and identifying the component that is causing the delay.
If the part causing the problem in the application is due to the software, it is necessary to extract the part causing the problem starting from the top of the application (Modules) to the smallest component (Methods) by drill down analyzing .

Drill Down Analysis

Drill Down Analysis

As a result of Drill Down analysis, the parts causing the fault in the application are identified, reported and shared with the Application Development units. Once the problems’ Root Cause analysis has been done fixation and the removal of the problem is done much more quickly. According to industry averages, the ability to detect a problem in a software can often reach several times as much as the amount of time spent on the solution.

All rights Reserved. İdea Teknoloji 2016