JP2018028738A - Communication control program, communication control device, and communication control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a communication control program that can reduce the influence of deterioration in performance of a system due to log output.SOLUTION: A communication control program issues a load state determination request (invocation of workload determination processing) to determine a load on a work processing part S901, determines whether the load on the work processing part is a heavy load S902, when the load is a heavy load Yes in S902, outputs an acquired log collection information to a log intermediate file storage part S903, and when the log is not a heavy load No in S902, issues a log editing request (invocation of log editing processing) S904. A sub routine of the log editing processing includes acquiring a template of a log message from a log message storage part, embedding the log collection information in the acquired template of the log message for editing, and outputting the edited log message to a log file storage part.SELECTED DRAWING: Figure 9

Description

  The present invention relates to a communication control program for controlling log output.

  In operating the system, the log plays an important role in grasping what happened in the system. For example, the log is used for status monitoring during program operation, detection when an abnormality occurs, and investigation of the cause. In addition, it is stored for a predetermined period as a business trail and used for various audits.

  An example of a conventional log output mechanism is as follows. When the log output process is called during the execution of the program, the log message definition file is searched using the message ID embedded in the program as a key to obtain the log message. Because the cause cannot be investigated only with the stylized log message, information that can only be acquired at that timing, such as arguments and variable values, is dynamically embedded in the log message, edited, and output to the log file. In other words, a series of processes including a log message acquisition process, an embedded information acquisition process, a log message editing process, and a log message output process are performed before the log message is output. A technique for outputting a log message is disclosed, for example, in Patent Document 1 below.

JP 2014-149783 A

  However, for example, when high-speed processing is required, such as in securities trading business, it is difficult for the system to satisfy the required processing performance by performing the above-described series of processing.

  An object of this invention is to provide the communication control program which can suppress the influence of the performance degradation of the system by log output in view of the said subject.

  In order to achieve the above object, the present invention provides a communication control program for controlling log output processing, which is information necessary for generating a log that can be acquired at the time of a call based on a log output call. And a step of outputting the acquired information as log intermediate file information to a predetermined storage area before log generation is started.

  In the communication control program of the present invention, the communication control program further includes a step of determining whether or not a load of a business processing unit that executes business processing in the target business of log output exceeds a predetermined load, When it is determined that the log information is over, outputting the acquired information as the log intermediate file information is a preferable mode.

  In the communication control program of the present invention, whether or not the load of the business processing unit exceeds the predetermined load based on a time zone, a data transmission / reception amount per unit time, or a predetermined load situation. Judging is a preferred embodiment.

  The communication control program according to the present invention further includes a step of generating a log using the log intermediate file information in the predetermined storage area and outputting the generated log when a predetermined condition is satisfied. This is a preferred embodiment.

  In addition, the present invention is a communication control device that controls processing of log output, and based on a log output call, an acquisition unit that acquires information necessary for generating a log that can be acquired at the time of the call; And an output unit that outputs the acquired information as log intermediate file information to a predetermined storage area before log generation is started.

  Further, the present invention is a communication control method for controlling the processing of log output, the step of acquiring information necessary for generating a log that can be acquired at the time of calling based on the call of log output; A step of outputting the acquired information as log intermediate file information to a predetermined storage area before log generation is started.

  According to the present invention, it is possible to suppress the influence of system performance degradation caused by log output.

It is a figure which shows an example of a structure of the communication control system containing the server which mounts the communication control program which concerns on embodiment. It is a figure which shows an example of a structure of the operation | movement monitoring apparatus in embodiment. It is a figure which shows an example of the function structure of the server which concerns on embodiment. It is a figure which shows an example of the hardware constitutions for implement | achieving the server which concerns on embodiment. It is a figure for demonstrating the process when the work process part in embodiment is high load. It is a figure for demonstrating the process when the work process part in embodiment is low load. It is a figure for demonstrating the log output post-process by the log output post-processing part in embodiment. It is a flowchart which shows an example of the processing flow of the log output in the server 2 which mounts the communication control program which concerns on embodiment. It is a flowchart which shows the subroutine of the log output process in embodiment. It is a flowchart which shows the subroutine of the work load determination process in embodiment. It is a flowchart which shows the subroutine of the log edit process in embodiment. It is a flowchart which shows the subroutine of the log output post-process in embodiment. It is a figure which shows an example of the log intermediate | middle file in embodiment. It is a figure which shows an example of the template of the log message in embodiment. It is a figure which shows an example of the business load determination standard (standard by a time slot | zone) in embodiment. It is a figure for demonstrating the process when the work process part in embodiment is high load. It is a figure for demonstrating the process when the work process part in embodiment is low load. It is a flowchart which shows the subroutine of the edit process of the log message in embodiment. It is a figure which shows an example of the embedded character conversion table in embodiment. FIG. 10 is a diagram for describing a specific example of log message merging processing and sorting processing in the embodiment;

  Hereinafter, embodiments will be described with reference to the drawings. First, an example of a communication control system including a server that implements a communication control program according to an embodiment will be described with reference to FIG. The communication control system 1 includes a server 2 (communication control device) and an operation monitoring device 3. The server 2 and the operation monitoring device 3 are connected via a network 4.

  When the server 2 performs a predetermined job, when the log output process is called (an event that is a log output target occurs), information necessary for generating a log (hereinafter also referred to as a log message) (for example, , Time stamp, message ID, embedded character, etc.). Then, the server 2 outputs the acquired information as a log intermediate file before starting log generation, that is, before log generation processing to be performed in the future. Here, the predetermined business is, for example, business requiring high-speed processing, such as securities trading business. Detailed processing in the server 2 (communication control program) will be described later.

  As shown in FIG. 2, the operation monitoring apparatus 3 includes a log intermediate file output by the server 2 and a monitoring program 20 that monitors the log file, and a monitoring screen 21 that outputs a monitoring result. Specifically, the operation monitoring apparatus 3 displays a log message or the like stored in a log file storage unit 38 described later on the monitoring screen 21. Thereby, the supervisor can grasp what happened in the system.

  Next, an example of a functional configuration of a server that implements the communication control program according to the embodiment will be described with reference to FIG. As shown in FIG. 3, the server 2 includes a business processing unit 30, a log output processing unit 31, a log editing processing unit 32, a log output post-processing unit 33, a business load determination processing unit 34, a business load storage unit 35, and a log message. The storage unit 36 includes a log intermediate file storage unit 37 and a log file storage unit 38. The configuration of the server 2 is not limited to this, and may include other configurations.

  The business processing unit 30 is a processing unit that realizes main business functions of the server 2, and transmits and receives data in the case of a communication control program. It also collects information for log output and measures the amount of data sent and received per unit time to determine the business load (load status) of the business processing unit 30.

  The log output processing unit 31 receives a log output request from the business processing unit 30 and performs log output processing. At this time, as will be described later, the log output processing unit 31 refers to the determination result of the business load determination processing unit 34, and when the business load is high, only the log collection information is stored as a log intermediate file. Output to 37. When the business load is low, the log output processing unit 31 makes a log editing request to the log editing processing unit 32 and passes the log collection information.

  Here, the log collection information is information necessary for generating a log and can be acquired only when the log output process is called. Specifically, the above-mentioned time stamp, message ID, embedded character, and the like are output to the log intermediate file storage unit 37 in the CSV (Comma-Separated Values) format, for example, as a log intermediate file.

  An example of the log intermediate file is shown in FIG. The log intermediate file is configured in the order of, for example, a time stamp, a message ID, and embedded characters. One log intermediate file is stored in the log intermediate file storage unit 37 as one record. In this example, there are five embedded characters, but this is not restrictive.

  The log editing processing unit 32 receives a log editing request from the log output processing unit 31 and performs log editing processing when the business load is low. Specifically, using the message ID of the log collection information as a key, the corresponding log message (log message template) is acquired from the log message storage unit 36, and the log collection information is embedded in the acquired log message for editing (generation). To do. The editing result (the log message after editing) is output to the log file storage unit 38. The log message is edited into a format in which the supervisor who manages the operation monitoring apparatus 3 can easily confirm the meaning of the message visually. The log message may be edited by a device or program other than the server 2.

  An example of a log message template stored in the log message storage unit 36 is shown in FIG. There are types of log messages such as error (E), warning (W), information (I), and debug (D). FIG. 14 shows templates of an error message (ERROR) and a warning message (WARNING). For example, in the error message template, the message content (ERROR: 001 Error occurred. A =% s, B =% d, C =% x, at% s-% d) is associated with the message ID (E001). . The% is called an embedded identifier, and the s, d, and x are called format specifiers. Log collection information is embedded in% s,% d, and% x. Details of the log message editing process will be described later.

  The log output post-processing unit 33 receives a log output post-processing request from the business processing unit 30 according to a business end instruction or the like, and performs post-log output processing. Specifically, the log output post-processing unit 33 reads the log collection information stored in the log intermediate file storage unit 37 when the business load is high. Then, the log output post-processing unit 33 acquires the corresponding log message from the log message storage unit 36 using the message ID as a key, and edits (generates) the log collection information embedded in the acquired log message.

  Further, the log output post-processing unit 33 merges the edited log message and the log message in the log file storage unit 38 (the log message edited at low load) and sorts them in the order of the time stamp ( And output to the log file storage unit 38. While a predetermined task is being performed, there may be a case where the workload is low and the load is high. Therefore, it is necessary to merge log messages edited at each load after the end of business. Therefore, the post-log output processing unit 33 merges the log message at the time of high load that is edited after the end of the business and the log message that is edited at the time of low load and stored in the log file storage unit 38. And sort and output. Details of the merge processing and sort processing by the log output post-processing unit 33 will be described later. The log output post-processing unit 33 can be arranged in the same device (program) or in another device (program).

  The business load determination processing unit 34 determines the load of the business processing unit 30 with reference to the business load determination standard. Examples of the business load determination criteria include a time zone, a data transmission / reception amount, and a job processing unit 30 with a high load or a low load set in advance. Specifically, when the load determination time is in a predetermined time zone, it is determined that the load of the business processing unit 30 is high (high load). Further, when the data transmission / reception amount per unit time exceeds a predetermined threshold, the business processing unit 30 determines that the load is high. Further, when the load of the business processing unit 30 is set in advance, the load of the business processing unit 30 is determined based on the set load. For example, when the load is set as a high load in advance, the load of the business processing unit 30 is determined as a high load.

  The business load storage unit 35 stores a business load determination criterion used when the business load determination processing unit 34 determines a load. FIG. 15 shows an example of the business load determination standard (standard based on time zone). For example, during the start of work (9:00 to 10:00), before lunch break (11:00 to 12:00), and before the end of work (16:00 to 17:00), it becomes a heavy load due to the concentration of requests such as orders. Suppose that there is an empirical rule of low load without concentration. In that case, the business load determination criteria are as shown in FIG. It is determined whether the load is high or low using such a business load determination criterion.

  As described above, the log message storage unit 36 stores a log message (a log message template) in association with a message ID.

  Next, an example of a hardware configuration for realizing the server 2 that implements the communication control program according to the embodiment will be described with reference to FIG. The hardware configuration includes, for example, a CPU 41, a HDD (Hard Disk Drive) 42, a RAM (Random Access Memory) 43, a ROM (Read Only Memory) 44, a graphic processing device 45, an input interface (I / F) 46, a communication interface ( I / F) 47 and bus 48 are provided. The CPU 41, HDD 42, RAM 43, ROM 44, graphic processing device 45, input interface (I / F) 46, and communication interface (I / F) 47 are connected to each other via a bus 48, for example.

  The CPU 41 reads a program (for example, a communication control program) for performing various processes of the server 2 stored in the HDD 42 or the like via the bus 48, temporarily stores the read program in the RAM 43, and the program Various processes are performed according to the above.

  The HDD 42 stores application programs for performing various processes of the server 2, data necessary for the processes of the server 2, and the like.

  The RAM 43 is a volatile memory and temporarily stores a part of an OS (Operating System) program and application programs to be executed by the CPU 41. The RAM 43 stores various data necessary for processing by the CPU 41.

  The ROM 44 is a non-volatile memory, and stores programs such as a boot program and BIOS (Basic Input / Output System).

  The graphic processor 45 can be connected to the monitor 400 and generates information to be displayed on the monitor 400.

  The input interface (I / F) 46 receives information input via the keyboard 401, the mouse 402, or the like.

  The communication interface (I / F) 47 performs data transmission / reception via the network 4 with the outside (such as the operation monitoring device 3 or a terminal used by a user).

  The bus 48 is a path that mediates transmission / reception of control signals, data signals, and the like between the devices. Note that the hardware configuration for realizing the operation monitoring apparatus 3 includes a CPU, an HDD, various interfaces, and the like, similar to the server 2.

  Next, the flow of processing when the above-described job processing unit 30 is heavily loaded will be described with reference to FIGS. As shown in FIG. 5, the server 2 receives a message transmitted by a user for an order in a securities transaction or the like. Here, if the message transmission of the order by message reception is an event to be logged, the business processing unit 30 recognizes that a log output event has occurred. The business processing unit 30 acquires log collection information (for example, time stamp, message ID, embedded character, etc.) when a log output target event occurs. The embedded character is information indicating the state of the program when the event occurs, and is mainly a variable value of the program. In the example shown in FIG. 16, there are embedded characters from the first to the fifth, in order of the value of variable A (aaa), the value of variable B (1), the value of variable C (16), and the value of variable D (ddd). , The value of the variable E (5).

  The business processing unit 30 issues a log output request to the log output processing unit 31 after acquiring the log collection information. The log output processing unit 31 issues a load status determination request to the business load determination processing unit 34. The business load determination processing unit 34 acquires a business load determination standard from the business load storage unit 35, and determines, for example, the business load as a high load based on the acquired business load determination standard. The log output processing unit 31 outputs only the acquired log collection information to the log intermediate file storage unit 37 as a log intermediate file because the business load is high. An example of the output log intermediate file is described in detail in FIG.

  At this time, the operation monitoring apparatus 3 monitors the log intermediate file and the log file by the monitoring program 20 and outputs a monitoring result to the monitoring screen 21 when an event to be monitored occurs. The same applies to a low load described later.

  On the other hand, the flow of processing when the business processing unit 30 is lightly loaded will be described with reference to FIGS. Since the processing until the business load is determined by the business load determination processing unit 34 is the same as the case of the high load shown in FIG. When the business load determination processing unit 34 determines that the load is low as a result of the business load determination, the log output processing unit 31 issues a log editing request to the log editing processing unit 32. At this time, the log output processing unit 31 passes the log collection information to the log editing processing unit 32.

  The log editing processing unit 32 acquires a corresponding log message template from the log message storage unit 36 using the message ID included in the log collection information passed from the log output processing unit 31 as a key. The log editing processing unit 32 edits (generates) a log message according to the acquired log message template. That is, the log editing processing unit 32 sequentially analyzes the character string of the template character by character, and when a position where the embedded character is embedded appears (embedding identifier appears), the embedded character of the acquired log collection information is displayed item by item. Edit log messages while converting. Details of the log message editing process will be described later. The log editing processing unit 32 outputs the edited log message to the log file storage unit 38. An example of the edited log message is described in detail in FIG.

  Next, post-log output processing by the log output post-processing unit 33 will be described with reference to FIGS. When a business end instruction is issued from a monitor or the like and the business processing unit 30 satisfies a predetermined condition, that is, when a business end event is detected, a log output post-processing request is issued to the log output post-processing unit 33 To do. The log output post-processing unit 33 reads a record in the log intermediate file storage unit 37 and edits (generates) a log message for each record as follows.

  The log output post-processing unit 33 acquires a corresponding log message template from the log message storage unit 36 using the message ID of the read record as a key. The log output post-processing unit 33 reflects the time stamp and other embedded characters included in the record on the acquired log message template, and edits the log message. The method of reflecting the time stamp and the embedded character in the template is the same as the method by the log editing processing unit 32 at the time of low load described above. As described above, the log message editing process is performed as a post process after the end of the work, so that the processing time required to output the log of one event in the work can be shortened and the work processing performance can be improved.

  The log output post-processing unit 33 reads all log messages in the log file storage unit 38 (log messages edited at low load). The log output post-processing unit 33 merges the edited log message and the log message read from the log file storage unit 38 and sorts the log messages in ascending order of time stamps, for example. The log output post-processing unit 33 outputs the log messages merged and sorted to the log file storage unit 38. In addition, since the work is finished, the monitoring by the operation monitoring apparatus 3 is also finished.

  Next, an example of a processing flow of log output in the server 2 that implements the communication control program according to the embodiment will be described with reference to FIG. As shown in FIG. 8, when the server 2 (communication control program) determines whether or not an event in business (for example, an event such as a securities transaction) has occurred (step S801), and determines that an event has occurred (Yes in step S801), business processing corresponding to the event that has occurred is performed (step S802). If it is not determined that an event has occurred (No in step S801), the process returns to step S801.

  The server 2 determines whether a log output target event (for example, a message transmission event) has occurred (step S803), and if it occurs (Yes in step S803), acquires log collection information (step S804). Then, a log output request (call of log output processing) is issued (step S805). The log output process will be described later. If no log output target event has occurred (No in step S803), the process advances to step S806.

  The server 2 determines whether the received event is a business end event (step S806). If the received event is a business end event (Yes in step S806), the log output post-processing request (log output post-processing (Call) is issued (step S807). The log output post-processing will be described later.

  Next, the log output processing subroutine will be described with reference to FIG. The server 2 (communication control program) issues a load status determination request (call of a business load determination process) in order to determine the load of the business processing unit 30 (step S901). The business load determination process will be described later. The server 2 determines whether or not the load of the business processing unit 30 is high (step S902). If the load is high (Yes in step S902), the acquired log collection information is sent to the log intermediate file storage unit 37. Output (step S903). On the other hand, if the load is not high (No in step S902), a log edit request (call log edit processing) is issued (step S904). The log editing process will be described later.

  Next, a subroutine for the business load determination process will be described with reference to FIG. The server 2 (communication control program) sets the business load as, for example, a default low load (step S1001), and obtains the business load determination criterion from the business load storage unit 35 (step S1002). The server 2 determines whether or not the acquired business load determination criterion is a determination criterion based on a time zone (step S1003), and if it is based on a time zone (Yes in step S1003), acquires information on the current time (step S1004). ).

  The server 2 determines whether or not the acquired time is a high load time zone (step S1005). If the acquired time is a high load time zone (Yes in step S1005), the server 2 sets the work load as a high load (step S1005). S1006).

  On the other hand, if the acquired business load determination criterion is not the determination criterion based on the time zone (No in step S1003), the server 2 determines whether or not the determination criterion is based on the data transmission / reception amount per unit time (step S1007). If it is based on the amount (Yes in step S1007), the data transmission / reception amount per unit time is acquired (step S1008). The server 2 determines whether or not the acquired data transmission / reception amount is equal to or greater than a predetermined threshold (step S1009), and if it is equal to or greater than the predetermined threshold (Yes in step S1009), sets the business load as a high load ( Step S1010). If it is not equal to or greater than the predetermined threshold (No in step S1009), the business load determination process ends.

  If the acquired business load determination criterion is not a determination criterion based on the amount of data transmitted / received per unit time (No in step S1007), the server 2 has a load set in advance, that is, a high load or a low load. It is determined whether or not a load is set in advance (step S1011). If the load is set in advance (Yes in step S1011), it is determined whether or not the setting is a high load (step S1012). If the load is high (Yes in step S1012), the business load is set to be high (step S1013). If the load is not set in advance (No in step S1011) and the setting is not high (No in step S1012), the business load determination process ends.

  Next, the log editing process subroutine will be described with reference to FIG. The server 2 (communication control program) acquires a log message template from the log message storage unit 36 (step S1101), and embeds the log collection information in the acquired log message template for editing (step S1102). Details of the log message editing process will be described later. The server 2 outputs the edited log message to the log file storage unit 38 (step S1103).

  Next, the log output post-processing subroutine will be described with reference to FIG. The server 2 (communication control program) reads one record from the log intermediate file storage unit 37 (step S1201), and acquires a log message template corresponding to the message ID of the record read in step S1201 from the log message storage unit 36. (Step S1202). The server 2 compiles the log collection information in the acquired log message template and edits it (step S1203). Details of the log message editing process will be described later. At this time, the edited log message is stored in a buffer (not shown) (step S1204). The server 2 determines whether or not there is a next record (step S1205). If there is a next record (No in step S1205), the process returns to step S1201.

  On the other hand, if there is no next record (Yes in step S1205), the server 2 reads all log messages (log messages edited at low load) from the log file storage unit 38 and merges (adds) them to the buffer ( Step S1206). Then, the server 2 sorts all log messages in the buffer in order of time stamp (step S1207). Details of the log message merge processing and sort processing will be described later. The server 2 outputs all log messages in the buffer to the log file storage unit 38 (step S1208).

  The log message editing process subroutine will be described with reference to FIG. In the following description, the processing subject is described as the log output post-processing unit 33. However, in the case of log message editing processing at low load, the processing subject is the log editing processing unit 32.

  The log output post-processing unit 33 deletes data from the beginning of the acquired template until the first quotation mark is detected (step S1801a). The log output post-processing unit 33 sets the character next to the deleted quotation mark as the reading position and sets the embedded character counter N to 1 (step S1801b). At this time, the log output post-processing unit 33 embeds the time stamp acquired from the record at the head of the deleted template. In this example, the deletion of the template data is performed based on the detection of the quotation mark. However, the present invention is not limited to the quotation mark, and may be another mark or a mark.

  The log output post-processing unit 33 reads one character from the reading position (step S1802). When the template acquired here is a template with the message ID E001 in the templates shown in FIG. 14, the read character is “E”.

  The log output post-processing unit 33 determines whether or not the read character is the embedded identifier% (step S1803). When the read character is the embedded identifier% (Yes in step S1803), the log output post-processing unit 33 further reads one character (step S1804) and determines what format specifier the read character is. Judgment is made (step S1805).

  Here, what conversion is performed by the character (format specifier) following the embedded identifier is determined using, for example, an embedded character conversion table shown in FIG. For example, when the format specifier is “s”, the embedded character is embedded as it is without being converted. When the format specifier is “d”, the embedded character is converted into a decimal number and embedded. When the format specifier is “x”, the embedded character is converted into a hexadecimal number and embedded. In this example, three types of conversion examples are given, but more advanced editing such as specifying the number of digits of numerical values may be performed.

  When the format specifier is “s”, the log output post-processing unit 33 concatenates (embeds) the Nth embedded character in the log message (template) (step S1806). When the format specifier is “d”, the log output post-processing unit 33 converts the Nth embedded character into a decimal number (step S1807), and concatenates the converted character string to the log message (step S1808). When the format specifier is “x”, the log output post-processing unit 33 converts the Nth embedded character into a hexadecimal number (step S1809), and concatenates the converted character string to the log message (step S1810).

  After concatenation, the log output post-processing unit 33 increments the embedded character counter N according to the number of embedded characters (step S1811). The log output post-processing unit 33 determines whether or not the character indicating the template reading position is a quotation mark corresponding to the first quotation mark (step S1812). In the case of the corresponding quotation mark (Yes in step S1812), the log output post-processing unit 33 determines that the last character of the template has been reached, and the corresponding quotation mark linked to the log message in step S1814 is determined. Delete the log message and finish the log message editing process. On the other hand, if it is not the corresponding quotation mark (No in step S1812), the reading position is incremented (step S1813).

  On the other hand, if the read character is not an embedded identifier in step S1803 (No in step S1803), the log output post-processing unit 33 concatenates the read character to the log message (step S1814).

  Next, a specific example of the log message merge processing and sort processing will be described with reference to FIG. As illustrated in FIG. 20, the log output post-processing unit 33 edits the log message based on the log intermediate file read from the log intermediate file storage unit 37 and the template acquired from the log message storage unit 36. The edited log message is stored (added) in the buffer.

  Thereafter, when it is determined that there is no next record (log intermediate file), the log output post-processing unit 33 reads all log messages (log messages edited at low load) from the log file storage unit 38. In this example, two log messages among all log messages are shown. All read log messages are merged (added) into the buffer. The merged log message is enclosed by a square broken line.

  The log output post-processing unit 33 sorts the log messages stored in the buffer in ascending order using, for example, a time stamp as a key, and outputs the log message to the log file storage unit 38. Note that the sorting method is not limited to the method using the time stamp as a key. For example, the sorting may be performed according to the importance of the error code.

  According to the server 2 (communication control program) as described above, it is possible to suppress the influence of system performance deterioration due to log output.

  In the above-described embodiment, the main processing of the server 2 has been described as being executed by software processing by the CPU. However, all or part of this processing may be realized by hardware.

  Further, the above-described embodiment is not limited to the above-described embodiment, and various changes can be made without departing from the gist of the embodiment.

DESCRIPTION OF SYMBOLS 1 Communication control system 2 Server 3 Operation monitoring apparatus 4 Network 20 Monitoring program 21 Monitoring screen 30 Business processing part 31 Log output processing part 32 Log edit processing part 33 Log output post-processing part 34 Business load judgment processing part 35 Business load storage part 36 Log message storage unit 37 Log intermediate file storage unit 38 Log file storage unit 41 CPU
42 HDD
43 RAM
44 ROM
45 graphic processing unit 46 input interface 47 communication interface 48 bus 400 monitor 401 keyboard 402 mouse

Claims (6)

A communication control program for controlling log output processing,
Obtaining information necessary to generate a log, which can be acquired at the time of the call, based on the call of the log output;
Outputting the acquired information as log intermediate file information to a predetermined storage area before log generation is started,
A communication control program executed by a computer. A step of determining whether or not a load of a business processing unit that executes a business process in the target business of the log output exceeds a predetermined load;
The communication control program according to claim 1, wherein when it is determined that the predetermined load is exceeded, the acquired information is output as the log intermediate file information.   3. The apparatus according to claim 2, wherein it is determined whether or not a load of the business processing unit exceeds the predetermined load based on a time zone, a data transmission / reception amount per unit time, or a preset load status. The communication control program described in 1.   4. The method according to claim 1, further comprising a step of generating a log using the log intermediate file information in the predetermined storage area and outputting the generated log when a predetermined condition is satisfied. The communication control program described in 1. A communication control device for controlling log output processing,
An acquisition unit that acquires information necessary for generating a log, which can be acquired at the time of the call, based on a log output call;
An output unit that outputs the acquired information as log intermediate file information to a predetermined storage area before log generation is started;
A communication control apparatus comprising: A communication control method for controlling log output processing,
Obtaining information necessary to generate a log, which can be acquired at the time of the call, based on the call of the log output;
Outputting the acquired information as log intermediate file information to a predetermined storage area before log generation is started,
A communication control method comprising:

Images