MANAGEMENT SERVER, MANAGEMENT SYSTEM, AND MANAGEMENT METHOD

• US 20140281760A1
• Filed: 12/26/2011
• Published: 09/18/2014
• Est. Priority Date: 12/26/2011
• Status: Active Grant

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Yoshizawa, Masahiro, Sato, Tatsuya, Oyamatsu, Masayuki
• Granted Patent: US 9,411,673 B2
• Time in Patent Office: Days
• US Class Current: 714/57
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0787 Storage of error reports, e.g. persistent data storage, storage using memory protection
• CPC Class Codes: G06F 11/3065 Monitoring arrangements determined by the means or processing involved in reporting the monitored data error or fault reporting or logging G06F11/0766
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence

Abstract

It is provided a management server is configured to store an access log including a monitoring subject ID, or a monitoring item ID when a request for outputting a historical data is inputted, an incident data including a time, a monitoring subject ID, or a monitoring item ID when an incident indicating a failure in the each of the devices; associate the incident data with the access log; update data included in the access log to a string of characters abstracted; generate an abstract access log; identify first abstract access log from the generated abstract access log based on the first incident data when a value indicating first incident data is inputted; identify a condition for the historical data to be outputted based on the first abstract access log and the first incident data; and output the identified condition for the historical data.

Claims

1. A management server, which is to be coupled to devices, for collecting historical data indicating a status of each of the devices,

the historical data including a value indicating the status of the each of the devices, a time at which the historical data is generated, a monitoring subject ID assigned to the each of the devices whose status is indicated by the historical data, and a monitoring item ID indicating a meaning of the value indicating the status,

the management server comprising:

a processor;

a memory; and

an interface,

wherein the management server is configured to;

store, in the memory, in case where a request for outputting the historical data is inputted via the interface, an access log including at least one of a time at which outputting of the historical data is requested, the monitoring subject ID included in the historical data requested to be outputted, or the monitoring item ID included in the historical data requested to be outputted;

store, in the memory, in case where an incident indicating a failure or prediction of a failure occurs in the each of the devices, incident data including at least one of a time at which the incident has occurred, a monitoring subject ID assigned to the each of the devices where the incident has occurred, or a monitoring item ID for which the incident has occurred;

associate the incident data with the access log;

update data included in the access log to a string of characters abstracted by a predetermined rule in accordance with the incident data associated with the access log and the access log;

generate an abstract access log including the data updated to the abstracted string of characters;

identify, in case where a value indicating first incident data is inputted via the interface, at least one first abstract access log from the generated abstract access log based on the first incident data;

identify a condition for the historical data to be outputted based on the first abstract access log and the first incident data, the condition including at least one of pieces of data including a time at which the historical data is generated, a monitoring subject ID included in the historical data, and a monitoring item ID included in the historical data; and

output the identified condition for the historical data.

2. The management server according to claim 1, wherein the management server is further configured to:

identify, in case where the value indicating the first incident data is inputted via the interface, second incident data similar to the first incident data from the incident data stored in the memory;

identify at least one first access log associated with the second incident data from the access logs stored in the memory; and

identify the abstract access log as the first abstract access log, the abstract access log being generated in accordance with the first access logs and the second incident data.

3. The management server according to claim 2, wherein the management server is further configured to:

calculate a first degree of importance in a work of solving an incident indicated by the second incident data from the first access log and the second incident data for the at least one first abstract access log; and

output the condition for the historical data identified based on the first abstract access log and the first incident data so that the conditions are more highlighted in descending order of the first degree of importance.

4. The management server according to claim 3, wherein:

each of the devices is classified into at least one group;

the access log includes a group ID indicating the group;

the incident data includes a group ID indicating the group into which the each of the devices where the incident has occurred is classified; and

the management server is further configured to calculate, in case where a group ID included in the second incident data matches the group ID included in the first access log, the first degree of importance by adding a predetermined value to the first degree of importance.

5. The management server according to claim 1, wherein the management server is further configured to:

define dependency relation data indicating a relation between a device where an incident has occurred and the each of the devices which are influenced by the incident;

determine whether or not one of the devices indicated by the monitoring subject ID included in the incident data and one of the devices indicated by the monitoring subject ID included in the access log have the relation defined by the dependency relation data; and

update, in case where a result of the determination shows that the one of the devices indicated by the monitoring subject ID included in the incident data and the one of the devices indicated by the monitoring subject ID included in the access log have the relation defined by the dependency relation data, the monitoring subject ID included in the access log to a string of characters indicating the defined relation to generate the abstract access log.

6. The management server according to claim 1, wherein the management server is further configured to:

define service data indicating services provided by the devices;

determine whether or not the service data defines one of the services provided by one of the devices indicated by the monitoring subject ID included in the incident data which matches a service provided by one of the devices indicated by the monitoring subject ID included in the access log; and

update, in case where a result of the determination shows that the service data defines the one of the services provided by the one of the devices indicated by the monitoring subject ID included in the incident data which matches the service provided by the one of the devices indicated by the monitoring subject ID included in the access log, the monitoring subject ID included in the access log to a string of characters indicating the defined service to generate the abstract access logs.

7. The management server according to claim 1, wherein:

the access log includes a requester ID indicating a requester requesting output of the historical data;

the incident data includes a time at which the incident was solved; and

the management server is further configured to;

hold responsibility data including the requester ID, the monitoring subject ID indicating a device to be monitored by the requester, and a monitoring item ID indicating an item to be monitored by the requester;

determine whether or not the access log is related to the incident data by determining, based on the access log, the incident data, and the responsibility data, whether or not the access log indicates that output of the historical data was requested until solution of an incident indicated by the incident data since occurrence of the incident, whether or not the monitoring subject ID and the monitoring item ID included in the incident data indicate a monitoring subject and a monitoring item which the requester ID included in the access log is responsible for, or whether or not the monitoring subject ID included in the incident data matches the monitoring subject ID included in the access log; and

associate the incident data with the access log in case where a result of the determination shows that the access log is related to the incident data.

8. The management server according to claim 1, wherein:

the abstract access log includes an incident ID indicating the incident data associated with the access log updated with the abstracted string of characters; and

the management server is further configured to;

update data included in the first incident data to at least one string of characters abstracted by a predetermined rule in case where the first incident data is stored in the memory via the interface;

generate at least one piece of first abstract incident data including the data updated to the abstracted string of characters, and the incident ID indicating the first incident data;

identify the first abstract incident data in case where the value indicating the first incident data is inputted via the interface; and

identify at least one second abstract access log including the incident ID included in the identified first abstract incident data as the first abstract access log.

9. The management server according to claim 8, wherein the management server is further configured to:

calculate second degree of importance in a work of solving an incident indicated by the first abstract incident data from the second abstract access logs and the first abstract incident data for each piece of the first abstract incident data; and

delete the first abstract incident data that includes the second abstract access log whose second degree of importance has a distribution smaller than a predetermined value.

10. A management system, comprising a management server, which is to be coupled to devices, for collecting historical data indicating a status of each of the devices,

the historical data including a value indicating the status of the each of the devices, a time at which the historical data is generated, a monitoring subject ID assigned to that device whose status is indicated by the historical data, and a monitoring item ID indicating a meaning of the value indicating the status,

the management server comprising:

a processor;

a memory; and

an interface,

wherein the management system is configured to;

store, in the memory, in case where a request for outputting the historical data is inputted via the interface, an access log including at least one of a time at which outputting of the historical data is requested, the monitoring subject ID included in the historical data requested to be outputted, or the monitoring item ID included in the historical data requested to be outputted;

store, in the memory, in case where an incident indicating a failure or prediction of a failure occurs in the each of the devices, incident data including at least one of a time at which the incident has occurred, a monitoring subject ID assigned to the each of the devices where the incident has occurred, or a monitoring item ID for which the incident has occurred;

associate the incident data with the access log;

update data included in the access log to a string of characters abstracted by a predetermined rule in accordance with the incident data associated with the access log and the access log;

generate an abstract access log including the data updated to the abstracted string of characters;

identify, in case where a value indicating first incident data is inputted via the interface, at least one first abstract access log from the generated abstract access log based on the first incident data;

identify a condition for the historical data to be outputted based on the first abstract access log and the first incident data, the condition including at least one of pieces of data including a time at which the historical data is generated, a monitoring subject ID included in the historical data, and a monitoring item ID included in the historical data; and

output the identified condition for the historical data.

11. The management system according to claim 10, wherein the management system is further configured to:

identify, in case where the value indicating the first incident data is inputted via the interface, second incident data similar to the first incident data from the incident data stored in the memory;

identify at least one first access log associated with the second incident data from the access logs stored in the memory; and

identify the abstract access log as the first abstract access log, the abstract access log being generated in accordance with the first access log and the second incident data.

12. The management system according to claim 10, wherein:

the abstract access log includes an incident ID indicating the incident data associated with the access log updated with the abstracted string of characters; and

the management system is further configured to;

update data included in the first incident data to at least one string of characters abstracted by a predetermined rule in case where the first incident data is stored in the memory via the interface;

generate at least one piece of first abstract incident data including the data updated to the abstracted string of characters, and the incident ID indicating the first incident data;

identify the first abstract incident data in case where the value indicating the first incident data is inputted via the interface; and

identify at least one second abstract access log including the incident ID included in the identified first abstract incident data as the first abstract access log.

13. A management method, which is to be performed by a management server, which is to be coupled to devices, for collecting historical data indicating a status of each of the devices,

the historical data including a value indicating the status of the each of the devices, a time at which the historical data is generated, a monitoring subject ID assigned to the each of the devices whose status is indicated by the historical data, and a monitoring item ID indicating a meaning of the value indicating the status,

the management server comprising:

a processor;

a memory; and

an interface,

the management method comprising;

storing, by the processor, in the memory, in case where a request for outputting the historical data is inputted via the interface, an access log including at least one of a time at which outputting of the historical data is requested, the monitoring subject ID included in the historical data requested to be outputted, or the monitoring item ID included in the historical data requested to be outputted;

storing, by the processor, in the memory, in case where an incident indicating one of a failure that has occurred in the each of the devices and prediction of the failure, incident data including at least one of a time at which the incident has occurred, a monitoring subject ID assigned to the each of the devices where the incident has occurred, or a monitoring item ID for which the incident has occurred;

associating, by the processor, the incident data with the access log;

updating, by the processor, data included in the access log to a string of characters abstracted by a predetermined rule in accordance with the incident data associated with the access log and the access log;

generating, by the processor, an abstract access log including the data updated to the abstracted string of characters;

identifying, by the processor, in case where a value indicating first incident data is inputted via the interface, at least one first abstract access log from the generated abstract access log based on the first incident data;

identifying, by the processor, a condition for the historical data to be outputted based on the first abstract access log and the first incident data, the condition including at least one of pieces of data including a time at which the historical data is generated, a monitoring subject ID included in the historical data, and a monitoring item ID included in the historical data; and

outputting, by the processor, the identified condition for the historical data.

14. The management method according to claim 13, further comprising:

identifying, by the processor, in case where the value indicating the first incident data is inputted via the interface, second incident data similar to the first incident data from the incident data stored in the memory;

identifying, by the processor, at least one first access log associated with the second incident data from the access logs stored in the memory; and

identifying, by the processor, the abstract access log as the first abstract access log, the abstract access log being generated in accordance with the first access log and the second incident data.

15. The management method according to claim 13, wherein:

the abstract access log includes an incident ID indicating the incident data associated with the access log updated with the abstracted string of characters; and

the management method further comprises;

updating, by the processor, data included in the first incident data to at least one string of characters abstracted by a predetermined rule when the first incident data is stored in the memory via the interface;

generating, by the processor, at least one piece of first abstract incident data including the data updated to the abstracted string of characters, and the incident ID indicating the first incident data;

identifying, by the processor, the first abstract incident data when the value indicating the first incident data is inputted via the interface; and

identifying, by the processor, at least one second abstract access log including the incident ID included in the identified first abstract incident data as the first abstract access log.