JP2019133308A - Electronic apparatus and log acquisition system - Google Patents

Abstract

To provide an electronic apparatus and a log acquisition system that can facilitate analysis of a cause of a failure.SOLUTION: MFP comprises a storage part managing failure factor candidate information indicating at least one candidate of a failure factor for each failure occurring in MFP, log recording setting means executing a setting whether a log of a candidate of a failure factor is recorded or not for each candidate of a failure factor, and hardware control means and function realization means recording a log according to the setting executed by the log recording setting means, the log recording setting means executes a setting to record a candidate of a failure factor that is associated with the occurred failure by the failure factor candidate information automatically when a failure has occurred (S502).SELECTED DRAWING: Figure 22

Description

  The present invention relates to an electronic device and a log acquisition system that acquire logs.

  2. Description of the Related Art Conventionally, as an electronic device that acquires a log, an apparatus including hardware including an operation unit and a control program that controls the hardware is known (for example, see Patent Document 1). The apparatus described in Patent Literature 1 includes operation information for an operation unit, communication information between processes in a control program, a control command from the control program to hardware, and status notification information from the hardware to the control program. Then, the generation time of each information is added and acquired as a log.

  Therefore, the apparatus described in Patent Document 1 can analyze the cause of the malfunction by using a log when the malfunction occurs. In particular, the device described in Patent Document 1 is not only for communication information between processes in a control program, a control command from the control program to hardware, and status notification information from the hardware to the control program, but also for an operation unit. Since the operation information is also included in the log, it is possible to distinguish whether the cause of the failure is due to a user's operation error.

JP 2002-207399 A

  In the device described in Patent Document 1, since detailed information processed by software inside the device is included in the log, problems caused by a person with a high technical level such as a developer of the device may be caused. Appropriate support can be provided by logs for detailed analysis of the cause. However, in the apparatus described in Patent Document 1, since a log required for detailed analysis of the cause of the failure needs to be identified from a large number of logs by the analyst of the cause of the failure, the cause of the failure There is a problem that the burden on the analyst is large.

  SUMMARY An advantage of some aspects of the invention is that it provides an electronic device and a log acquisition system that can facilitate the analysis of the cause of a failure.

  The electronic device according to the present invention includes: information management means for managing failure factor candidate information indicating at least one candidate for the failure for each failure occurring in the electronic device; and whether to record the candidate log A log recording setting unit configured to execute the setting for each candidate; and a log recording unit configured to record the log in accordance with the setting performed by the log recording setting unit. When the error occurs, the setting for recording the log of the candidate associated with the error that has occurred in the defect factor candidate information is automatically executed.

  With this configuration, when a failure occurs, the electronic device of the present invention automatically executes a setting for recording a log of failure factor candidates associated with the failure in the failure factor candidate information. Therefore, it is possible to suppress the recording of logs unnecessary for the analysis of the cause of the failure, and as a result, the analysis of the cause of the failure can be facilitated. In addition, when a failure occurs, the electronic device of the present invention automatically executes a setting for recording a failure factor candidate log that is associated with the failure in the failure factor candidate information. Therefore, it is not necessary for the user to perform a setting for recording a log of candidate fault factors that have occurred, and the cause of the fault can be easily analyzed.

  The electronic apparatus of the present invention may include an instruction receiving device that receives an instruction, and the log recording setting unit may execute the setting according to the instruction received by the instruction receiving device.

  With this configuration, the electronic device according to the present invention executes the setting of whether or not to record the log of the cause of the failure according to the instruction received by the instruction receiving device. When the analysis of the cause of the above is completed, the setting for not recording unnecessary logs is executed by the user, so that the free space in the storage area necessary for storing the logs can be suppressed.

  The electronic apparatus of the present invention may include a display device, and the log recording setting unit may display the setting on the display device.

  With this configuration, the electronic device of the present invention displays a setting on whether or not to record a log of candidate failure factors on the display device, so that the user can confirm the automatically executed setting, which is convenient. Can be improved.

  In the electronic device of the present invention, the electronic device executes a function in response to an input by a user, and the electronic device displays the content of the input and the execution result of the function as an execution unit of the function. You may provide the function log acquisition means which acquires the function log included for every.

  With this configuration, the electronic device of the present invention acquires a function log including the content of the input by the user and the execution result of the function according to the input by the user for each function execution unit. The function log can facilitate understanding of how the function is executed as a result of executing such an input. Therefore, the electronic device of the present invention allows the analyst of the failure to analyze the rough cause of the failure in the function log before causing the analyst of the failure to analyze the detailed cause of the failure using the candidate log of the failure. Therefore, convenience can be improved.

  The log acquisition system according to the present invention includes information management means for managing failure factor candidate information indicating at least one candidate for the failure for each failure occurring in an electronic device, and whether to record the candidate log. A log recording setting unit configured to execute the setting for each candidate; and a log recording unit configured to record the log in accordance with the setting performed by the log recording setting unit. When the error occurs, the setting for recording the log of the candidate associated with the error that has occurred in the defect factor candidate information is automatically executed.

  With this configuration, when a failure occurs in the electronic device, the log acquisition system of the present invention is configured to record a defect factor candidate log associated with the failure that occurred in the failure factor candidate information. Is automatically executed, it is possible to suppress the recording of logs unnecessary for the analysis of the cause of the failure, and as a result, the analysis of the cause of the failure can be facilitated. Also, the log acquisition system of the present invention automatically sets a setting for recording a log of defect factor candidates that is associated with the defect in the defect factor candidate information when a defect occurs in the electronic device. Therefore, it is not necessary for the user to execute a setting for recording a log of candidate fault factors that have occurred, and the cause of the fault can be easily analyzed.

  The electronic device and log acquisition system of the present invention can facilitate analysis of the cause of the failure.

It is a block diagram of the service execution system which concerns on one embodiment of this invention. FIG. 2 is a block diagram of the MFP shown in FIG. 1. It is a figure which shows an example of the log configuration table classified by factor shown in FIG. It is a figure which shows an example of the malfunction factor candidate information shown in FIG. It is a figure which shows an example of the log for markets shown in FIG. FIG. 2 is a block diagram of the cloud server shown in FIG. 1 when realized by one server computer. 3 is a flowchart of the operation of the MFP shown in FIG. 2 when acquiring one node execution unit log. It is a flowchart of the IN information acquisition process shown in FIG. It is a flowchart of the input content information acquisition process shown in FIG. It is a flowchart of the instruction | indication setting information acquisition process shown in FIG. It is a flowchart of the OUTPUT information acquisition process shown in FIG. 3 is a flowchart of the operation of the MFP shown in FIG. 2 when a node execution unit log related to the MFP itself is moved to a node other than the MFP itself. FIG. 7 is a flowchart of the operation of the cloud server shown in FIG. 6 when one node execution unit log is acquired. 14 is a flowchart of IN information acquisition processing shown in FIG. 13. It is a flowchart of the input content information acquisition process shown in FIG. It is a flowchart of the instruction | indication setting information acquisition process shown in FIG. It is a flowchart of the OUTPUT information acquisition process shown in FIG. 4 is a flowchart of the operation of the MFP shown in FIG. 2 when acquiring a service unit log. It is a flowchart of the own apparatus log collection process shown in FIG. 3 is an operation flowchart of the MFP shown in FIG. 1 when a node execution unit log request is received. FIG. 7 is an operation flowchart of the cloud server illustrated in FIG. 6 when a node execution unit log request is received. 3 is a flowchart of the operation of the MFP shown in FIG. 2 when a problem occurs. 3 is a flowchart of the operation of the MFP shown in FIG. 2 when editing a factor-specific log configuration table in accordance with an instruction from a user. 3 is a flowchart of the operation of the MFP shown in FIG. 2 when controlling hardware. 3 is a flowchart of the operation of the MFP shown in FIG. 2 when executing a function.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  First, the configuration of a service execution system according to an embodiment of the present invention will be described.

  FIG. 1 is a block diagram of a service execution system 10 according to the present embodiment.

  A service execution system 10 shown in FIG. 1 is a system in which a plurality of nodes cooperate to execute a service in response to an input by a user.

  The service execution system 10 includes an MFP (Multifunction Peripheral) 20 as an electronic device as a node. The MFP 20 belongs to a network 11 such as a LAN (Local Area Network). The service execution system 10 includes MFP 30 and MFP 40 belonging to the network 11 as nodes. The configurations of the MFP 30 and the MFP 40 are the same as those of the MFP 20, respectively. In addition to the MFP 30 and the MFP 40, the service execution system 10 may include an electronic device belonging to the network 11 as a node.

  The service execution system 10 includes an MFP 50 having the same configuration as the MFP 20 and a cloud server 60 that provides a cloud service, as nodes. The MFP 50 and the cloud server 60 do not belong to the network 11 but belong to the network 12 such as the Internet connected to the network 11. In addition to the MFP 50, the service execution system 10 may include an electronic device belonging to the network 12 as a node. In addition to the cloud server 60, the service execution system 10 may include a cloud server belonging to the network 12 as a node.

  The cloud server 60 may be realized by one computer or may be realized by a plurality of computers.

  In the service executed by the service execution system 10, when the cloud service provided by the cloud server 60 is a storage service, for example, image data of an image read from a document by a scanner described later of the MFP 20 is sent to the cloud server 60. The MFP 20 will be described later based on image data stored in the cloud server 60 in accordance with an instruction to the cloud server 60 by a user via a service to be stored and a GUI (Graphical User Interface) provided by the cloud server 60. MF based on image data stored in the cloud server 60 in response to a service for executing printing by the printer and an instruction to the MFP 20 by a user via an operation unit (to be described later) of the MFP 20. There is a service that executes printing by a P20 printer.

  FIG. 2 is a block diagram of the MFP 20.

  An MFP 20 shown in FIG. 2 includes an operation unit 21 that is an input device such as buttons for inputting various operations, a display unit 22 that is a display device such as an LCD (Liquid Crystal Display) that displays various types of information, and a sheet. Fax communication via a printer 23 which is a printing device for printing an image on a recording medium such as a scanner 24, a scanner 24 which is a reading device for reading an image from a document, an external facsimile apparatus (not shown) and a communication line such as a public telephone line A fax communication unit 25 that is a fax device that performs communication, and a communication unit 26 that is a communication device that communicates with an external device via a network such as a LAN or the Internet, or directly by wire or wireless without going through the network. , Semiconductor memory to store various information, H A storage unit 27 that is a nonvolatile storage device such as a DD (Hard Disk Drive) and a control unit 28 that controls the entire MFP 20 are provided.

  The functions executed by the MFP 20 include, for example, a print function for printing an image based on print data input via the communication unit 26 on a recording medium by the printer 23, and an image read from an original by the scanner 24 to the printer. 23, a copy function for printing on a recording medium by the scanner 23, a transmission function for transmitting an image read from the document by the scanner 24 via the communication unit 26, and a fax transmission for an image read from the document by the scanner 24 via the fax communication unit 25. Various functions such as a FAX function to store, an image read from an original by the scanner 24 or an image based on print data input via the communication unit 26 in the storage unit 27, and a log of the MFP 20 Printing information on a recording medium by the printer 23 Port function and, and a Web information reference-setting function is present or perform the setting to the outside of the computer or the information in MFP20 from MFP20. The MFP 20 executes a print function, a copy function, a transmission function, a FAX function, a BOX function, and a report function in units of jobs. However, the MFP 20 does not execute the Web information reference / setting function in units of jobs.

  Each of the operation unit 21 and the communication unit 26 is a device that receives an instruction, and configures an instruction receiving device.

  The storage unit 27 stores a log acquisition program 27a as an application program for acquiring a log. For example, the log acquisition program 27a may be installed in the MFP 20 at the manufacturing stage of the MFP 20, or may be additionally installed in the MFP 20 from an external storage medium such as a USB (Universal Serial Bus) memory, or on the network. To the MFP 20 may be additionally installed.

  The storage unit 27 stores the content of the user's input to the service execution system 10 (hereinafter referred to as “user input content”) and the execution result of the service by the service execution system 10 according to the user's input to the service execution system 10. (Hereinafter referred to as “service execution result”) can be stored as a market log 27b as a service log (function log) including each service (function) execution unit. An MFP service person who is a person on the MFP seller side corresponds to a customer, that is, an MFP user in the market. When the customer inputs an instruction for causing the service execution system to execute the service to the MFP via the operation unit or the communication unit of the MFP, or the cloud server provides an instruction for causing the service execution system to execute the service When the execution result of the service by the service execution system does not become the one desired by the customer when input from the GUI to the cloud server, such an operation of the service execution system that is not desired by the customer, that is, a problem The service person may be requested to explain the event. The market log 27b is a log acquired as information that allows a service person to accurately explain a problem event that has occurred in the service execution system 10 in response to a request from a customer.

  The storage unit 27 can store a development log 27c including a signal that the software transmits to the hardware in the MFP 20, a signal that is transmitted and received between the plurality of software in the MFP 20, and a signal that the software receives from the hardware in the MFP 20. It is. When a seller of an MFP receives a complaint from a customer, that is, an MFP user, about a problem event that has occurred in the MFP, the seller of the MFP reports the complaint received from the customer to the developer of the MFP. When a developer accepts a complaint from a customer via a seller, the developer needs to understand the internal behavior and state of the MFP when the problem event occurs in order to solve the problem event pointed out by the customer. . The development log 27c is acquired as information that enables the developer to accurately grasp the internal behavior and state of the MFP when the problem event occurs in order to solve the problem event that has occurred in the MFP 20. It is. The development log 27 c is difficult to be interpreted by the service person of the MFP 20.

  The storage unit 27 stores a factor-by-factor log configuration table 27d that indicates, for each defect factor candidate, whether or not to log a defect factor candidate log that occurs in the MFP 20.

  FIG. 3 is a diagram illustrating an example of the log configuration table 27d for each factor.

  As illustrated in FIG. 3, the factor-specific log configuration table 27 d is a log as a setting for whether or not to record a failure factor candidate identifier, a failure factor candidate, and a failure factor candidate log. A combination with the record execution setting is shown for each candidate for the cause of the failure. The cause of the failure includes a hardware factor included in the MFP 20 and a software factor included in the MFP 20. Hardware factors include, for example, “HDD” that is part of the storage unit 27 (see FIG. 2), “SD card” that is part of the storage unit 27, and the MFP 20 (see FIG. 2). There are a “power supply device” for supplying power, a “paper feed cassette device” which is a part of the printer 23 (see FIG. 2), and a “scanner” indicating the scanner 24 (see FIG. 2). . Software factors include, for example, “device panel” as a display function by the display unit 22 (see FIG. 2) and “copy” as a function of printing an image read from a document by the scanner 24 on a recording medium by the printer 23. "Function", "print function" as a function for printing an image based on print data input from the communication unit 26 (see FIG. 2) on a recording medium by the printer 23, and an image read from the document by the scanner 24 "FAX function" as a function for transmitting a fax via the fax communication unit 25 (see FIG. 2), "authentication / authorization" as a function for executing authentication and authorization for a user, and energy saving in the MFP 20 "Energy saving" as a function to execute the operation of the And "Event Notification and transmission" as functions or to send or, there is a "box function" as function of storing data in the storage unit 27. There are many causes of defects other than those shown in FIG. For example, the cause of the failure includes an “image processing function” as a function for performing image processing on image data and a “network control function” as a function for performing control related to network communication via the communication unit 26. .

  As illustrated in FIG. 2, the storage unit 27 stores defect factor candidate information 27 e indicating at least one defect factor candidate for each defect occurring in the MFP 20. Therefore, the memory | storage part 27 comprises the information management means which manages the defect factor candidate information 27e.

  FIG. 4 is a diagram illustrating an example of the defect factor candidate information 27e.

  As illustrated in FIG. 4, the failure factor candidate information 27 e indicates a combination of a failure occurring in the MFP 20 and a failure factor candidate identifier for each failure. For example, in the example illustrated in FIG. 4, “error B” as a defect is associated with “00004”, “00005”, and “00007” as identifiers of defect cause candidates.

  2 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) storing programs and various data, and a RAM (Random Access Memory) used as a work area of the CPU. And. The CPU executes a program stored in the ROM or the storage unit 27.

  The control unit 28 executes the log acquisition program 27 a to obtain a market log acquisition unit 28 a as a function log acquisition unit that acquires a market log as a function log. When the free capacity of the storage area of the MFP 20 (hereinafter referred to as “node execution unit log storage area”) for storing a log related to the MFP 20, that is, a node execution unit log described later, is less than a specific capacity. In addition, a log moving unit 28b for moving the node execution unit log stored in the node execution unit log storage area to a node other than the MFP 20 is realized.

  The control unit 28 includes a log recording setting unit 28c configured to execute, for each defect factor candidate, a setting as to whether or not to record a defect factor candidate log generated in the MFP 20 by executing the log acquisition program 27a. Realize.

  The control unit 28, by executing the log acquisition program 27a, controls any one piece of hardware included in the MFP 20, that is, any piece of hardware indicated as a factor in the factor-specific log configuration table 27d. The control means 28d is realized. By executing the log acquisition program 27a, the control unit 28 realizes at least one hardware control unit similar to the hardware control unit 28d other than the hardware control unit 28d. A plurality of hardware control means realized by the control unit 28 controls different hardware, respectively. Each of the plurality of hardware control means realized by the control unit 28 can record a log relating to the hardware controlled by itself, and constitutes a log recording means.

  The control unit 28 executes the log acquisition program 27a, thereby realizing any one function of the MFP 20, that is, any one function indicated as a factor in the factor-specific log configuration table 27d. 28e is realized. By executing the log acquisition program 27a, the control unit 28 realizes at least one function realization unit similar to the function realization unit 28e in addition to the function realization unit 28e. Each of the plurality of function realizing means realized by the control unit 28 realizes different functions. Each of the plurality of function realizing means realized by the control unit 28 can record a log relating to a function realized by itself, and constitutes a log recording means.

  FIG. 5 is a diagram illustrating an example of the market log 27b.

  The market log 27b shown in FIG. 5 includes a log for each service execution unit (hereinafter referred to as “service unit log”). All the service unit logs included in the market log 27b have the same configuration. Hereinafter, the service unit log 70 will be described on behalf of all the service unit logs included in the market log 27b.

  The service unit log 70 includes a log for each execution unit in each node in the service execution system 10 (hereinafter referred to as “node execution unit log”). All of the node execution unit logs included in the service unit log 70 have the same configuration. Hereinafter, the node execution unit log 80 will be described as a representative of all the node execution unit logs included in the service unit log 70.

  The node execution unit log 80 includes information related to “IN” (hereinafter referred to as “IN information”) 81, information related to “ACTION” (hereinafter referred to as “ACTION information”) 82, and information related to “OUTPUT” (hereinafter referred to as “OUTPUT”). Information ”) 83.

  The IN information 81 includes input content information 81a indicating specific input contents (hereinafter referred to as “input contents”) by the user to the service execution system 10 and instruction setting information 81b indicating settings instructed from outside the node. Including.

  When the node execution unit log 80 is a log related to the MFP 20, the input content information 81 a includes operation unit input content information indicating input content to the operation unit 21 and communication unit input indicating content input by the user via the communication unit 26. It is either content information. When the node execution unit log 80 is a log related to the cloud server 60, the input content information 81 a is GUI input content information indicating the input content via the GUI provided by the cloud server 60.

  When the node execution unit log 80 is a log of an operation according to an instruction from another node by the node in the service execution system 10, since the input content does not exist, the IN information 81 does not include the input content information 81a.

  The IN information 81 including the input content information 81a is information indicating the user input content. On the other hand, the IN information 81 not including the input content information 81a is not information indicating the user input content.

  When the node execution unit log 80 is a log related to the MFP 20, the instruction setting information 81b indicates job setting (hereinafter referred to as “job setting”). Here, as described above, since the Web information reference / setting function is not executed for each job, the IN information 81 does not include the instruction setting information 81b regarding the Web information reference / setting function.

  The operation unit input content information is information indicating specific input content to the operation unit 21 such as which button of the operation unit 21 is pressed. The operation unit input content information includes all specific input content to the operation unit 21. Accordingly, the operation unit input content information may include input content not directly related to the instruction setting information 81b. Although not shown, the IN information 81 includes time and user identification information (hereinafter referred to as “user ID”) in association with each input content in the operation unit input content information. The time associated with each input content in the operation unit input content information indicates the time when the input to the operation unit 21 is executed. The user ID associated with each input content in the operation unit input content information indicates the user ID of the user who executed the input to the operation unit 21.

  The communication unit input content information is information indicating specific input content obtained based on a packet received via the communication unit 26, such as what protocol is used and where it is accessed from. Although not shown, the IN information 81 includes a time and a user ID in association with each input content in the communication unit input content information. The time associated with each input content in the communication unit input content information indicates the time when the input via the communication unit 26 is executed. The user ID associated with each input content in the communication unit input content information indicates the user ID of the user who executed the input via the communication unit 26.

  The GUI input content information is information indicating specific input content to the GUI, such as which operation area of the GUI has been operated. The GUI input content information includes all specific input contents for the GUI. Accordingly, the GUI input content information may include input content not directly related to the instruction setting information 81b. Although not shown, the IN information 81 includes a time and a user ID in association with each input content in the GUI input content information. The time associated with each input content in the GUI input content information indicates the time when the input to the GUI is executed. The user ID associated with each input content in the GUI input content information indicates the user ID of the user who executed the input to the GUI.

  The instruction setting information 81b is information indicating the setting contents for the service by the user when the IN information 81 includes the input contents information 81a. For example, when the node execution unit log 80 is a log related to the MFP 20, the instruction setting information 81 b is generated by the control unit 28 based on the input content indicated in the input content information 81 a when the function is executed on a job basis. Indicates. For example, the job setting is a print setting in the case of a print function job (hereinafter referred to as “print job”), and a copy setting in the case of a copy function job (hereinafter referred to as “copy job”). . There may be a problem in the process of generating the instruction setting information 81b by the node based on the input content shown in the input content information 81a. Therefore, the instruction setting information 81b needs to be acquired separately from the input content information 81a. Although not shown, the IN information 81 includes a time and a user ID in association with the instruction setting information 81b. The time associated with the instruction setting information 81b indicates the time when the function provided by the MFP 20 is started in the case of the MFP 20, and the execution of the cloud service provided by the cloud server 60 in the case of the cloud server 60. Indicates the time when was started. In the case of the MFP 20, the user ID associated with the instruction setting information 81 b indicates the user ID of the user who has instructed execution of the function provided by the MFP 20. In the case of the cloud server 60, the cloud server 60 The user ID of the user who has instructed execution of the provided cloud service is shown.

  The ACTION information 82 includes execution operation information 82 a that specifically indicates an operation executed by a node in the service execution system 10 in response to an input corresponding to the IN information 81. The execution operation information 82a does not include a function execution result by the MFP 20 or a cloud service execution result by the cloud server 60. The ACTION information 82 is not indispensable information for grasping the problem phenomenon that has occurred in the service execution system 10, and therefore may not be included in the market log 27b.

  The OUTPUT information 83 is runtime setting information 83a indicating settings when the MFP 20 actually executes a job or the cloud server 60 actually executes a cloud service with respect to the setting indicated by the instruction setting information 81b. And execution result information 83b indicating the execution result of the function by the operation executed by the MFP 20 or the execution result of the cloud service executed by the cloud server 60 according to the setting indicated in the execution time setting information 83a. It is out. As described above, since the Web information reference / setting function is not executed for each job, the OUTPUT information 83 does not include the runtime setting information 83a for the Web information reference / setting function. When the OUTPUT information 83 includes the execution time setting information 83a, the OUTPUT information 83 includes the execution time setting information 83a in association with the execution result information 83b.

  Although not shown, the OUTPUT information 83 includes a time and a user ID in association with the execution result information 83b. The time associated with the execution result information 83b indicates the time when the function provided by the MFP 20 is completed in the case of the MFP 20, and the execution of the cloud service provided by the cloud server 60 is completed in the case of the cloud server 60. Indicates the time. The user ID associated with the execution result information 83b indicates the user ID of the user who instructed the execution of the function provided by the MFP 20 in the case of the MFP 20, and in the case of the cloud server 60, the cloud server 60 The user ID of the user who has instructed execution of the provided cloud service is shown.

  In the case of the MFP 20, the runtime setting information 83 a is information indicating the setting contents for the functions provided by the MFP 20. In the case of the cloud server 60, the runtime setting information 83 a is information on the execution of the cloud service provided by the cloud server 60. This is information indicating setting contents for the cloud service. For example, the control unit 28 of the MFP 20 may not be able to apply a plurality of settings input by the user at the same time when the job is actually executed, or the settings input by the user may depend on the state of the MFP 20. These settings are automatically changed when the job is executed if they cannot be applied when the job is executed. That is, the job setting indicated by the instruction setting information 81b is not always applied to the job as it is when the job is executed. Therefore, the runtime setting information 83a needs to be acquired separately from the instruction setting information 81b.

  FIG. 6 is a block diagram of the cloud server 60 when it is realized by one server computer.

  A cloud server 60 illustrated in FIG. 6 includes an operation unit 61 that is an input device such as a keyboard and a mouse to which various operations are input, a display unit 62 that is a display device such as an LCD that displays various information, a LAN, A communication unit 63 that is a communication device that communicates with an external device directly via a wired or wireless network via a network such as the Internet, or a nonvolatile memory such as a semiconductor memory or HDD that stores various information. A storage unit 64 that is a storage device of the nature, and a control unit 65 that controls the entire cloud server 60.

  The control unit 65 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM that is used as a work area for the CPU. The CPU executes a program stored in the ROM or the storage unit 64.

  The control unit 65 provides a GUI. The user can access the GUI via a computer such as a PC (Personal Computer) and input an instruction for causing the service execution system 10 to execute the service to the cloud server from the GUI.

  The control unit 65 executes the cloud service in units of transactions. Here, a transaction means this process when the cloud service is executed by only one process in the present embodiment. When a transaction means a process, the transaction identification information (hereinafter referred to as “transaction ID”) means process identification information (hereinafter referred to as “process ID”).

  Next, the operation of the service execution system 10 will be described.

  The market log acquisition unit 28a of the MFP 20 continues to acquire the market log 27b while the MFP 20 is activated.

  An operation of the MFP 20 when acquiring the market log 27b will be described.

  First, the operation of the MFP 20 when acquiring a node execution unit log related to the MFP 20 itself will be described.

  The market log acquisition unit 28a of the MFP 20 continues to acquire the node execution unit log while the MFP 20 is activated.

  FIG. 7 is a flowchart of the operation of the MFP 20 when acquiring one node execution unit log.

  As illustrated in FIG. 7, the market log acquisition unit 28 a acquires the user ID of the user who is logged in to the MFP 20 (S <b> 101).

  Next, the market log acquisition unit 28a executes IN information acquisition processing for acquiring IN information (S102).

  FIG. 8 is a flowchart of the IN information acquisition process shown in FIG.

  As shown in FIG. 8, the market log acquisition means 28a determines whether or not there is an input by the user (S121).

  When it is determined in S121 that there is an input by the user, the market log acquisition unit 28a executes an input content information acquisition process for acquiring the input content information (S122). The market log acquisition unit 28a executes an input content information acquisition process each time an input to the operation unit 21 is executed or an input via the communication unit 26 is executed.

  FIG. 9 is a flowchart of the input content information acquisition process shown in FIG.

  As shown in FIG. 9, the market log acquisition means 28a identifies the place where the input was executed (S141), and determines whether the place identified in S141 is the operation unit 21 or the communication unit 26 ( S142).

  When it is determined in S142 that the market-oriented log acquisition unit 28a is the operation unit 21, the input content for the operation unit 21 is acquired (S143), and the input content acquired in S143 is stored in the node execution unit log in the storage unit 27. The operation part input content information in the area is stored (S144).

  If it is determined in S142 that the market-oriented log acquisition unit 28a is the communication unit 26, the input content via the communication unit 26 is acquired (S145), and the input content acquired in S145 is stored in the node execution unit log in the storage unit 27. It memorize | stores in the communication part input content information in the storage area for data (S146).

  The market log acquisition means 28a acquires the time when the input was executed after the processing of S144 or S146 (S147), and associates the time acquired in S147 with the input content stored in S144 or S146. 27 is stored in the node execution unit log storage area (S148).

  Next, the market log acquisition unit 28a stores the user ID of the user acquired in S101 in the node execution unit log storage area of the storage unit 27 in association with the input content stored in S144 or S146 (S149). ), And ends the input content information acquisition process shown in FIG.

  As shown in FIG. 8, the market log acquisition unit 28a determines in S121 that there was no input by the user or when the execution of the function is started after the input content information acquisition process of S122, the instruction setting is performed. An instruction setting information acquisition process for acquiring information is executed (S123), and the IN information acquisition process shown in FIG. 8 ends.

  FIG. 10 is a flowchart of the instruction setting information acquisition process shown in FIG.

  As illustrated in FIG. 10, the market log acquisition unit 28 a acquires a job ID that is identification information of a target job (S <b> 161). Here, the control unit 28 manages a job by assigning a different job ID to each target job when executing the job. Therefore, the market-oriented log acquisition unit 28a can use the job ID assigned to the job for acquiring the node execution unit log.

  The log acquisition unit 28a for the market uses the input content to the operation unit 21 or the input content via the communication unit 26 and the cloud via the communication unit 26 as the job setting of the job specified by the job ID acquired in S161. The job setting generated by the control unit 28 is acquired based on any of the instruction contents from the server 60 (S162), and the job setting acquired in S162 is indicated in the storage area for the node execution unit log in the storage unit 27. The setting information is stored (S163).

  Next, the market log acquisition unit 28a acquires the time when the target job was started (S164), and associates the time acquired in S164 with the instruction setting information stored in S163, in the node execution unit of the storage unit 27. Store in the log storage area (S165).

  Next, the market-oriented log acquisition unit 28a stores the user ID of the user acquired in S101 in the node execution unit log storage area of the storage unit 27 in association with the instruction setting information stored in S163 (S166). Then, the instruction setting information acquisition process shown in FIG.

  The market log acquisition means 28a is based on the combination of the time stored in S148 and the combination of user IDs stored in S149, the time stored in S165, and the combination of user IDs stored in S166. The operation unit input content information stored in S144 or the communication unit input content information stored in S146 and the instruction setting information stored in S163 are associated as the same node execution unit log information.

  As illustrated in FIG. 7, the market log acquisition unit 28a executes an ACTION information acquisition process for acquiring ACTION information after the IN information acquisition process of S102 (S103). In the ACTION information acquisition process, the market log acquisition unit 28a acquires the operation content of the MFP 20 corresponding to the IN information acquired in S102 and stores it in the execution operation information in the node execution unit log storage area of the storage unit 27. To do. Next, the market log acquisition unit 28a stores the user ID of the user acquired in S101 in the node execution unit log storage area of the storage unit 27 in association with the stored execution operation information, and performs the ACTION information acquisition process. Exit.

  Note that the market log acquisition unit 28a acquires a job ID that is identification information of a target job, and corresponds to the content of the operation of the MFP 20 when the job specified by the acquired job ID is executed in the IN information. You may acquire as the content of operation | movement of MFP20 to perform. In this case, the market-oriented log acquisition unit 28a executes the instruction setting information stored in S163 and the execution information stored in the ACTION information acquisition process based on the job ID acquired in S161 and the job ID acquired in the ACTION information acquisition process. The operation information is associated with the same node execution unit log information.

  Next, when the execution of the function ends, the market-oriented log acquisition unit 28a executes OUTPUT information acquisition processing for acquiring OUTPUT information (S104), and ends the operation illustrated in FIG.

  FIG. 11 is a flowchart of the OUTPUT information acquisition process shown in FIG.

  As shown in FIG. 11, the market log acquisition unit 28a determines whether or not the function that has been executed is a Web information reference / setting function (S181).

  If the market log acquisition unit 28a determines in S181 that the function that has been executed is not a Web information reference / setting function, the market log acquisition unit 28a acquires a job ID that is identification information of the target job (S182).

  The market log acquisition unit 28a acquires the job setting at the time of executing the target job as the job setting of the job specified by the job ID acquired in S182 (S183), and stores the job setting acquired in S183. The information is stored in the runtime setting information in the 27 node execution unit log storage area (S184).

  Next, the market log acquisition unit 28a determines the type of job included in the job setting acquired in S183 (S185).

  When the market log acquisition unit 28a determines in S185 that the print job is a print job, it acquires the execution result of the target print job (S186). Here, the execution result acquired in S186 includes, for example, information on whether or not the target print job has ended normally, information on the number of recording media printed by the target print job, and the target print. Information on whether printing by the job was monochrome printing or color printing and information on whether printing by the target print job was single-sided printing or double-sided printing are included.

  When the market log acquisition unit 28a determines in S185 that the job is a copy job, it acquires the execution result of the target copy job (S187). Here, the execution result acquired in S187 includes, for example, information on whether or not the target copy job has been normally completed, information on the number of recording media printed by the target copy job, and target copy. Information on whether printing by the job was monochrome printing or color printing and information on whether printing by the target copy job was single-sided printing or double-sided printing are included.

  If the market log acquisition unit 28a determines in S185 that the job is a transmission function job (hereinafter referred to as "transmission job"), it acquires the execution result of the target transmission job (S188). Here, the execution result acquired in S188 includes, for example, information on whether or not the target transmission job has been completed normally, and information on the size of data transmitted via the communication unit 26 by the target transmission job. Information on the other party to which data is transmitted via the communication unit 26 by the target transmission job such as the cloud server 60, transmission by e-mail, transmission by SMB (Server Message Block), transmission by FTP (File Transfer Protocol), etc. , Information on a data transmission method by the target transmission job is included.

  If the market log acquisition unit 28a determines in S185 that the job is a FAX function job (hereinafter referred to as "FAX job"), the execution result of the target FAX job is acquired (S189). Here, the execution result acquired in S189 includes, for example, information on whether or not the target FAX job has ended normally, and information on the size of the data transmitted via the fax communication unit 25 by the target FAX job. And the information of the other party to whom data is transmitted via the fax communication unit 25 by the target FAX job.

  When the market log acquisition unit 28a determines in S185 that the job is a BOX function job (hereinafter referred to as a "BOX job"), the execution result of the target BOX job is acquired (S190). Here, the execution result acquired in S190 includes, for example, information on whether or not the target BOX job has ended normally and information on the size of data stored in the storage unit 27 by the target BOX job. included.

  If the market log acquisition unit 28a determines in S185 that the job is a report function job (hereinafter referred to as a “report job”), it acquires the execution result of the target report job (S191). Here, the execution result acquired in S191 includes, for example, information on whether or not the target report job has ended normally.

  When the process of S186, S187, S188, S189, S190, or S191 ends, the market log acquisition unit 28a stores the execution result acquired in S186, S187, S188, S189, S190, or S191 at the time of execution setting stored in S184. The information is stored in the execution result information in the node execution unit log storage area of the storage unit 27 in association with the information (S192).

  If the market log acquisition unit 28a determines in S181 that the function that has been executed is the Web information reference / setting function, the market log acquisition unit 28a acquires the execution result of the target Web information reference / setting function (S193), and acquires it in S193. The execution result is stored in the execution result information in the node execution unit log storage area of the storage unit 27 (S194).

  The market log acquisition means 28a acquires the time when the target function is completed after the processing of S192 or S194 (S195), and associates the time acquired in S195 with the execution result information stored in S192 or S194. The data is stored in the node execution unit log storage area of the storage unit 27 (S196).

  Next, the market log acquisition means 28a stores the user ID of the user acquired in S101 in the node execution unit log storage area of the storage unit 27 in association with the execution result information stored in S192 or S194 ( S197), the OUTPUT information acquisition process shown in FIG.

  Note that the market-oriented log acquisition unit 28a uses the same job ID acquired in S161 and the instruction setting information stored in S192 and the execution result information stored in S192 based on the job ID acquired in S182. Associate as node execution unit log information.

  Regarding operations when the MFPs other than the MFP 20 included in the service execution system 10 such as the MFPs 30, 40, 50 acquire the node execution unit log related to the MFP itself, the operation when the MFP 20 acquires the node execution unit log related to the MFP 20 itself is described. Since it is the same as the operation, the description is omitted.

  Next, the operation of the MFP 20 when the node execution unit log related to the MFP 20 itself is moved to a node other than the MFP 20 will be described.

  FIG. 12 is a flowchart of the operation of the MFP 20 when the node execution unit log related to the MFP 20 itself is moved to a node other than the MFP 20.

  The log moving unit 28b of the MFP 20 continues to repeatedly execute the operation illustrated in FIG. 12 when the market log acquisition unit 28a acquires a node execution unit log related to the MFP 20 itself.

  As illustrated in FIG. 12, the log moving unit 28b determines whether or not the free capacity of the node execution unit log storage area of the storage unit 27 is equal to or less than a specific capacity (S201).

  When the log moving unit 28b determines in S201 that the free capacity of the node execution unit log storage area of the storage unit 27 is not equal to or less than the specific capacity, the operation illustrated in FIG.

  When the log moving unit 28b determines in S201 that the free capacity of the storage area for the node execution unit log in the storage unit 27 is equal to or less than the specific capacity, the node execution unit for the MFP 20 is determined from all the nodes included in the service execution system 10. The free capacity of a specific storage area (hereinafter referred to as “storage area for other nodes”) for storing the log is acquired (S202).

  Next, the log moving unit 28b acquires in S202 whether or not there exists an MFP that belongs to the same network as the MFP 20, that is, the free space of the storage area for other nodes that belongs to the network 11 is greater than or equal to a specific capacity. A determination is made based on the information (S203).

  When the log moving means 28b determines in S203 that there is an MFP belonging to the network 11 and having a free capacity of the other node storage area equal to or larger than a specific capacity, the log movement means 28b is stored in the node execution unit log storage area of the storage unit 27. The node execution unit log related to the MFP 20 is moved to any one of the MFPs belonging to the network 11 and having a free capacity of the storage area for other nodes equal to or greater than a specific capacity (S204). Here, the log moving unit 28 b deletes the moved node execution unit log from the node execution unit log storage area of the storage unit 27.

  When the log moving unit 28b determines in S203 that there is no MFP belonging to the network 11 and having a free capacity of the other node storage area equal to or greater than a specific capacity, the log moving unit 28b stores the other node's storage for the plurality of MFPs belonging to the network 11. It is determined based on the information acquired in S202 whether or not the total free capacity of the area is equal to or greater than a specific capacity (S205).

  When the log moving unit 28b determines in S205 that the total free capacity of the other node storage areas of the plurality of MFPs belonging to the network 11 is greater than or equal to the specific capacity, the log moving means 28b stores the node execution unit log storage area of the storage unit 27 in the node execution unit log storage area. The stored node execution unit log related to the MFP 20 is moved to a plurality of MFPs belonging to the network 11 while being distributed in a weighted round robin according to the free capacity of the other node storage area of each MFP (S206). . That is, the log moving unit 28b distributes and moves logs to a plurality of MFPs with a data amount corresponding to the free capacity of the storage area for other nodes of each MFP. Here, the log moving unit 28 b deletes the moved node execution unit log from the node execution unit log storage area of the storage unit 27.

  When the log moving unit 28b determines in S205 that the total free capacity of the other-node storage areas of the plurality of MFPs belonging to the network 11 is not equal to or greater than the specific capacity, the log moving unit 28b Based on the information acquired in S202, it is determined whether or not the total free capacity of the node storage area is equal to or greater than a specific capacity (S207).

  When the log moving unit 28b determines in S207 that the total free capacity of the storage areas for other nodes of the plurality of MFPs included in the service execution system 10 is greater than or equal to the specific capacity, the log moving unit 28b The node execution unit logs related to the MFP 20 stored in the area are distributed to a plurality of MFPs included in the service execution system 10 while being distributed in a weighted round robin according to the free capacity of the other node storage area of each MFP. (S208). That is, the log moving unit 28b distributes and moves logs to a plurality of MFPs with a data amount corresponding to the free capacity of the storage area for other nodes of each MFP. Here, the log moving unit 28 b deletes the moved node execution unit log from the node execution unit log storage area of the storage unit 27.

  When the log moving means 28b determines in S207 that the total free capacity of the storage areas for other nodes of the plurality of MFPs included in the service execution system 10 is not a specific capacity or more, the log moving means 28b stores the node execution unit log in the storage unit 27. As many portions of the node execution unit log relating to the MFP 20 stored in the area as possible are weighted to a plurality of MFPs included in the service execution system 10 according to the free capacity of the other node storage area of each MFP. Dispersed and moved by round robin (S209). That is, the log moving unit 28b distributes and moves logs to a plurality of MFPs with a data amount corresponding to the free capacity of the storage area for other nodes of each MFP. Here, the log moving unit 28 b deletes the moved node execution unit log from the node execution unit log storage area of the storage unit 27.

  Next, the log moving unit 28b moves the node execution unit log related to the MFP 20 stored in the node execution unit log storage area of the storage unit 27 to any cloud server included in the service execution system 10 (S210). ). Here, the log moving unit 28 b deletes the moved node execution unit log from the node execution unit log storage area of the storage unit 27.

  The log moving unit 28b ends the operation illustrated in FIG. 12 after the process of S204, S206, S208, or S210.

  Regarding the operation when the MFP other than the MFP 20 included in the service execution system 10 such as the MFP 30, 40, 50 moves the node execution unit log related to the MFP itself to a node other than the MFP itself, the MFP 20 executes the node execution unit related to the MFP 20 itself. Since the operation is the same as when the log is moved to a node other than the MFP 20, the description thereof is omitted.

  Next, the operation of the cloud server 60 when acquiring a node execution unit log related to the cloud server 60 itself will be described.

  The control unit 65 of the cloud server 60 continues to acquire the node execution unit log while the cloud server 60 is activated.

  FIG. 13 is a flowchart of the operation of the cloud server 60 when acquiring one node execution unit log.

  As illustrated in FIG. 13, the control unit 65 acquires the user ID of the user who is logging in to the cloud server 60 (S301).

  Next, the control unit 65 executes an IN information acquisition process for acquiring IN information (S302).

  FIG. 14 is a flowchart of the IN information acquisition process shown in FIG.

  As shown in FIG. 14, the control unit 65 determines whether or not there is an input by the user (S321).

  If it is determined in S321 that there is an input by the user, the control unit 65 executes an input content information acquisition process for acquiring the input content information (S322). In addition, whenever the input with respect to GUI which the cloud server 60 provides is performed, the control part 65 performs an input content information acquisition process.

  FIG. 15 is a flowchart of the input content information acquisition process shown in FIG.

  As illustrated in FIG. 15, the control unit 65 acquires the input content for the GUI (S341), and stores the input content acquired in S341 in the GUI input content information (S342).

  Next, the control unit 65 acquires the time when the input was executed (S343), and stores the time acquired in S343 in association with the input content stored in S342 (S344).

  Next, the control unit 65 stores the user ID of the user acquired in S301 in association with the input content stored in S342 (S345), and ends the input content information acquisition process shown in FIG.

  As illustrated in FIG. 14, the control unit 65 determines that there is no input by the user in S321, or when the execution of the cloud service is started after the input content information acquisition process of S322, the instruction setting information is displayed. An instruction setting information acquisition process for acquisition is executed (S323), and the IN information acquisition process shown in FIG. 14 ends.

  FIG. 16 is a flowchart of the instruction setting information acquisition process shown in FIG.

  As illustrated in FIG. 16, the control unit 65 acquires a transaction ID that is identification information of a target transaction (S361). Here, the control unit 28 manages the transaction by assigning a different transaction ID to each target transaction when executing the transaction. Therefore, the control unit 65 can use the transaction ID assigned to the transaction for acquiring the node execution unit log.

  The control unit 65 sets the input content to the GUI provided by the cloud server 60 as the transaction setting specified by the transaction ID acquired in S361 (hereinafter referred to as “transaction setting”) and the MFP 20 via the communication unit 63. The transaction setting generated based on any of the instruction contents is acquired (S362), and the transaction setting acquired in S362 is stored in the instruction setting information (S363).

  Next, the control unit 65 acquires the time when the target transaction is started (S364), and stores the time acquired in S364 in association with the instruction setting information stored in S363 (S365).

  Next, the control unit 65 stores the user ID of the user acquired in S301 in association with the instruction setting information stored in S363 (S366), and ends the instruction setting information acquisition process shown in FIG.

  Note that the control unit 65 determines in S342 based on the combination of the user ID stored in S344, the combination of user IDs stored in S345, the time stored in S365, and the user ID stored in S366. The stored GUI input content information and the instruction setting information stored in S363 are associated as the same node execution unit log information.

  As illustrated in FIG. 13, after the IN information acquisition process in S302, the control unit 65 executes an ACTION information acquisition process for acquiring ACTION information (S303). In the ACTION information acquisition process, the control unit 65 acquires the operation content of the cloud server 60 corresponding to the IN information acquired in S302 and stores it in the execution operation information. Next, the control unit 65 stores the user ID of the user acquired in S301 in association with the stored execution operation information, and ends the ACTION information acquisition process.

  Note that the control unit 65 acquires a transaction ID that is identification information of the target transaction, and corresponds to the IN information, the contents of the operation of the cloud server 60 when the transaction specified by the acquired transaction ID is executed. You may acquire as the content of the operation | movement of the cloud server 60. FIG. In this case, the control unit 65, based on the transaction ID acquired in S361 and the transaction ID acquired in the ACTION information acquisition process, the instruction setting information stored in S363, the execution operation information stored in the ACTION information acquisition process, Are associated as information of the same node execution unit log.

  Next, when the execution of the target transaction is completed, the control unit 65 executes OUTPUT information acquisition processing for acquiring OUTPUT information (S304), and ends the operation illustrated in FIG.

  FIG. 17 is a flowchart of the OUTPUT information acquisition process shown in FIG.

  As illustrated in FIG. 17, the control unit 65 acquires a transaction ID that is identification information of a target transaction (S381).

  The control unit 65 acquires the transaction setting at the time of executing the target transaction as the transaction setting of the transaction specified by the transaction ID acquired at S381 (S382), and uses the transaction setting acquired at S382 as the runtime setting information. Store (S383).

  Next, the control unit 65 determines the type of transaction output included in the transaction setting acquired in S382 (S384).

  When the control unit 65 determines in S384 that the output to the GUI provided by the cloud server 60 (hereinafter referred to as “standard output”) is obtained, the control unit 65 acquires the execution result of the target standard output (S385). Here, the execution result acquired in S385 includes, for example, information on whether or not the target standard output has ended normally.

  If the control unit 65 determines in S384 that the transmission is to be transmitted to a node in the service execution system 10 (hereinafter referred to as “transmission output”), the control unit 65 acquires the execution result of the target transmission output (S386). Here, the execution result acquired in S386 includes, for example, information on whether or not the target transmission output has ended normally, and information on the size of the data transmitted via the communication unit 63 by the target transmission output. , Information on the transmission method of data by target transmission output such as transmission by e-mail, transmission by SMB, transmission by FTP, etc. And are included.

  When the control unit 65 determines in S384 that the data is stored in the storage unit 64 (hereinafter referred to as “stored output”), the control unit 65 acquires the execution result of the target stored output (S387). Here, the execution result acquired in S387 includes, for example, information on whether or not the target storage output has been normally completed, and information on the size of the data stored in the storage unit 27 by the target storage output. included.

  When the process of S385, S386, or S387 ends, the control unit 65 stores the execution result acquired in S385, S386, or S387 in the execution result information in association with the execution time setting information stored in S383 (S388).

  After the process of S388, the control unit 65 acquires the time at which the target transaction has ended (S389), and stores the time acquired in S389 in association with the execution result information stored in S388 (S390).

  Next, the control unit 65 stores the user ID of the user acquired in S301 in association with the execution result information stored in S388 (S391), and ends the OUTPUT information acquisition process shown in FIG.

  The control unit 65 uses the same node execution unit to store the instruction setting information stored in S363 and the execution result information stored in S388 based on the transaction ID acquired in S361 and the transaction ID acquired in S381. Associate as log information.

  Regarding operations when a cloud server other than the cloud server 60 included in the service execution system 10 acquires a node execution unit log related to the cloud server itself, the cloud server 60 acquires a node execution unit log related to the cloud server 60 itself. Since the operation is the same as that in FIG.

  Next, the operation of the MFP 20 when acquiring a service unit log will be described.

  FIG. 18 is a flowchart of the operation of the MFP 20 when acquiring a service unit log.

  As illustrated in FIG. 18, the market-oriented log acquisition unit 28 a executes a self-device log collection process for collecting a node execution unit log related to the MFP 20 among the target service unit logs (S 401).

  FIG. 19 is a flowchart of the own device log collection process shown in FIG.

  As illustrated in FIG. 19, the market log acquisition unit 28a targets only one job ID that is associated with the target service of the target service unit log and is not yet targeted (S421).

  Next, the market log acquisition unit 28a determines whether or not the node execution unit log associated with the target job ID has been moved to another node, that is, a node other than the MFP 20 (S422).

  When the market log acquisition unit 28a determines in S422 that the node execution unit log associated with the target job ID has not been moved to another node, the node execution unit log associated with the target job ID is obtained. Obtained from the node execution unit log storage area of the storage unit 27 (S423).

  When the market-oriented log acquisition unit 28a determines in S422 that the node execution unit log associated with the target job ID has been moved to another node, the node execution unit log associated with the target job ID is Obtained by collecting the node execution unit log from the destination node (S424).

  After the process of S423 or S424, the market-oriented log acquisition unit 28a determines whether there is an untargeted job ID associated with the target service of the target service unit log (S425).

  If the market log acquisition unit 28a determines in S425 that there is a job ID that is not yet targeted, the market log acquisition unit 28a executes the process of S421.

  When the market log acquisition unit 28a determines in S425 that there is no job ID that is not yet targeted, the market log acquisition unit 28a ends the own device log collection processing illustrated in FIG.

  As illustrated in FIG. 18, the market log acquisition unit 28 a sends a request for a node execution unit log related to an MFP other than the MFP 20 among the target service unit logs to the MFPs other than the MFP 20 after the own device log collection processing in S 401. Execute (S402).

  FIG. 20 is a flowchart of the operation of the MFP 30 when a node execution unit log request is received.

  As shown in FIG. 20, the log acquisition unit for the market of the MFP 30 is still subject to the target service unit log, that is, the target service of the service unit log that has received a request for the node execution unit log from the MFP 20. Only one job ID that does not exist is targeted (S441).

  Next, the market log acquisition unit of the MFP 30 determines whether or not the node execution unit log associated with the target job ID has been moved to another node, that is, a node other than the MFP 30 (S442).

  When the log acquisition unit for the market of the MFP 30 determines in S442 that the node execution unit log associated with the target job ID has not been moved to another node, the node execution unit log associated with the target job ID is determined. Is acquired from the node execution unit log storage area of the storage unit of the MFP 30 (S443).

  When the market log acquisition unit of the MFP 30 determines in S442 that the node execution unit log associated with the target job ID has been moved to another node, the node execution unit log associated with the target job ID is This node execution unit log is acquired by collecting it from the destination node (S444).

  The log acquisition unit for the market of the MFP 30 determines whether there is an untargeted job ID associated with the target service of the target service unit log after the processing of S443 or S444 (S445).

  If the log acquisition unit for the market of the MFP 30 determines in S445 that there is a job ID that is not yet targeted, the process of S441 is executed.

  When the log acquisition unit for the market of the MFP 30 determines in S445 that there is no job ID that is not yet targeted, the node execution unit log acquired in each of all the processes of S443 and S444 executed in the process shown in FIG. Is transmitted to the MFP 20 (S446), and the operation shown in FIG.

  The operation when the MFP 30 receives a node execution unit log request from the MFP 20 has been described above, but the operation when the MFP 20 other than the MFP 30 receives a node execution unit log request from the MFP 20 is the same. .

  As illustrated in FIG. 18, the market log acquisition unit 28 a executes, after the process of S <b> 402, a request for a node execution unit log related to the cloud server among the target service unit logs to the cloud server (S <b> 403).

  FIG. 21 is a flowchart of the operation of the cloud server 60 when a node execution unit log request is received.

  As illustrated in FIG. 21, the control unit 65 performs processing for one transaction that is associated with the target service unit log, that is, the target service of the service unit log that has received a request for the node execution unit log from the MFP 20 and has not yet been targeted. Only the ID is targeted (S461).

  Next, the control unit 65 acquires a node execution unit log associated with the target transaction ID (S462).

  Next, the control unit 65 determines whether or not there is an untargeted transaction ID associated with the target service of the target service unit log (S463).

  If the control unit 65 determines in S463 that there is a transaction ID that is not yet targeted, the control unit 65 executes the process of S461.

  If the control unit 65 determines in S463 that there is no transaction ID that is not yet targeted, the control unit 65 transmits the node execution unit log acquired in each of all the processes of S462 executed in the process shown in FIG. (S464), the operation shown in FIG.

  The operation when the cloud server 60 receives a node execution unit log request from the MFP 20 has been described above. However, a cloud server other than the cloud server 60 also receives a node execution unit log request from the MFP 20. The operation is similar.

  As illustrated in FIG. 18, the market log acquisition unit 28 a obtains all the node execution unit logs acquired in the own device log collection process in S 401, the process in S 402, and the process in S 403 after the process in S 403. The information is associated with the same service unit log and stored in the market log 27b (S404), and the operation shown in FIG. 18 ends.

  Next, the operation of the MFP 20 when a problem occurs will be described.

  FIG. 22 is a flowchart of the operation of the MFP 20 when a problem occurs.

  The control unit 28 performs the operation shown in FIG. 22 when a malfunction occurs in the MFP 20. As illustrated in FIG. 22, the control unit 28 generates failure information including an identifier of a factor candidate associated with a failure that has occurred in the MFP 20 in the failure factor candidate information 27 e (S <b> 501).

  Next, the log record setting unit 28c automatically updates the log configuration table 27d for each factor so that the log record implementation setting associated with the identifier included in the failure information generated in S501 is turned ON. (S502).

  Next, the log recording setting unit 28c starts the restart process of the MFP 20 (S503) and ends the operation shown in FIG. Therefore, the MFP 20 restarts after the operation shown in FIG. The MFP 20 may be in a state that cannot be used by the user due to the occurrence of a malfunction. There is a time when it can be used again by the user.

  Next, the operation of the MFP 20 when editing the factor-specific log configuration table 27d in accordance with an instruction from the user will be described.

  FIG. 23 is a flowchart of the operation of the MFP 20 when editing the log configuration table 27d for each factor according to an instruction from the user.

  When the start of editing of the log configuration table 27d by factor is instructed via the operation unit 21 or the communication unit 26, the control unit 28 starts the operation illustrated in FIG. For example, a user such as a service person can instruct the start of editing of the log configuration table 27d for each factor via the operation unit 21 or the communication unit 26.

  As illustrated in FIG. 23, the log recording setting unit 28c determines whether or not a change in the factor-specific log configuration table 27d is instructed via the operation unit 21 or the communication unit 26 (S521).

  When the log recording setting unit 28c determines in S521 that an instruction to change the factor-by-factor log configuration table 27d has been issued, the log recording setting unit 28c changes the factor-by-factor log configuration table 27d in accordance with an instruction via the operation unit 21 or the communication unit 26 ( S522). For example, the log recording setting unit 28c can turn ON the log recording execution setting associated with the specific factor candidate, or can set the log recording execution setting associated with the specific factor candidate. Can also be turned off.

  In S521, the log recording setting unit 28c determines that the change in the factor-by-factor log configuration table 27d has not been instructed, or when the processing in S522 ends, the end of the editing in the factor-by-factor log configuration table 27d is the operation unit 21 or It is determined whether or not an instruction is given via the communication unit 26 (S523).

  If the log recording setting unit 28c determines in S523 that the end of editing of the factor-specific log configuration table 27d has not been instructed, the log recording setting unit 28c executes the process of S521.

  When the log recording setting unit 28c determines in S523 that an instruction to end editing of the log configuration table 27d for each factor is given, the operation of FIG. 23 ends.

  The log recording setting unit 28c displays the factor-specific log configuration table 27d on the display unit 22 when the display of the factor-specific log configuration table 27d is instructed via the operation unit 21.

  In addition, when the display of the factor-specific log configuration table 27d is instructed from an external computer via the communication unit 26, the log recording setting unit 28c causes the computer that has instructed the display of the factor-specific log configuration table 27d to The display data of the log configuration table 27d is transmitted. Therefore, the computer that instructed the MFP 20 to display the log configuration table 27d for each factor can display the log configuration table 27d for each factor on the display unit of the computer based on the display data transmitted from the MFP 20. .

  Next, the operation of the MFP 20 when controlling hardware will be described.

  FIG. 24 is a flowchart of the operation of the MFP 20 when controlling hardware.

  The hardware control unit 28d repeatedly executes the operation shown in FIG. 24 at a specific timing when controlling the hardware that is the control target of the hardware control unit 28d itself.

  As shown in FIG. 24, the hardware control unit 28d has the log recording execution setting set to be associated with the hardware to be controlled by the hardware control unit 28d itself in the factor-specific log configuration table 27d. Whether or not (S541).

  When the hardware control unit 28d determines in S541 that the log recording execution setting is ON, the hardware control unit 28d is in a state of recording the log related to the hardware that is the control target of the hardware control unit 28d itself in the development log 27c ( S542), the operation shown in FIG.

  If the hardware control unit 28d determines in S541 that the log recording execution setting is OFF, the hardware control unit 28d does not record the log related to the hardware to be controlled by the hardware control unit 28d itself in the development log 27c ( S543), the operation shown in FIG.

  In the above description, when the hardware control unit 28d controls the hardware that is the control target of the hardware control unit 28d itself, the log related to the hardware that is the control target of the hardware control unit 28d is stored in the development log 27c. Explains about recording. Similarly, when the hardware control means other than the hardware control means 28d controls the hardware that is the control target of the hardware control means itself, a log related to the hardware that is the control target of the hardware control means itself is developed. Can be recorded in the destination log 27c.

  Next, the operation of the MFP 20 when executing the function will be described.

  FIG. 25 is a flowchart of the operation of the MFP 20 when executing a function.

  The function realization means 28e repeatedly performs the operation shown in FIG. 25 at a specific timing when executing the function that is the realization target of the function realization means 28e itself.

  As shown in FIG. 25, the function realizing unit 28e determines whether or not the log recording execution setting associated with the function to be realized by the function realizing unit 28e itself in the factor-based log configuration table 27d is ON. Is determined (S561).

  When the function realization means 28e determines in S561 that the log recording execution enable / disable setting is ON, the function realization means 28e enters a state of recording a log related to the function that is the realization target of the function realization means 28e itself in the development log 27c (S562). The operation shown in FIG. 25 ends.

  When the function realization means 28e determines in S561 that the log recording execution enable / disable setting is OFF, the function realization means 28e enters a state in which the log related to the function to be realized by the function realization means 28e itself is not recorded in the development log 27c (S563). The operation shown in FIG. 25 ends.

  In the above description, when the function realization means 28e executes a function that is the realization target of the function realization means 28e itself, the log related to the function that is the realization target of the function realization means 28e itself is recorded in the development log 27c. doing. Similarly, when a function realization unit other than the function realization unit 28e executes a function that is a realization target of the function realization unit itself, the log for the function that is the realization target of the function realization unit itself is recorded in the development log 27c. be able to.

  As described above, when a failure occurs, the MFP 20 automatically executes a setting for recording a log of failure factor candidates associated with the failure in the failure factor candidate information 27e. In this case (S502), it is possible to suppress the recording of a log unnecessary for the analysis of the cause of the failure, and as a result, the analysis of the cause of the failure can be facilitated. Further, since the MFP 20 can suppress the recording of a log unnecessary for the analysis of the cause of the failure, it is possible to suppress the free space of the storage area necessary for storing the log.

  When a failure occurs, the MFP 20 automatically executes a setting for recording a failure factor candidate log associated with the failure in the failure factor candidate information 27e (S502). Therefore, it is not necessary for the user to execute a setting for recording a log of candidate failure factors, and the cause of the failure can be easily analyzed.

  The MFP 20 sets whether or not to record a log of defect cause candidates in accordance with an instruction received by the operation unit 21 or the communication unit 26 (S522). When analysis of the cause is completed, the setting for not recording unnecessary logs is performed by the user, so that the free space in the storage area necessary for storing the logs can be suppressed.

  Since the MFP 20 displays the factor-specific log configuration table 27d on the display unit 22, the user can be made to confirm the settings automatically executed in S502 for the factor-specific log configuration table 27d, improving convenience. can do.

  The MFP 20 acquires the log 27b for the market including the contents of the input by the user and the execution result of the function according to the input by the user for each function execution unit (S404). As a result of the execution, the market log 27b can facilitate understanding of how the function has been executed. Therefore, the MFP 20 allows the analyst of the failure to obtain a rough cause of the failure before the analyst of the failure causes the detailed cause of the failure to be analyzed by the failure cause candidate log, that is, the development log 27c. Can be analyzed by the log 27b for the market, so that convenience can be improved.

  It should be noted that the MFP 20 adds the function executed by the MFP 20 and the function executed by another device to the service log realized in cooperation with each other, or replaces the log of the service with the MFP 20 A log of a function that is executed independently without being linked with the other device can be included in the market log 27b.

  The MFP 20 acquires the log 27b for the market including the contents of the input by the user and the execution result of the service according to the input by the user for each execution unit of the service, so what input is executed by the user. As a result, the understanding of how the service was performed can be facilitated by the market log 27b. Therefore, the MFP 20 can strengthen support for explanation to the user about the trouble by a person who does not have a high technical level such as a service person.

  When explaining a problem event occurring in the service execution system 10 to the customer, the service person can accurately explain the problem event to the customer by using the IN information and the OUTPUT information in the service unit log of the market log 27b. In particular, since the market-oriented log 27b includes IN information and OUTPUT information for each execution unit of the service, the service person can grasp a problem phenomenon that has occurred in the service execution system 10 for each service by the service execution system 10. .

  For example, the service person indicates in the log 27b for the market whether or not the cause of the execution of the service performed by the service execution system 10 is not the one desired by the customer is due to an error in the customer's operation on the service execution system 10. It can be judged based on.

  The MFP 20 can include the contents of the transmission from the node to the other node in the node execution unit log (S188 and S386), so that the node understands the contents transmitted by the node to the other node at the time of executing the service. This can be facilitated by service logs. Therefore, the MFP 20 can enhance support for explaining the problem to the user by a person who does not have a high technical level.

  The MFP 20 can include the contents received from the other nodes by the node in the node execution unit log (S163 and S363), so that the node understands the contents received from the other nodes when the service is executed. This can be facilitated by service logs. Therefore, the MFP 20 can enhance support for explaining the problem to the user by a person who does not have a high technical level.

  The MFP 20 can include the content of the transmission from the node to the other node in the node execution unit log (S188 and S386), and include the content of the reception from the other node by the node in the node execution unit log. (S163 and S363), it is possible to facilitate understanding of whether or not data is normally transmitted and received between nodes at the time of execution of the service by using the service log.

  In this embodiment, the MFP 20 stores IN information and OUTPUT information of all node execution unit logs related to the same service in the service unit log. Therefore, the service person can confirm the flow of time-series processing in each node related to the same service by using the market log 27b. However, the MFP 20 stores, in the service unit log, only the IN information about the user input content and the OUTPUT information about the final output of the service among the IN information and the OUTPUT information of all the node execution unit logs related to the same service. You may do it.

  Since the MFP 20 includes the instruction setting information and the runtime setting information in the service unit log of the market log 27b, how the setting content executed for the service by the user is finally changed when the service is executed. The market log 27b can facilitate the understanding of whether or not

  By confirming the log 27b for the market, the service person can explain the situation to the customer, that is, the user of the MFP 20 at an early stage with respect to the problem event that has occurred in the service execution system 10, and substitutes for the customer. It is possible to propose a method. In the market, it is important to promptly propose alternatives to customers rather than investigating the cause in detail. The log 27b for the market is not suitable for detailed cause investigation, but it is possible to make a rough cause investigation, so that it is possible to promptly propose an alternative method to the customer.

  When execution of a service for executing printing by the printer 23 of the MFP 20 based on the image data stored in the cloud server 60 is instructed to the service execution system 10 by the customer, when printing is not executed by the printer 23, An example in which a service person has received a report from a customer that “printing will not be performed” will be described. If the service person recognizes that the reason why the printing is not executed by confirming the log 27b for the market is that the communication between the MFP 20 and the cloud server 60 is defective, the service person promptly And suggesting alternative methods to the customer, such as “printing by the printer 23 based on image data stored in a computer other than the cloud server 60, such as the customer's PC”. Can do. If the service person recognizes that the reason why the printing is not executed by checking the log 27b for the market is that the printing function of the MFP 20 is defective, the service person can explain the situation to the customer at an early stage. In addition, an alternative method such as “a service using a function other than the print function of the MFP 20” can be proposed to the customer.

  Since the MFP 20 acquires the development log 27c in addition to the market log 27b, the market log 27b is suitable for explaining the problem to the user by a person who does not have a high technical level such as a service person. The development log 27c can appropriately support the detailed analysis of the cause of the failure by a person having a high technical level such as a developer.

  In the service execution system 10, at least one of the nodes stores the node execution unit log storage of the node itself when the free capacity of the node execution unit log storage area of the node itself is equal to or less than a specific capacity (YES in S 201). Since the node execution unit log stored in the area is moved to a node other than the node itself (S204, S206, S208, S209, or S210), the capacity of the node execution unit log storage area can be virtually increased. Therefore, the service execution system 10 enhances support for explaining the problem to the user by a person who does not have a high technical level even when the node execution unit log storage area includes a node having a small free space. can do.

  The service execution system 10 distributes the node execution unit log to a plurality of nodes even when there is no node having a sufficiently large free capacity in the storage area for other nodes (NO in S203). Since it is moved (S206, S208, S209, or S210), even if the node execution unit log storage area includes a node with a small free capacity, a person who does not have a high technical level is notified to the user for the trouble. Support for explanations can be strengthened.

  Since the service execution system 10 moves the node execution unit log preferentially to the image forming apparatus (S204, S206, S208, or S209), the node execution unit is transferred to a general-purpose apparatus such as a NAS (Network Attached Storage) or a PC. Compared with the case of moving the log, leakage of the node execution unit log can be suppressed.

  Since the service execution system 10 preferentially moves the log to an image forming apparatus belonging to the same network as the node from which the node execution unit log is moved (S204 or S206), the node from which the node execution unit log is moved is Compared with the case of moving the log to an image forming apparatus that belongs to a network different from the network to which it belongs, the leakage of the node execution unit log and the load imposed on the network by the movement of the node execution unit log can be suppressed.

  The service execution system 10 has a great merit that the leakage of the node execution unit log can be suppressed when confidential information or personal information is included in the node execution unit log.

  In the service execution system 10, when the node execution unit log is requested from a node other than the MFP itself (S402), the MFP collects the node execution unit log from the node to which the node execution unit log is moved (S444), The collected node execution unit log is transmitted to the node that requested the node execution unit log (S446). With this configuration, the service execution system 10 does not need to recognize the node execution unit log management status in the node execution unit log request destination node because the node execution unit log request source node does not need to recognize the node execution unit log management status. Even when a node having a small free space in the storage area is included, it is possible to reinforce support for explaining the problem to the user by a person who does not have a high technical level with a simple configuration.

  In the present embodiment, the MFP 20 acquires the free capacity of the storage area for other nodes from other nodes (S202), and executes the processes of S203 to S209 based on the free capacity acquired in S202. However, instead of acquiring the free capacity of the storage area for the other node from the other node, the MFP 20 acquires information on whether or not the other node has an HDD or SSD (Solid State Drive), and the HDD or SSD. The node execution unit log related to the MFP 20 stored in the node execution unit log storage area of the storage unit 27 may be moved to the node provided with.

  The MFP 20 corresponds to a print job, a copy job, a transmission job, a FAX job, a BOX job, and a report job in this embodiment, but may correspond to other types of jobs. Similarly, the cloud server 60 supports standard output, transmission output, and storage output, but may support other types of output.

  The electronic apparatus of the present invention may be an image forming apparatus other than an MFP such as a printer dedicated machine, a copy dedicated machine, a scanner dedicated machine, or a fax dedicated machine, or may be an electronic apparatus other than the image forming apparatus such as a PC. The service execution system 10 may include an image forming apparatus other than the MFP, such as a printer dedicated machine, a copy dedicated machine, a scanner dedicated machine, or a fax dedicated machine, or may include an electronic device other than the image forming apparatus such as a PC. good.

  When the service execution system 10 includes a plurality of electronic devices as nodes, the service execution system 10 may not include the cloud server as a node. The service execution system 10 is a system that includes a plurality of electronic devices as nodes and does not include a cloud server as a node, and the plurality of electronic devices execute services in cooperation with an input by a user. When the service execution system 10 includes only a plurality of MFPs as nodes, for example, one MFP included in the service execution system 10 receives print data from a PC as a service executed by the service execution system 10 In this case, after this MFP automatically divides the print data into a plurality of print data, at least one of the plurality of print data generated by the division is automatically distributed to other MFPs included in the service execution system 10. Thus, a service for dividing and printing one print data by a plurality of MFPs, and image data of an image read from a document by a scanner of one MFP included in the service execution system 10 are separated from this MFP. A service to send from the address book of the MFP to a destination designated by the user; It exists.

  In the present embodiment, the service execution system 10 is such that the MFP 20 collects service unit logs. However, the service unit log may be collected by an MFP other than the MFP 20, may be collected by a cloud server, or may be collected by a computer other than the MFP and the cloud server, such as a management server that manages the MFP 20, for example. good.

  The MFP 20 constitutes a log acquisition system that acquires a log for market and a log for development. However, the log acquisition system may include a configuration other than the MFP 20. For example, a part of the configuration of the MFP 20 such as an information management unit that manages defect factor candidate information may be provided by a device external to the MFP 20.

20 MFP (electronic equipment, log acquisition system)
21 Operation unit (instruction receiving device)
22 Display unit (display device)
26 Communication unit (instruction receiving device)
27 Storage unit (information management means)
27b Market log (function log)
27c Development log (probable cause log)
27d Factor-specific log configuration table (setting whether or not to log candidate failure factors)
27e Defect factor candidate information 28c Log recording setting means 28d Hardware control means (log recording means)
28e Function realization means (log recording means)

Claims (5)

Electronic equipment,
Information management means for managing defect factor candidate information indicating at least one defect factor candidate for each defect occurring in the electronic device;
Log recording setting means for executing setting for each candidate whether or not to record the candidate log;
Log recording means for recording the log according to the setting executed by the log recording setting means,
The log recording setting means automatically executes the setting for recording the log of the candidate associated with the defect that has occurred in the defect factor candidate information when the defect has occurred. Features electronic equipment. An instruction receiving device for receiving instructions;
The electronic apparatus according to claim 1, wherein the log recording setting unit executes the setting according to the instruction received by the instruction receiving device. With a display device,
The electronic apparatus according to claim 1, wherein the log recording setting unit displays the setting on the display device. The electronic device executes a function in response to an input by a user,
The said electronic device is provided with the function log acquisition means which acquires the content log of the said input and the execution result of the said function for every execution unit of the said function, The function log acquisition means characterized by the above-mentioned. The electronic device in any one of. Information management means for managing defect factor candidate information indicating at least one candidate for the defect for each defect occurring in the electronic device;
Log recording setting means for executing setting for each candidate whether or not to record the candidate log;
Log recording means for recording the log according to the setting executed by the log recording setting means,
The log recording setting means automatically executes the setting for recording the log of the candidate associated with the defect that has occurred in the defect factor candidate information when the defect has occurred. A featured log acquisition system.

Images