Our latest news
There exist two alternatives when it comes to monitoring the end-user experience: the synthetic transactions, where a robot is programmed to execute certain operation that simulates the users work every from time to time; the real end-user experience, where the users real application use is captured.
The robots of the synthetic transactions, allows us to make certain simulation operations, and monitoring that simulations we obtain some statistics such as the response time End-to-End (since the user makes the request till we receive the last pack that tells us that all the information has been received) or produced errors. It is a great way to know the performance of our applications, as their availability.
The end-user real experience, captures the real operations executed by the users, and allows us to obtain more complete statistics, including the response time End-to-End and allows us to split that time, including the rendering time of the page on the user equipment, the red latency and the processing time on the Datacenter to serve that requests. Moreover, we can get to know the request detail at the application server level, with the only method, classes or SQL sentences execution times involved on the requests. This way is easier and faster to detect the source of the performance problem, for this reason the incident resolution time will be reduced.
Once seen the difference, are these solutions supplementary or selective? The correct answer is that they are totally supplementary. Let’s check the reasons:
- The synthetic transactions, allows us to generate workload over our application, this way in case the users were not using it, and our application fails, or the performance is not the adequate, we will detect the problem and anticipate restoring the system before the users is even affected.
- The end-user real experience will allow us to dispose of the maximum detail of our application execution, independently if the workload comes from the end-user or the transaction robot. On the last point example, the monitorization of the real experience will allow us to have the detail of the existing problem, making it easier to the team to solve the issue.
Lastly, it is important to mention that both the synthetic transactions and the end-user real experience tend to be oriented to web applications, although there are exceptions. Here are end-user real experience solutions that will allow us to analyze not only web application but also C applications. In the synthetic transaction application, there are solutions that will allow us to analyze any kind of application, either client/server or mainframe or Citrix applications… for more information don’t doubt to contact us via email email@example.com.