In the introduction first of all we just tell you how to utilize and select tools and even with careful development and operation, it is not uncommon for a Web system to fail or for a project to be delayed in response to a sudden failure. Once a problem occurs, it is of course important to correctly grasp the situation and respond promptly, but it is also important to analyze the content and tendency of the problem and utilize the obtained knowledge for the next development.
Currently, tools for monitoring systems and tools for collecting and analyzing past data are being developed, and it is easier to solve problems by using these tools.
Here are five recommended tools to “visualize” the status of Web system failures.
The reason why it is necessary to “visualize” the trouble situation again
As mentioned at the beginning, when a problem occurs, it is necessary to grasp the situation correctly and respond promptly. Naturally, to solve a problem, it is necessary to accurately “visualize” “what kind of trouble is occurring”, “whether it is reproduced at the development site”, and “what is the cause”.
To put it the other way around, if the trouble situation is not “visualized”, it may take time to detect and analyze the problem, or other members may not be able to judge whether the problem is solved. There is also.
An experienced engineer may be able to guess the cause and deal with it, even if there are no measurements or the information about the problem is a little unclear. However, excessive reliance on specific members with experience and skills will impair stable project management at development sites where the mobility of human resources is high, and know-how for problem-solving will not be accumulated. It also leads to.
In addition, to solve problems and troubles in the system as a team, we not only collect information after it happens but also monitor the system and quantify it by using quantitative data daily in case of an emergency.・ It is also important to collect qualitative data, analyze it, and provide feedback to catch and prevent signs of trouble at an early stage.
5 tools to “visualize” the phenomenon and cause of failure
He said that it is especially important to collect and analyze information before trouble occurs in system development. Here, we will introduce five tools to visualize events and causes in case of system failure or trouble.
 Hardware resources utilize and select tools
It is a tool to monitor the resource usage of hardware such as CPU and memory usage and swap occurrence status. If your system is slowing down or you don’t get a response, you can use this tool to find out where the problem is, whether it’s a server hardware failure or a specific program. Can be identified.
 Load generation tool
It is a tool to put a load on the system in a pseudo manner and check the movement and status of the system. Check the performance by artificially creating a situation where multiple users access the server at the same time or process a large amount of data. In addition, when the processing speed decreases or an error occurs due to an increase in load, it may be used to reproduce the situation and help to fix the problem. Load testing is difficult to do manually, so load generation tools are commonly used.
 GC log analysis tool
A tool for collecting and analyzing garbage collection (GC) logs. If the system speed slows down or the system continues to be unresponsive while the server is being used repeatedly, it is possible that the unnecessary memory area has not been released and the memory has run out. Analysis tools are often used to identify areas of memory shortage, which often leads to early resolution of the problem.
 APM (Application Management) Tool
APM tools are tools that monitor the application performance of your web system. In terms of monitoring performance, it is the same as a hardware resource monitoring tool, with the difference that the APM tool monitors performance from an end-user perspective. It enables early detection of failures and prompt response, improving customer satisfaction and improving operational efficiency.
 Data analysis tool
By using the data analysis tool, it is possible to grasp the detailed tendency of the failure and investigate the cause. You can load the acquired data into the tool, find standard deviations and correlation coefficients, perform regression analysis and tests, and get new insights. The visualization itself is possible with the tools already introduced, but the strength of data analysis tools is that they can be analyzed from various angles.
This time, I introduced the necessity of “visualization” and the tools for visualization. By establishing a system that can utilize tools that automatically acquire and analyze internal information of the system, it is possible not only to quickly grasp system failures and solve problems quickly but also to prevent a recurrence.
To obtain the full effect of “visualization”, let’s work after clarifying the purpose.
If you ever want to know about similar things, check out the Facebook page Maga Techs