JP2022117443A - Device, method, and program for processing information - Google Patents

Abstract

To provide an information processing device, information processing method, and information processing program, which allow for reducing the cost of analyzing causes of errors and operating records of processing targets using execution logs.SOLUTION: An information processing device according to an embodiment comprises log recording means configured to record execution logs for one or more processing targets in a hierarchical structure for each granularity, and viewer means configured to display a viewer screen on a display unit to hierarchically present the execution logs recorded in the hierarchical structure.SELECTED DRAWING: Figure 5

Description

The present invention relates to an information processing device, an information processing method, and an information processing program.

For example, in the existing general log storage format, there was a problem that logs with different granularity were mixed and displayed on the log viewer. Therefore, identifying the operation that caused the error and viewing the log along with the series of executions was costly. As a conventional log storage system, for example, Patent Document 1 is available.

JP 2020-77174 A

However, Japanese Patent Laid-Open No. 2002-200000 does not describe anything about using execution logs to reduce the cost of analyzing error causes and operation records.

The present invention has been made in view of the above, and provides an information processing apparatus, an information processing method, and an information processing apparatus capable of reducing the cost of analyzing error causes and operation records by using an execution log for a processing target. The purpose is to provide an information processing program.

In order to solve the above-described problems and achieve the object, the present invention provides an information processing apparatus comprising a control unit, wherein the control unit stores one or more processing target execution logs in a hierarchical structure for each granularity. and a viewer means for displaying a viewer screen on a display unit and hierarchically displaying the execution log recorded in the hierarchical structure.

Further, according to one aspect of the present invention, the hierarchical display may include a drill-down display or a tree structure display.

Further, according to one aspect of the present invention, the log recording means stores the execution log in a summary log including date and time, log level indicating normal or error, processing target, and summary key information, date and time, log level, process A detailed log containing contents and detailed key information and a detailed log containing dates, log levels, operation contents and detailed key information are recorded in tables in a hierarchical structure, respectively, and the viewer means displays the summary on the viewer screen. Displaying the detailed log from the summary log using the key information and the detailed key information, and displaying the detailed log from the detailed log using the detailed key information and the detailed key information in a drill-down or tree structure You can decide.

Further, according to one aspect of the present invention, the log recording means adds a different execution type code to the summary log when the detailed log differs in type and/or the number of columns, and adds a different execution type code to the summary log. A table may be separately recorded for each.

Further, according to one aspect of the present invention, the execution log may include an RPA (Robotic Process Automation) execution log.

Further, according to one aspect of the present invention, the detailed log includes execution robot information, operation target information, and loop count information recorded according to the RPA flow definition, and the detailed log is recorded according to an automatic operation command. It may include operation target item information and input information.

Further, according to one aspect of the present invention, the control unit further displays a log deletion screen displayed on the display unit according to a log policy that sets whether deletion is possible for each log granularity and, if deletion is possible, the storage period. A log deletion means for deleting the log specified by may be provided.

Further, according to one aspect of the present invention, the execution log may include a log of processing from login to logout of the user for the processing target.

Further, in order to solve the above-described problems and achieve the object, the present invention provides an information processing method executed by an information processing apparatus having a control unit, comprising one or more and a viewer step of displaying a viewer screen on a display unit and hierarchically displaying the execution logs recorded in the hierarchical structure. It is characterized by

Further, in order to solve the above-described problems and achieve the object, the present invention provides an information processing program to be executed by an information processing apparatus having a control unit, wherein the control unit performs one or more processes To execute a log recording step of recording target execution logs in a hierarchical structure for each granularity, and a viewer step of displaying the execution logs recorded in the hierarchical structure in a hierarchical manner by displaying a viewer screen on the display unit. characterized by being an information processing program of

According to the present invention, it is possible to reduce the cost of analyzing the causes of errors and operation records by using the execution log of the processing target.

FIG. 1 is a diagram showing an example of an RPA operation definition. FIG. 2 is a diagram illustrating an example of a log of RPA processing. FIG. 3 is a diagram for explaining problems of conventional logs. FIG. 4 is a diagram showing a structural example of a log table according to this embodiment. FIG. 5 is a block diagram showing an example of the configuration of the information processing apparatus according to this embodiment. FIG. 6 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 7 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 8 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 9 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 10 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 11 is a diagram for explaining a specific example of processing of the information processing apparatus according to this embodiment. FIG. 12A is a diagram for explaining a specific example of processing of the information processing apparatus according to the embodiment. FIG. 12B is a diagram for explaining a specific example of processing of the information processing apparatus according to the embodiment. FIG. 13 is a diagram for explaining a specific example of processing of the information processing apparatus according to this embodiment. FIG. 14 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 15 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 16 is a diagram for explaining a specific example of processing of the information processing apparatus according to this embodiment. FIG. 17 is a diagram for explaining a specific example of processing of the information processing apparatus according to this embodiment. FIG. 18 is a diagram for explaining a specific example of processing of the information processing apparatus according to this embodiment. FIG. 19 is a diagram for explaining a specific example of processing of the information processing apparatus according to this embodiment. FIG. 20 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 21 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 22 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 23 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 24 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 25 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 26 is a diagram for explaining a specific example of processing of the information processing apparatus according to the present embodiment. FIG. 27 is a diagram for explaining a specific example of processing of the information processing apparatus according to this embodiment. FIG. 28 is a diagram for explaining Modification 1 of the information processing apparatus according to the present embodiment. FIG. 29 is a diagram for explaining Modification 2 of the information processing apparatus according to the present embodiment. FIG. 30 is a diagram for explaining Modification 2 of the information processing apparatus according to the present embodiment. FIG. 31 is a diagram for explaining Modification 2 of the information processing apparatus according to the present embodiment. FIG. 32 is a diagram for explaining Modification 2 of the information processing apparatus according to the present embodiment.

Embodiments of an information processing apparatus, an information processing method, and an information processing program according to the present invention will be described in detail below with reference to the drawings. In addition, this invention is not limited by this embodiment.

[1. Overview]
Recently, there has been an increasing demand for automatic operation of applications called, for example, RPA (Robotic Process Automation). This is against the background of the desire to promote the automation of routine work, partly due to movements such as work style reform.

Such RPA has automation tools for automating operations. Specifically, by registering (defining) a plurality of operations by the user and executing the registered operations, it is possible to easily execute standardized operations after the second time. .

In such RPA, a definition is required for automatic operation of the application, and easiness of creating the definition and easiness of investigation when unexpected is required.

FIG. 1 is a diagram showing an example of an RPA operation definition. In the example of the operation definition shown in FIG. 1, for the business system, (1) a value is set in A, (2) a value is set in B, and (3) a value is set in C.

An overview of a typical log will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of a log of RPA processing. A general log is a mixture of logs from multiple executors and lists the processing details in chronological order. Since RPA is operated automatically, it is often difficult for a person to grasp the processing details during execution, and information is generally obtained from logs. In the example of the log shown in FIG. 2, the logs of the processing details of different processing targets by multiple executors are listed in chronological order.

Problems with conventional logs will be described with reference to FIG. FIG. 3 is a diagram for explaining problems of conventional logs. It is costly to perform result analysis from a log listing complicated processing details. Especially when executing a complicated flow with different processing procedures depending on the request, such as RPA,
The log itself becomes complicated due to the mixture of the processing contents of different executions and the difference in log granularity. Therefore, it took a lot of time to confirm the results and analyze the location where the problem occurred.

For example, in Fig. 3, it is difficult to identify the location of the problem from the conventional log and investigate the cause, because the processing contents of different processing targets are mixed, so it is difficult to grasp the contents of the processing before and after. costs due to the reason.

In this embodiment, in order to solve the problem that it costs a lot to identify and analyze the cause of an error by referring to the execution logs of one or more processing targets (for example, applications), the execution logs are hierarchically arranged. Manage by structure. Specifically, the normal/error logs that occur in a complex definition-based process flow are structured by granularity, divided into multiple tables in a hierarchical structure, and recorded. Viewability of the log is improved by making it possible to view it in a down or tree structure).

FIG. 4 is a diagram showing a structural example of a log table according to this embodiment. In this embodiment, the execution log is recorded in a three-level hierarchical structure of summary log, detailed log, and detailed log.

By the way, in general, there are mainly two storage purposes for logs. The first is a record of the details of the operation, and it is mainly used to save a short-term necessary log (detailed log and detailed log in this specification) that is checked mainly to identify the cause of the error. be. The second is storage of logs (summary logs of this specification correspond) that need to be stored for a long time, which is necessary to satisfy audit requirements.

However, there is a concern that the details and detailed logs will become bloated. The number of records tends to increase as the granularity of the log becomes finer. For this reason, there is a concern that a log with fine granularity will increase the file capacity when recording.

Therefore, in the present embodiment, (1) logs recorded in an arbitrary period can be selected and deleted for each granularity, and (2) a period that cannot be deleted can be set for each log granularity, and necessary logs can be deleted. Implemented a function to prevent accidental deletion of

As a result, (1) it is possible to selectively delete detailed logs and detailed logs that cause bloated capacity, and (2) logs that are necessary for audit requirements (summary logs, etc.) can be stored for a long time or cannot be deleted. It is possible to prevent log deletion due to erroneous operation.

In the following explanation, the execution log of the automatic operation of RPA will be explained, but the present invention is not limited to RPA, but is applicable to general business systems and systems that can create flows by combining definitions and tasks. Execution logs are also applicable.

[2. Constitution]
A configuration of information processing apparatus 100 according to the present embodiment will be described with reference to FIG. FIG. 5 is a block diagram showing an example of the configuration of information processing apparatus 100 according to this embodiment.

The information processing device 100 is a commercially available desktop personal computer. Note that the information processing apparatus 100 is not limited to a stationary information processing apparatus such as a desktop personal computer, and may be a portable type such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), a smart phone, or a tablet personal computer. It may be an information processing device.

The information processing apparatus 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108, as shown in FIG. Each unit included in the information processing apparatus 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicably connects the information processing device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with another device via a communication line. Here, the network 300 has a function of connecting the information processing apparatus 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data stored in the storage unit 106, which will be described later, may be stored in a server.

An input device 112 and an output device 114 are connected to the input/output interface section 108 . The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that cooperates with the mouse to provide a pointing device function. Note that, hereinafter, the output device 114 may be referred to as the monitor 114 and the input device 112 may be referred to as the keyboard 112 or the mouse 112 . Further, the user's operation on the screen (GUI or the like) of the output device (monitor) 114 with the input device 112 may be simply referred to as "user operation".

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for performing various processes by giving commands to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

The storage unit 106 includes a definition file 106a, a log table 106b, a log policy file 106c, and the like.

The definition file 106a is for storing a definition (also referred to as "RPA robot execution definition") defining a series of operation commands for the automatic operation unit (RPA system) 102a to automatically operate one or more processing targets. is a file. A group unit defining a series of operation instructions necessary for one execution of processing (one loop), which is defined for each application to be processed, is defined as a “robot or RPA robot”. The details of the "RPA robot execution definition" will be described later.

The log table 106b is a table for storing the execution log created by the log recording unit 102a1 of the automatic operation unit (RPA system) 102a. It is stored in the summary log table, detailed log table, and detailed log table in a hierarchical structure.

The log policy file 106c is a file for storing a log policy that is set on the log policy setting screen and defines whether deletion is possible for each log granularity and, if deletion is possible, the retention period (period during which deletion is not possible).

The control unit 102 is a CPU or the like that comprehensively controls the information processing apparatus 100 . The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

The control unit 102 is configured to be able to access a definition file 106a, a log table 106b, and the like stored in the storage unit 106. FIG. Note that the definition file 106a and the log table 106b may be provided in another location (for example, the server 200) as long as the control unit 102 can access them.

The control unit 102 functionally and conceptually includes an automatic operation unit (RPA system) 102a and an application 102b.

The automatic operation unit (RPA system) 102a executes automatic operations on the application 102b according to the definition that defines a series of operations on the application 102b registered in the definition file 106a.

The automatic operation unit (RPA system) 102a functionally and conceptually includes a log recording unit 102a1, a viewer unit 102a2, and a log deletion unit 102a3. The automatic operation unit 102a is incorporated in the aforementioned RPA. In addition to being incorporated into RPA, it may be incorporated into other automatic operation tools such as RDA (Robotic Desktop Automation).

The log recording unit 102a1 generates execution logs of a plurality of processing targets (applications 102b) and records them in a log table 106b in a hierarchical structure for each granularity.

The log recording unit 102a1 stores an execution log as a summary log including date and time, log level indicating normal or error, processing target, and summary key information, a detailed log including date and time, log level, processing content, and detailed key information, , log level, operation content, and detailed log including detailed key information may be recorded in the log table 106b in a hierarchical structure.

When the detailed logs differ in type and/or number of columns, the log recording unit 102a1 may add different execution type codes to the summary log and record a separate table for each different execution type code. .

The viewer unit 102a2 displays a viewer screen on the monitor 114 and hierarchically displays the execution logs recorded in the hierarchical structure in the log table 106b.

Hierarchical display may include drill-down display or tree structure display. The viewer unit 102a2 uses the summary key information and the detail key information on the viewer screen to drill down from the summary log to the detail log, use the detail key information and the detail key information, and drill down or tree structure from the detail log to the detail log. may be displayed with .

The log deletion unit 102a3 deletes the log specified on the log deletion screen displayed on the monitor 114 from the log table 106b according to the log policy of the log policy file 106c.

The application 102b is one or a plurality of applications to be processed, and includes, for example, business applications such as order receiving, purchasing, ordering, shipping, and sales, and various applications such as browsers. The invention is also applicable to other applications. Applications are stored in the storage unit 106, and the application stored in the storage unit 106 that is executed by the control unit 102 is functionally conceptually expressed as the application 102b of the control unit 102. FIG.

[3. Specific example of processing]
A specific example of the processing of the control unit 102 of the information processing apparatus 100 according to the present embodiment will be described with reference to FIGS. 6 to 20. FIG. 6 to 20 are diagrams for explaining specific examples of the processing of the control unit 102 of the information processing apparatus 100 according to the present embodiment.

The automatic operation unit (RPA system) 102a of the control unit 102 executes the following processing (flow) according to the RPA robot execution definition (program and data) stored in the definition file 106a. The processing (flow) shown below indicates processing executed by the automatic operation unit 102a according to the RPA execution definition, but for the sake of simplicity, the RPA execution definition may be described as the subject of action.

(3-1. Common (basic) definition)
The common definition of the RPA robot execution definition will be described with reference to FIGS. 6 to 11. FIG. First, the underlying common definition is described.

(Definition of RPA flow)
FIG. 6 is a diagram showing an execution flow including processing before and after execution of the RPA robot. It is assumed that the data to be input to the robot is prepared in Excel or the like, and that the data is input repeatedly.

In FIG. 6, when the RPA flow is started (step S1), the RPA data source is read (step S2). Here, for example, a data source prepared by Excel or the like is read.

Execute the RPA data source loop (step S3). Here, loop processing is performed for the number of read data.

When the loop starts (step S4), the RPA robot is executed (step S7). Detailed settings such as how to make the robot move are made separately. Determine success or failure of the execution result. If the execution result is successful (step S8), the next loop is executed (step S10). If the execution results in failure (step S9), a handling pattern is selected according to the operation. (1) In the case of error continuation type (processing is continued even after an error occurs) (step S11), the next loop is executed (step S10). (2) In the case of the stop-on-error type (the process is stopped when an error occurs) (step S12), the RPA scenario ends (step S13).

When the loop ends (step S5), the RPA flow ends (step S6).

(RPA robot execution definition)
A detailed definition in "RPA Robot Execution" is explained. The processing parts are combined to define the behavior of the robot. The RPA robot execution definition consists of (1) Layer 1 (L1): RPA flow definition, (2) Layer 2 (L2): Robot execution definition, (3) Layer 3 (L3): Internal implementation of screen operation processing. ing.

(1) Layer 1 (L1): RPA flow definition This is the aforementioned "RPA flow definition". It becomes a layer set by the RPA execution setter.

(2) Layer 2 (L2): Robot execution definition Detailed execution definition of the robot. It becomes a layer set by the RPA execution setter. Operation processing corresponding to screen items is prepared as parts, and robot behavior is defined by combining them. In a general RPA tool, components for various processes are prepared in addition to the screen operation process.

For example, the screen shot shooting process is a process that is incorporated when it is desired to take a screen shot at an arbitrary timing. Standby processing is processing that waits for time-consuming processing such as screen transition and registration processing. It is common to set the waiting time at the time of setting. The screen item value acquisition process is a process of acquiring what kind of value is input on the screen. The branching process is a process of branching the behavior of the robot based on conditions such as screen item values. Loop processing is processing that is used when repeated input is required, such as for detailed items.

(3) Layer 3 (L3): Internal implementation of screen operation processing This is the internal implementation of the “screen operation processing component” incorporated in the robot execution definition. This is a layer that RPA execution setters are unaware of. By incorporating common processing into this layer, it is possible to simplify RPA settings and make them highly functional.

FIG. 7 shows (1) Layer 1 (L1): RPA flow definition, (2) Layer 2 (L2): Robot execution definition, (3) Layer 3 (L3): An example of the processing flow for internal implementation of screen operation processing. It is a figure which shows.

In FIG. 7, L1: In the RPA flow definition, when the RPA flow is started (step S21), a series of pre-processing is executed (step S22), the RPA robot is executed (step S23), and a series of post-processing is executed. After that (step S24), the RPA flow ends (step S25).

L2: In the robot execution definition, when RPA robot execution is started (step S31), for example, a text box is entered (step S32), a check box is entered (step S33), a radio button is entered (step S34), and a series of The process is executed (step S35), the registration button is pressed (step S36), and the RPA robot execution is terminated (step S37).

L3: In the internal implementation of the screen operation process, when the operation process is started (step S41), the item to be operated is specified (step S42). For example, the operation target item is specified based on the ID and coordinates. If the identification of the operation target item fails (step S44), that is, if the operation target item does not exist, an error occurs and the "RPA robot execution" is immediately interrupted.

If the operation target item is successfully identified (step S43), input data is acquired (step S45). Specifically, the data to be input to the target item is obtained from the data read by "Read RPA data source".

If the acquisition of the input data fails (step S47), the "RPA robot execution" is immediately interrupted as an error.

If the acquisition of the input data succeeds (step S46), a series of pre-processing is executed (step S48), an operation process is executed (step S49), a series of post-processing is executed (step S50), and an execution log is output and stored in the log table 106b (step S51), and the operation process is terminated (step S52).

(execution log)
As an execution log, it is assumed that there are three stages of logs: a summary log, a detailed log, and a detailed log.
A summary log is a log created for each RPA flow execution instruction. A detailed log is a log output for each processing unit (L1: each step unit in the RPA flow definition) in one execution of the RPA flow. The detailed log is a log output for each processing unit (L2: each step unit of the RPA robot execution definition) in the RPA robot execution definition. Successful execution results and error data may be included.

FIG. 8 is a diagram showing an example of a summary log. The summary log may include data of SEQ, log level indicating success or failure of execution result, execution definition name, execution start date and time, execution end date and time, execution ID, and execution type CD.

FIG. 9 is a diagram showing an example of a detailed log. The detailed log may include data such as execution ID, SEQ, log level, execution content, execution robot name, operation target application name, loop SEQ, execution start date and time, and execution end date and time.

FIG. 10 is a diagram showing an example of a detailed log. The detailed log may include execution ID, detailed SEQ, SEQ, log level, execution content, operation target item name, input information, and execution date and time data.

FIG. 11 is a diagram showing an example of a screen shot log. The screen shot log may include execution ID, detailed SEQ, detailed SEQ, and screen data.

(3-2. Implementation and processing of log recording unit)
12A and 12B, implementation of log processing (definition that defines automatic operation of the log recording unit 102a1) will be described. The log recording unit 102a1 divides the execution log into a summary log including date and time, log level, processing target, and key information, a detailed log including date and time, log level, processing details, and key information, a date and time, log level, operation details, A detailed log including key information is recorded in the log table 106b in a hierarchical structure. The log recording unit 102a1 may record the detailed log and/or the detailed log in separate tables if the type and/or the number of columns are different.

12A and 12B are diagrams for explaining implementation of log processing. 12A and 12B are diagrams for explaining an example in which log processing is implemented in FIGS. 6 and 7. FIG.

Detailed log output and summary log output are implemented in the execution definition (L2) of the robot, and detailed log output is implemented in the internal implementation (L3) of screen operation processing. Detail log output processing exists in common within the processing on the RPA flow definition.

12A and 12B, each time the RPA flow is started, read processing, and loop start processing is executed, a detailed log is output and stored in the log table 106b (T1 to T3), and the RPA robot in the first loop In execution (A), a detailed log of each processing content (RAP robot execution start, text box input, check box input, radio button input, ..., registration button pressed, RPA robot execution end) is output, and the log table 106b (T10), and at the end of the RPA robot execution (A) in the first loop, a detailed log is output and stored in the log table 106b (T4).

Similarly, in the RPA robot execution (B) of the first loop, a detailed log of each processing content is output and stored in the log table 106b, and when the RPA robot execution (B) of the first loop ends, the detailed log is output. and store it in the log table 106b (T5). Execute this in a loop. Subsequently, a detailed log of the loop termination process is output and stored in the log table 106b (T7), and a detailed log of the RPA flow termination process is output and stored in the log table 106b (T8). Finally, a summary log is output and stored in the log table 106b (T9).

The common variable part of L2 generates an execution ID "XXXX-XXXX" and a detailed log SEQ "1" at the start of detailed log output, counts up the detailed log SEQ for each detailed log output, and starts a loop. At times, a loop SEQ "1" is issued and the loop SEQ is counted up for each loop. Also, at the start of RPA robot execution, issue a detailed log SEQ "1", count up the detailed log SEQ for each RPA robot execution process (for example, text box input, check box input, radio button input), Reset at the end of RPA robot execution. When the execution of the next RPA robot is started, the detailed log SEQ is similarly counted.

(Specific example 1)
A specific example 1 of the processing of the log recording unit 102a1 and the viewer unit 102a2 will be described with reference to FIGS. 13 and 14. FIG. The log recording unit 102a1 stores an execution log as a summary log including date/time, log level, processing target, and summary key information, a detailed log including date/time, log level, processing content, and detailed key information, and a date/time, log level, and operation log. A detailed log including contents and detailed key information is recorded in the log table 106b in a hierarchical structure. The viewer unit 102a2 displays a viewer screen on the monitor 114 and hierarchically displays the execution logs recorded in the hierarchical structure in the log table 106b. Specifically, the hierarchical display may be display by drilling down. For example, on the viewer screen, the summary key information and the detail key information are used to drill down from the summary log to the detail log, and from the detail log to the detail log using the detail key information and the detail key information.

FIG. 13 is a diagram showing examples of summary logs, detailed logs, and detailed logs stored in the log table 106b. A summary log, a detailed log, and a detailed log are hierarchically divided and stored on the log table 106b, and at that time, key information for linking each is generated and added to the summary log, the detailed log, and the detailed log. By doing so, the structure is structured so that the summary log, detailed log, and detailed log can be drilled down hierarchically and browsed. Note that the key information is not limited to the following example, and may be any information as long as it can be associated with the summary log, detailed log, and detailed log. As will be described later, detailed logs and detailed logs may be individually managed by preparing dedicated log tables suitable for their operations.

In FIG. 13, the summary log includes date and time, log level, processing target, and summary key information (parent key). As for the log level, Error indicates failure, and other information such as Info indicates success. In the example shown in FIG. 13, the first line contains the date and time "2020/3/6 16:41", the log level "Error", the processing target "order receipt/shipment RPA", and the summary key information (parent key) "A001". It's becoming

The detailed log includes date and time, log level, processing content, and detailed key information (child key). The child key of the detail key information may be associated with the parent key as, for example, parent key+SEQ number. In the example shown in the figure, the first line contains the date and time "2020/3/6 16:41", log level "info", processing content "order receiving system start", detail key information (child key "A001_001"), 3 The line is date and time "2020/3/6 16:44", log level "Error", processing content "start shipping system", and detail key information (child key "A001_002").

The detailed log includes date and time, log level, operation details, and detailed key information (grandchild key). Detailed key information (grandchild key) may be child key + SEQ number. In the example shown in the figure, the first line contains the date and time "2020/3/6 16:41", log level "info", operation content "number of orders received = 10", detailed key information (grandchild key "A001_001_001"), The third line contains the date and time "2020/3/6 16:45", the log level "info", the operation content "input "2020/3/6" on the shipping date", and the detailed key information (grandchild key "A001_002_001"). It's becoming

The fourth line is the date and time "2020/3/6 16:46", the log level "info", the operation content "input "10" for the number of shipments", the detailed key information (grandchild key "A001_002_002"), and the fifth line is , date and time “2020/3/6 16:47”, log level “Error”, operation content “error display: insufficient inventory” input”, detailed key information (grandchild key “A001_002_003”).

FIG. 14 is a diagram showing a display example of the viewer screen. In FIG. 14, the data in FIG. 13 are partially omitted for the sake of simplicity of explanation. The viewer unit 102a2 is configured so that the summary log, detailed log, and detailed log stored in the log table 106b can be viewed by hierarchically drilling down based on key information. By drilling down from the summary log for each processing unit to the detailed log as needed, it is possible to efficiently grasp the overall results and perform analysis for problem investigation.

In FIG. 14, the viewer unit 102a2 reads the summary log of the log table 106b and displays the screen of the summary log viewer (FIG. 14A). In the summary log viewer, you can narrow down the display target by selecting the date and time and log level with filters. When a line to be viewed is selected on the summary log viewer, the detailed log having child keys including the parent key of the selected line is displayed on the detailed log viewer (FIG. 14(B)). Subsequently, when a line is selected in the detailed log view, a detailed log having grandchild keys including child keys of the selected line is displayed in the detailed log viewer (FIG. 14(C)).

In the example shown in FIG. 14, in the summary log viewer, for example, the first line with an error (date and time "2020/3/6 16:41", log level "Error", processing target "order receipt/shipment RPA", key When the information (parent key) "A001") is selected, a detailed log (date and time "2020/3/6 16: 41", log level "info", processing content "start order reception system", key information (child key "A001_001"), date and time on the second line "2020/3/6 16:44", log level "Error", The processing content "shipping system activation" and key information (child key "A001_002") are displayed in the detail log viewer (FIG. 14(B)).

In the detailed log viewer, for example, if you select the second line that is in error, the detailed log that has the grandchild key including the child key "A001_002" of the selected second line (the date and time of the first line "2020/3/6 16: 45", log level "info", operation content "input "2020/3/6" in shipping date", key information (grandchild key "A001_002_001"), date and time in the second line "2020/3/6 16:46" ', log level 'info', operation content 'enter '10' in number of shipments', key information (grandchild key 'A001_002_002)', date and time of 3rd line '2020/3/6 16:47', log level 'Error' , operation content "error display: inventory quantity is insufficient", and key information (child key "A001_002_003")) are displayed in the detailed log viewer (FIG. 14(C)).

In this way, it is possible to efficiently display the log necessary for identifying the cause of the error.

(Specific example 2)
A specific example 2 of the processing of the log recording unit 102a1 and the viewer unit 102a2 will be described with reference to FIGS. 15 to 20. FIG. The log recording unit 102a1 may record the detailed log and/or the detailed log in separate tables if the type and/or the number of columns are different.

In the log table 106b, it is possible to separately manage tables of detailed logs and detailed logs with different types, numbers of columns, processing targets, and the like. By preparing a log table in a format suitable for each process, it is possible to efficiently manage only the minimum necessary information. Here, a case will be described where detailed logs with different numbers of columns are separately managed.

FIG. 15 is a diagram showing an example of a summary log. The summary log may include data of SEQ, log level, execution definition name, execution start date/time, execution end date/time, execution ID, and execution type CD. In the example shown in FIG. 15, the first line contains SEQ "1", log level "Info", execution definition name "Order RPA flow", execution start date and time "2020/1/3 9:40:00", execution end Date and time "2020/1/3 9:45:00", execution ID "A000001", execution type CD "AAA", the fourth line is SEQ "4", log level "Info", execution definition name "Order RPA flow , execution start date and time “2020/1/3 9:47:00”, execution end date and time “2020/1/3 9:51:00”, execution ID “B000001”, and execution type CD “BBB”. . The execution ID becomes summary key information. The execution type CD is a CD indicating the execution type, and detailed logs can be divided by the execution type CD. In this example, a detailed log A corresponding to the execution type CD "AAA" and a detailed log B corresponding to the execution type CD "BBB" are created.

FIG. 16 is a diagram showing an example of detailed log A. As shown in FIG. The detailed log A may include execution ID, SEQ, log level, execution content, execution robot name, operation target application name, loop SEQ, execution start date and time, execution end date and time, and XXX data. The execution ID and SEQ are detailed key information.

FIG. 17 is a diagram showing an example of a detailed log B. FIG. The detailed log B may include execution ID, SEQ, log level, execution content, execution robot name, operation target URL, loop SEQ, execution start date and time, execution end date and time, YYY, and ZZZ data. The execution ID and SEQ are detailed key information.

FIG. 18 is a diagram showing an example of a detailed log. The detailed log may include execution ID, detailed SEQ, SEQ, log level, execution content, operation target item name, input information, and execution date and time data. Execution ID, detail SEQ, and SEQ are detailed key information. FIG. 19 is a diagram showing an example of a screen shot.

In the examples of FIGS. 15 to 19, the viewer unit 102a2 reads the summary log of FIG. 15 and displays the screen of the summary log viewer. Then, in the summary log viewer, for example, the third line (SEQ "3", log level "Error", execution definition name "Journal RPA flow", ..., execution ID "A000003", execution type CD "AAA") is selected, the viewer unit 102a2 reads the record of the selected execution ID "A000003" from the detail log A and displays it on the detail log A viewer. When a line is selected in the detailed log A viewer, the viewer unit 102a2 reads the execution ID and SEQ record of the selected line from the detailed log A and displays them on the detailed log viewer.

The viewer unit 102a2 is a summary log viewer, for example, the fifth line (SEQ "5", log level "Error", execution definition name "Journal RPA flow", ..., execution ID "B000002", execution type CD "BBB") is selected, the viewer unit 102a2 reads the record of the selected execution ID "B000002" from the detailed log B and displays it on the detailed log B viewer. When a line is selected on the detail log B viewer, the viewer unit 102a2 reads the record of the execution ID and SEQ of the selected line from the detailed log and displays it on the detailed log viewer.

FIG. 20 is a diagram for explaining an example of a viewer. In FIG. 20, display of key information and the like is omitted for simplicity of explanation. In the following description, it is assumed that the log table 106b stores data of a summary log, a detailed log, and a detailed log for displaying the viewer shown in FIG.

For summary log "RPA for application" and execution method CD "1", prepare a table of business application operation RPA details log, and for summary log "RPA for Web" and execution method CD "2", browser operation RPA details Prepare a log table, divide it into tables with a structure suitable for each necessary information, and save it. The business application operation RPA detail log and the browser operation RPA detail log have different column information structures, and the column information is switched according to the table structure.

In FIG. 20A, when the log level "Error", "RPA for application", execution method CD "1" on the first line is selected in the summary log viewer, the object is selected from the RPA detailed log for business application. , and displays a viewer of the business application operation RPA detail log as shown in FIG. 20(B). When a line is selected on the business application operation RPA detail log viewer, the target record is read from the detailed log and displayed on the detailed log viewer (FIG. 20(D)).

Also, in FIG. 20A, when the log level "Info", "RPA for Web application", execution method CD "2" on the third line is selected in the summary log viewer, the browser operation RPA detailed log is displayed. , and displays the RPA detailed log viewer for browser operation as shown in FIG. 20(C). When a row is selected in the browser operation RPA detail log viewer, the target record is read out from the detailed log and displayed in the detailed log viewer (FIG. 20(D)).

For the detailed log, although the logs extracted and displayed by the two patterns of calling are different, the same log viewer screen and table can be used.

(Specific example 3)
A specific example 3 of the processing of the log deletion unit 102a3 will be described with reference to FIGS. 21 to 27. FIG. The log deletion unit 102a3 deletes the log specified on the log deletion screen from the log table 106b according to the log policy that sets the retention period (the period during which the log cannot be deleted) if it can be deleted or deleted for each log granularity. The log deletion unit 102a3 controls display and data acceptance of the log policy setting screen and the log deletion screen.

More specifically, the log deletion unit 102a3 displays a log policy setting screen on the monitor 114 according to the operator's operation, and according to the operator's operation on the log policy setting screen, log granularity (summary log, A log policy is set for each item (detailed log, detailed log) and whether or not it can be deleted and how long it is retained if it can be deleted, and registered in the log policy file 106c. In addition, the log deletion unit 102a3 displays a log deletion screen on the monitor 114 according to the operator's operation, and according to the log policy of the log policy file 106c, according to the operator's operation on the log deletion screen, deletes the specified log. is deleted from the log table 106b.

FIG. 21 is a diagram showing a display example of a log policy setting screen. On the log policy setting screen, it is possible to set a log policy that indicates whether or not deletion is possible for each log granularity and how long the log should be retained if deletion is possible.

In the example of the log policy setting screen shown in FIG. 21, each of the summary log, detail log, and detailed log has check boxes (checked: can be deleted, unchecked: cannot be deleted) and storage periods. It has a field for specification and a save button for saving the log policy set on the log policy setting screen. On the log policy setting screen, the log policy can be arbitrarily set according to the system user's audit requirements.

In the example shown in FIG. 21, the summary log cannot be deleted, the detail log can be deleted and the storage period is "4 months", and the detailed log can be deleted and the storage period is "2 months".

FIG. 22 is a diagram showing a display example of a log deletion screen. FIG. 23 is a diagram for explaining how to select a log to be deleted on the log deletion screen. FIG. 24 is a diagram showing another display example of the log deletion screen.

On the log deletion screen shown in FIG. 22, logs can be selectively deleted according to log granularity. The log deletion screen shown in FIG. 22 includes an extraction condition specification area for specifying log extraction conditions, and logs corresponding to the specified extraction conditions (summary log (see FIG. 15), detail log (see FIGS. 16 and 17). , a delete area for displaying the number of detailed logs (see FIG. 18) and specifying a log to be deleted, and a delete button for executing deletion of the specified log.

In the extraction condition specification area, specify the range of data to be displayed by execution year and month.

The deletion area displays the year and month of execution, deletion check boxes and the number of summary logs, detailed logs, and detailed logs. With reference to the log table 106b, the numbers of summary logs, detailed logs, and detailed logs are totaled and displayed for each execution year and month for the period of execution year and month designated in the extraction condition designation area. From the displayed data, the log to be deleted can be selected by checking the delete check box.

As shown in FIG. 23A, if there are logs corresponding to children of the selected location, they can be selected together. This is to ensure that child logs do not remain without associated parent logs. For example, when the deletion check box for the detailed log number "125" is checked for the execution year and month "2021/07", the deletion check box for the detailed log number "6250" corresponding to the child of this detailed log is automatically checked.

As shown in FIG. 23(B), when the child log is unchecked for the same reason, the parent log is also unchecked. For example, if you uncheck the delete check box for the detailed log number "6250" for the execution year and month "2021/07", the delete check box for the detailed log number "125" that is the parent of this detailed log is automatically unchecked. .

Also, on the log deletion screen shown in FIG. 22, the log that is set to be non-deletable in the log policy and the log that is set to be deletable but is still in storage cannot be deleted. When the deletion check box is checked for the log to be deleted and the delete button is pressed, the log to be deleted is deleted from the log table 106b.

In the example shown in FIG. 22, the execution year and month "2021/04 to 2021/12" are specified in the extraction condition specification area, and the summary log of each month of the execution year and month "2021/04 to 2021/12", The number of detailed logs and the number of detailed logs are displayed. The current month is 2021/12. In the example of the log policy setting screen shown in FIG. 21, the summary log cannot be deleted, the detailed log cannot be deleted for the current month and the storage period is "4 months", and the detailed log cannot be deleted for the current month and the storage period is "2 months". For example, logs that cannot be deleted may be identified with different colors.

On the log deletion screen of FIG. 22, when the deletion check box of the log to be deleted is checked and the execution button is pressed, the log to be deleted is deleted from the log table 106b and shown in FIG. The screen is updated as shown.

In the above description, an example in which the execution log is composed of a summary log, a detailed log, and a detailed log has been described, but the present invention is not limited to this, and logs can be managed with other types or different granularities. can be FIG. 25 is a diagram showing another configuration example of the execution log. FIG. 25 shows a parent-child relationship image of logs (upper is parent, lower is child). It consists of an acceptance file log and a screen shot log that is a child of the detail log.

The screen shot log is a log of shots of screens targeted for RPA operation (see FIG. 19). The acceptance file log is a log that saves file information that describes the input values to the operation target screen accepted when executing RPA (in FIG. 12A, the log of the file read by reading the RPA data source ).

The parent-child relationship between the four different types of logs is determined by which layer the process for saving the log belongs to. Logs with the same granularity as the layer that stores the logs will be the parent. Since the recording process of the received file log is the process of the L2 layer (the process associated with the detailed log output process T2 in FIG. 12A), the parent is the detailed log. Since the process of recording the screen shot log is the process of the L3 layer (the process associated with the detailed log output process T10 in FIG. 12A), the parent is the detailed log.

26 and 27 are diagrams showing display examples of the log policy setting screen and the log deletion screen when the execution log is composed of a summary log, a detailed log, a detailed log, an acceptance file log, and a screen shot log. .

In the example of the log policy setting screen shown in Fig. 26, the summary log cannot be deleted, the detailed log can be deleted and the storage period is "4 months", the acceptance file log can be deleted and the storage period is "2 months", and the detailed log can be deleted. The storage period is set to "2 months", and the screen shot log can be deleted and the storage period is set to "1 month". In this case, in the example of the log deletion screen shown in FIG. 27, the summary log cannot be deleted, the detailed log is the current month and the storage period is "4 months", the received file log is the current month and the storage period is "2 months", and the detailed log is the current month. and the storage period is "2 months", and the screen shot log is controlled so that it cannot be deleted during the current month and the storage period is "1 month".

[4. Modification]
(Modification 1)
In the log viewer described above, logs are hierarchically displayed by drilling down, but the present invention is not limited to this, and the viewer unit 102a2 displays logs in a tree format within one screen, for example. Thus, hierarchical display may be performed. FIG. 28 is a diagram illustrating a display example of the log viewer of Modification 1. FIG. In the summary log viewer shown in FIG. 28, when a desired line of the summary log is selected by moving the mouse cursor, for example, a pop-up of the record of the detailed log corresponding to the selected line is displayed, and the desired line of the detailed log is displayed. When the mouse cursor is placed on and selected, a pop-up of the detailed log record corresponding to the selected line is displayed (not shown), thereby hierarchically displaying the log in a tree format.

(Modification 2)
Although the RPA log has been described above, the present invention is not limited to this. Logs other than RPA may also be hierarchically stored in a table, and the stored logs may be hierarchically displayed. For example, similar to RPA, it can be applied to a system that combines tasks to define a flow.

Logs of general applications may also be hierarchized and saved, and the saved logs may be hierarchized and displayed.

For example, the log recording unit 102a1 may hierarchize and store a log of processing from user login to logout, and the viewer unit 102a2 may hierarchize and display the stored log on the viewer screen. This makes it possible to easily check the series of processes from user login to logout.

29 to 32 are diagrams for explaining a case where a log of processing from user login to logout is saved and confirmed by preview. FIG. 29 shows a display example of the viewer screen. When a user logs in, starts an application job, and performs various operations, for example, a summary log, a detailed log, and a detailed log as shown in FIGS. 30 to 32 are created and stored in the log table. 22 is displayed based on the saved log in the log table.

FIG. 29 shows a display example of the viewer screen. FIG. 30 is a diagram showing an example of a summary log (login information log). The summary log shown in the figure may include data such as SEQ, user, date and time, content, login GUID, and the like. A login GUID is a unique ID issued when a user logs in, and serves as summary key information.

FIG. 31 is a diagram showing an example of a detailed log. The detailed log example shown in the figure may include data such as login GUID, SEQ, log level, date and time, operation, job name, and the like. The login GUID and SEQ are detailed key information.

FIG. 32 is a diagram showing an example of a detailed log. The example of the detailed log shown in the figure may include data such as login GUID, detailed SEQ, SEQ, log level, date and time, contents, and operation. The login GUID, detailed SEQ, and SEQ are detailed key information.

For example, in FIG. 29, when the record of the user "XXX" on the first line of the summary log is selected on the viewer screen, the record containing the login GUID "XXXX..." is read from the detailed log, Job start and operation record data are displayed as a processing sequence. In the processing sequence, for example, when "execute printing" of the operation record is selected, a record including the login GUID "XXXX..." and SEQ "12" of the record of "executing printing" of the operation record is retrieved from the detailed log. Read out and display data such as No, date and time, content, and operation as a detailed review. In this way, the logs are hierarchically displayed.

As described above, according to the present embodiment, the log recording unit 102a1 records the execution log of one or more processing targets in a hierarchical structure for each granularity, and the viewer screen is displayed on the monitor 114 to display the hierarchical structure. and a viewer unit 102a2 that hierarchically displays the execution log recorded in a structure, so that it is possible to reduce the cost of analyzing the cause of error and operation record for the processing target using the execution log. Become.

[5. Contribution to the Sustainable Development Goals (SDGs) led by the United Nations]
Since this embodiment can contribute to improving operational efficiency and promoting appropriate management decisions of companies, it is possible to contribute to Goals 8 and 9 of the SDGs.

In addition, the present embodiment can contribute to the reduction of disposal loss and the promotion of paperless and computerization.

In addition, since this embodiment can contribute to strengthening control and governance, it is possible to contribute to Goal 16 of the SDGs.

[6. Other embodiments]
The present invention may be implemented in various different embodiments other than the embodiments described above within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all of the processes described as being manually performed Alternatively, some can be done automatically by known methods.

In addition, unless otherwise specified, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed arbitrarily.

Also, with respect to the information processing apparatus 100, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, the processing functions of the information processing apparatus 100, particularly the processing functions performed by the control unit 102, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing apparatus to execute the processing described in this embodiment, and the information processing apparatus as necessary. 100 mechanically read. That is, the storage unit 106 such as ROM or HDD (Hard Disk Drive) stores computer programs for giving commands to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM, and constitutes the control section 102 in cooperation with the CPU.

Further, this computer program may be stored in an application program server connected to the information processing apparatus 100 via any network, and all or part of it can be downloaded as necessary. be.

Also, the program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" means memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Disc (Registered trademark) such as Blu- shall include any "portable physical medium".

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single configuration, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, the installation procedure after reading, and the like.

The various databases and the like stored in the storage unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks. programs, tables, databases, and files for web pages.

Further, the information processing apparatus 100 may be configured as an information processing apparatus such as a known personal computer or workstation, or may be configured as the information processing apparatus to which arbitrary peripheral devices are connected. Further, the information processing apparatus 100 may be implemented by installing software (including programs, data, etc.) that causes the information processing apparatus to implement the processing described in the present embodiment.

Furthermore, the specific form of distribution and integration of the device is not limited to the one shown in the figure, and all or part of it can be functionally or physically arranged in arbitrary units according to various additions or functional additions. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be implemented selectively.

100 Information processing device 102 Control unit 102a Automatic operation unit (RPA system)
102a1 Log recording unit 102a2 Viewer unit 102a3 Log deletion unit 102b Application 104 Communication interface unit 106 Storage unit 106a Definition file 106b Log table 106c Log policy file 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (10)

An information processing device comprising a control unit,
The control unit
log recording means for recording execution logs of one or more processing targets in a hierarchical structure for each granularity;
viewer means for displaying a viewer screen on the display unit and hierarchically displaying the execution log recorded in the hierarchical structure;
An information processing device comprising: 2. The information processing apparatus according to claim 1, wherein said hierarchical display includes a drill-down display or a tree structure display. The log recording means stores the execution log as a summary log including date and time, log level indicating normal or error, processing target, and summary key information, and a detailed log including date and time, log level, processing details, and detailed key information; Record date and time, log level, operation details, and detailed logs including detailed key information in each table in a hierarchical structure,
The viewer means, on the viewer screen, uses the summary key information and the detail key information to convert the summary log to the detail log, uses the detail key information and the detail key information, and converts the detail log to 3. The information processing apparatus according to claim 2, wherein the detailed log is displayed in a drill-down or tree structure. When the detailed log differs in type and/or number of columns, the log recording means adds a different execution type code to the summary log, and records a separate table for each different execution type code. The information processing apparatus according to claim 3, wherein: 5. The information processing apparatus according to claim 1, wherein the execution log includes an RPA (Robotic Process Automation) execution log. The detailed log includes execution robot information, operation target information, and loop count information recorded according to the RPA flow definition, and the detailed log includes operation target item information and input information recorded according to the automatic operation command. 6. The information processing apparatus according to claim 5, characterized by: 5. The information processing apparatus according to any one of claims 1 to 4, wherein the execution log includes a log of processing from login to logout of the user for the processing target. The control unit further includes log deletion means for deleting logs specified on a log deletion screen displayed on the display unit in accordance with a log policy that sets whether deletion is possible for each log granularity and, if deletion is possible, the retention period. The information processing apparatus according to any one of claims 1 to 7, characterized by comprising: An information processing method executed by an information processing device having a control unit,
executed by the control unit;
a log recording step of recording one or more processing target execution logs in a hierarchical structure for each granularity;
a viewer step for displaying a viewer screen on the display unit and hierarchically displaying the execution log recorded in the hierarchical structure;
An information processing method comprising: An information processing program to be executed by an information processing apparatus having a control unit,
In the control unit,
a log recording step of recording one or more processing target execution logs in a hierarchical structure for each granularity;
a viewer step for displaying a viewer screen on the display unit and hierarchically displaying the execution log recorded in the hierarchical structure;
Information processing program for executing

Images