Storage device, control method thereof, and program

Abstract

To solve the problem in which: there was no mechanism allowing a manager to promptly and easily check a log which could not be transferred when transfer of a log message to a server failed in the past.SOLUTION: An NAS 101 includes the steps of: notifying a prescribed notification destination of unsuccessful transfer of a log message when an attempt to transfer the message fails (NO in S504); notifying the prescribed notification destination of a path of a link on a shared holder of a log containing an unsuccessfully transferred log message and information for identifying the log message (S510 and S511) when a link to the log is created on the shared holder (YES in S508); and notifying the prescribed notification destination of access information to the screen referencing the log and information for identifying the log message (S509 and S511) when a link to the log is not created on the shared holder (NO in S508).SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to a storage device connectable to a network, a control method thereof, and a program. [Background technology]

[0002] Among devices that can be connected to a network, such as routers and NAS (Network Attached Storage), there are some that have the function of sending log messages recorded by the device to a server using the syslog mechanism. Traditionally, syslog has been used to send and receive log messages using UDP (User Datagram Protocol), which has problems with reliability. However, in recent years, syslog servers such as rsyslog, which extend the functions of conventional syslog to enable log messages to be exchanged using TCP (Transmission Control Protocol), have become widespread. In addition, in order to improve the reach of log messages to be sent, there is also a technology that confirms the connection with the server using an echo request and an echo response, and then sends the log message (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2010-213194 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional devices that transfer log messages to a server, there was no mechanism for administrators to quickly and easily check the logs that could not be transferred if the transfer of the log messages to the server failed. Therefore, even if some kind of abnormality occurred in the server receiving the log messages, it may not be noticed, and the response may be delayed, resulting in a long delay in the transfer of log messages.

[0005] The present invention has been made to solve the above problems, and aims to provide a mechanism for notifying a failure to transfer a log message when a server that receives logs has an abnormality and the log message cannot be transferred, and for making it easy to check the log that could not be transferred. [Means for solving the problem]

[0006] The present invention is a storage device connectable to a network, comprising: a recording means for recording a generated log message as a log; a creation means capable of creating a link to the log in a shared folder; a transfer means for transferring the log message to a specified transfer destination; and a notification means for notifying a specified notification destination if transfer of the log message fails, wherein, if a link to the log has been created in the shared folder, the notification means notifies a path to a link on the shared folder of a log containing the log message whose transfer failed and information identifying the log message; and, if a link to the log has not been created in the shared folder, notifies access information to a screen for referencing the log and information identifying the log message. Effect of the Invention

[0007] According to the present invention, when a log message cannot be transferred due to an abnormality in the server receiving the log, the failure to transfer the log message can be notified, and the log that could not be transferred can be easily checked. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of the overall configuration of a system according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a block diagram showing an example of the hardware configuration of a NAS. [Diagram 3] FIG. 2 is a block diagram showing an example of a software configuration of a NAS. [Figure 4A] FIG. 13 is a diagram showing an example of a NAS management screen (login screen). [Figure 4B] FIG. 13 is a diagram showing an example of a NAS management screen (dashboard screen). [Figure 4C] FIG. 13 is a diagram showing an example of a NAS management screen (log management and setting screen). [Figure 4D] FIG. 13 is a diagram showing an example of a NAS management screen (log setting change screen). [Diagram 5] 6 is a flowchart showing an example of a log transfer process in the first embodiment. [Figure 6] FIG. 13 is a diagram showing an example of a log recorded in a NAS. [Figure 7] FIG. 11 is a diagram showing an example of a transfer failure notification in the first embodiment. [Figure 8] FIG. 11 is a diagram showing an example of a transfer success notification in the first embodiment. [Figure 9] 13 is a flowchart showing an example of a log transfer process in the second embodiment. [Figure 10] FIG. 11 is a diagram showing an example of a transfer failure log message writing file in the second embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a transfer failure notification in the second embodiment. [Figure 12] 13 is a flowchart showing an example of a log transfer process in the third embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a transfer failure notification in the third embodiment. [Figure 14] FIG. 13 is a diagram showing an example of a transfer failure notification in the third embodiment. [Figure 15] FIG. 13 is a diagram showing an example of a transfer success notification in the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. [First embodiment] FIG. 1 is a diagram showing an example of the overall configuration of a system according to an embodiment of the present invention. In the system of this embodiment, a NAS 101, a log collection server 102, and an administrator PC 103 are connected to each other so as to be able to communicate with each other via a network 100. In this embodiment, each of the devices is configured to have one device, but a plurality of devices may be connected to the network 100.

[0010] The NAS 101 is a storage device that can be connected to a network and has the function of storing and managing files via the network. The NAS 101 provides a storage service that manages and shares various types of data, such as documents and images. With this storage service, a "personal folder" that can only be used by the user himself / herself and a "shared folder" that can be used jointly by users can be set up and these folders can be used to store data. By using the shared folder, data can be easily shared between users.

[0011] The log collection server 102 is a device having a function of receiving log messages sent by the NAS 101 or a network device (not shown) and centrally monitoring and storing the log messages.

[0012] The administrator PC 103 is a PC (Personal Computer) used by an administrator who manages the entire system according to this embodiment, or at least the NAS 101, to perform settings and maintenance work on the NAS 101. In the following explanation, the administrator refers to the administrator of the NAS 101. The administrator PC 103 can access the NAS 101 to perform settings and the like for the NAS 101. In addition, the administrator PC 103 can access the administrator's personal folders and shared folders in the NAS 101 to view and save data.

[0013] FIG. 2 is a block diagram showing an example of the hardware configuration of the NAS 101 shown in FIG. The CPU 201 executes control programs and application programs stored in the ROM 202 and storage device 204 to control the functions of the hardware blocks connected to the bus 200 and the NAS 101 . The ROM 202 is a memory dedicated to reading data, and stores, for example, the basic control program for the NAS 101 . The RAM 203 is a memory from / to which data can be read / written, and is used as a working memory for the CPU 201, for example.

[0014] The storage device 204 is used as a storage area for control programs and application programs that run on the NAS 101, as well as temporary data during the execution of each program and permanent data. The storage device 204 is also used as a storage area for saving files placed by users who use the NAS 101. The storage device 204 can be configured, for example, with a hard disk drive (HDD) or a solid state drive (SSD).

[0015] The communication device 205 connects the NAS 101 to the network 100, enabling data communication between the devices in the system according to this embodiment. The input device 206 is an operation unit for accepting input operations by the administrator of the NAS 101, and is, for example, a keyboard, a mouse, a hard key, or a touch panel. The display device 207 is a device for displaying the setting screen and status information of the NAS, and is, for example, a liquid crystal display or a touch panel. The administrator of the NAS 101 can give instructions via the input device 206 in accordance with the contents displayed on the display device 207, check the status and settings of the NAS 101, give setting instructions, and so on.

[0016] FIG. 3 is a block diagram showing an example of the software configuration of the NAS 101. As shown in FIG. The software configuration shown in FIG. 3 is realized by the CPU 201 reading out a program stored in the ROM 202 or the storage device 204 into the RAM 203 and executing it.

[0017] The file management unit 301 corresponds to a file system, and manages and controls the storage state in the storage device 204, and manages and controls the input and output of files stored in the NAS 101 and files used internally by the NAS 101. The file management unit 301 provides the above-mentioned storage services.

[0018] The log recording unit 302 writes (records as a log) log messages related to the operation of the NAS 101 that are generated on the NAS 101 into a log file managed by the file management unit 301 . The setting management unit 303 manages the settings of the NAS 101 .

[0019] The log transfer unit 304 transfers the log message recorded by the log recording unit 302 to the log collection server 102 in accordance with the settings of the setting management unit 303. If the transfer of the log message fails or succeeds, the log transfer unit 304 requests a notification from the notification unit 305 in accordance with the settings of the setting management unit 303 as necessary. In response to a request from the log transfer unit 304, the notification unit 305 issues a notification to the set notification destination according to the settings made by the setting management unit 303.

[0020] A management application for configuring settings related to the logs of the NAS 101 will be described below with reference to FIGS. 4A to 4D. 4A to 4D are diagrams showing an example of a user interface screen (management screen) of a management application that is displayed by the setting management unit 303 of the NAS 101 for the administrator of the NAS 101. FIG.

[0021] The management application is a web application executed by the setting management unit 303, and the screens shown in Fig. 4A to Fig. 4D are displayed on the web browser by the setting management unit 303 responding to an access from the web browser running on the administrator PC 103, for example. The management application also accepts input to these screens via the web browser. However, this is not limiting, and an application program installed on the administrator PC 103 may display these screens and accept input. Alternatively, these screens may be displayed on the display device 207 provided in the NAS 101, and input may be accepted from the input device 206.

[0022] FIG. 4A is a login screen 400 for logging into the management application. In this embodiment, in order to view or set information on the NAS 101 using the management application, it is assumed that a predetermined administrator's login ID and password must be entered on the login screen 400 .

[0023] The administrator enters a login ID in login ID input field 401, a password in password input field 402, and presses OK button 403. When setting management unit 303 detects that OK button 403 has been pressed, it checks whether the login ID and password belong to a legitimate administrator, and if it determines that they belong to a legitimate administrator, it displays the dashboard screen of FIG.

[0024] FIG. 4B shows the dashboard screen that is displayed after logging in to the management application. The dashboard screen shown in FIG. 4B has a menu area 411 and a dashboard area 410. A menu area 411 is an area that displays a list of the menus of the management application, and is similarly displayed on the screens shown in Figs. 4C and 4D, which will be described later.

[0025] In the menu area 411, 412 to 416 are menu items, and when pressed, transition to the screen of that menu takes place. For example, when the dashboard menu 412 is pressed, transition to the dashboard screen of FIG. 4B takes place. When the network setting menu 413 is pressed, transition to a network setting screen (not shown) takes place. When the file sharing setting menu 414 is pressed, transition to a file sharing setting screen (not shown) takes place. When the storage setting menu 415 is pressed, transition to a storage setting screen (not shown) takes place. When the log management and setting menu 416 is pressed, transition to a log management and setting screen shown in FIG. 4C (described later) takes place.

[0026] In the dashboard area 410, information relating to the operating status of the NAS 101 is displayed, and the contents of the status to be notified, the transition of the CPU usage rate, and the like can be confirmed.

[0027] FIG. 4C shows the log management and setting screen for checking and viewing the log setting information. The log management / setting screen has a menu area 411 and a log management / setting area 420 .

[0028] The log management / settings area 420 displays setting information related to logs and buttons for viewing logs. The log transfer settings 421 indicate a setting as to whether or not logs recorded by the NAS 101 are to be sent to the log collection server 102. The transfer destination settings 422 indicate a setting of the IP address of the log collection server 102 to which the logs are to be transferred when logs are transferred. The transfer failure notification settings 423 indicate whether or not to notify by electronic mail (hereinafter referred to as "email") if the log transfer fails. The notification destination settings 424 indicate a setting of the email address to which the notification is to be sent when a transfer failure is to be notified. A link to log setting 425 indicates whether or not a link for accessing a log file is to be created in a shared folder. A shared folder setting 426 indicates a setting of the path of the shared folder in which the link is to be created when a link to a log is to be created. The settings indicated by 421 to 426 are stored in the storage device 204 under the management of the setting management unit 303, for example.

[0029] The log view button 427 is a link for displaying the log. When the log view button 427 is pressed, the setting management unit 303 reads the log and displays it on the web browser. However, this is not limited to this, and an application associated with the format of the log file may be started and displayed. When the close button 429 is pressed, the screen transitions to the dashboard screen of FIG. 4B, for example. When the change button 428 is pressed, the screen transitions to a log setting change screen shown in FIG. 4D.

[0030] FIG. 4D shows a log setting change screen for changing the log settings. The log setting change screen has a menu area 411 and a log setting change area 440 . The log setting change area 440 displays settings related to logs. Reference numeral 441 denotes a checkbox for setting the log transfer setting 421 as to whether or not to transfer the log. When the checkbox 441 is checked, the log transfer setting 421 is set to "Yes", and when the checkbox 441 is unchecked, the log transfer setting 421 is set to "No".

[0031] Reference numeral 442 denotes an input field for setting the transfer destination setting 422 when transferring logs, and becomes configurable when the check box 441 is checked. In the transfer destination input field 442, the IP address of the log collection server 102 is basically specified, but the host name of the log collection server 102 may be specified if name resolution is possible.

[0032] A check box 443 is used to set the transfer failure notification setting 423 as to whether or not to notify of a transfer failure. When the check box 443 is checked, the transfer failure notification setting 423 is set to "Yes", and when the check box 443 is unchecked, the transfer failure notification setting 423 is set to "No".

[0033] Reference numeral 444 denotes an input field for setting the notification destination setting 424 when notifying of a transfer failure, and this can be set by checking the check box 443. In this embodiment, the notification method is email, and the email address of the notification destination is set in 444. Although not shown in the figure because these are general settings, settings such as the email server required for email transmission are set on a screen displayed from the network setting menu 413.

[0034] A check box 445 is used to set whether or not to create a link to a log in the link setting 425. When the check box 445 is checked, the link setting 425 to a log is set to "create", and when the check box 445 is unchecked, the link setting 425 to a log is set to "do not create".

[0035] Reference numeral 446 denotes an input field for setting the shared folder setting 426, which is the path of the shared folder to which the link is to be created when a link to a log is to be created, and this can be set when the check box 445 is checked. The path of the shared folder is specified as the path of a folder that is set for sharing on the NAS 101, and a link to the log is created in the folder of the path specified here. In this embodiment, if the path of the specified shared folder is "\\192.168.1.5\share\log", the link to the log is created as "\\192.168.1.5\share\log\log.lnk". In this case, "192.168.1.5" is the IP address of the NAS 101. In this embodiment, the link to the log is created as a link to the log file itself, but it may be created as a link to the folder in which the body of the log file is located. Alternatively, a specified folder may be created in the specified shared folder, and the link may be created under that folder.

[0036] When the OK button 448 is pressed, the settings entered on this screen are reflected and the screen transitions to the log management and setting screen of Fig. 4C. When the Cancel button 449 is pressed, the settings entered are not reflected and the screen transitions to the log management and setting screen of Fig. 4C.

[0037] 5 is a flowchart showing an example of processing when the NAS 101 of the first embodiment transfers a log to the log collection server 102. The processing of this flowchart is executed every time a log message to be recorded occurs when the log transfer setting 421 is set to "Yes". Each step shown in FIG. 5 is realized by the CPU 201 of the NAS 101 reading into the RAM 203 a program corresponding to each software component shown in FIG. 3, which is stored in the ROM 202 or the storage device 204, and executing the program.

[0038] In S501, the log transfer unit 304 initializes a transfer failure flag, which indicates that the log transfer is failing, to “false.” The transfer failure flag is held in the RAM 203, for example.

[0039] Next, in S502, the log transfer unit 304 acquires the log message to be transferred from the log recording unit 302. FIG. 6 is a diagram showing an example of a log recorded in the NAS 101. As shown in FIG. In this embodiment, the log message corresponds to, for example, one line of data in a log such as that shown in Fig. 6 recorded by the log recording unit 302. For example, "Feb 10 15:03:25 xxxxx" in 601 is a log message. Similarly, 602 to 606 are also log messages.

[0040] In "Feb 10 15:03:25 xxxxx" in the log message 601, the "Feb 10 15:03:25" portion is the date and time when the log was recorded. In this example, the log message 601 indicates that it was recorded on February 10th at 15:03:25. It is possible to identify the log message by this log recording date and time. In this embodiment, it is assumed that log message 601 is a log message when a transfer that had been successful up until that point fails, and furthermore, it is assumed that thereafter, transfers continue to fail until log message 605 at 15:25:40 on February 10, and that transfers become successful from the next log message 606 at 15:25:41 on February 10.

[0041] Next, in S503, the log transfer unit 304 transfers the log message acquired in S502 to the log collection server 102. Next, in S504, the log transfer unit 304 judges whether the transfer was successful. If the transfer was successful (YES in S504), the log transfer unit 304 advances the process to S512. The process from S512 onwards will be described later. On the other hand, if the transfer has failed (NO in S504), the log transfer unit 304 advances the process to S505.

[0042] In S505, the log transfer unit 304 judges whether the transfer failure notification setting 423 is set to "Yes." If the transfer failure notification setting 423 is set to "No" (NO in S505), the log transfer unit 304 returns the process to step S502 and controls to transfer the next log message. On the other hand, if the transfer failure notification setting 423 is set to "Yes" (YES in S505), the log transfer unit 304 advances the process to S506.

[0043] In S506, the log transfer unit 304 determines whether the transfer failure flag is "true." If the transfer failure flag is already "true" (YES in S506), the log transfer unit 304 returns the process to S502 and controls to transfer the next log message. On the other hand, if the transfer failure flag is "false" (NO in S506), the log transfer unit 304 advances the process to S507.

[0044] In S507, the log transfer unit 304 sets the transfer failure flag to "true" to indicate that the log transfer is failing. Next, in S508, the log transfer unit 304 requests the notification unit 305 to notify the transfer failure, and the notification unit 305 judges whether the link setting 425 to the log is set to "create." If the link setting 425 to the log is set to "not create" (NO in S508), the notification unit 305 advances the process to S509.

[0045] In S509, the notification unit 305 creates a transfer failure notification mail as shown in FIG. FIG. 7A is a diagram showing an example of a notification email created by the notification unit 305 in S509 of FIG. 5, and corresponds to a transfer failure notification in the case where a link to the log is not created in the shared folder. In the email in FIG. 7(a), 701 is a message indicating that the transfer has failed.

[0046] 702 is a character string indicating the date and time of the log message 601 whose transfer failed. This functions as information for identifying the log message, and is entered to make it easier to identify which log message failed to be transferred when viewing the log. When the administrator receives a transfer failure notification email and checks the log, if the administrator has not yet received a transfer success notification email (described below), he or she can determine that the log message after the date and time entered in 702 is the log message whose transfer failed.

[0047] Reference numeral 703 denotes a uniform resource locator (URL) for executing log viewing, which is described to facilitate confirmation of a log message for which transfer has failed, and functions as access information for a screen for referencing the log. When the URL for executing log viewing 703 is accessed with a web browser, the setting management unit 303 displays the login screen 400 if the user has not yet logged in to the management application. Then, the user can log in on the displayed login screen 400, or if the user has already logged in, the setting management unit 303 displays a screen similar to that displayed when the log viewing button 427 is pressed.

[0048] Returning now to the explanation of the flowchart in FIG. On the other hand, if the link setting 425 to the log is set to "create" (YES in S508), the notification unit 305 advances the process to S510. In S510, the notification unit 305 creates a transfer failure notification mail as shown in FIG. 7(b). FIG. 7B is a diagram showing an example of a notification email created by the notification unit 305 in S510 of FIG. 5, and corresponds to a transfer failure notification in the case where a link to the log is created in the shared folder. In the email in FIG. 7(b), 701 and 702 are the same as those in FIG. 7(a).

[0049] Reference numeral 711 denotes a path of a link to a log created in a shared folder, which is described to facilitate checking of a log message in the event of a transfer failure. By opening the link indicated by the path 711 to the link on the shared folder, it is possible to open the log recorded by the NAS 101.

[0050] Returning now to the explanation of the flowchart in FIG. After the process of S509 or S510, the notification unit 305 advances the process to S511. In S511, the notification unit 305 sends the transfer failure notification email created in S509 or S510 above to the notification destination set in the notification destination setting 424. After sending the notification, the notification unit 305 returns control to the log transfer unit 304. Then, the log transfer unit 304 returns the process to S502 and controls to transfer the next log message.

[0051] The following describes the case where the transfer of the log message was successful (YES in S504). In this case, in S512, it is determined whether the transfer failure flag is "true". Here, if the transfer failure flag is "false" (NO in S512), the log transfer unit 304 returns the process to S502 and controls to transfer the next log message. On the other hand, if the transfer failure flag is "true" (YES in S512), the log transfer unit 304 advances the process to S513.

[0052] In S513, the log transfer unit 304 sets the transfer failure flag to "false" to indicate that the log transfer has changed from failure to success. Next, in S514, the log transfer unit 304 determines whether the transfer failure notification setting 423 is set to "Yes." If the transfer failure notification setting 423 is set to "No" (NO in S514), the log transfer unit 304 returns the process to step S502 and controls to transfer the next log message. On the other hand, if the transfer failure notification setting 423 is set to "Yes" (YES in S514), the log transfer unit 304 advances the process to S515.

[0053] In S515, the log transfer unit 304 requests the notification unit 305 to notify the transfer failure, and the notification unit 305 judges whether the link setting 425 to the log is set to "create." If the link setting 425 to the log is set to "not create" (NO in S515), the notification unit 305 advances the process to S516.

[0054] In S516, the notification unit 305 creates a forwarding success notification email as shown in FIG. 8(a). FIG. 8A is a diagram showing an example of a notification email created by the notification unit 305 in S516 of FIG. 5, and corresponds to a transfer failure notification in the case where a link to the log is not created in the shared folder. In the email in FIG. 8(a), 801 is a message indicating that the transfer was successful.

[0055] 802 is a character string indicating the date and time of the log message 606 that was successfully transferred. This is entered in order to make it easier to identify which log messages were successfully transferred when viewing the log. When the administrator receives the successful transfer notification email and checks the log, he or she can determine that the log messages that have failed to be transferred are those that are after the date and time entered in 702 in the failed transfer notification email and up to the log message immediately preceding the log message entered in 802. 803 is a URL for executing log viewing, which is entered to facilitate checking of a log message indicative of a transfer failure, similar to 703 in FIG. 7A.

[0056] Returning now to the explanation of the flowchart in FIG. On the other hand, if the link setting 425 to the log is set to "create" (YES in S515), the notification unit 305 advances the process to S517. In S517, the notification unit 305 creates a forwarding success notification email as shown in FIG. 8(b). FIG. 8B is a diagram showing an example of the notification mail created by the notification unit 305 in S517 of FIG. 5, and corresponds to a transfer failure notification in the case where a link to the log is created in the shared folder. In the email in FIG. 8(b), 801 and 802 are the same as in FIG. 8(a). 811 indicates the path of the link to the log created in the shared folder, which is entered to facilitate confirmation of a log message indicating successful transfer, similar to the path 711 of the link to the log in FIG. 7(b).

[0057] Returning now to the explanation of the flowchart in FIG. After the process of S516 or S517, the notification unit 305 advances the process to S518. In S518, the notification unit 305 sends the transfer success notification email created in S516 or S517 above to the notification destination set in the notification destination setting 424. After sending the notification, the notification unit 305 returns control to the log transfer unit 304. Then, the log transfer unit 304 returns the process to S502 and controls to transfer the next log message.

[0058] As described above, according to the first embodiment, when a log message cannot be transferred, a notification is made containing information that makes it easy to check the log that could not be transferred. This makes it possible to make the administrator aware of the failure to transfer the log message and to easily check the log message that could not be transferred. In addition, in this embodiment, when a link to the log is created, the path of the link to the log is included in the notification content. This makes it possible to make the log check more convenient for the administrator who uses the link to the log. For example, in response to a failure to transfer the log message, if a link to the log is not created in the shared folder, the notification unit 305 notifies the administrator of access information to a screen that refers to the log (a URL such as 703 in FIG. 7(a)) and information that identifies the log message (date and time information such as 702 in FIG. 7(a)) (S509, S511). On the other hand, if a link to the log has been created in the shared folder, the notification unit 305 notifies the path to the link on the shared folder of the log containing the log message whose transfer failed (a path such as 711 in FIG. 7(b)) and information for identifying the log message (date and time information such as 702 in FIG. 7(b)) (S510, S511). With this configuration, in a device that transfers log messages to a server, if the server receiving the log has an abnormality and the log message cannot be transferred, it is possible to notify the failure to transfer the log message and make it easy to check the log that could not be transferred.

[0059] In addition, the notification email in Fig. 7(b) may include URL 703 for executing log viewing in Fig. 7(a) in addition to path 711 for the link to the log. Similarly, the notification email in Fig. 8(b) may include 803 in Fig. 8(a) in addition to path 811 for the link to the log. This makes it easier to view the log file from the URL for executing log viewing in addition to the link to the log, thereby further improving usability.

[0060] In addition, if the log transfer fails, the next log message is acquired and transferred, but the log message whose transfer failed may be resent until the transfer is successful. In that case, the date and time of the successful log transfer may be written in the date and time 802 in the transfer success notification created in S516 or S517.

[0061] Also, multiple types of logs may be transferred, and the type of log to be transferred may be selected. In this case, a log viewing button 427 may be provided for each type of log, and a link to the log may be created for each type of log in a specified shared folder. Furthermore, in this case, the URL 703 for executing log viewing and the path 711 of the link to the log, which are written in the transfer failure notification email, may be written according to the type of log whose transfer has failed. Furthermore, in this embodiment, notification is made by email, but notification may also be made by other chat services, messaging services, or the like. Furthermore, the present invention is not limited to storage devices that can be connected to a network, such as NAS, but can be applied to any device that transfers log messages to a server.

[0062] In the process shown in the flowchart of Fig. 5, a failure notification is issued when a log message transfer that had been successful up until that point fails, no new failure notifications are issued while the log message transfer continues to fail thereafter, and a success notification is issued when the log message transfer is subsequently successful. However, a configuration in which a notification is issued every time a log message transfer fails may also be used.

[0063] Second Embodiment In the second embodiment, in addition to the notification contents in the first embodiment described above, a log message for the period during which transfer failed is written as a file in a shared folder to which a link to the log is created, and the path to that file is also notified. In the second embodiment, the explanation of the parts that overlap with the first embodiment will be omitted, and only the differences will be explained.

[0064] Fig. 9 is a flowchart showing an example of processing when the NAS 101 of the second embodiment transfers a log to the log collection server 102. The processing of this flowchart is executed every time a log message to be recorded occurs when the log transfer setting 421 is set to "Yes". Each step shown in Fig. 5 is realized by the CPU 201 of the NAS 101 reading into the RAM 203 a program corresponding to each software component shown in Fig. 3, which is stored in the ROM 202 or the storage device 204, and executing the program.

[0065] In the process of Fig. 9, the same step numbers are assigned to the same steps as in Fig. 5 of the first embodiment. Note that Fig. 9 differs from Fig. 5 in that the processes of S901 to S904 are added when S504 is NO, and S510 is replaced with S905 and S517 is replaced with S906. These differences will be described below.

[0066] In S901, the log transfer unit 304 determines whether the link setting 425 to the log is set to "create." If the link setting 425 to the log is set to "not create" (NO in S901), the log transfer unit 304 advances the process to S505. On the other hand, if the link setting 425 to the log is set to "create" (YES in S901), the log transfer unit 304 advances the process to S902.

[0067] In S902, the log transfer unit 304 determines whether or not the transfer failure flag is “true.” If the transfer failure flag is “false” (NO in S902), the log transfer unit 304 advances the process to S903.

[0068] In S903, the log transfer unit 304 creates a new file (transfer failure log message write file 1000 as shown in FIG. 10) into which the log messages that failed to be transferred in S503 are written. In this embodiment, the transfer failure log message write file 1000 is created in the folder set in the shared folder setting 426 when creating a link to the log. The file name to be created is added with, for example, a character string indicating the date and time of creation so that the file name is not duplicated within the folder. After creating the transfer failure log message write file 1000, the log transfer unit 304 writes the log messages that failed to be transferred in S503 above into that file, and the process proceeds to S505.

[0069] FIG. 10A shows an example of a transfer failure log message writing file 1000 into which the log message is written in S903 of FIG. 9, using the log message of FIG. 6 as in the first embodiment. In the above S903, as shown in FIG. 10(a), only the log message 601 in which the log transfer failure occurred has been written out.

[0070] On the other hand, if the transfer failure flag is already "true" (YES in S902), the log transfer module 304 advances the process to S904. In S904, the log transfer unit 304 additionally writes the log message that failed to be transferred in S503 above into the latest transfer failure log message writing file 1000, and the process proceeds to S505.

[0071] Here, an example of a transfer failure log message writing file 1000 into which the log message is written in S904 of FIG. 9 is shown in FIGS. 10(b) and 10(c) using the log message of FIG. 6 as in the first embodiment. In the above S904, as shown in Fig. 10(b), the state is such that log messages from log message 601 onwards when the log transfer failure continues have been written out. Then, finally, as shown in Fig. 10(c), log messages up to log message 605 before the log transfer succeeds are written out.

[0072] In the second embodiment, if the transfer failure notification setting 423 is set to "no" in S505 (NO in S505), the log transfer unit 304, although not shown in the figure, sets the transfer failure flag to "true" if it is "false" and then returns the process to step S502.

[0073] Also, in S905, the notification unit 305 creates a transfer failure notification email (such as the email in FIG. 11(a)) that describes the path of the link to the log created in the specified shared folder and the path of the transfer failure log message write file 1000. Then, the notification unit 305 advances the process to S511. FIG. 11A is a diagram showing an example of the failure notification created in S905 of FIG. FIG. 11(a) includes, in addition to the contents of FIG. 7(b), a path 1101 of the transfer failure log message writing file 1000 (that is, information indicating the location of the transfer failure log message writing file 1000).

[0074] Also, in S906, the notification unit 305 creates a transfer success notification email (an email like that shown in FIG. 11(b)) that includes the path of the link to the log created in the specified shared folder and the path of the transfer failure log message write file 1000. FIG. 11B is a diagram showing an example of the success notification created in S906 of FIG. FIG. 11(b) includes a path 1101 to a transfer failure log message writing file 1000 in addition to the contents of FIG. 8(b).

[0075] As described above, in the second embodiment, in addition to the first embodiment, log messages for the period during which transfer failed are written to a shared folder in which a link to the log has been created as a transfer failure log message write file 1000, and the path to that file is also notified. This makes it easier to check the log messages for which transfer failed from the transfer failure log message write file 1000 in which only messages for which transfer failed are written.

[0076] The transfer failure log message write file 1000 that is no longer needed can be manually deleted from the shared folder, but may also be automatically deleted by the setting management unit 303 or the like after a certain period of time has passed since no more data was written to the file. Also, a UI for deleting the transfer failure log message write file 1000 that is no longer needed may be provided on the management application screen, and the file may be deleted from there. Furthermore, when multiple types of logs are to be transferred, a transfer failure log message writing file 1000 may be created for each type of log.

[0077] Third Embodiment The third embodiment is configured to notify the user of a log message indicating a failed transfer in addition to the notification content in the first embodiment. In the third embodiment, the description of the parts that overlap with the first embodiment will be omitted, and only the differences will be described.

[0078] Fig. 12 is a flowchart showing an example of processing when the NAS 101 of the third embodiment transfers a log to the log collection server 102. The processing of this flowchart is executed every time a log message to be recorded occurs when the log transfer setting 421 is set to "Yes". Each step shown in Fig. 5 is realized by the CPU 201 of the NAS 101 reading into the RAM 203 a program corresponding to each software component shown in Fig. 3, which is stored in the ROM 202 or the storage device 204, and executing the program.

[0079] In the process of Fig. 12, the same step numbers are assigned to the same steps as in Fig. 5 of the first embodiment. In Fig. 12, the process of S1201 is added after the case of YES in S505, and S1204 is added after S507. Another difference is that S506, S509, S510, S516, and S517 are replaced with S1203, S1205, S1206, S1207, and S1208, respectively. These differences will be described below.

[0080] In S1201, the log transfer unit 304 stores the log message that failed to be transferred in S503 in a transfer failure log message list on the RAM 203. Note that this is not limiting, and the transfer failure log message list may be stored on the storage device 204.

[0081] Next, in S1203, the log transfer unit 304 determines whether or not the transfer failure flag is “true.” If the transfer failure flag is “false” (NO in S1203), the log transfer unit 304 advances the process to S507. On the other hand, if the transfer failure flag is already "true" (YES in S1203), the log transfer unit 304 advances the process to S1204.

[0082] In S1204, the log transfer unit 304 judges whether the state satisfies the notification condition. In this embodiment, the state is judged to satisfy the notification condition immediately after the transfer failure flag becomes "true" and when the transfer of the log message has failed for a certain period of time (e.g., 5 minutes) or more since the previous log message for which a transfer failure notification was issued. However, this is not limited to this, and the certain period of time may be 1 minute or 10 minutes, or instead of the elapsed time, a notification may be issued when the number or size of messages held reaches a certain value. In addition, the administrator may be able to set these conditions.

[0083] Here, if the notification conditions are met (YES in S1204), the log transfer unit 304 advances the process to S508. On the other hand, if the notification conditions are not met (NO in S1204), the log transfer unit 304 returns the process to S502 and controls so as to transfer the next log message.

[0084] In S1205, notification unit 305 creates a transfer failure notification email (such as the email in FIG. 13(a)) that describes the URL for performing log viewing and the log message stored in the transfer failure log message storage list. After creation, notification unit 305 clears the log message described in the transfer failure notification email from the transfer failure log message storage list.

[0085] FIG. 13A is a diagram showing an example of a forwarding failure notification email created immediately after the forwarding failure flag becomes "true" in S1205 of FIG. In FIG. 13(a), 701, 702, and 703 are the same as in FIG. 7(a). 1301 is a sentence indicating that a log message of failed transfer will be written below it. When the transfer of the log message 601 in FIG. 6 fails and the transfer failure flag becomes "true" from "false", the log message 601 is held in S1201 and written below 1301.

[0086] FIG. 13(b) is an example of a transfer failure notification email that is created when log message transfer continues to fail for five minutes or more after the transfer failure notification of FIG. 13(a). In Fig. 13(b), 701, 702, 703, and 1301 are the same as in Fig. 13(a). When the notification email in Fig. 13(b) is created, log message 602 that failed to be transferred after log message 601 notified in the previous notification in Fig. 13(a) through log message 603, which is the message that occurred more than five minutes ago, are held in S1201. Therefore, in the notification email in Fig. 13(b), log messages 602 to 603 are written under 1301.

[0087] In addition, in S1206, the notification unit 305 creates a transfer failure notification email (email as shown in FIG. 14) that describes the path of the link to the log and the log message stored in the transfer failure log message storage list. After creation, the notification unit 305 clears the log message described in the transfer failure notification email from the transfer failure log message storage list.

[0088] FIG. 14A is a diagram showing an example of a forwarding failure notification email created immediately after the forwarding failure flag becomes "true" in S1206 of FIG. FIG. 14(a) is different in that the URL 703 for executing log viewing in FIG. 13(a) is replaced with a path 711 of the link to the log in FIG. 7(b). Also, Fig. 14(b) is an example of a transfer failure notification email that is created when log message transfer has failed for more than five minutes since the transfer failure notification in Fig. 14(a). Fig. 14(b) differs in that URL 703 for viewing the log in Fig. 13(b) is replaced with path 711 for the link to the log in Fig. 7(b). The transfer failure notification email shown in FIG. 14 may include URL 703 for executing log viewing in FIG.

[0089] In S1207, the notification unit 305 creates a transfer success notification email (such as the email in FIG. 15(a)) that includes a URL for viewing the log and the log message stored in the transfer failure log message storage list. After creation, the notification unit 305 clears the log message included in the transfer failure notification email from the transfer failure log message storage list.

[0090] FIG. 15A is a diagram showing an example of the forwarding success notification email created in S1207 of FIG. In FIG. 15(a), 801, 802, and 803 are the same as in FIG. 8(a). 1301 is a sentence indicating that a log message of failed transfer will be written below it, similar to Fig. 13(a). Now, assume that the transfer is successful in log message 606, the transfer failure flag changes from "true" to "false", and the messages held in S1201 are log message 604 to log message 605. In this case, log message 604 to log message 605 will be written below 1301 in the notification email in Fig. 15(a).

[0091] Also, in S1208, notification unit 305 creates a transfer success notification email (email such as that shown in FIG. 15(b)) that describes the path of the link to the log and the log message stored in the transfer failure log message storage list. After creation, notification unit 305 clears the log message described in the transfer failure notification email from the transfer failure log message storage list.

[0092] FIG. 15B is a diagram showing an example of the forwarding success notification email created in S1208 of FIG. FIG. 15(b) is different in that 803 in FIG. 15(a) is replaced with 811 in FIG. 8(b). The transfer failure notification email shown in FIG. 15(b) may include 803 in FIG. 15(a) (a URL for executing the same process as when the log viewing button 427 is pressed).

[0093] In the above description, when the transfer failure notification setting 423 is set to "Yes", regardless of whether the link to log setting 425 is set to "Yes", the log message whose transfer has failed is stored in the transfer failure log message storage list in S1201. However, it may be possible to determine whether the link to log setting 425 is set to "Yes", and execute S1201 to store the log message whose transfer has failed in the transfer failure log message storage list only if the link to log setting 425 is set to "Yes". In this case, S509 in Fig. 5 is executed instead of S1205, and S516 in Fig. 5 is executed instead of S1207.

[0094] As described above, in the third embodiment, a notification is made including the log message itself for which transfer has failed. This allows the message for which transfer has failed to be checked without viewing the log itself. On the other hand, if you want to check the log message for which transfer has failed before the next notification arrives, you can also check the log directly from the URL 703 for viewing the log or the path 711 for the link to the log.

[0095] Furthermore, if for some reason the notification email cannot be sent or if the transfer failure notification setting 423 is set to "No," the notification content may be displayed on the LCD panel of the NAS main unit. The notification content may also be displayed in the dashboard area 410 of the dashboard screen of the management application in FIG. 4B. Furthermore, if a link has been created in a shared folder, the notification content may be placed as a file in that shared folder.

[0096] According to each embodiment described above, in a device that transfers log messages to a server, if the server receiving the logs has an abnormality and the log messages cannot be transferred, the failure to transfer the log messages can be notified and the logs that could not be transferred can be easily checked. This can significantly improve the usability when the administrator manages the log transfer status.

[0097] It goes without saying that the configurations and contents of the various data described above are not limited to those described above, and the data may have various configurations and contents depending on the application and purpose. Although one embodiment has been described above, the present invention can be embodied, for example, as a system, an apparatus, a method, a program, a storage medium, etc. Specifically, the present invention may be applied to a system composed of multiple devices, or may be applied to an apparatus composed of a single device. Furthermore, any combination of the above-described embodiments is also included in the present invention.

[0098] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. Furthermore, the present invention may be applied to a system made up of a plurality of devices, or to an apparatus made up of a single device. The present invention is not limited to the above-mentioned embodiment, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and are not excluded from the scope of the present invention. In other words, the present invention includes all configurations that combine the above-mentioned embodiments and their modifications.

[0099] The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) A storage device connectable to a network, A recording means for recording the generated log message as a log; A creating means capable of creating a link to the log in a shared folder; A transfer means for transferring the log message to a predetermined transfer destination; a notification means for notifying a predetermined notification destination when the transfer of the log message has failed, The storage device is characterized in that, if a link to the log is created in a shared folder, the notification means notifies the user of a path to a link on the shared folder of a log containing the log message whose transfer failed and information identifying the log message, and, if a link to the log is not created in the shared folder, notifies the user of access information to a screen for viewing the log and information identifying the log message. (Configuration 2) When a link to the log is created in a shared folder, the transfer means writes the log message that has failed to be transferred as a file in the shared folder; 2. The storage device according to configuration 1, wherein the notification means includes in the notification information information indicating the location of the file written by the transfer means. (Configuration 3) 3. The storage device according to configuration 2, wherein the file written by the transfer means is deleted a certain period of time after no more writing is done to the file. (Configuration 4) 2. The storage device according to configuration 1, wherein the notification means includes in the notification the contents of the log message regarding the transfer failure. (Configuration 5) the notification means issues the notification as a first notification when the transfer of the log message fails and the previous transfer of the log message was successful, and issues a second notification when the transfer of the log message is successful and the previous transfer of the log message was unsuccessful; The storage device according to any one of configurations 1 to 4, characterized in that in the second notification, if a link to the log has been created in a shared folder, a path to a link on the shared folder of a log containing the successfully transferred log message and information identifying the log message are notified, and if a link to the log has not been created in the shared folder, access information to a screen for viewing the log and information identifying the log message are notified. (Configuration 6) 6. The storage device according to any one of configurations 1 to 5, wherein the information for identifying the log message is information indicating a date and time of the log. (Configuration 7) 7. The storage device according to any one of configurations 1 to 6, wherein the notification means issues a notification by email, a chat service, or a messaging service. (Method 1) A method for controlling a storage device that is connectable to a network and has a recording unit that records a generated log message as a log, and a creating unit that can create a link to the log in a shared folder, comprising: a forwarding step of forwarding the log message to a predetermined destination; a notification step of notifying a predetermined notification destination when the transfer of the log message has failed, a notification step of notifying, when a link to the log has been created in a shared folder, a path to a link on the shared folder of a log containing the log message whose transfer failed and information identifying the log message; and, when a link to the log has not been created in the shared folder, notifying, when a link to the log has been created in the shared folder, access information to a screen for viewing the log and information identifying the log message. (Program 1) A program for causing a computer to function as each of the means of the storage device according to any one of configurations 1 to 7.

Claims

1. A storage device connectable to a network, A recording means for recording the generated log message as a log; A creating means capable of creating a link to the log in a shared folder; A transfer means for transferring the log message to a predetermined transfer destination; a notification means for notifying a predetermined notification destination when the transfer of the log message has failed, The storage device is characterized in that, if a link to the log is created in a shared folder, the notification means notifies the user of a path to a link on the shared folder of a log containing the log message whose transfer failed and information identifying the log message, and, if a link to the log is not created in the shared folder, notifies the user of access information to a screen for viewing the log and information identifying the log message.

2. When a link to the log is created in a shared folder, the transfer means writes the log message for which transfer has failed as a file in the shared folder; 2. The storage device according to claim 1, wherein said notification means includes information indicating the location of the file written by said transfer means in the notification.

3. 3. The storage device according to claim 2, wherein the file written by said transfer means is deleted a certain period of time after no more writing is done to the file.

4. 2. The storage device according to claim 1, wherein said notification means includes the content of the log message indicating the transfer failure in the notification.

5. the notification means issues the notification as a first notification when the transfer of the log message fails and the previous transfer of the log message was successful, and issues a second notification when the transfer of the log message is successful and the previous transfer of the log message was unsuccessful; A storage device as described in any one of claims 1 to 4, characterized in that in the second notification, if a link to the log has been created in a shared folder, a path to a link on the shared folder of a log containing the successfully transferred log message and information identifying the log message are notified, and if a link to the log has not been created in the shared folder, access information for a screen for viewing the log and information identifying the log message are notified.

6. 5. The storage device according to claim 1, wherein the information for identifying the log message is information indicating a date and time of the log.

7. 5. The storage device according to claim 1, wherein the notification means issues a notification by email, a chat service, or a messaging service.

8. A method for controlling a storage device that is connectable to a network and has a recording unit that records a generated log message as a log, and a creating unit that can create a link to the log in a shared folder, comprising: a forwarding step of forwarding the log message to a predetermined destination; a notification step of notifying a predetermined notification destination when the transfer of the log message has failed, a notification step of notifying, when a link to the log has been created in a shared folder, a path to a link on the shared folder of a log containing the log message whose transfer failed and information identifying the log message; and, when a link to the log has not been created in the shared folder, notifying, when a link to the log has been created in the shared folder, access information to a screen for viewing the log and information identifying the log message.

9. A program for causing a computer to function as each of the means of the storage device according to any one of claims 1 to 4.

Images