JP5545761B2 - Failure analysis support system, failure analysis support method, and failure analysis support program - Google Patents

Description

  The present invention relates to a failure analysis support system, a failure analysis support method, and a failure analysis support program, and more particularly to a failure analysis support system, a failure analysis support method, and a failure analysis support program in a Web system.

  As an example of a technique for performing failure analysis in a computer system, for example, Japanese Patent Application Laid-Open No. 2009-237749 discloses the following technique. That is, the failure information collection function registers execution information of the Web business application by the application execution information management function, and acquires exception information necessary for failure analysis from the exception information knowledge by the exception information management function. The application fault data collection function generates application configuration information from the application configuration file of the Web business application based on the exception information acquired by the exception information management function, and collects execution information of the registered Web business application, When a Web business application failure occurs, failure information necessary for failure cause analysis is automatically collected.

  Patent Document 2 (Japanese Unexamined Patent Application Publication No. 2009-301252) discloses the following technique. That is, Web application information is acquired by the basic information recording means, and the internal state reproduction information generating unit generates the internal state reproduction procedure of the Web application from the request, response, and operation data. The internal state reproduction unit accesses the web application according to the above-described reproduction procedure, and the test execution unit performs a test of the web application based on the test rule database to obtain a test result. The test effect determination unit determines whether there is a Web application affected by the test result, and the internal state reproduction unit reproduces the test effect in the state before the test execution in order to realize the continuation of the test.

  Patent Document 3 (Japanese Patent Laid-Open No. 9-325903) discloses the following technique. That is, in a failure recording method for recording failure information necessary for failure analysis of a computer system having a main storage device and an input / output device, an input / output information collecting means representing an operation state of the input / output device, an operation of the computer system Time series information collection means representing the history, system load collection means representing the load on the computer system, system abnormality monitoring means for reporting abnormal events occurring on the computer system, and operations executed on the computer system Collection means for collecting application program status information representing processing status, user-defined information collection means for collecting failure information defined by the user, collection information registration means for registering the type of information to be collected in advance, and the collection information registration According to the registered contents of the means, information on the various information collecting means and abnormality monitoring means is collected. And a fault information recording means for recording in the recording area on the device.

JP 2009-237749 A JP 2009-301252 A JP 9-325903 A

  In the conventional failure analysis technology, under what load conditions the Web system was operating when a failure occurred, for example, what CPU (Central Processing Unit) usage rate, memory usage, and number of concurrent requests it was operating at It is unknown. For this reason, a great number of man-hours and periods are required for the reproduction test and the analysis work.

  Alternatively, conventional failure analysis techniques can only collect information about a single application. In addition, information necessary for failure analysis is not sufficient, such as collecting only the request URL for information related to application execution.

  This is because the conventional failure analysis technology is limited to failure analysis of native applications on a certain OS (Operating System), and it is premised that a problem application can be obtained, or The assumption is that the failure is not caused by the surrounding components that operate in a related manner, but the application itself.

  That is, the conventional failure analysis technology is difficult to apply to the field of Web systems in which a plurality of applications operate and it is not known when a failure occurs. In addition, conventional failure analysis technology reproduces failures that occur as a result of continuous loads that squeeze memory, processes, and threads, and failures that occur when multiple requests are processed simultaneously. The problem was that failure analysis was prolonged because of the inability to do this.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a failure analysis support system, a failure analysis support method, and a failure analysis support program capable of appropriately performing failure analysis in a Web system. Is to provide.

In order to solve the above-mentioned problem, a failure analysis support system according to an aspect of the present invention is a failure analysis support system for analyzing a failure in an operation system for executing a Web application. System monitoring unit for monitoring the load status of the client, a request monitoring unit for monitoring requests from one or a plurality of Web browsers, and an API call for monitoring an API (Application Program Interface) called by the request There is an exception in the Web application when the monitoring unit, the system monitoring unit, the request monitoring unit, the monitoring information storage unit for storing the monitoring results of the API call monitoring unit, and the request processing are performed. Monitor whether it occurs, and if an exception occurs, From the exception monitoring unit for generating exception information indicating the contents of the exception, and outputting the generated exception information and each monitoring result stored in the monitoring information storage unit as a log file. receiving a script generation unit for generating a script based on the log file, e Bei a failure reproducing portion for reproducing the occurrence of the exception based on the script generated by the script generating unit, the The script generation unit reproduces the request status for generating a script for reproducing the status of the request at the time when the exception occurred based on the monitoring result of the request monitoring unit and the monitoring result of the API call monitoring unit. Monitoring results of the script generation unit, the request monitoring unit, and the API call monitoring unit Based on the monitoring result of the fault monitoring application execution script generation unit for generating a script for reproducing the execution status of the Web application at the time when the exception occurred based on the viewing result and the exception information, and the monitoring result of the system monitoring unit And a system status reproduction script generation unit for generating a script for reproducing the load status of the operational system at the time when the exception occurred .

In order to solve the above problem, a failure analysis support method according to an aspect of the present invention is a failure analysis support method for analyzing a failure in an operation system for executing a Web application, wherein the operation system A step of monitoring a load status of the device, a step of monitoring a request from one or a plurality of Web browsers, a step of monitoring an API called by the request, and a monitoring result of the load status, the request and the API And monitoring whether an exception occurs in the Web application when the request is being processed, and if an exception occurs, generates exception information indicating the content of the exception, Output the generated exception information and each stored monitoring result as a log file. And the step, seen including the steps of: generating a script based on the log file, and a step to reproduce the occurrence of the exception based on the generated the script, the step of generating the script, the request monitoring results and Based on the monitoring result of the API, a step of generating a script for reproducing the status of the request at the time when the exception occurred, and based on the monitoring result of the request, the monitoring result of the API, and the exception information The step of generating a script for reproducing the execution status of the Web application at the time when the exception occurred and the load status of the operational system at the time when the exception occurred are based on the monitoring result of the load status. Steps to generate a script to reproduce Including.

In order to solve the above-mentioned problem, a failure analysis support program according to an aspect of the present invention is a failure analysis support program for analyzing a failure in an operational system for executing a Web application. A step of monitoring a load status of the operational system, a step of monitoring a request from one or a plurality of Web browsers, a step of monitoring an API called by the request, and a monitoring of the load status, the request and the API A step of storing the result, and monitoring whether or not an exception occurs in the web application when the request is being processed. If an exception occurs, exception information indicating the content of the exception is displayed. Generated, generated exception information, and each stored monitoring result And outputting as a log file, and generating a script based on the log file, generated based on the script is a program for executing a step of reproducing the occurrence of the exception, the script The generating step includes generating a script for reproducing the status of the request at the time when the exception occurred based on the monitoring result of the request and the monitoring result of the API, the monitoring result of the request, and the above Based on the monitoring result of the API and the exception information, the step of generating a script for reproducing the execution status of the Web application at the time when the exception occurred, and the exception occurs based on the monitoring result of the load status The above operational system at the time And generating a script to reproduce the load situation.

  According to the present invention, failure analysis can be appropriately performed in a Web system.

It is a figure which shows the structure of the failure analysis assistance system which concerns on embodiment of this invention. It is a schematic block diagram of the information processing apparatus which concerns on embodiment of this invention. It is a flowchart which shows the operation | movement procedure at the time of the operational system which concerns on embodiment of this invention performs a system monitoring process. It is a flowchart which shows the operation | movement procedure at the time of the operational system which concerns on embodiment of this invention performing a request monitoring process and an API call process. It is a flowchart which shows the operation | movement procedure at the time of the operational system which concerns on embodiment of this invention performing an exception monitoring process. It is a flowchart which shows the operation | movement procedure when the test type | system | group system which concerns on embodiment of this invention performs a failure reproduction process. It is a figure which shows the specific example which recorded on the log file the data on the application server in the failure analysis assistance system which concerns on embodiment of this invention. It is a figure which shows the specific example which recorded on the log file the data on the application server in the failure analysis assistance system which concerns on embodiment of this invention. It is a figure which shows the specific example which recorded on the log file the data on the application server in the failure analysis assistance system which concerns on embodiment of this invention. It is a figure which shows the specific example which recorded on the log file the data on the application server in the failure analysis assistance system which concerns on embodiment of this invention. It is a figure which shows the specific example which recorded on the log file the data on the application server in the failure analysis assistance system which concerns on embodiment of this invention. It is a figure which shows the specific example of the procedure script file produced | generated from the log file in the test type | system | group system which concerns on embodiment of this invention. It is a figure which shows the specific example of the procedure script file produced | generated from the log file in the test type | system | group system which concerns on embodiment of this invention. It is a figure which shows the specific example of the procedure script file produced | generated from the log file in the test type | system | group system which concerns on embodiment of this invention. It is a figure which shows the structure of the modification of the failure analysis assistance system which concerns on embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals and description thereof will not be repeated.

[Configuration and basic operation]
FIG. 1 is a diagram showing a configuration of a failure analysis support system according to an embodiment of the present invention.

  Referring to FIG. 1, the failure analysis support system 401 includes an operational system 201 and a test system 301. The operational system 201 includes the application server 10. The test system 301 includes an application server 50 and a server (script generation unit) 60. Note that the application server 10, the application server 50, and the server 60 may be separate devices or a single device.

  In the operational system 201, a plurality of Web applications 71 operate. A plurality of Web browsers in the operational system 201 can be mounted on an information processing apparatus different from the application server 10, for example, and can execute the Web application 71 via the application server 10.

  When a failure occurs in the operational system 201, the test system 301 acquires a log from the operational system 201 and analyzes the failure based on the acquired log.

  The application server 10, the application server 50, and the server 60, which are information processing apparatuses according to the embodiment of the present invention, typically have a basic structure of a computer having a general-purpose architecture, and execute a program installed in advance. By doing so, various functions as described later are provided. In general, such a program is stored in a recording medium such as a flexible disk and a CD-ROM (Compact Disk Read Only Memory) or distributed via a network or the like. When such a general-purpose computer is used, an OS (Operating System) for providing basic functions of the computer is provided in addition to the application for providing the functions according to the embodiment of the present invention. It may be installed. In this case, the program according to the embodiment of the present invention executes processing by calling necessary modules out of program modules provided as a part of the OS in a predetermined order and / or timing. May be. That is, the program itself according to the embodiment of the present invention does not include the module as described above, and the process may be executed in cooperation with the OS. Therefore, the program according to the embodiment of the present invention may have a form that does not include the above-described module.

  Furthermore, the program according to the embodiment of the present invention may be provided by being incorporated in a part of another program such as an OS. Even in this case, the program itself according to the embodiment of the present invention does not include a module included in the other program as described above, and the process is executed in cooperation with the other program. That is, the program according to the embodiment of the present invention may be in a form incorporated in such another program.

  Alternatively, some or all of the functions provided by program execution may be implemented as a dedicated hardware circuit.

  FIG. 2 is a schematic configuration diagram of the information processing apparatus according to the embodiment of the present invention.

  Referring to FIG. 2, the information processing apparatus is an information processing apparatus such as a portable information terminal, a personal computer, and a server, and includes a CPU (Central Processing Unit) 101 that is an arithmetic processing unit, a main memory 102, a hard disk 103, An input interface 104, a display controller 105, a data reader / writer 106, and a communication interface 107 are provided. These units are connected to each other via a bus 121 so that data communication is possible.

  The CPU 101 performs various operations by developing programs (codes) stored in the hard disk 103 in the main memory 102 and executing them in a predetermined order. The main memory 102 is typically a volatile storage device such as a DRAM (Dynamic Random Access Memory), and stores data indicating various arithmetic processing results in addition to programs read from the hard disk 103. To do. The hard disk 103 is a non-volatile magnetic storage device, and stores various setting values in addition to programs executed by the CPU 101. The program installed in the hard disk 103 is distributed in a state of being stored in the recording medium 111 as will be described later. In addition to the hard disk 103 or instead of the hard disk 103, a semiconductor storage device such as a flash memory may be employed.

  The input interface 104 mediates data transmission between the CPU 101 and an input unit such as a keyboard 108, a mouse 109, and a touch panel (not shown). That is, the input interface 104 receives an external input such as an operation command given by the user operating the input unit.

  The display controller 105 is connected to a display 110 that is a typical example of a display unit, and controls display on the display 110. That is, the display controller 105 displays the result of image processing by the CPU 101 to the user. The display 110 is, for example, an LCD (Liquid Crystal Display) or a CRT (Cathode Ray Tube).

  The data reader / writer 106 mediates data transmission between the CPU 101 and the recording medium 111. That is, the recording medium 111 circulates in a state where a program executed by the information processing apparatus is stored, and the data reader / writer 106 reads the program from the recording medium 111. In addition, the data reader / writer 106 writes a processing result in the information processing apparatus to the recording medium 111 in response to an internal command of the CPU 101. The recording medium 111 is, for example, a general-purpose semiconductor storage device such as CF (Compact Flash) and SD (Secure Digital), a magnetic storage medium such as a flexible disk, or a CD-ROM (Compact Disk Read Only). Memory).

  The communication interface 107 mediates data transmission between the CPU 101, a personal computer, a server device, and the like. The communication interface 107 typically has an Ethernet (registered trademark) or USB (Universal Serial Bus) communication function. Instead of installing the program stored in the recording medium 111 in the information processing apparatus, a program downloaded from a distribution server or the like via the communication interface 107 may be installed in the information processing apparatus.

  In addition, another output device such as a printer may be connected to the information processing apparatus as necessary.

[Control structure]
Next, a control structure for providing various functions in the application server 10, the application server 50, and the server 60 will be described.

  FIG. 1 also shows a control structure provided by the failure analysis support system according to the embodiment of the present invention. Each block of the failure analysis support system shown in FIG. 1 is provided by developing a program (code) stored in the hard disk 103 in the main memory 102 and causing the CPU 101 to execute it. Note that some or all of the modules shown in FIG. 1 may be provided by firmware implemented in hardware. Alternatively, part or all of the control structure shown in FIG. 1 may be realized by dedicated hardware and / or a wiring circuit.

  Referring to FIG. 1, the application server 10 includes a request monitoring unit 21, a system monitoring unit 22, an API call monitoring unit 23, and an exception monitoring unit 24 as its control structure. The application server 10 also includes an information holding table (monitoring information storage unit) 30. The application server 50 includes a failure reproduction unit 80 as its control structure. The server 60 includes, as its control structure, a request status reproduction script generation unit 61, a fault application execution script generation unit 62, and a system status reproduction script generation unit 63. The test system 301 includes a log file 43 and a procedure script file 70. Note that the application server 50 and the server 60 may be separate devices or a single device.

  In the active system 201, the system monitoring unit 22 monitors the load status of the active system.

  The request monitoring unit 21 monitors requests from one or a plurality of Web browsers.

  The API call monitoring unit 23 monitors the API (Application Program Interface) of the Web application 71 called by the request.

  The information holding table 30 stores the monitoring results of the system monitoring unit 22, the request monitoring unit 21, and the API call monitoring unit 23.

  The exception monitoring unit 24 monitors whether or not an exception occurs in the Web application 71 when a request is being processed. If an exception occurs, the exception monitoring unit 24 generates exception information indicating the content of the exception, The generated exception information and each monitoring result stored in the information holding table 30 are output as a log file.

  In the test system 301, the script generation unit 60 generates a script based on the log file received from the exception monitoring unit 24.

  The failure reproduction unit 80 reproduces the occurrence of an exception by executing the script generated by the script generation unit 60.

  More specifically, the request monitoring unit 21 monitors requests processed in the application server 10 and continues to record monitoring results for a predetermined time in the information holding table 30.

  The system monitoring unit 22 monitors the CPU usage rate and the memory usage amount of the application server 10, and continues to record monitoring results for a predetermined time in the information holding table 30.

  The API call monitoring unit 23 monitors the type of API that is called by a request processed in the application server 10, and continues to record a monitoring result for a predetermined time in the information holding table 30.

  The exception monitoring unit 24 monitors whether an exception has occurred in the application 71 in the processing of the request. When an exception occurs in the application 71, the exception monitoring unit 24 includes exception information indicating the content of the exception that has occurred, information recorded in the information holding table 30 by the request monitoring unit 21, the system monitoring unit 22, and the API call monitoring unit 23. Is output to the log file 41.

  Further, the system monitoring unit 22, the request monitoring unit 21, and the API call monitoring unit 23 are realized as plug-ins of the operational system 201.

  More specifically, the request monitoring unit 21, the system monitoring unit 22, the API call monitoring unit 23, and the exception monitoring unit 24 are implemented as plug-ins of the application server 10 in the operational system 201, thereby starting the application server 10. Sometimes it is automatically activated.

  The collection information of the log file 41 is sent to the test system 301 through an electronic recording medium such as a USB memory, file transfer, and the like, and is taken into the log file 43.

  In the test system 301, the request status reproduction script generation unit 61, the failure application execution script generation unit 62, and the system status reproduction script generation unit 63 read the log file 43 collected by the operational system 201, and the situation when the failure occurs Each script for reproducing is generated and output to the procedure script file 70.

  More specifically, the request status reproduction script generation unit 61 generates a script for reproducing the request status at the time when the exception occurred based on the monitoring result of the request monitoring unit 21 and the monitoring result of the API call monitoring unit 23. Generate.

  The failure application execution script generation unit 62 is a script for reproducing the execution status of the Web application 71 at the time when the exception occurred based on the monitoring result of the request monitoring unit 21, the monitoring result of the API call monitoring unit 23, and exception information. Is generated.

  The system status reproduction script generation unit 63 generates a script for reproducing the load status of the operational system at the time when the exception occurred based on the monitoring result of the system monitoring unit 22.

  The failure reproduction unit 80 reads and executes the procedure script file 70 to reproduce the situation when the failure occurs.

[Operation]
Next, operations of the operational system 201 and the test system 301 according to the embodiment of the present invention will be described with reference to the drawings. In the embodiment of the present invention, the failure analysis support method according to the embodiment of the present invention is implemented by operating the operation system 201 and the test system 301. Therefore, the description of the failure analysis support method according to the embodiment of the present invention is replaced with the following description of the operation of the operational system 201 and the test system 301. In the following description, FIG. 1 is referred to as appropriate.

  FIG. 3 is a flowchart showing an operation procedure when the operational system according to the embodiment of the present invention performs the system monitoring process.

  Referring to FIG. 3, first, when application server 10 is activated, system monitoring unit 22 is activated by application server 10 and starts recording system information (step A1).

  The system monitoring unit 22 records system information in the information holding table 30 at the same time as activation. The information to be recorded is the CPU usage rate and the memory usage status (step A2).

  Here, the system monitoring unit 22 periodically monitors the system information at regular intervals, for example, every 5 minutes, records the system information, and then enters sleep (waiting state) (steps A2 to A4).

  Next, after recording the system information and receiving an instruction to end monitoring from the application server 10 before entering sleep, the system monitoring unit 22 ends the process without sleeping (YES in step A3). .

  Alternatively, the system monitoring unit 22 cancels the sleep and ends the process when receiving an instruction to end the monitoring from the application server 10 even during the sleep (YES in Step A5).

  On the other hand, the system monitoring unit 22 records system information again when no monitoring end instruction is received from the application server 10 when the specified sleep time has elapsed (NO in step A5). Step A2).

  FIG. 4 is a flowchart showing an operation procedure when the operational system according to the embodiment of the present invention performs a request monitoring process and an API call process.

  Referring to FIG. 4, first, when application server 10 is activated, request monitoring unit 21 is activated by application server 10 and starts recording request information (steps B1 and B2).

  Next, when the application server 10 receives the request (YES in step B3), the request monitoring unit 21 records information on the request in the information holding table 30 (step B4). Information to be recorded includes a request URL, a URL parameter, an HTTP request header, and an HTTP request body.

  Next, after the request monitoring unit 21 records the request information, the request received by the application server 10 transitions to an execution state. When the request transits to the execution state, the application server 10 activates the API call monitoring unit 23. The activated API call monitoring unit 23 starts monitoring the API call (step B5).

  Next, the API call monitoring unit 23 monitors the execution of the request. When the API is called (YES in step B6), the API information is recorded in the information holding table 30 (step B7). The information to be recorded is the name of the API, the argument, and the class to which the calling API belongs.

  Next, after the API call monitoring unit 23 records the API information in the information holding table 30, if the request processing has ended (YES in step B8), the API call monitoring unit 23 ends the processing (step B9).

  On the other hand, if the request processing has not ended (NO in step B8), the API call monitoring unit 23 monitors the API call again (step B5).

  Next, when the request processing is completed, the request monitoring unit 21 records response information in the information holding table 30 (step B10). Information to be recorded includes an HTTP response status, an HTTP response header, and an HTTP response body.

  Next, after recording the response information in the information holding table 30, the request monitoring unit 21 ends the process (step B12) when receiving an instruction to end monitoring from the application server 10 (YES in step B11). ).

  On the other hand, when the request monitoring unit 21 has not received a monitoring end instruction from the application server 10 (NO in step B11), the request monitoring unit 21 records the request information again (step B2).

  FIG. 5 is a flowchart showing an operation procedure when the operational system according to the embodiment of the present invention performs the exception monitoring process.

  Referring to FIG. 5, first, when application server 10 is activated, exception monitoring unit 24 is processed by application server 10 and starts monitoring the occurrence of an exception (step C1).

  Next, when activated, the exception monitoring unit 24 enters sleep (waiting state) until an exception occurs, and waits until an exception occurs. When an exception occurs, the exception monitoring unit 24 is activated and collects exception information (steps C2 to C4). Information to be collected includes exception messages, stack traces, and exception occurrence times.

  Next, the exception monitoring unit 24 writes the collected exception information and the information recorded in the information holding table 30 by the request monitoring unit 21, the system monitoring unit 22, and the API call monitoring unit 23 in the log file 41 (step C5). .

  Here, the log file 41 is sent to the test system 301 through an electronic recording medium such as a USB memory or file transfer, and is prepared as a log file 43.

  Next, after the exception monitoring unit 24 writes the exception information to the log file 41 and receives an instruction to end monitoring from the application server 10 (YES in step C6), the exception monitoring unit 24 ends the process.

  On the other hand, if the exception monitoring unit 24 has not received an instruction to end monitoring (NO in step C6), the exception monitoring unit 24 enters sleep again (step C2).

  If the exception monitoring unit 24 receives an instruction to end monitoring from the application server 10 even during sleep (YES in step C3), the exception monitoring unit 24 cancels sleep and ends the process.

  FIG. 6 is a flowchart showing an operation procedure when the test system according to the embodiment of the present invention performs the failure reproduction process.

  Referring to FIG. 6, first, the script generation unit 60 reads the log file 43 and extracts only information useful for failure reproduction from the log file 43 (step D1).

  More specifically, in the script generation unit 60, information extracted by the request situation reproduction script generation unit 61 is request information and API call information (data D2 and D3). The request situation reproduction script generation unit 61 generates a script that reproduces the situation at the time of failure taking into account the number of simultaneous requests based on the number of requests recorded in the request information and the time when the request is received.

  Information extracted by the failure application execution script generation unit 62 is request information, API call information, and exception information (data D2, D3, and D4). The fault application execution script generation unit 62 generates an execution script by merging request information and API information as initial information at the time of receiving a request not described in the exception information.

  The information extracted by the system status reproduction script generation unit 63 is system information (data D5). The system status reproduction script generation unit 63 outputs a script for adjusting the load based on the data in order to faithfully reproduce the CPU usage rate and the memory usage amount recorded as numerical values in the system information.

  Next, the request situation reproduction script generation unit 61, the fault application execution script generation unit 62, and the system situation reproduction script generation unit 63 write a script composed of fixed keywords on the basis of the extracted information. A script file 70 is generated (steps D6 to D8).

  Next, the procedure script file 70 is read by the failure reproduction unit 80 (step D9).

  Next, the failure reproduction unit 80 first acquires a system status reproduction script from the procedure script file 70 and reproduces the status of the active system 201 at the time when the failure occurred in the application server 10.

  Subsequently, the failure reproduction unit 80 acquires a request status reproduction script from the procedure script file 70 and reproduces the status of the request at the time when the failure occurred in the application server 10.

  Further, the failure reproduction unit 80 acquires a failure application execution script from the procedure script file 70, and reproduces the request in which the problem failure has occurred (step D10).

  Next, a specific example of acquiring various logs and reproducing a failure by the failure analysis support system 401 will be described.

  7 to 11 are diagrams showing specific examples in which data on the application server in the failure analysis support system according to the embodiment of the present invention is recorded in a log file.

  12 to 14 are diagrams showing specific examples of the procedure script file generated from the log file in the test system according to the embodiment of the present invention.

  The application server 10 is ready to accept requests as soon as it starts. At the same time as the application server 10 is activated, the system monitoring unit 22 starts recording system information and records the CPU usage rate and the memory usage amount as shown in FIG.

  Next, when the application server 10 receives the request, the request monitoring unit 21 starts recording. For each request, the request URL, URL parameters, HTTP request header, and HTTP request body are recorded as shown in FIG.

  Next, when the execution of the request starts, the API call monitoring unit 23 starts recording, and records the name and argument of the called API as shown in FIG. This API call record is associated with the request record, and the request API call is recorded in the top row of FIG.

  Next, when the execution of the request is finished, the request monitoring unit 21 records the execution result of the request, that is, the response information as shown in FIG.

  Each time a new request is received, information as shown in FIGS. 7, 8, and 9 is recorded in the information holding table 30. Since the capacity of the information holding table 30 is limited, information recorded in the information holding table 30 is information for a certain period, for example, 30 minutes. When this fixed period elapses, old information is sequentially discarded. It is assumed that the application server 10 receives a plurality of requests at the same time. In this case, the request monitoring unit 21 records all requests within the range of the certain period.

  In the state where the system information and the request information are continuously recorded in this way, when an exception occurs in a certain request, the exception monitoring unit 24 collects exception information as shown in FIG.

  The exception monitoring unit 24 uses the collected exception information (FIG. 11) as system information (FIG. 10), request information (FIG. 7), API information (FIG. 8), and response information (FIG. 9) recorded in the information holding table 30. ) And log file 41. This written information is retained for 30 minutes, for example, retroactively from the time of exception occurrence, and indicates the status of the application server 10 at the time when the exception occurred.

  In the test system 301, a procedure script file 70 necessary for reproducing the phenomenon is generated.

  That is, the script generation unit 60 extracts only valid information from the log file 43 in which information shown in FIGS. 7 to 11 is recorded, and writes a script necessary for failure reproduction to the procedure script file 70.

  Next, the request situation reproduction script generating unit 61 records the request information (FIG. 7) and the API information (FIG. 8), and the situation at the time considering the number of simultaneous requests from the number of requests and the time when the requests are received. Is output a request reproduction script (FIG. 12).

  Next, the failure application execution script generation unit 62 determines when and when the request in which the failure has occurred is generated from the request information (FIG. 7), API information (FIG. 8), and exception information (FIG. 11). A fault application execution script (FIG. 13) that reproduces whether an exception has occurred by calling is output.

  Next, the system status reproduction script generation unit 63 adjusts the load based on the data in order to faithfully reproduce the CPU usage rate and the memory usage amount recorded as numerical values in the system information (FIG. 10). The script (FIG. 14) is output.

  Next, the failure reproduction unit 80 reads and executes the generated procedure script file 70 to reproduce the status of the system at the time when the exception occurred in the application server 10 and the status of the request. Reproduce the request in which the exception occurs at the same timing as the exception occurred in.

  As described above, in the failure analysis support system according to the embodiment of the present invention, the system monitoring unit 22 monitors the load status of the operational system. The request monitoring unit 21 monitors requests from one or a plurality of Web browsers. The API call monitoring unit 23 monitors an API called by a request. The information holding table 30 stores the monitoring results of the system monitoring unit 22, the request monitoring unit 21, and the API call monitoring unit 23. The exception monitoring unit 24 monitors whether or not an exception occurs in the Web application 71 when a request is being processed. If an exception occurs, the exception monitoring unit 24 generates exception information indicating the content of the exception, The generated exception information and each monitoring result stored in the information holding table 30 are output as a log file. The script generation unit 60 generates a script based on the log file received from the exception monitoring unit 24. The failure reproduction unit 80 reproduces the occurrence of an exception based on the script generated by the script generation unit 60.

  Here, specific differences between the techniques described in Patent Documents 1 to 3 and the failure analysis support system according to the embodiment of the present invention include, for example, the following points.

  That is, the techniques described in Patent Documents 1 to 3 are not configured to collect information when a failure occurs in the operational system and reproduce the failure in the test system. In particular, the technique described in Patent Document 2 assumes operation in a test system.

  In contrast, in the failure analysis support system according to the embodiment of the present invention, it is possible to collect information optimized for reproducing a failure in a test system.

  In addition, the technique described in Patent Document 3 is not configured to collect transaction information such as requests, and assumes a process abnormality, and a Web assumed by the failure analysis support system according to the embodiment of the present invention. The target level is completely different from application anomalies.

  As described above, the techniques described in Patent Literatures 1 to 3 are different from the failure analysis support system according to the embodiment of the present invention in various points.

  In other words, when a failure occurs in the Web application that operates on the operational system, the internal operation of the application server 10 is monitored in order to support failure analysis. As a result, the request status, API call, and system load status are collected, and the failure is reproduced in the test system based on the collected information.

  For example, the CPU usage rate and the memory usage amount are collected periodically. As a result, it is possible to reproduce what load state the active system 201 was in until the failure occurred.

  Further, for example, all request URLs are collected, and API call status generated by extending the request is also collected. This makes it possible to accurately reproduce how many requests were made before and at the time of the failure.

  Further, for example, the load status and request status of a Web system in which a plurality of Web applications operate are collected for a certain period and updated continuously. Thereby, in a Web system in which a plurality of Web applications operate, information for reproducing the failure can be obtained at any time when the failure occurs.

  Then, a plurality of collected information is merged to generate a script, and the generated script is executed. In this way, the configuration using a script that can be easily reused facilitates failure analysis work in other test systems, and the failure reproduction can be easily changed by making minor modifications to the script. be able to.

  In other words, the failure analysis support system according to the embodiment of the present invention can record the request that directly caused the failure occurrence and the request status when the failure occurred in the operational system. Further, in the test system, it is possible to reproduce the request that directly causes the failure and the request status when the failure occurs.

  Further, in the operational system, it is possible to record the detailed operation of the request that directly caused the failure and the request when the failure occurred. In the test system, it is possible to reproduce the detailed operation of the request that directly caused the failure and the request when the failure occurred.

  In addition, in the operational system, it is possible to record under what load conditions the application server was operating when a failure occurred. In the test system, it is possible to reproduce under what load condition the application server was operating when a failure occurred.

  Therefore, it is possible to accurately reproduce the situation until the failure occurs, and to reproduce the same failure as that occurring in the operation system in the test system.

  That is, among the components in the failure analysis support system according to the embodiment of the present invention, the request monitoring unit 21, the system monitoring unit 22, the API call monitoring unit 23, the exception monitoring unit 24, and the script generation unit 60. In addition, with the minimum configuration including the failure reproduction unit 80 and the information holding table 30, it is possible to achieve the object of the present invention to appropriately perform failure analysis in the Web system.

  In the failure analysis support system according to the embodiment of the present invention, the system monitoring unit 22, the request monitoring unit 21, and the API call monitoring unit 23 are realized as plug-ins of the operational system.

  That is, when a failure occurs in a Web application operating on the operational system, a unit that operates as a plug-in of the application server 10 is provided to support the analysis of the failure, and the operation inside the application server 10 is directly monitored. To do.

  With such a configuration, for example, it is possible to collect information at a customer as a plug-in of an operational system.

  Further, in the failure analysis support system according to the embodiment of the present invention, the request situation reproduction script generation unit 61 is based on the monitoring result of the request monitoring unit 21 and the monitoring result of the API call monitoring unit 23 at the time when an exception has occurred. Generate a script to reproduce the request status in. The failure application execution script generation unit 62 is a script for reproducing the execution status of the Web application 71 at the time when the exception occurred based on the monitoring result of the request monitoring unit 21, the monitoring result of the API call monitoring unit 23, and exception information. Is generated. Then, the system status reproduction script generation unit 63 generates a script for reproducing the load status of the active system at the time when the exception occurred based on the monitoring result of the system monitoring unit 22.

  As described above, the failure can be appropriately reproduced in the test system by selecting the appropriate information from the information when the failure occurs in the operation system and generating the script.

  FIG. 15 is a diagram showing a configuration of a modification of the failure analysis support system according to the embodiment of the present invention.

  Referring to FIG. 15, the failure analysis support system 402 includes an operational system 202 and a test system 301. The application server 10 further includes a user code analysis unit 25 as a control structure as compared with the operational system 201.

  The user code analysis unit 25 analyzes the code of the user program when an exception occurs. More specifically, the user code analysis unit 25 analyzes the code of the Web application 71 and monitors processing other than the API executed by the request. The information holding table 30 further stores the monitoring result of the user code analysis unit 25.

  In the active system 201, only the content of the request, the content of the API call, and the time when these are executed are recorded. For this reason, the failure caused by the code of the user application cannot be reproduced.

  On the other hand, in the failure analysis support system 402, in the operational system 202, the user code analysis unit 25 analyzes the code of the user application when an exception occurs and records up to the code logic. Then, the failure application execution script generation unit 62 in the test system 301 generates a script and the failure reproduction unit 80 reproduces the script.

  With such a configuration, it is possible to reproduce a failure that occurs depending on the code of the user application.

  The above embodiment should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

  Although a part or all of the above embodiments can be described as the following supplementary notes, the scope of the present invention is not limited to the following supplementary notes.

[Appendix 1]
A failure analysis support system for analyzing a failure in an operational system for executing a Web application,
A system monitoring unit for monitoring the load status of the operational system;
A request monitoring unit for monitoring requests from one or more Web browsers;
An API call monitoring unit for monitoring an API (Application Program Interface) called by the request;
A monitoring information storage unit for storing monitoring results of the system monitoring unit, the request monitoring unit, and the API call monitoring unit;
Monitors whether or not an exception occurs in the Web application when the request is being processed, and if an exception occurs, generates exception information indicating the contents of the exception and generates the generated exception Information, and an exception monitoring unit for outputting each monitoring result stored by the monitoring information storage unit as a log file;
A script generation unit for generating a script based on the log file received from the exception monitoring unit;
A failure analysis support system comprising: a failure reproduction unit for reproducing the occurrence of the exception based on the script generated by the script generation unit.

[Appendix 2]
The failure analysis support system according to appendix 1, wherein the system monitoring unit, the request monitoring unit, and the API call monitoring unit are realized as plug-ins of the operational system.

[Appendix 3]
The script generation unit
Based on the monitoring result of the request monitoring unit and the monitoring result of the API call monitoring unit, a request status reproduction script generation unit for generating a script for reproducing the status of the request at the time when the exception occurred;
Fault application execution for generating a script for reproducing the execution status of the Web application at the time when the exception occurred based on the monitoring result of the request monitoring unit, the monitoring result of the API call monitoring unit, and the exception information A script generator,
Appendix 1 or 2 including a system status reproduction script generation unit for generating a script for reproducing the load status of the operational system at the time when the exception occurred based on the monitoring result of the system monitoring unit Failure analysis support system described in 1.

[Appendix 4]
The failure analysis support system further includes:
A user code analysis unit for analyzing the code of the Web application and monitoring processing other than the API executed by the request;
4. The failure analysis support system according to any one of appendices 1 to 3, wherein the monitoring information storage unit further stores a monitoring result of the user code analysis unit.

[Appendix 5]
A failure analysis support method for analyzing a failure in an operational system for executing a web application,
Monitoring the load status of the operational system;
Monitoring requests from one or more web browsers;
Monitoring the API invoked by the request;
Storing the load status, the request and the monitoring result of the API;
Monitors whether or not an exception occurs in the Web application when the request is being processed, and if an exception occurs, generates exception information indicating the contents of the exception and generates the generated exception Outputting information and each stored monitoring result as a log file;
Generating a script based on the log file;
And reproducing the occurrence of the exception based on the generated script.

[Appendix 6]
6. The failure analysis support method according to appendix 5, wherein monitoring of the load status, monitoring of the request, and monitoring of the API are performed using a plug-in of the operational system.

[Appendix 7]
The step of generating the script includes:
Generating a script for reproducing the status of the request at the time when the exception occurred based on the monitoring result of the request and the monitoring result of the API;
Generating a script for reproducing the execution status of the Web application at the time when the exception occurred, based on the monitoring result of the request, the monitoring result of the API, and the exception information;
The failure analysis support method according to appendix 5 or 6, including a step of generating a script for reproducing the load status of the active system at the time when the exception occurred based on the monitoring result of the load status.

[Appendix 8]
The failure analysis support method further includes:
Analyzing the code of the web application and monitoring processing other than the API executed by the request;
The failure analysis support method according to any one of appendices 5 to 7, further comprising storing a monitoring result of a process other than the API in the step of storing the monitoring result.

[Appendix 9]
A failure analysis support program for analyzing a failure in an operational system for executing a web application,
Monitoring the load status of the operational system;
Monitoring requests from one or more web browsers;
Monitoring the API invoked by the request;
Storing the load status, the request and the monitoring result of the API;
Monitors whether or not an exception occurs in the Web application when the request is being processed, and if an exception occurs, generates exception information indicating the contents of the exception and generates the generated exception Outputting information and each stored monitoring result as a log file;
Generating a script based on the log file;
A failure analysis support program for executing the step of reproducing the occurrence of the exception based on the generated script.

[Appendix 10]
The failure analysis support program according to appendix 9, wherein the step of monitoring the load state, the step of monitoring the request, and the step of monitoring the API are executed using a plug-in of the operational system.

[Appendix 11]
The step of generating the script includes:
Generating a script for reproducing the status of the request at the time when the exception occurred based on the monitoring result of the request and the monitoring result of the API;
Generating a script for reproducing the execution status of the Web application at the time when the exception occurred, based on the monitoring result of the request, the monitoring result of the API, and the exception information;
11. The failure analysis support program according to appendix 9 or 10, including a step of generating a script for reproducing the load status of the active system at the time when the exception occurred based on the monitoring result of the load status.

[Appendix 12]
The failure analysis support program further includes:
Analyzing the code of the web application and monitoring processing other than the API executed by the request;
12. The failure analysis support program according to any one of appendices 9 to 11, wherein in the step of storing the monitoring result, a monitoring result of a process other than the API is further stored.

  According to the present invention, for example, when a failure occurs in a business application, it is possible to collect information necessary for analyzing the failure in the test system. Therefore, the present invention has industrial applicability.

10 application server 50 application server 60 server (script generation unit)
71 Web application 21 Request monitoring unit 22 System monitoring unit 23 API call monitoring unit 24 Exception monitoring unit 25 User code analysis unit 30 Information holding table (monitoring information storage unit)
43 log file 61 request status reproduction script generation unit 62 fault application execution script generation unit 63 system status reproduction script generation unit 70 procedure script file 80 fault reproduction unit 101 CPU
DESCRIPTION OF SYMBOLS 102 Main memory 103 Hard disk 104 Input interface 105 Display controller 106 Data reader / writer 107 Communication interface 108 Keyboard 109 Mouse 110 Display 111 Recording medium 121 Bus 201, 202 Operation system 301 Test system 401, 402 Fault analysis support system

Claims (5)

A failure analysis support system for analyzing a failure in an operational system for executing a Web application,
A system monitoring unit for monitoring the load status of the operational system;
A request monitoring unit for monitoring requests from one or more Web browsers;
An API call monitoring unit for monitoring an API (Application Program Interface) called by the request;
A monitoring information storage unit for storing monitoring results of the system monitoring unit, the request monitoring unit, and the API call monitoring unit;
Monitors whether or not an exception occurs in the Web application when the request is being processed, and if an exception occurs, generates exception information indicating the contents of the exception and generates the generated exception Information, and an exception monitoring unit for outputting each monitoring result stored by the monitoring information storage unit as a log file;
A script generation unit for generating a script based on the log file received from the exception monitoring unit;
Bei example a failure reproducing portion for reproducing the occurrence of the exception, based on the script generated by the script generating unit,
The script generation unit
Based on the monitoring result of the request monitoring unit and the monitoring result of the API call monitoring unit, a request status reproduction script generation unit for generating a script for reproducing the status of the request at the time when the exception occurred;
Fault application execution for generating a script for reproducing the execution status of the Web application at the time when the exception occurred based on the monitoring result of the request monitoring unit, the monitoring result of the API call monitoring unit, and the exception information A script generator,
A failure analysis support system including a system status reproduction script generation unit for generating a script for reproducing the load status of the operational system at the time when the exception occurred based on the monitoring result of the system monitoring unit .   The failure analysis support system according to claim 1, wherein the system monitoring unit, the request monitoring unit, and the API call monitoring unit are realized as plug-ins of the operational system. The failure analysis support system further includes:
A user code analysis unit for analyzing the code of the Web application and monitoring processing other than the API executed by the request;
The monitoring information storage unit further wherein storing the monitoring result of the user code analyzer, failure analysis support system according to claim 1 or 2. A failure analysis support method for analyzing a failure in an operational system for executing a web application,
Monitoring the load status of the operational system;
Monitoring requests from one or more web browsers;
Monitoring the API invoked by the request;
Storing the load status, the request and the monitoring result of the API;
Monitors whether or not an exception occurs in the Web application when the request is being processed, and if an exception occurs, generates exception information indicating the contents of the exception and generates the generated exception Outputting information and each stored monitoring result as a log file;
Generating a script based on the log file;
Viewing including the steps to reproduce the occurrence of the exception based on the generated script,
The step of generating the script includes:
Generating a script for reproducing the status of the request at the time when the exception occurred based on the monitoring result of the request and the monitoring result of the API;
Generating a script for reproducing the execution status of the Web application at the time when the exception occurred, based on the monitoring result of the request, the monitoring result of the API, and the exception information;
And a step of generating a script for reproducing the load status of the operational system at the time when the exception occurred based on the monitoring result of the load status . A failure analysis support program for analyzing a failure in an operational system for executing a web application,
Monitoring the load status of the operational system;
Monitoring requests from one or more web browsers;
Monitoring the API invoked by the request;
Storing the load status, the request and the monitoring result of the API;
Monitors whether or not an exception occurs in the Web application when the request is being processed, and if an exception occurs, generates exception information indicating the contents of the exception and generates the generated exception Outputting information and each stored monitoring result as a log file;
Generating a script based on the log file;
A program for executing the step of reproducing the occurrence of the exception based on the generated script ,
The step of generating the script includes:
Generating a script for reproducing the status of the request at the time when the exception occurred based on the monitoring result of the request and the monitoring result of the API;
Generating a script for reproducing the execution status of the Web application at the time when the exception occurred, based on the monitoring result of the request, the monitoring result of the API, and the exception information;
A failure analysis support program , comprising: generating a script for reproducing the load status of the active system at the time when the exception occurred based on the monitoring result of the load status .

Images