JP2018088224A - Monitoring server, control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mechanism for starting a chat room (examination room) required for occurrence of a failure, and efficiently supporting troubleshooting.SOLUTION: A monitoring server acquiring a log from a plurality of information processors determines whether or not a chat room is registered for the log based on the content of the acquired log, determines whether or not the chat room is newly opened for the log based on a registration state of the chat room for the past log, newly opens the chat room with a user associated with the information processor as a participant user when having determined that the chat room is registered and is newly opened, and registers the log and the opened chat room in association with each other.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a technique for monitoring a log of a computer system.

  It is required to monitor a log indicating an operation status and a failure status output from a computer system, detect the occurrence of the failure early, and take measures to recover from the failure in a short time.

  There is already a system that supports troubleshooting of systems in the network. In the system of Patent Document 1, when a failure message is received, a person in charge is assigned based on past cases and the like to establish a chat channel.

JP 2006-309615 A

  However, in the method described in Patent Document 1, since a person in charge is assigned to each failure message based on past cases and a chat channel is established, there is a possibility that the number of chat rooms may increase more than necessary.

  When dealing with a failure, it is not necessary to negotiate the response if it is a known failure, and in many cases, the response may be advanced based on the knowledge accumulated in the known countermeasures. In Patent Document 1, since a chat channel is established and the response is advanced regardless of whether the failure is known or unknown, an unnecessary chat channel is also established.

  Also, even when the same failure message repeatedly appears in a short time, Patent Document 1 does not compare the failure messages, so a chat channel is opened for each message, and the same chat channel is disturbed. .

  Even if a plurality of failure messages are transmitted, there may be one cause. In such a case, the system of Patent Document 1 can only negotiate the correspondence with the chat channel as different cases and register them as separate cases.

  Accordingly, an object of the present invention is to provide a mechanism for starting up a chat room (examination room) necessary when a failure occurs and efficiently supporting the solution of the failure.

  The present invention is a monitoring server that acquires logs from a plurality of information processing apparatuses, and a first determination unit that determines whether to register a chat room for the log based on the contents of the acquired logs The second determination means for determining whether or not to newly open a chat room for the log based on the registration status of the chat room with respect to the past log, and the chat room is registered and determined to be newly opened A chat room registration unit that newly opens a chat room with a user associated with the information processing apparatus as a participating user and registers the log and the established chat room in association with each other. .

  According to the present invention, it is possible to start up a chat room required when a failure occurs and efficiently support the solution of the failure.

It is a system configuration figure showing an example of composition of a system monitoring portal system. It is a block diagram which shows an example of the hardware constitutions of the information processing apparatus applicable to an operator terminal, an administrator terminal, a system monitoring server, and a monitoring target system server. It is a functional block diagram of a system monitoring portal system. It is a flowchart which shows an example of a system monitoring process. It is a flowchart which shows an example of a log acquisition process. It is a flowchart which shows an example of a log monitoring timeline display process. It is a flowchart which shows an example of a log monitoring timeline display process. It is a flowchart which shows an example of a room display process. It is a flowchart which shows an example of a new room establishment process. It is a flowchart which shows an example of the process at the time of a reference information link click. It is a flowchart which shows an example of a knowledge registration process. It is a flowchart which shows an example of a room integration process. It is a data figure which shows an example of the data group used with a system monitoring portal system. It is a data figure which shows an example of the log table used with a system monitoring portal system. It is a data figure which shows an example of the data group used with a system monitoring portal system. It is a screen image which shows an example of a log monitoring timeline screen (for managers). It is a screen image which shows an example of a log monitoring timeline screen (for operators). It is a screen image which shows an example of the examination room screen. It is a screen image which shows an example of a knowledge reference screen. It is a screen image which shows an example of a knowledge registration screen. It is a screen image which shows an example of a knowledge information search screen. It is a screen image which shows an example of a user search screen (administrator). It is a screen image which shows an example of a user search screen (operator). It is a screen image which shows an example of a user registration screen. It is a screen image which shows an example of an importance definition search screen. It is a screen image which shows an example of an importance definition registration screen.

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

  FIG. 1 is a system configuration diagram showing an example of the configuration of the system monitoring portal system of the present invention.

  In FIG. 1, one or a plurality of monitoring target system servers 104 and a system monitoring server 103 are connected via a LAN 106 so as to communicate with each other. The operator terminal 101 and the administrator terminal 102 are communicably connected to the system monitoring server 103 via the Internet 105.

  In the monitoring target system server 104, the monitoring target system operates and the log is accumulated.

  The system monitoring server 103 is a server that collects logs of the monitoring target system server 104, displays a timeline and a study room on the operator terminal 101 and the administrator terminal 102, and accumulates / provides past knowledge information.

  Hereinafter, the hardware configuration of the information processing apparatus applicable to the system monitoring server 103, the monitoring target system server 104, the operator terminal 101, and the administrator terminal 102 illustrated in FIG. 1 will be described with reference to FIG.

  2 is a block diagram illustrating a hardware configuration of an information processing apparatus applicable to the system monitoring server 103, the monitoring target system server 104, the operator terminal 101, and the administrator terminal 102 illustrated in FIG. It is.

  In FIG. 2, reference numeral 201 denotes a CPU that comprehensively controls each device and controller connected to the system bus 204. Further, the ROM 202 or the external memory 211 is necessary to realize a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS), which is a control program of the CPU 201, or a function executed by each server or each PC. Various programs to be described later are stored.

  A RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program or the like necessary for execution of processing from the ROM 202 or the external memory 211 into the RAM 203 and executing the loaded program.

  An input controller 205 controls input from a keyboard (KB) 209 or a pointing device such as a mouse (not shown). A video controller 206 controls display on a display device such as the display 210. There are various types of displays such as CRTs and liquid crystal displays.

  A memory controller 207 is provided in an external storage device (hard disk (HD)), a flexible disk (FD), or a PCMCIA card slot for storing a boot program, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a CF card memory connected via an adapter.

  A communication I / F controller 208 is connected to and communicates with an external device via a network (for example, the LAN 106 shown in FIG. 1), and executes communication control processing in the network. For example, communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the display 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. Further, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the display 210.

  Various programs to be described later for realizing the present invention are recorded in the external memory 211 and executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, definition files and various information tables used when executing the program are also stored in the external memory 211, and a detailed description thereof will be described later.

  Next, the functional configuration of the system monitoring portal system of the present invention will be described with reference to FIG.

  FIG. 3 is a block diagram illustrating an example of a functional configuration of the system monitoring portal system.

  The system monitoring portal system includes an operator terminal 101, an administrator terminal 102, a system monitoring server 103, and a monitoring target system server 104.

  The operator terminal 101 and the administrator terminal 102 have a display control unit and an operation receiving unit, the display control unit is a functional unit that displays screen display data transmitted from the system monitoring server 103 on the display 210, and the operation receiving unit is a user. This is a functional unit that receives an operation from the server and transmits the result to the system monitoring server 103, and is usually realized by a Web browser.

  The monitored system server 104 has a log output unit. The log output unit is a functional unit that outputs a log indicating the operation status or failure status of its own server or peripheral device periodically or when an event occurs. Then, a function of transmitting to the system monitoring server 103 may be provided.

  The system monitoring server 103 includes a log acquisition unit 301, a log analysis unit 302, a knowledge management unit 303, a study room management unit 304, and a screen display control unit 305.

  The log acquisition unit 301 is a functional unit that acquires logs from the monitoring target system server 104 at regular and irregular intervals. The log analysis unit 302 is a functional unit that analyzes the content of the acquired log and transmits the result to other functional units according to the content of the log. The knowledge management unit 303 is a functional unit that accumulates and manages knowledge such as failure response methods collected and registered by the examination room. The study room management unit 304 is a functional unit that performs operation management related to the study room from newly opened to closed study rooms, and executes integration of a plurality of study rooms in accordance with user operations. The screen display control unit 305 is a functional unit that displays a necessary screen on the operator terminal 101 and the administrator terminal 102 and receives a result of a user operation on the screen. Usually, it is realized by a Web application server function.

  Next, detailed processing of this embodiment will be described with reference to the drawings.

  Hereinafter, the system monitoring process in the system monitoring portal system of this embodiment will be described with reference to FIG.

  FIG. 4 illustrates log acquisition and timer execution for timeline display. This processing is performed by the system monitoring server 103, and logs are periodically acquired from the monitoring target system server 104 based on a timer and displayed on the operator terminal 101 and the administrator terminal 102 as timelines (FIGS. 16 and 17). .

  In step S401, a timer for controlling the timing for acquiring the log from the monitoring target system server 104 is started.

  In step S402, it is determined whether a preset time has elapsed. If it has not elapsed, the determination is repeated until it has elapsed. If the set time has elapsed, the process proceeds to step S403.

  In step S403, a log is acquired from the monitoring target system server 104. The log acquisition process will be described later with reference to FIG.

  In step S404, the acquired log is displayed in a timeline. The timeline display process will be described later with reference to FIGS.

In step S405, it is determined whether or not there is an instruction to end monitoring. If there is an instruction to end monitoring, this flow ends. If there is no monitoring end instruction, the process returns to step S401 and is repeated. The monitoring end instruction is performed when special work such as system maintenance occurs, and basically the monitoring process is continuously performed.
This is the end of the system monitoring process.

  FIG. 5 describes the log acquisition processing in step S403 in FIG.

  This processing flow is executed by the system monitoring server 103.

  In step S <b> 501, log data is acquired from the monitoring target system server 104. The log data includes the date and time when the log is generated, the system name, the log classification, the log content, the URL of the generated Web application, and the like.

  In step S502, detected character string data is acquired from the detected character string table 1300 (FIG. 13A). The detection character string table has a detection character string and a room opening flag as items. Each item is used in the subsequent processing.

  In step S503, the log data and the detected character string are collated.

  In step S504, it is determined whether or not a detected character string is included in the log based on the result in step S503. If it is included, the process proceeds to step S505. If it is not included, nothing is done and this flow is terminated.

In step S505, the log data is written in the log table 1400 (FIG. 14), and this flow is terminated. The log table 1400 has a log CD, date and time, system name, category, content, URL, and TimeLine as items. The log CD is a code for uniquely identifying the log registered in the log table 1400, and TimeLine indicates whether the display processing of the log has been performed (0: unprocessed, 1: processed). For other items, register the corresponding items of log data.
This is the end of the log acquisition process.

  6 and 7, the log monitoring timeline display process in step S404 of FIG. 4 will be described.

  This processing flow is executed by the system monitoring server 103, and the output result is displayed on the operator terminal 101 and the administrator terminal 102.

  In step S601, log data of TimeLine = 0 is acquired from the log table 1400 in the order of log CDs.

  In steps S602 to S621, the obtained log data of TimeLine = 0 (hereinafter referred to as TL log) is repeatedly processed. When there is a TL log, the process proceeds to step S603 and subsequent steps.

  In step S603, the TL log is displayed on the log monitoring timeline. In this embodiment, the display data is sequentially transmitted to the display devices of the operator terminal 101 and the administrator terminal 102 and the display contents are sequentially updated. However, after the display data for one screen is created, the display data is transmitted. It may be displayed on the screen.

  In step S604, a detected character string with a room opening flag of 1 is acquired from the detected character string table 1300.

In step S605, the detected character string acquired in step S604 is collated with the classification of the TL log, and the process proceeds to step S606.

  In step S606, based on the result of step S605, it is determined whether or not the detected character string matches the TL log classification. If there is a match, the process proceeds to step S607, and if not, the process proceeds to step S617.

  In step S607, the log table 1400 is searched, and a log whose system name, category, content, and URL completely match the TL log (hereinafter, the same log) is searched.

  In step S608, if the same log exists as a result of the search in step S607, the process proceeds to step S609, and if not, the process proceeds to step S611.

  In step S609, the knowledge log correspondence table 1520 (FIG. 15C) is searched using the log CD of the same log as a key.

  In step S610, as a result of step S609, if knowledge exists, the process proceeds to step S611, and if not, the process proceeds to step S612.

  In step S611, a reference information link to the knowledge reference screen 2400 (FIG. 19) is displayed as reference information on the timeline. Display examples are shown at 2102 in FIG. 16 and 2202 in FIG.

  In step S612, the error URL of the TL log is collated with the importance level definition table 1310 (FIG. 13B). The importance level definition table 1310 can be edited on the importance level definition registration screen 3100 (FIG. 26), and can be inquired on the importance level definition search screen 3000 (FIG. 25).

  In step S613, it is determined whether or not they match as a result of step S612. If they do not match, the process proceeds to step S614, and if they match, the process proceeds to step S615.

  In step S614, “unknown error” is displayed on the timeline. Display examples are shown at 2104 in FIG. 16 and 2204 in FIG.

  In step S615, room display processing is executed. The room display process will be described later with reference to FIG.

  In step S620, the TimeLine flag of the log table 1400 is changed to 1.

  In step S621, if log data of TimeLine = 0 still exists, the process is repeated from step S602, and if not, the process proceeds to step S622.

  In step S622, the log monitoring timeline screens 2100 (FIG. 16) and 2200 (FIG. 17) are displayed on the operator terminal 101 and the administrator terminal 102 based on the display data created by the above processing.

This is the end of the log monitoring timeline display process.
FIG. 8 illustrates room display processing.

  In step S701, the log / consideration room correspondence table 1330 (FIG. 13D) is referenced using the log CD of the same log as a key to search whether there is a room already opened with the same log as the TL log. At this time, if the system name, classification, content, and URL of the TL log completely match, it is determined that there is an existing room.

  In step S702, the result of step S701 is determined. If there is an existing room, the process proceeds to step S703, and if there is no existing room, the process proceeds to step S707.

  In step S703, the status of the existing room is confirmed with reference to the examination room table 1320 (FIG. 13C).

  In step S704, if the status of the existing room is under consideration (CLOSE = 0) as a result of step S703, the process proceeds to step S705, and if it is closed (CLOSE = 1), the process proceeds to step S706.

  In step S705, the existing room under consideration is automatically displayed. A display example is shown in FIG.

In step S706, a new room is opened. This process will be described later with reference to FIG.
This completes the room display process.
FIG. 9 illustrates the new room opening process.

  In step S801, a new room ID is numbered and registered in the examination room table 1320 (FIG. 13C).

  In step S802, the new room ID is registered in the log / consideration room correspondence table 1330 (FIG. 13D) associated with the log CD.

  In step S803, participating users are acquired from the chat user table 1340 (FIG. 13E) using the system name of the target log as a key. The chat user table 1340 can be inquired and edited on the administrator user search screen 2700 (FIG. 22). On the user search screen 2800 for the operator, only inquiry is possible. The user registers on the user registration screen 2900 (FIG. 24).

In step S804, a new chat room is displayed on the operator terminal 101 and the administrator terminal 102. A display example is shown in FIG.
This completes the new room opening process.

  In FIG. 10, the process at the time of clicking the reference information link displayed on the log monitoring timeline screen (FIGS. 16 and 17) in step S611 will be described.

  In step S901, a click on the reference information links (2102, 2202) on the log monitoring timeline screens 2100 and 2200 is detected.

  In step S902, from the knowledge table 1510 (FIG. 15B), the knowledge log correspondence table 1520 (FIG. 15C), the knowledge / person-in-charge correspondence table 1530 (FIG. 15D), the knowledge CD, the knowledge registration date, Get title, correspondence, log contents, person in charge.

  In step S903, the latest knowledge among the acquired knowledge is displayed on the knowledge reference screen 2400 (FIG. 19). Past knowledge is displayed as link information at the bottom of the page (2408).

  This completes the processing when the reference information link is clicked.

  In FIG. 11, the knowledge registration process will be described.

  In step S1001, it is determined whether a click on the knowledge registration button (2307) on the examination room screen (FIG. 18) has been detected. Step S1001 is repeated until detection, and if detected, the process proceeds to step S1002.

  In step S1002, a knowledge registration screen 2500 (FIG. 20) is displayed.

  In step S1003, when the click of the knowledge registration button (2307) is detected, the process proceeds to step S1004.

  In step S1004, it is determined whether there is a chat close check (2507) on the knowledge registration screen 2500. If it is checked, the process proceeds to step S1005, and if it is not checked, the process proceeds to step S1006.

  In step S1005, CLOSE = 1 is registered in the examination room table 1320 (FIG. 13C).

  In step S1006, the knowledge table 1510 (FIG. 15B), the knowledge / log correspondence table 1520 (FIG. 15C), and the knowledge / person-in-charge correspondence table 1530 (FIG. 15D) are entered on the knowledge information registration screen. Registered knowledge information.

The registered knowledge can be searched on the knowledge information search screen 2600 (FIG. 21).
This completes the knowledge registration process.
In FIG. 12, the room integration process will be described.

  In step S1101, the administrator's click on the integration button 2109 on the log monitoring timeline screen 2100 (FIG. 16) is detected. Step S1101 is repeated until it is detected.

  In step S1102, all examination rooms under examination to be integrated are closed. Specifically, CLOSE = 1 in the examination room table 1320 (FIG. 13C) is set.

  In step S1103, a new room ID is assigned and assigned to the room after integration, and is registered in the examination room table 1320 as CLOSE = 0.

  In step S1104, the log CD of the room before integration is acquired from the log / consideration room correspondence table 1330 (FIG. 13D).

In step S1105, the correspondence between all log CDs acquired in step 1104 and the room ID after integration is registered in the log / review room correspondence table 1330.
This completes the room integration process.

  Next, an example of the data table used in this embodiment will be described with reference to FIGS. 13, 14, and 15. FIG.

  FIG. 13A shows a detected character string table 1300, which includes a detected character string and a room opening flag. When the detected character string registered in this table is included in the log error category, the log is registered in the log table (FIG. 14) and displayed on the timeline. Further, for a log including a detection character string whose room opening flag is 1, knowledge display and room opening are performed.

  FIG. 13B shows an importance level definition table 1310, which includes a URL, a category, and contents. In this table, URLs, categories, and contents with high importance that need to be opened and examined even if no knowledge exists are registered.

  FIG. 13C shows a study room table 1320, which includes a study room ID and a CLOSE flag. Data is created when the examination room is opened, and if the CLOSE flag is 0, it is opened and 1 means closed. At the time of room integration, all rooms before integration are closed, a new examination room ID is assigned, and a new room is opened.

  FIG. 13D shows a log / review room correspondence table 1330. Consists of log CD and study room ID. One log room ID is linked to one log CD. At the time of room integration, the integrated room ID is registered for all log CDs to be integrated.

  FIG. 13E shows a chat user table 1340, in which a person in charge corresponding to each system to be automatically invited when the examination room is opened is registered in advance. It consists of a system name, a user CD, and a user name.

  FIG. 14 shows a log table 1400, which includes a log CD, date and time, system name, category, content, URL, and TimeLine flag. All logs having classifications included in the detected character string table 1300 are written and displayed on the log monitoring timeline screens 2100 and 2200 (FIGS. 16 and 17).

  Log CD is the log CD, date and time is the log output date and time described in the log obtained from the server, system name is the system name of the log output source, category is the log error category, content is the log content, URL is included in the log The location URL and TimeLine are set to TimeLine = 1 for logs displayed on the log monitoring timeline screens 2100 and 2200, and 0 for undisplayed logs.

  FIG. 15A shows a chat table 1500 in which chat contents in the study room are registered in real time. It is composed of a study room ID, a sequence number (SEQ), a user CD, a speech date and time, and a speech content.

  FIG. 15B shows a knowledge table 1510, which includes a knowledge CD, a knowledge registration date, a title, and error handling contents.

  FIG. 15C shows a knowledge log correspondence table 1520, which includes a knowledge CD and a log CD.

FIG. 15D shows a knowledge / person-in-charge correspondence table 1530, which includes a knowledge CD and a correspondence person-in-charge CD.
This is the end of the description of the data table.

  Next, an example of a screen provided to the user in the present embodiment will be described with reference to FIGS.

  FIG. 16 is a log monitoring timeline screen 2100 for the administrator.

  The date / time, system name, category, content, and URL of the log acquired from the log table 1400 are displayed on the timeline 2101.

  Buttons 2105, 2106, and 2107 are arranged at the bottom of the timeline 2101, and a study room list 2108 is displayed below the buttons 2105, 2106, and 2107.

  The reference information display 2102 in step S611 is displayed on the right side of the corresponding log. If this is clicked, it will change to the knowledge reference screen 2400 (FIG. 19).

  When a room is displayed in step S705 or step S804, “consideration room” is displayed on the right side of the corresponding log (2103). The number in the parenthesis is the number of participants in the study room.

  The unknown error display 2104 in step S614 is displayed on the right side of the corresponding log. When this is clicked, a room for examination is opened through the room display process (FIG. 8), and the number of participants is displayed in parentheses.

  When the importance level search button 2105 is clicked, the screen changes to the importance level definition search screen 3000 (FIG. 25).

  When a knowledge information search button 2106 is clicked, a transition is made to a knowledge information search screen 2600 (FIG. 21).

  If a user search / registration button 2107 is clicked, a transition is made to the user search screen 2800 (FIG. 23).

  A list of study rooms is displayed in the study room list 2108, and the rooms under study are arranged in the upper order and the closed rooms are arranged in the lower order, and are arranged in descending order of the participants. There is an integration button 2109 at the top of the room list, and the rooms selected by the check box 2110 can be integrated.

  The room under consideration is displayed as an under-consideration button 2111, and the room after closing is displayed as a closed 2112. When the room is clicked, an examination room screen 2300 (FIG. 18) can be displayed.

  FIG. 17 shows a log monitoring timeline screen 2200 for the operator.

  The date / time, system name, category, content, and URL of the log acquired from the log table 1400 are displayed on the timeline 2201.

  A knowledge information search button 2205 is arranged at the bottom of the timeline 2201, and a study room list 2206 is further displayed therebelow.

  The reference information display 2202 in step S611 is displayed on the right side of the corresponding log. If this is clicked, it will change to the knowledge reference screen 2400 (FIG. 19).

  When a room is displayed in step S705 and step S804, “consideration room” is displayed on the right side of the corresponding log (2203). The number in the parenthesis is the number of participants in the study room.

  The unknown error display 2204 in step S614 is displayed on the right side of the corresponding log. When this is clicked, a room for examination is opened through the room display process (FIG. 8), and the number of participants is displayed in parentheses.

  When a knowledge information search button 2205 is clicked, a transition is made to a knowledge information search screen 2600 (FIG. 21).

  In the examination room list 2206, examination rooms under examination are displayed in descending order of the participants.

By clicking on the examination button 2207, the examination room screen 2300 (FIG. 18) can be displayed.
FIG. 18 shows a study room screen 2300.

  In the upper part of the screen, the examination room ID 2301 being displayed, the examination log 2302, and the participants 2303 are displayed.

  Participants' remarks are displayed in a chat window 2304, and rooms before and after integration of study rooms are displayed in tabs.

  The content of the message is entered in the text box 2305, and when a button 2306 for speaking is clicked, it is registered in the chat table 1500 and displayed in the chat window 2304 of all participants. When a closed room is displayed, the text box 2305 and the speak button 2306 are disabled.

  When the knowledge registration button 2307 is clicked, a transition is made to the knowledge registration screen 2500 (FIG. 20).

When the member invitation button 2308 is clicked, the administrator transitions to a user search screen 2700 (FIG. 22) and the operator transitions to a user search screen 2800 (FIG. 23).
FIG. 19 shows a knowledge reference screen 2400.

  A knowledge CD 2401, a title 2402, a knowledge registration date 2404, and correspondence contents 2405 are acquired from the knowledge table 1510 and displayed.

  The log content is acquired from the log table 1400 from the log CD associated with the knowledge CD from the knowledge log correspondence table 1520 and displayed (2403).

  The correspondence person in charge is acquired from the knowledge person-in-charge correspondence table 1530 from the correspondence person ID associated with the knowledge CD and displayed (2406).

  The study room ID is acquired from the log / consideration room correspondence table 1330 using the log CD associated with the knowledge CD as a key, and the chat contents of the chat table 1500 are displayed (2407).

  In the chat history 2407, when there are examination histories of a plurality of rooms, tabs are divided and displayed.

  If there is knowledge of the same log, a link to the knowledge reference screen 2400 (FIG. 19) is displayed (2408).

  FIG. 20 shows a knowledge registration screen 2500, which transitions when a knowledge registration button 2307 on the examination room screen 2300 (FIG. 18) is clicked. Alternatively, when a new registration button 2606 is clicked on the knowledge information search screen 2600 (FIG. 21), a transition is made.

  The knowledge registration date and time text box 2501 is used to input the knowledge registration date and time.

  In the knowledge title text box 2502, a knowledge title is entered.

  Although the error content text box 2503 and the corresponding person in charge text box 2504 are displayed with information input in advance, they can be edited. However, when a transition is made by clicking the new registration button 2606 on the knowledge information search screen 2600 (FIG. 21), a blank is displayed.

  In the error handling content text box 2505, the handling content and result are input.

  The chat history 2506 includes a check box 2507 for confirming chat history close and a chat content display 2508. A check box 2507 selects whether to close the latest room under consideration. If there is a closed examination room before integration, the chat content display 2508 is displayed with the second and subsequent tabs.

  When a registration button 2509 is clicked, these pieces of information are registered in the knowledge table 1510, the knowledge / log correspondence table 1520, and the knowledge / person-in-charge correspondence table 1530.

When an update button 2510 is clicked, the knowledge table 1510, the knowledge / log correspondence table 1520, and the knowledge / person in charge correspondence table 1530 are updated.

  FIG. 21 transitions when the knowledge information search buttons 2106 and 2205 on the log monitoring timeline screens 2100 and 2200 (FIGS. 16 and 17) of the administrator are clicked on the knowledge information search screen 2600.

  Enter date 2601, error content 2602, person in charge 2603, URL 2604 and click search button 2605 to search knowledge from knowledge table 1510, knowledge / log correspondence table 1520, knowledge / person in charge correspondence table 1530, and display the result in list 2607. indicate.

  A new registration button 2606 is displayed only to the administrator, and when clicked, a transition is made to the knowledge registration screen 2500 (FIG. 20).

  In the knowledge displayed in the list 2607, a reference button 2608, an update button 2609, and a delete button 2610 are displayed.

  When a reference button 2608 is clicked, the display changes to a knowledge reference screen 2400 (FIG. 19).

When the update button 2609 is clicked, a transition is made to the knowledge registration screen (FIG. 25).

When the delete button 2610 is clicked, the knowledge information is deleted from the knowledge table 1510, the knowledge / log correspondence table 1520, and the knowledge / person-in-charge correspondence table 1530.

  FIG. 22 shows a user search screen 2700 for the administrator. The user clicks the user search / registration button 2107 on the log monitoring timeline screen 2100 (FIG. 16) of the administrator, or the administrator clicks the member on the examination room screen 2300 (FIG. 18). When the invite button 2308 is clicked, a transition is made.

  When search conditions are entered in the target system text box 2701, target user text box 2702, and target user CD text box 2703 and the search button 2704 is clicked, the chat user table 1340 is searched, and the result is displayed in the search result list 2706.

  When a new registration button 2705 is clicked, the screen shifts to a user registration screen 2900 (FIG. 24).

  The search result list 2706 displays a system name, a user name, and a user CD, and an invite button 2707, an update button 2708, and a delete button 2709 are displayed to the right of each data.

  When a transition is made by clicking the user search / registration button 2107 on the administrator's log monitoring timeline screen 2100 (FIG. 21), the invitation button 2707 is invalid, and only the update button 2708 and the delete button 2709 are valid.

  When the administrator transitions from the member invitation button 2308 on the examination room screen 2300 (FIG. 18), only the invitation button 2707 is valid.

  When the invite button 2707 is clicked, the user is invited and the screen returns to the examination room screen 2300 (FIG. 18).

  When an update button 2708 is clicked, the screen shifts to a user registration screen 2900 (FIG. 24).

  When a delete button 2709 is clicked, the user data is deleted from the chat user table 1340.

  FIG. 23 shows a user search screen 2800 for the operator, and transitions are made when the operator clicks the member invitation button 2308 on the examination room screen 2300 (FIG. 18).

  When a search condition is input to the target system text box 2801, the target user text box 2802, and the target user CD text box 2803 and the search button 2804 is clicked, the chat user table 1340 is searched, and the result is displayed in the search result list 2805.

  The search result list 2805 displays a system name, a user name, and a user CD, and an invitation button 2806 is displayed on the right of each data.

  Clicking on the invite button 2806 invites the user and returns to the study room screen 2300 (FIG. 18).

  FIG. 24 shows a user registration screen 2900, which transitions when the administrator clicks the new registration button 2705 on the user search screen 2700 (FIG. 22).

  When the administrator transitions from the new registration button 2705 on the user search screen 2700, only the registration button is enabled, and when the administrator transitions from the update button 2708, only the update button is enabled.

  When the registration contents are input into the target system text box 2901, the target user text box 2902, and the target user CD text box 2903 and the registration button 2904 or the update button 2905 is clicked, the user information is registered / updated in the chat user table 1340.

  FIG. 25 shows an importance level definition search screen 3000, which transitions when an importance level search button 2105 is clicked on the log monitoring timeline screen 2100 for the administrator (FIG. 16).

  When a search condition is entered in the target URL text box 3001, the category pull-down 3002, and the error content text box 3003 and a search button 3004 is clicked, the importance definition table 1310 is searched, and the result is displayed in the list 3006.

  If a new registration button 3005 is clicked, a transition is made to the importance definition registration screen 3100 (FIG. 26).

  The search result list 3006 includes target URLs, classifications, and error contents, and an update button 3007 and a delete button 3008 are displayed on the right side of each data.

  When an update button 3007 is clicked, the importance level definition registration screen 3100 (FIG. 26) is entered.

  Clicking a delete button 3008 deletes the data from the importance definition table 1310.

  FIG. 26 shows an importance level definition registration screen 3100. The transition is made by clicking the new registration button 3005 or the update button 3007 on the importance level definition search screen 3000 (FIG. 25).

  When the transition is made from the new registration button 3005 on the importance level definition search screen 3000, only the registration button 3104 is validated, and when the transition is made from the update button 3007, only the update button 3105 is validated.

When information is input to the target URL text box 3101, the category pull-down 3102, and the error content text box 3103 and the registration button 3104 or the update button 3105 is clicked, the information is registered in the importance definition table 1310.
This is the end of the description of the screen.

  As described above, it becomes possible to set up a study room necessary when a failure occurs. In addition, when similar study rooms exist, a plurality of study rooms can be integrated into one study room by a user operation.

  It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The program according to the present invention is a program that allows a computer to execute the processing methods of the flowcharts shown in FIGS. 4 to 5. Is remembered. The program according to the present invention may be a program for each processing method of each apparatus shown in FIGS.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by executing the reading.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk, solid state drive, or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention.

  In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

101 Administrator terminal 102 Administrator terminal 103 System monitoring server 104 Monitored system server 105 Internet 106 LAN

Claims (7)

A monitoring server that acquires logs from a plurality of information processing devices,
First determination means for determining whether to register a chat room for the log based on the content of the acquired log;
Second determination means for determining whether or not to newly open a chat room for the log based on a registration status of the chat room for a past log;
If it is determined that the chat room is registered and newly opened, a chat room is newly opened with the user associated with the information processing apparatus as a participating user, and the log and the opened chat room are registered in association with each other. And a chat room registration means.   2. The monitoring server according to claim 1, wherein the second determination unit determines that a chat room is not newly opened when a chat room has already been registered with respect to a log having the same content in the past. . Knowledge recording means for recording the recorded content of the chat room in a storage device as knowledge corresponding to the log;
The monitoring server according to claim 1, further comprising: a knowledge display unit that displays knowledge about a past log when it is determined by the second determination unit that a chat room is not newly opened.   The chat room registration unit registers the log and a chat room corresponding to the past log in association with each other when the second determination unit determines that the chat room is not newly opened. The monitoring server according to any one of claims 1 to 3. It has a means to integrate multiple chat rooms and create a new chat room.
5. The registration unit according to claim 1, wherein the registration unit registers the log associated with the chat room before integration in association with the new chat room. 6. Monitoring server. A monitoring server control method for acquiring logs from a plurality of information processing devices,
A first determination step in which the first determination means determines whether to register a chat room for the log based on the content of the acquired log;
A second determination step, wherein the second determination means determines whether or not to newly open a chat room for the log based on the registration status of the chat room with respect to a past log;
When it is determined that the chat room registration unit registers the chat room and establishes a new chat room, a chat room is newly opened with a user associated with the information processing apparatus as a participating user, and the log and the chat room opened And a chat room registration step of registering in association with each other. A program that can be executed by a monitoring server that acquires logs from a plurality of information processing devices,
The monitoring server,
First determination means for determining whether to register a chat room for the log based on the content of the acquired log;
Second determination means for determining whether or not to newly open a chat room for the log based on a registration status of the chat room for a past log;
If it is determined that the chat room is registered and newly opened, a chat room is newly opened with the user associated with the information processing apparatus as a participating user, and the log and the opened chat room are registered in association with each other. A program characterized by functioning as a chat room registration means.

Images