JP2017207995A - Service monitoring device and service monitoring method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce burden of a system operator without restricting an application range to services, and monitor an application service without depending on program knowledge or correction ability of the system operator.SOLUTION: A server 20 includes: a service use execution part 231 for acquiring a user operation procedure and executing services; a determination information extracting part 232 for extracting a character string from respective images indicating an execution result of the services executed multiple times in beforehand by the service use execution part 231; a monitoring information setting part 233 for discriminating character string portions that are common among the multiple character strings extracted by the determination information extracting part 232, and setting the common character string portions as monitoring information; and a failure determination part 234 for determining existence of failure in executing the services, on the basis of a comparison between the character strings extracted from the images indicating the execution result of the services reproduced by the service use execution part 231 and the character string portions set as the monitoring information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a service monitoring apparatus and a service monitoring method.

  In the operation of a system in which system resource virtualization and dynamic configuration change are performed in recent years, it is necessary to quickly detect the influence on the application service user due to a system failure. For this reason, it is necessary to monitor not only the conventional hardware failure detection but also the normality of the application service. In addition, since application services have different configurations and operations for each application, a standard monitoring method has not been established, and it is necessary to create a monitoring method individually.

  Conventionally, in order to automatically generate a monitoring method for application services, a service monitoring method has been proposed in which a log generated by a service is analyzed based on the described flow diagram, and a monitoring program corresponding to the service is generated and executed from the analysis result. (For example, refer to Patent Document 1).

  In addition, a method called application performance management (APM) for managing an application service by confirming the normality of the service or an improved portion by measuring the performance of the application has been proposed (for example, see Non-Patent Document 1).

JP 2000-47912 A

“Java (registered trademark) run-time monitoring, Part 1: Run-time performance and availability monitoring for Java systems,” [Search May 10, 2016, Internet <URL: http://www.ibm.com/ developerworks / library / j-rtm1 / index.html>

  However, the conventional method has a problem that the burden on the system operator is large and the application range is limited, and knowledge and correction of the program are necessary, and the monitoring work of the application service is complicated.

  Specifically, in the method described in Patent Document 1, it is necessary to create a flow diagram for analyzing a log for each service, and it is necessary for a system operator to create a flow diagram. In addition, the method described in Patent Document 1 requires that the application service to be monitored be a service content in which a log that can generate a monitoring method is output from a flow diagram, which limits the scope of application. It was.

  Further, the method described in Non-Patent Document 1 has a problem that the system operator needs knowledge of the application service program and the ability to modify the application service in order to measure the performance of the application service.

  The present invention has been made in view of the above, and does not limit the scope of application to the service, reduces the load on the system operator, and does not depend on the knowledge or correction ability of the system operator's program. It is an object of the present invention to provide a service monitoring apparatus and a service monitoring method that enable service monitoring.

  In order to solve the above-described problems and achieve the object, the service monitoring apparatus according to the present invention acquires a user operation procedure for executing a service, and executes a service use execution unit for executing the service and a service use execution unit in advance. A determination information extraction unit that extracts a character string from each image indicating the execution result of a service that has been executed a plurality of times, and a common character string portion among a plurality of character strings extracted by the determination information extraction unit are determined and at least common A monitoring information setting unit for setting a character string part to be monitored as monitoring information, a character string extracted as a determination target from an image showing a service execution result reproduced by the service use execution unit, and a character string part set as monitoring information And a failure determination unit that determines whether or not there is a failure in execution of the service based on the comparison.

  According to the present invention, the application range to a service is not limited, the load on the system operator is reduced, and the application service can be monitored regardless of the system operator's program knowledge and correction capability.

FIG. 1 is a diagram for explaining an example of the configuration of a service monitoring system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of determination information. FIG. 3 is a diagram illustrating an example of monitoring information. FIG. 4 is a diagram illustrating the determination process of the failure determination unit illustrated in FIG. FIG. 5 is a diagram illustrating the determination process of the failure determination unit illustrated in FIG. FIG. 6 is a diagram for explaining the flow of service monitoring processing by the server shown in FIG. FIG. 7 is a flowchart showing a processing procedure of service monitoring processing according to the present embodiment. FIG. 8 is a flowchart showing the processing procedure of the pre-setting process shown in FIG. FIG. 9 is a flowchart showing a processing procedure of the monitoring process shown in FIG. FIG. 10 is a diagram illustrating an example of a computer in which a server is realized by executing a program.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In addition, this invention is not limited by this embodiment. Moreover, in description of drawing, the same code | symbol is attached | subjected and shown to the same part.

[Embodiment]
First, regarding a service monitoring system having a service monitoring apparatus according to an embodiment, a schematic configuration of the service monitoring system, a processing flow in the service monitoring apparatus, and a specific example will be described.

[Service monitoring system configuration]
First, the configuration of a service monitoring system according to an embodiment will be described with reference to FIG. FIG. 1 is a diagram for explaining an example of the configuration of a service monitoring system according to an embodiment of the present invention.

As shown in FIG. 1, the service monitoring system 1 according to the first embodiment includes a monitoring terminal 10 and a server (service management device) 20. The monitoring terminal 10 and the server 20 are connected by, for example, a dedicated line. The server 20 is connected to an application server 30 that provides an application service (hereinafter referred to as “service”) via, for example, a LAN. The application server 30 is connected to a user terminal 50 that uses a service provided by the application server 30 via a network 40 such as the Internet.

  The monitoring terminal 10 acquires a user operation procedure when using the service by the input device, and outputs a failure determination result by the server 20 from a display or the like.

  The server 20 determines whether there is a failure in executing the service provided by the application server 30. The server 20 extracts a character string from each image indicating an execution result of a service executed a plurality of times in advance based on the acquired user operation procedure as a pre-setting process, and at least is common among the extracted character strings. Set the character string part as monitoring information. Therefore, the server 20 automatically performs an operation of extracting information (monitoring information) that is a basis for determining whether or not there is a failure in service execution from an image indicating the service execution result. Subsequently, the server 20 determines the failure in executing the service based on the comparison between the character string extracted as the determination target from the image showing the service execution result reproduced periodically and the character string portion set as the monitoring information. A monitoring process for determining whether or not there is a problem is executed.

[Configuration of monitoring terminal]
Here, the configuration of the monitoring terminal 10 will be described. As illustrated in FIG. 1, the monitoring terminal 10 includes an input unit 11, a control unit 12, a communication unit 13, a storage unit 14, and an output unit 15.

  The input unit 11 is an input interface that receives various operations from the system operator. For example, the input unit 11 includes an input device such as a keyboard, a mouse, a touch panel, and a voice input device. When the system operator executes an operation for using the service in advance, the input unit 11 acquires a user operation procedure for executing the service. This user operation procedure is information indicating a user operation event (mouse operation or keyboard input). Note that the system operator performs the same operation procedure as that of the actual service use user via the input unit 11.

  The control unit 12 has an internal memory for storing a program that defines various processing procedures and the necessary data, and executes various processes using these programs. For example, the control unit 12 is an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

  The communication unit 13 is a communication interface that transmits and receives various types of information to and from the server 20. The storage unit 14 is realized by a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. Data used during execution is stored.

  The output unit 15 is, for example, a liquid crystal display, a printer, or the like, and outputs various types of information related to management of service execution. The output unit 15 outputs a determination result regarding the presence or absence of a service failure by the server 20.

[Server configuration]
Next, the configuration of the server 20 will be described. The server 20 includes a communication unit 21, a storage unit 22, and a control unit 23.

  The communication unit 21 is a communication interface that transmits and receives various types of information between the monitoring terminal 10 and the application server 30.

  The storage unit 22 is realized by a semiconductor memory device such as a RAM or a flash memory, or a storage device such as a hard disk or an optical disk, and stores a processing program for operating the server 20, data used during execution of the processing program, and the like. Is done. The storage unit 22 includes a user operation storage unit 221, a determination information storage unit 222, and a monitoring information storage unit 223.

  The user operation storage unit 221 stores a user operation procedure for executing a service. The user operation procedure is acquired by the input unit 11 of the monitoring terminal 10, and the server 20 receives the user operation procedure from the monitoring terminal 10 via the communication units 13 and 21, and the user operation storage unit 221. To remember. The user operation storage unit 221 stores a user operation procedure for each service.

  The determination information storage unit 222 stores, as determination information, a character string extracted from an image indicating an execution result of a service executed in advance by a service use execution unit 231 (described later) by a determination information extraction unit 232 (described later). The determination information storage unit 222 stores a plurality of pieces of determination information for the same user operation procedure.

  FIG. 2 is a diagram illustrating an example of determination information. FIG. 2 shows an image including a character string extracted from each image indicating a login result of the service A that has been executed a plurality of times in advance in the pre-setting process (described later). For example, the upper part of FIG. 2A shows an image G1 corresponding to the first execution result, and the lower part of FIG. 2A shows an image G2 corresponding to the second execution result. The regions R11a, R11b, R12a, and R12b of the image G1 include character strings “Login to service A”, “Login time:”, “09”, “:”, and “11”. R21a, R21b, R22a, and R22b of the image G2 include character strings “login to service A”, “login time:”, “10”, “:”, and “14”. Note that FIG. 2B also shows a monitoring image Gt. This monitoring image Gt will be described later.

  The monitoring information storage unit 223 stores the monitoring information set by the monitoring information setting unit 233 (described later). The monitoring information storage unit 223 stores monitoring information for each service. The monitoring information is set based on a character string stored in the determination information storage unit 222. Here, the monitoring information will be specifically described with reference to FIG.

  FIG. 3 is a diagram illustrating an example of monitoring information. The monitoring image Gt illustrated in FIG. 3 is monitoring information corresponding to the login result of the service A, and is image information including a character string extracted from an image indicating the login result of the service A. In FIG. 3, the monitoring image Gt is divided into regions R1a, R1b, R2a, and R2b for explanation.

  The region R1a includes the character strings “Login to service A” and “Login time:”. The region R1b includes a character string “:”. The character strings in the areas R1a and R1b are always displayed when a login operation is performed on the service A, and are common parts in the image indicating the login execution result of the service A. For this reason, the character strings in the regions R1a and R1b are set as monitoring information by the monitoring information setting unit 233, assuming that the character strings need to be matched when the service A is logged in. In the failure determination unit 234 (described later), the presence or absence of a failure in the service A is determined by comparing the character string portions of the areas R1a and R1b with the character string to be determined.

  On the other hand, the regions R2a and R2b include character strings “hh” and “mm”. The character string in the area R2a is a character string indicating the time of the login time of the service A, and the character string in the area R2b is a character string indicating the minutes of the login time of the service A. Therefore, the character strings in these regions R2a and R2b are portions where the character strings change every time login is executed. For this reason, the character string portions of the regions R2a and R2b are set by the monitoring information setting unit 233 as character string portions that allow change. The failure determination unit 234 (described later) also determines whether or not a number corresponding to the regions R2a and R2b in the character string to be determined includes a number indicating an hour or minute, and the failure of the service A Determine presence or absence.

  Returning to FIG. 1, the controller 23 will be described. The control unit 23 has an internal memory for storing a program that defines various processing procedures and the necessary data, and executes various processes using these. For example, the control unit 23 is an electronic circuit such as a CPU or MPU. The control unit 23 includes a service use execution unit 231, a determination information extraction unit 232, a monitoring information setting unit 233, and a failure determination unit 234.

  The service use execution unit 231 stores a user operation procedure for executing a service and executes the service. In other words, the service use execution unit 231 stores the user operation procedure at the time of service use acquired from the input unit 11 of the monitoring terminal 10 in the user operation storage unit 221. Then, the service use execution unit 231 reproduces a user operation event (mouse operation or keyboard input) using the user operation procedure stored in the user operation storage unit 221 and executes the user's service use. Then, the service use execution unit 231 acquires an image indicating the execution result of the executed service, that is, a captured image of the service use screen.

  For example, in the pre-setting process for setting the monitoring information in advance, the service use execution unit 231 executes the service for which the monitoring information is to be set a plurality of times in advance, and displays each execution result of the service. To get. On the other hand, in the monitoring process for monitoring the presence / absence of a failure in the service, the service use execution unit 231 periodically reproduces the service to be monitored and acquires an image indicating the execution result of the service. In the monitoring process, the service use execution unit 231 reproduces the service to be monitored, for example, once every 5 minutes.

  The determination information extraction unit 232 extracts a character string as determination information from each image indicating the execution result of the service executed by the service use execution unit 231 a plurality of times in advance in the pre-setting process. In other words, the determination information extraction unit 232 acquires a plurality of pieces of determination information for the same user operation for the preset target service. In addition, the determination information extraction unit 232 extracts a character string as a determination target from each image indicating the execution result of the monitored service periodically executed by the service use execution unit 231 in the monitoring process. The determination information extraction unit 232 extracts a character string by character recognition (OCR (Optical Character Recognition / Reader)) or the like for each of the plurality of captured images output from the service use execution unit 231. The determination information extraction unit 232 stores the extracted character string in the determination information storage unit 222.

  Specifically, with reference to FIG. 2, a character string extraction process by the determination information extraction unit 232 in the preset process will be described. First, R11a, R11b, R12a, and R12b of the image G1 include character strings “login to service A”, “login time:”, “09”, “:”, and “11”. Therefore, the determination information extraction unit 232 extracts the character strings “login to service A”, “login time:”, “09”, “:”, “11” from R11a, R11b, R12a, R12b. On the other hand, R21a, R21b, R22a, and R22b of the image G2 include character strings “login to service A”, “login time:”, “10”, “:”, and “14”. Therefore, the determination information extraction unit 232 extracts the character strings “Login to service A”, “Login time:”, “10”, “:”, “11” from R21a, R21b, R22a, R22b. Then, the determination information extraction unit 232 stores each extracted character string in the determination information storage unit 222 as determination information.

  The monitoring information setting unit 233 determines a common character string portion among the plurality of character strings extracted by the determination information extraction unit 232, and sets at least the common character string portion as monitoring information. The monitoring information setting unit 233 determines a common character string portion based on the character string stored in the determination information storage unit 222.

  Alternatively, the monitoring information setting unit 233 determines a common character string portion among the plurality of character strings extracted by the determination information extraction unit 232 as a character string portion that needs to be matched, and other than the common character string portion. The character string portion is determined as a character string portion that is allowed to change. Then, the monitoring information setting unit 233 sets, as monitoring information, a combination of a character string portion that needs to match and a character string portion that allows change.

  Specifically, the case where the monitoring information setting unit 233 sets the monitoring information (monitoring image Gt) corresponding to the login result of the service A will be described using the images G1 and G2 illustrated in FIG. As shown in the images G1 and G2, among the character strings included in the images G1 and G2, R11a, R11b, R21a, and R21b of the images G1 and G2 are all character strings “login to service A” and “login time”. :",":"It is included. In other words, the character strings “login to service A”, “login time:”, and “:” are common to the images G1 and G2. Therefore, for the login result of service A, the monitoring information setting unit 233 determines that the character strings “login to service A”, “login time:”, and “:” are common.

  In other words, the character strings “login to service A”, “login time:”, and “:” in images G1 and G2 are always shown when the login operation for service A is performed, and the login result of service A It is a common part in the image which shows. Therefore, at the time of executing the login of service A, the character strings “login to service A”, “login time:”, and “:” are set by the monitoring information setting unit 233 as the character string portions that need to be matched. Is done.

  On the other hand, the character strings “09”, “11”, “10”, “14” indicating the hour or minute of the actual login time are included in the regions R12a, R12b, R22a, R22b of the images G1, G2. The character strings in the regions R12a, R12b, R22a, and R22b of the images G1 and G2 differ depending on the time when each login operation is actually executed. That is, the login character strings “09”, “11”, “10”, and “14” in the regions 12a, R12b, R22a, and R22b of the images G1 and G2 are portions that change every time the login to the service A is executed. is there. For this reason, the character string portions of the regions 12a, R12b, R22a, and R22b are set by the monitoring information setting unit 233 as character string portions that allow change.

  As a result, the monitoring information setting unit 233 sets the monitoring image Gt illustrated in FIG. 2 as monitoring information corresponding to the login result of the service A. In the monitoring image Gt, the character strings “login to service A”, “login time:”, and “:” in the areas R1a and R1b are character string portions that need to be matched when the service A login is executed.

  In addition, the character strings “hh” and “mm” in the areas R2a and R2b of the monitoring image Gt are character string parts that allow change, and do not necessarily need to match. The character string “hh” in the region R2a of the monitoring image Gt contains any number from “00” to “23” indicating the hour, and the character string “mm” in the region R2b is “00” indicating the minute. Enter any number from ~ 59. The failure determination unit 234 (described later) determines whether or not there is a failure in the service A by comparing at least the character string portions of the areas R1a and R1b of the monitoring image Gt with the character string to be determined. Further, the failure determination unit 234 (described later) also determines whether or not a number corresponding to the character string portion of the regions R2a and R2b is indicated with a number indicating an hour or minute in the character string to be determined. Then, the presence or absence of a failure in service A is determined.

  Therefore, next, the failure determination unit 234 will be described. The failure determination unit 234 periodically compares the character string extracted as the determination target from the image indicating the execution result of the service executed by the service use execution unit 231 with the character string portion set as the monitoring information. Next, it is determined whether there is a failure in executing the service.

  For example, the failure determination unit 234 determines that there is a failure in service execution when the character string portion extracted as the determination target and the character string set as the monitoring information do not match.

  Alternatively, the failure determination unit 234 corresponds to the character string extracted from the character string extracted as the determination target when the character string corresponding to the character string portion that needs to match the monitoring information does not match, or to the character string portion that allows change. If the character string to be processed is a character string that exceeds the allowable change, it is determined that there is a failure in the execution of the service.

  Specifically, the determination process of the failure determination unit 234 will be described with reference to FIGS. 4 and 5. 4 and 5 are diagrams for explaining the determination process of the failure determination unit 234. FIG. First, a description will be given with reference to FIG.

  An image Gh illustrated in FIG. 4 is an image including a character string extracted from an image indicating a login result to the service A that is executed by the service use execution unit 231 at a timing of the monitoring process. The failure determination unit 234 determines whether there is a failure in executing the service by comparing the monitoring image Gt with the image Gh to be determined. The region R1ha of the image Gh is a region corresponding to the region R1a in the monitoring image Gt. The region R1hb of the image Gh is a region corresponding to the region R1b in the monitoring image Gt. The region R2ha of the image Gh is a region corresponding to the region R2a in the monitoring image Gt. The region R2hb of the image Gh is a region corresponding to the region R2b in the monitoring image Gt.

  Therefore, the failure determination unit 234 compares the character strings of the regions R1ha and R1hb of the image Gh with the character strings of the regions R1a and R1b of the monitoring image Gt (see (1) in FIG. 4). In the example of FIG. 4, the character strings “login to service A” and “login time:” in the region R1ha of the image Gh, the character string “:” in the region R1hb, and the character string “service A in the region R1a of the monitoring image Gt”. "Login", "Login time:" and the character string ":" in the area R1b match (see (2) in FIG. 4). A number indicating “12” is shown in the region R2ha of the image Gh, and a number indicating “04” is shown in the region R2hb of the image Gh. Therefore, the failure determination unit 234 determines that the service A is normal (see (3) in FIG. 4).

  Next, description will be made with reference to FIG. An image Gi shown in FIG. 5 is an image including a character string extracted from an image indicating a result of login to the service A executed by the service use execution unit 231 at another timing of the monitoring process. A region R1ia of the image Gi is a region corresponding to the region R1a in the monitoring image Gt. A region R1ib of the image Gi is a region corresponding to the region R1b in the monitoring image Gt. A region R2ia of the image Gi is a region corresponding to the region R2a in the monitoring image Gt. A region R2ib of the image Gi is a region corresponding to the region R2b in the monitoring image Gt.

  In this case, the failure determination unit 234 compares the character string of the region R1ia of the image Gi with the character string of the regions R1a and R1b of the monitoring image Gt (see (1) in FIG. 5). In the example of FIG. 5, the region R1ia of the image Gi includes the character string “login error in the service A”, but the character string “login time:” of the region R1a of the monitoring image Gt and the character string “:” of the region R1b. Not shown. For this reason, the character string of the area R1ia of the image Gi and the character string of the area R1a of the monitoring image Gt do not match (see (2) in FIG. 5). Further, R2ia and R2ib of the image Gi are blank, and none of the numbers indicating hours or minutes is shown. Therefore, the failure determination unit 234 determines that the service A is abnormal and the service A has a failure (see (3) in FIG. 5).

  In this way, the server 20 does not simply determine whether the images match, but instead monitors a combination of a character string portion that needs to be matched and a character string portion that allows change from a plurality of character strings that are determination information. Information (for example, monitoring image Gt) is set, and it is possible to determine that a change part is allowed when the date and time are different. Accordingly, the server 20 eliminates false detections due to changes other than failures, and enables wide and practical monitoring of services.

  If the failure determination unit 234 determines that there is a failure in service execution, the failure determination unit 234 outputs a failure notification indicating that there is a failure in service execution to the monitoring terminal 10. In response to this, the monitoring terminal 10 outputs from the output unit 15 that there is a failure in the execution of the service. By confirming this output result, the system operator can recognize that there is a failure in the execution of the service.

[Service monitoring process flow]
Next, the flow of service monitoring processing by the server 20 will be described with reference to FIG. FIG. 6 is a diagram for explaining the flow of service monitoring processing by the server 20. As described above, the server 20 executes the pre-setting process and the monitoring process. In FIG. 6, description will be made assuming that the solid line arrow corresponds to the presetting process and the broken line arrow corresponds to the monitoring process.

  First, the pre-setting process will be described. The server 20 executes the pre-setting process for each operation procedure of each service. In the presetting process, first, an operation for using the service in advance by the system operator is executed by the input unit 11 of the monitoring terminal 10. In the server 20, the service use execution unit 231 acquires the user operation procedure at the time of service execution from the input unit 11 as indicated by the arrow Y1 (see (1) in FIG. 6).

  The service use execution unit 231 stores the user operation procedure in the user operation storage unit 221 as indicated by an arrow Y2 (see (2) in FIG. 6). Then, the service use execution unit 231 reproduces a user operation event (mouse operation or keyboard input) using the user operation procedure stored in the user operation storage unit 221 and executes the user's service use a plurality of times (FIG. 6). (See (2)). Then, the service use execution unit 231 acquires an image indicating the execution result of each executed service, that is, a captured image of the service use screen, and outputs it to the determination information extraction unit 232 as indicated by an arrow Y3 (FIG. 6). (See (3)).

  The determination information extraction unit 232 extracts a character string by character recognition for each of the plurality of captured images output from the service use execution unit 231 (see (4) in FIG. 6). Then, the determination information extraction unit 232 outputs, to the determination information storage unit 222, a character string extracted from each image indicating a service execution result by execution of each user operation procedure, as indicated by an arrow Y4 (FIG. 6 ( See 5)). The determination information storage unit 222 stores a plurality of character strings for the same user operation procedure (see (6) in FIG. 6).

  Subsequently, the monitoring information setting unit 233 reads an image showing a plurality of character string portions as determination information as indicated by an arrow Y5 (see (7) in FIG. 6). The monitoring information setting unit 233 generates monitoring information from the read determination information (see (8) in FIG. 6). Specifically, the monitoring information setting unit 233 determines that a common character string portion is a character string portion that needs to be matched between images showing a plurality of character string portions ((8) in FIG. 6). (See (a)). The monitoring information setting unit 233 determines that a different character string portion is a character string portion that allows a change between images indicating a plurality of character string portions (see (b) of (8) in FIG. 6). .

  Then, based on this result, the monitoring information setting unit 233 sets the monitoring information as indicated by the arrow Y6 (see (9) in FIG. 6) and stores it in the monitoring information storage unit 223. For example, the monitoring image Gt shown in FIG. 2 is set as the monitoring information corresponding to the login result of the service A.

  Subsequently, the monitoring process will be described. The server 20 periodically executes monitoring processing for each service operation procedure. First, as a monitoring process, the service use execution unit 231 periodically reproduces a user operation event using the user operation procedure stored in the user operation storage unit 221 and executes the user's service use (FIG. 6). (Refer to (11)). Then, the service use execution unit 231 acquires a captured image of the service use screen and outputs it to the determination information extraction unit 232 as indicated by an arrow Y11 (see (12) in FIG. 6).

  Then, the determination information extraction unit 232 extracts a character string from the captured image output from the service use execution unit 231 (see (13) in FIG. 6). Then, the determination information extraction unit 232 outputs the character string extracted from the captured image to the failure determination unit 234 as a determination target character string as indicated by an arrow Y12 (see (14) in FIG. 6).

  Subsequently, the failure determination unit 234 reads the character string portion set as the monitoring information corresponding to this user operation procedure as indicated by the arrow Y13 from the monitoring information storage unit 223 (see (15) in FIG. 6). . Then, the failure determination unit 234 compares the read monitoring information with the determination target acquired at the time of monitoring (see (16) in FIG. 6).

  Specifically, the failure determination unit 234 compares the character string portion read from the monitoring information storage unit 223 with the character string portion output to the failure determination unit 234 as the character string to be determined, and matches the monitoring information. If the character string corresponding to the required character string part does not match, or if the character string corresponding to the character string part that is allowed to change is a character string that exceeds the allowable change, the execution of the service is obstructed. Determine that there is.

  On the other hand, when the read monitoring information does not match the determination target acquired at the time of monitoring, the failure determination unit 234 determines that there is a failure in the service executed in this user operation procedure, as indicated by an arrow Y14. Then, the failure notification is output to the monitoring terminal 10 (see (17) in FIG. 6). In response to this, the monitoring terminal 10 outputs from the output unit 15 that there is a failure in service execution in this user operation procedure.

[Service monitoring processing procedure]
Next, with reference to FIG. 7, a processing procedure of service monitoring processing executed by the server 20 will be described. FIG. 7 is a flowchart showing a processing procedure of service monitoring processing according to the present embodiment.

  As illustrated in FIG. 7, the server 20 extracts a character string from an image indicating the execution result of a previously executed service, and performs a preset process for setting a common character string portion of the extracted character strings as monitoring information. (Step S1). Then, the server 20 determines whether or not there is a failure in executing the service based on a comparison between the character string extracted from the image indicating the execution result of the periodically executed service and the character string portion set as the monitoring information. A monitoring process is performed (step S2).

[Pre-configuration process]
FIG. 8 is a flowchart showing a processing procedure of the pre-setting process (step S1) shown in FIG.

  As illustrated in FIG. 8, first, the service use execution unit 231 acquires a user operation procedure to be processed in advance from the monitoring terminal 10 (step S11). Subsequently, the service use execution unit 231 reproduces a user operation event using the acquired user operation procedure, and performs a service use execution process for executing the user's service use a plurality of times (step S12). In this process, the service use execution unit 231 acquires a captured image indicating the execution result of each executed service, and outputs the captured image to the determination information extraction unit 232.

  The determination information extraction unit 232 performs a determination information extraction process for extracting a character string as determination information for each of the plurality of captured images output from the service use execution unit 231 (step S13). And the determination information extraction part 232 performs the determination information storage process which memorize | stores the some character string with respect to the extracted same user operation procedure in the determination information storage part 222 (step S14).

  Subsequently, the monitoring information setting unit 233 determines a common character string portion from a plurality of character string portions read out as determination information from the determination information storage unit 222, and at least uses the common character string portion as monitoring information. A monitoring information setting process to be set is performed (step S15). In addition, the monitoring information setting unit 233 determines a common character string portion among the plurality of character strings extracted by the determination information extraction unit 232 as a character string portion that needs to be matched, and other than the common character string portion. The character string portion may be determined as a character string portion that allows a change, and a combination of a character string portion that needs to match and a character string portion that allows a change may be set as monitoring information. The monitoring information setting unit 233 stores the set monitoring information in the monitoring information storage unit 223, and ends the pre-setting process corresponding to this user operation procedure.

[Monitoring process]
FIG. 9 is a flowchart showing the procedure of the monitoring process (step S2) shown in FIG.

  The control unit 23 determines whether it is the monitoring timing (step S21). This monitoring timing is set so that the monitoring process can be periodically executed for each user operation procedure to be monitored. If the control unit 23 determines that it is not the monitoring target timing (step S21: No), the control unit 23 returns to step S21 and executes the determination process of step S21 again.

  On the other hand, when the control unit 23 determines that it is the monitoring target timing (step S21: Yes), the service use execution unit 231 reads the monitoring target user operation procedure from the user operation storage unit 221 (step S22). ), A service operation reproduction process for reproducing the user operation event and executing the service use of the user is performed (step S23). In this case, the service use execution unit 231 acquires a captured image of the service use screen indicating the reproduced service execution result, and outputs the captured image to the determination information extraction unit 232.

  Then, the determination information extraction unit 232 performs a determination target extraction process for extracting a character string as a determination target from the captured image output from the service use execution unit 231 (step S24), and the extracted character string is determined as a failure determination unit. Output to H.234.

  Subsequently, the failure determination unit 234 reads from the monitoring information storage unit 223 the character string portion set as the monitoring information corresponding to this user operation procedure (step S25). Then, the failure determination unit 234 compares the character string portion read as the monitoring information with the character string to be determined, and the character string portion that requires the position read as the monitoring information and the character string to be determined It is determined whether or not they match (step S26). In step S26, the failure determination unit 234 compares the character string corresponding to the character string portion that needs to be matched with the monitoring information, and changes the character string corresponding to the character string portion that is allowed to change. It may be determined whether the character string exceeds the limit.

  If the failure determination unit 234 determines that the character string portion that needs to be read as the monitoring information matches the character string to be determined (step S26: Yes), the service executed in this user operation procedure is normal. (Step S27), the process returns to step S21. Alternatively, when the failure determination unit 234 further determines that the character string corresponding to the character string portion that allows the change in the monitoring target among the determination targets does not exceed the allowable change, It is determined that the service to be executed is normal.

  On the other hand, when the failure determination unit 234 determines that the character string portion that needs to be read as the monitoring information does not match the character string to be determined (step S26: No), the service executed in this user operation procedure Is determined to have a failure (abnormality) (step S28). Alternatively, if the failure determination unit 234 determines that the character string corresponding to the character string portion that allows the change in the monitoring information among the determination targets exceeds the allowable change, the user operation procedure The service to be executed is determined to be faulty. Then, the failure determination unit 234 outputs a failure notification to the monitoring terminal 10 (step S29).

[Effect of the embodiment]
As described above, in the present embodiment, the common character string portion extracted as monitoring information from the image indicating the execution result of the application service executed during the pre-setting process, and the execution of the service reproduced by the service use execution unit 231 Based on the comparison with the character string extracted as the determination target from the image indicating the result, it is determined whether there is a failure in executing the service. For this reason, according to the present embodiment, it is not necessary for the service content to output a log that can generate a monitoring method from the flow diagram, and the service can be monitored without limiting the scope of application to the service. is there. In other words, according to the present embodiment, the normality of the application service can be monitored even for services that could not be applied so far, so that the influence on the application service user can be detected more quickly. Become.

  Further, according to the present embodiment, the system operator only has to perform an operation for using the application service to be monitored during the pre-setting process. In other words, according to the present embodiment, it is not necessary to create a flow diagram for analyzing the log for each application service, and to know and modify the application, so that the load on the system operator can be reduced.

  Further, in the present embodiment, instead of simply determining whether images match, monitoring is performed by combining a character string portion that requires matching and a character string portion that allows change from a plurality of character strings that are determination information. Information is set, and it is possible to determine that the change part is allowed when the date is different. As a result, according to the present embodiment, it is possible to eliminate erroneous detection due to changes other than failures, and to perform wide and practical monitoring on application services.

  Therefore, according to the present embodiment, the scope of application service is not limited, the load on the system operator is reduced, and the application service is monitored regardless of the system operator's program knowledge and correction capability. to enable.

  In the present embodiment, the example in which the server 20 periodically executes the monitoring process has been described. However, the present invention is not limited to this. For example, the server 20 may execute the monitoring process when receiving a monitoring process execution instruction from the monitoring terminal 10. Alternatively, the server 20 may execute the monitoring process when the application server 30 has revised the application service.

  In the present embodiment, the monitoring information is a combination of a character string portion that needs to be matched and a character string portion that allows change based on a plurality of character strings extracted by the determination information extraction unit 232. Of course, but not limited to this. The monitoring information may be only a common character string portion, that is, a character string portion that needs to be matched among a plurality of character strings extracted by the determination information extraction unit 232. Also in this case, since it is possible to compare with the character string to be determined, it is possible to determine whether there is a failure in executing the service.

[Other embodiments]
[System configuration, etc.]
Each component of each illustrated device is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or a part of the distribution / integration is functionally or physically distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. Further, all or a part of each processing function performed in each device can be realized by a CPU and a program that is analyzed and executed by the CPU, or can be realized as hardware by wired logic.

  In addition, among the processes described in this embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

[program]
FIG. 10 is a diagram illustrating an example of a computer in which the server 20 is realized by executing a program. The computer 1000 includes a memory 1010 and a CPU 1020, for example. The computer 1000 also includes a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1090. The disk drive interface 1040 is connected to the disk drive 1100. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to a mouse 1110 and a keyboard 1120, for example. The video adapter 1060 is connected to the display 1130, for example.

  The hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, a program that defines each process of the server 20 is implemented as a program module 1093 in which a code executable by the computer 1000 is described. The program module 1093 is stored in the hard disk drive 1090, for example. For example, a program module 1093 for executing processing similar to the functional configuration in the server 20 is stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced by an SSD (Solid State Drive).

  The setting data used in the processing of the above-described embodiment is stored as program data 1094 in, for example, the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the memory 1010 and the hard disk drive 1090 to the RAM 1012 and executes them as necessary.

  The program module 1093 and the program data 1094 are not limited to being stored in the hard disk drive 1090, but may be stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and the program data 1094 may be stored in another computer connected via a network (LAN, WAN, etc.). Then, the program module 1093 and the program data 1094 may be read by the CPU 1020 from another computer via the network interface 1070.

  Although the embodiment to which the invention made by the present inventor is applied has been described above, the present invention is not limited by the description and the drawings that form part of the disclosure of the present invention according to this embodiment. That is, other embodiments, examples, operation techniques, and the like made by those skilled in the art based on the present embodiment are all included in the scope of the present invention.

DESCRIPTION OF SYMBOLS 1 Service monitoring system 10 Monitoring terminal 11 Input part 12,23 Control part 13,21 Communication part 14,22 Storage part 15 Output part 20 Server 30 Application server 40 Network 50 User terminal 221 User operation storage part 222 Judgment information storage part 223 Monitoring Information storage unit 231 Service use execution unit 232 Determination information extraction unit 233 Monitoring information setting unit 234 Failure determination unit

Claims (8)

A user operation procedure for executing a service, and a service use execution unit for executing the service;
A determination information extraction unit that extracts a character string from each image indicating an execution result of the service that is executed in advance by the service use execution unit a plurality of times;
A monitoring information setting unit that determines a common character string portion among a plurality of character strings extracted by the determination information extraction unit, and sets at least the common character string portion as monitoring information;
Based on a comparison between a character string extracted as an object to be determined from an image showing an execution result of the service reproduced by the service use execution unit and a character string portion set as the monitoring information, a failure in execution of the service A failure determination unit for determining the presence or absence of
A service monitoring apparatus comprising:   The failure determination unit determines that there is a failure in the execution of the service when a character string extracted as the determination target does not match a character string portion set as the monitoring information. The service monitoring apparatus according to claim 1.   The monitoring information setting unit determines the common character string portion as a character string portion that needs to be matched among the plurality of character strings extracted by the determination information extraction unit, and other than the common character string portion. The character string portion is determined as a character string portion that allows a change, and a combination of the character string portion that needs to be matched and the character string portion that allows the change is set as the monitoring information. Item 6. The service monitoring apparatus according to Item 1.   The failure determination unit, when the character string corresponding to the character string portion that needs to match the monitoring information, does not match among the character strings extracted as the determination target, or the character string portion that allows the change The service monitoring apparatus according to claim 3, wherein if the character string corresponding to the number exceeds a permitted change, it is determined that there is a failure in the execution of the service.   The service monitoring apparatus according to claim 1, wherein the failure determination unit periodically determines whether there is a failure in execution of the service.   6. The failure determination unit according to claim 1, wherein the failure determination unit outputs a failure notification indicating that there is a failure in the execution of the service when it is determined that there is a failure in the execution of the service. The service monitoring device according to claim 1. A determination information storage unit that stores the character string extracted by the determination information extraction unit;
The service monitoring apparatus according to claim 1, wherein the monitoring information setting unit determines the common character string portion based on a character string stored in the determination information storage unit. . A service monitoring method executed by a service management device that manages a failure in service execution,
The service management device acquires a user operation procedure for executing the service, and executes the service in advance.
The service management device extracting a character string from an image indicating an execution result of the service in the step of executing the service in advance;
The service management device determining a common character string portion of the extracted character strings, and setting at least the common character string portion as monitoring information; and
The service management device reproducing the service;
Based on a comparison between a character string extracted as an object of determination from an image indicating an execution result of the service in the step of reproducing the service and a character string portion set as the monitoring information, the service management device Determining whether there is a failure in execution of
A service monitoring method comprising:

Images