KR100939352B1 - Method and Apparatus for Monitoring Service Fault - Google Patents

Abstract

The present invention relates to a service failure monitoring apparatus and method.

The present invention includes the steps of (a) selecting a failure management object related to service operation from a database and registering it in a topology map; (b) setting each failure impact attribute (disability impact determination criteria and failure impact search range) of the failure management object; (c) selecting and setting a failure impact transmission path and a failure impact reception path for transmitting and receiving a failure impact determination result of the failure management object generated through the failure impact property; (d) generating a failure impact degree of a failure management object related to service operation when a failure occurs in a unit object; (e) outputting a failure location and failure impact of a failure management object related to service operation in a topology map; (f) searching for a server generated in the service, a faulty reception path and a faulty transmission path of the unit objects.

The present invention can be expected to be able to accurately and quickly handle the service failure management task by supporting to clearly understand the current status of the failure, the scope and impact of the failure occurred in the server component.

Service Management, Failure Management, Failure Monitoring, Failure Impact, Server Management

Description

Service failure monitoring device and method {Method and Apparatus for Monitoring Service Fault}

The present invention relates to a service failure monitoring apparatus and method, and more particularly, to a service failure monitoring apparatus and method through a failure propagation path definition.

In the conventional server failure management, failure management is performed on an individual server basis, local failure location and cause are monitored through failure events and error logs of each server, and the failures of individual servers are analyzed and recovered individually. do.

The conventional server failure management has a problem that it is difficult to determine which services or servers affect the failure of an individual server component when a failure occurs in a specific server component.

In addition, the conventional server failure management is difficult to determine how much the failure of the individual server component affects the services or servers, it is difficult to determine whether the failure of the individual services or servers from the internal or external causes There was this.

This conventional server failure management wastes a lot of time in analyzing the location and cause of server components that neglect the error of the server that is fatal to the operation of the service and cause the service failure. In addition, the conventional server failure management has a difficulty in grasp the extent and impact of the failure occurred in the server component, it was difficult to identify the response method and measures for failure occurred in the server component.

In order to solve such a problem, the present invention is to provide a service failure monitoring apparatus and method through the failure propagation path definition of the failure management object.

Service failure monitoring method according to an aspect of the present invention for achieving the technical problem is (a) a failure management object associated with the service operation, the failure management object includes a service, server and unit objects; Selecting from the stored database and registering it in the topology map; (b) setting a failure impact attribute of each of the service, the server, and the unit object, wherein the failure impact attribute includes a failure impact determination criterion and a failure impact search range; And (c) a failure impact level for transmitting and receiving a failure impact determination result of each of the service, the server, and the unit object generated using the failure impact property between the unit object and the server and between the server and the service. Selecting and setting the transmission path and the failure impact also receive path.

According to an aspect of the present invention, a service failure monitoring method includes: (a) a service and a plurality of servers related to the operation of the service, each server comparing the state values of the unit objects causing the failure with preset thresholds; Generating a result of determining a server failure effect degree based on a failure determination criterion and reflecting the failure status of each server into a topology map; And (b) generating a service failure impact determination result based on a second failure determination criterion and a failure impact search range based on each failure impact determination result of the plurality of servers. And establishing a fault propagation path between the unit objects of the.

According to an aspect of the present invention, a service failure monitoring apparatus selects a failure management object related to service operation, wherein the failure management object includes a service, a server, and a unit object from a database storing the failure management object and registers it in a topology map. Fault management object registration unit; An attribute setting unit for setting a failure impact attribute of the registered failure management object, wherein the failure impact attribute includes a first failure impact determination criterion, a second failure impact determination criterion, and a failure impact search range; And a failure impact transmission path and a failure impact reception path for transmitting and receiving a failure impact determination result generated by the failure management object using the failure impact property between the unit object and the server and between the server and the service. It includes a fault impact path selection unit for selecting and setting.

According to the above-described configuration, the present invention can be expected to have the effect of preventing and correcting errors in the server that are critical to the operation of the service in advance.

The present invention can be expected to be easy and easy to analyze the location and cause of the server components causing the service failure.

The present invention can be expected to be able to accurately and quickly handle the service failure management task by supporting to clearly understand the current status of the failure, the scope and impact of the failure occurred in the server component.

The present invention can expect the effect that can improve the accuracy of the response and action method for the failure occurred in the server component.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it may further include other components, except to exclude other components unless specifically stated otherwise. In addition, the terms “… unit”, “… unit”, “module”, “block”, etc. described in the specification mean a unit that processes at least one function or operation, which is hardware or software or a combination of hardware and software. It can be implemented as.

The failure management object related to service operation according to an embodiment of the present invention is classified into a service, a server group, a server, a unit object group, and a unit object.

Services include Internet Protocol Television (hereinafter referred to as "IPTV"), Voice over Internet Protocol (hereinafter referred to as "VoIP"), and Dynamic Host Configuration Protocol (DHCP). And a domain name service (hereinafter referred to as 'DNS'), and may be configured as an upper service or a lower service.

The server group includes an IPTV server farm, a VoIP server farm, a DHCP server farm, and a DNS server farm.

Servers include Server Management Servers (SMS), Database Management Servers (DBMS), Network Management Servers (NMS), Backup Management Servers (BMS), Storage management servers (STMS).

In addition, the server may be configured as an external server associated with another service or system and a basic server related to service operation.

The unit object group covers each unit object such as a central processing unit (CPU), memory, a disk, a network interface card (NIC), and an application process. Means. In addition, the unit object group may mean a plurality of unit objects, but may also mean a group of the same unit object (eg, the central processing unit 1, the central processing unit 2, the central processing unit 3, etc.).

1 is a block diagram schematically showing the internal configuration of the service failure monitoring apparatus 100 according to an embodiment of the present invention.

The service failure monitoring apparatus 100 according to an embodiment of the present invention includes a failure management object registration unit 110, an attribute setting unit 120, a failure impact path selector 130, a failure impact generation unit 140, and a failure. The impact transmission unit 150, the failure impact output unit 160, and the failure impact propagation path search unit 170 are included.

The failure management object registration unit 110 selects a failure management object (service, server group, server, unit object group, and unit object) related to service operation from a database (not shown) storing the failure management object and registers it in the topology map. . For example, a server managing a competitive e-mail service is retrieved from the database as a failure management object and dragged into the topology map.

The property setting unit 120 sets a failure impact property of a failure management object registered in the topology map. Here, the failure impact attribute includes a failure impact determination criterion, a failure impact determination type, each unit object, a threshold for comparing with a state value of each server, and a failure impact search range.

That is, the attribute setting unit 120 sets a failure impact determination criterion, a failure impact determination type, a threshold value, and a failure impact search range for a service, a server, and a unit object group. Here, failure impact judgment types include 'fatal', 'emergency', 'danger', 'caution', 'harmless', 'determined' and 'normal' and are based on the status, event, and attributes of the failure management object. You can choose to configure among them. Hereinafter, the criteria for determining the impact of disability and the scope of searching for the impact of disability will be described in detail.

Here, the threshold value and the failure impact determination type may set the threshold value and the failure impact determination type differently according to the type of failure management object causing the failure such as utilization rate, usage rate, and on / off.

Disability impact determination type according to an embodiment of the present invention will be divided into 'fatal', 'urgent', 'danger', 'caution', 'normal' for convenience of explanation. Of course, the type of failure impact determination can be configured as needed.

The failure impact path selector 130 selects and sets a failure impact transmission path and a reception path for transmitting and receiving the failure impact determination result generated by the failure management object between the unit object and the server and between the server and the service. Accordingly, embodiments of the present invention can search for a fault propagation path between fault management objects.

The failure impact generation unit 140 receives a state value of each unit object of the unit object group, and compares the state value of each unit object with a threshold value set in each unit object to generate a first failure impact degree. do.

In addition, the failure impact generation unit 140 generates a server failure impact determination result based on the first failure determination criterion generated by each unit object, and each server failure impact of a plurality of servers. Based on the determination result of the second failure determination criteria and the failure impact search range, the service failure impact determination result is generated.

The failure impact transmitter 150 transmits the failure impact determination result generated by the failure management object of a lower level to a failure management object of a higher level (unit object group => server, server => service).

The failure impact level output unit 160 outputs a server related to service and service operation, a failure state of each unit object group, a failure impact degree, and a failure impact determination result through a topology map.

The failure impact propagation path searching unit 170 selects a failure management object on the failure impact transmission / reception path and searches for a failure propagation path between a service, a server, and a unit object.

The criteria for determining the disability impact among the aforementioned disability influence attributes include 'average', 'quorum', 'maximum', and 'condition'.

The criterion for determining the influence of failure ('average value') determines the failure state of the corresponding failure management object by comparing the average value of the failure management object with the failure value by comparing the status values of the failure management object with a preset threshold.

The failure impact criterion ('quorum') compares the status values of the failure management object with a preset threshold to determine the failure status of the failure management object when the failure management objects causing the failure exceed the defined quorum. do.

The failure impact criterion ('maximum value') compares the status values of the failure management object with a preset threshold and determines the maximum value among the status values of the failure management object that caused the failure as the failure status of the failure management object. do.

The failure impact criterion ('condition value') compares the status values of the failure management object with a predetermined threshold value and the failure value of the failure management object when the status values of the failure management object that caused the failure exceed the condition value. Judging by the state.

Among the above-described disability impact attributes, the disability impact search range includes reflecting internal disturbances first, reflecting external disturbances first, and reflecting mixed disturbances.

Reflecting the internal failure impact first is a failure impact determination method that judges the failure status of the high-level failure management object by prioritizing the failure impact determination result generated by the internal components causing the failure. Here, the internal components are failure management objects related to service operation and are basic servers or unit objects of the basic server.

Priority reflecting the external failure impact is a failure impact determination method that judges the failure status of a high-level failure management object by prioritizing the result of failure impact determination generated by the external components that caused the failure. Here, the external components are unit objects of an external server or an external server of another service not directly related to the operation of the corresponding service.

The reflection of mixed failure impact is a failure impact determination method that determines the failure status of a higher level failure management object by mixing the failure impact determination results generated by the internal and external components that caused the failure.

2 is a diagram illustrating a process of setting a service failure impact map propagation path of servers related to service operation when a failure occurs in a unit object according to the first embodiment of the present invention.

The failure impact generation unit 140 receives the state value of each unit object from the server 1, the server 2, and the server 3, and compares the state value of each received unit object with a threshold value of each preset unit object. To determine the impact of failure.

As shown in FIG. 2, the central processing unit, memory, disk, and network interface card of the server 1 have status values of 90, 60, 50, 50, and normal, and a threshold value of each unit object is 90 (fatal) / 80. (Emergency) / 70 (Danger) / 60 or less (Normal), the threshold of the application process is set to Down / Wait.

Therefore, the failure impact generation unit 140 sets the failure impact determination result to 'fatal' according to the failure impact determination criteria ('maximum value').

Server 2's central processing unit, memory, disks, and network interface cards have status values of 50, 80, 30, 20, and Normal, and each unit object has a threshold of 90 (fatal) / 80 (urgent) / 70 (critical). / 60 or less (normal), the threshold of the application process is set to Down / Wait.

Accordingly, the failure impact generation unit 140 sets the failure impact determination result to 'urgent' according to the failure impact determination criteria ('maximum value').

Server 3's central processing unit, memory, disks, and network interface cards have status values of 10, 30, 20, 70, and Normal, and each unit object has a threshold of 90 (fatal) / 80 (urgent) / 70 (critical). / 60 or less (normal), the threshold of the application process is set to Down / Wait.

Therefore, the failure impact generation unit 140 sets the failure impact determination result to 'risk' according to the failure impact determination criteria ('maximum value').

The failure impact transmitter 150 transmits each failure impact determination result ('fatal', 'emergency', 'risk') generated by the server 1, the server 2, and the server 3 to the service.

The failure impact generation unit 140 determines a failure impact determination result of each of server 1, server 2, and server 3 received by the service, and a threshold value ('attention') of a predetermined service based on a failure impact determination criterion ('maximum value'). Based on ') and the range of disability impact search (' internal disability impact first '), the disability impact determination result (' fatality ') is generated. As a result, services ('fatal'), server 1 ('fatal'), server 1's central processing unit ('fatal'), server 2 ('urgent'), server 2's memory ('urgent'), server 3 ( 'Risk'), server 3's network interface card ('risk') is set up, so that the fault propagation path between service, server and unit object is established.

FIG. 3 is a diagram illustrating a process of setting a service failure impact propagation path of servers related to service operation when a failure occurs in a unit object according to a second embodiment of the present invention.

As shown in FIG. 3, the failure impact determination criteria and the failure impact determination results of the server 1, the server 2, and the server 3 are the same as in the first embodiment of FIG. 2, and thus redundant descriptions thereof will be omitted.

In FIG. 3, server 1, server 2, and server 3 are basic servers related to service operation, and server 4 is an external server associated with another service or system not directly related to the service.

Server 4's central processing unit, memory, disks, and network interface cards have status values of 10, 30, 20, 20, and Normal, and each unit object has a threshold of 90 (fatal) / 80 (urgent) / 70 (critical). / 60 or less (normal), the threshold of the application process is set to Down / Wait.

Therefore, the failure impact generation unit 140 sets the failure impact determination result to 'normal' according to the maximum value impact determination criteria.

The failure impact transmitter 150 uses the failure impact determination results ('fatal', 'emergency', 'risk', 'normal') generated by the server 1, the server 2, the server 3, and the server 4 as a service. send.

The failure impact generation unit 140 may determine the failure impact result of each of the server 1, the server 2, the server 3, and the server 4 received in the service and the threshold value ('normal') of the preset service, based on the quorum impact determination criteria and Based on the disability influence search range ('reflecting the mixed disability effect'), a disability impact determination result ('normal') is generated. Accordingly, services ('fatal'), server 1 ('fatal'), server 1's central processing unit ('fatal'), server 2 ('urgent'), server 2's memory ('urgent'), server 3 ('Risk'), Server 3's network interface card ('Risk'), and Server 4 ('Normal') establish the fault propagation path between the service, server, and unit object.

FIG. 4 is a diagram illustrating a process of setting a service failure impact propagation path of servers related to service operation when a failure occurs in a unit object according to a third embodiment of the present invention.

The central processing unit 1, central processing unit 2, central processing unit 3, central processing unit 4, and central processing unit 5 of the central processing unit group have status values of 90, 60, 50, 50, and 50, and the threshold values of each unit object. Set to 90 (fatal) / 80 (urgent) / 70 (danger) / 60 or less (normal).

Accordingly, the failure impact generation unit 140 sets the failure impact determination result to 'normal' according to the failure impact determination criterion ('quorum') of the CPU group.

Memory 1, Memory 2, Memory 3, Memory 4, and Memory 5 of the memory group have status values of 50, 80, 30, 20, and 20, and the threshold value of each unit object is 90 (fatal) / 80 (urgent) / 70 Set to (Danger) / 60 or less (Normal).

Therefore, the failure impact generation unit 140 sets the failure impact determination result to 'normal' according to the failure impact determination criterion ('quorum') of the memory group.

Hard disk 1, hard disk 2, hard disk 3, hard disk 4, and hard disk 5 of the hard disk group have status values of 10, 30, 20, 70, and 40, and the threshold value of each unit object is 90 (fatal) / Set it to 80 (Emergency) / 70 (Danger) / 60 or less (Normal).

Therefore, the failure impact generation unit 140 sets the failure impact determination result to 'normal' according to the failure impact determination criteria ('quorum') of the hard disk group.

The network interface card 1, network interface card 2, network interface card 3, network interface card 4, and network interface card 5 of the network interface group have status values of 10, 30, 20, 20, and 40, and a threshold value of each unit object. Set to 90 (fatal) / 80 (emergency) / 70 (danger) / 60 or less (normal).

Accordingly, the failure impact generation unit 140 sets the failure impact determination result to 'normal' according to the failure impact determination criteria ('quorum') of the network interface group.

The failure impact transmitter 150 determines the failure impact results of each of the CPUs, memory groups, hard disk groups, and network interface groups ('normal', 'normal', 'normal', and 'normal'). ) To the service.

The failure impact generation unit 140 determines the failure impact result of each of the central processing unit group, the memory group, the hard disk group, and the network interface group received by the service and the threshold value ('normal') of the preset service. Based on the degree determination criteria ('maximum value') and the disability influence search range ('internal disability influence first'), the disability influence determination result ('normal') is generated.

As a result, services ('normal'), central processing unit groups ('normal'), central processing unit 1 ('fatal'), memory groups ('normal'), memory 2 ('urgent'), and hard disk groups ( By setting up 'Normal', Hard Disk 4 ('Danger'), and Network Interface Card Group ('Normal'), fault propagation path between service, server and unit object is established.

The embodiments of the present invention described above are not implemented only by the apparatus and / or method, but may be implemented through a program for realizing a function corresponding to the configuration of the embodiments of the present invention, a recording medium on which the program is recorded, and the like. Such implementations may be readily implemented by those skilled in the art from the description of the above-described embodiments.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1 is a block diagram schematically illustrating an internal configuration of a service failure monitoring apparatus according to an exemplary embodiment of the present invention.

2 is a diagram illustrating a process of setting a service failure impact map propagation path of servers related to service operation when a failure occurs in a unit object according to the first embodiment of the present invention.

FIG. 3 is a diagram illustrating a process of setting a service failure impact propagation path of servers related to service operation when a failure occurs in a unit object according to a second embodiment of the present invention.

FIG. 4 is a diagram illustrating a process of setting a service failure impact propagation path of servers related to service operation when a failure occurs in a unit object according to a third embodiment of the present invention.

Claims (10)

(a) selecting a failure management object related to service operation, wherein the failure management object includes a service, a server, and a unit object; (b) setting respective failure impact attributes for the service, the server, and the unit object, wherein the failure impact attribute includes a failure impact determination criterion and a failure impact search range; And (c) generating a result of determining a failure impact degree for each of the service, the server, and the unit object based on the failure impact property to provide a service between a plurality of servers related to the operation of the service and a unit object of each server; Steps to Set Up the Fault Impact Propagation Path Service failure monitoring method comprising a. According to claim 1, After step (c), (d) comparing the status values of the failure management object causing the failure with a predetermined threshold value, and then analyzing the failure effects of the service, the server, and the unit object based on the failure determination criteria and the failure impact search range. Generating a result of determining the degree; And (e) transmitting the result of the failure impact determination of each of the generated service, server, and unit object from the unit object to the server and from the server to the service through the failure impact transmission path and the failure impact reception path; To establish a fault propagation path Service failure monitoring method further comprising. The method of claim 2, After step (e), Outputting a failure state, a failure location and a failure impact of the failure management object, and a failure impact determination result of each of the generated service, server, and unit object through the topology map; And Selecting a failure management object in the failure impact transmission path and the failure impact reception path to search for a failure propagation path between the service, the server, and the unit object; Service failure monitoring method further comprising. The method according to any one of claims 1 to 3, The criterion for determining the impact of failure is that after comparing the status values of the failure management object with the preset threshold, An average value influence criterion for reflecting an average value of the state values of the failure management object causing the failure as a failure state of the failure management object; A quorum influence determination criterion that reflects a failure state of the corresponding failure management object when the failure management objects causing the failure exceed a defined quorum; A maximum value influence determination criterion for reflecting a maximum value among the state values of the failure management object causing the failure as a failure state of the corresponding failure management object; And Criteria for determining the condition value influence that reflects the failure status of the corresponding failure management object when the status values of the failure management object causing the failure exceed the condition values The service failure monitoring method, characterized in that for selecting any one of the criteria. The method according to any one of claims 1 to 3, The failure impact search range, The internal component that causes the failure, wherein the internal component is a failure management object related to the operation of the service, includes a plurality of primary servers or respective unit objects of the plurality of primary servers. First reflecting the impact of an internal failure determined as a failure state of a high-level failure management object; The external component that caused the failure, wherein the external component is a failure management object of an external service not directly related to the service, includes a plurality of external servers or respective unit objects of the plurality of external servers. First reflecting an external failure influence that determines the failure state of the higher level failure management object by giving priority to the failure impact degree; And Reflects the mixed failure effect that determines the failure effect generated by the internal components and the external components as the failure state of the high level failure management object. Service failure monitoring method, characterized in that any one of. (a) A plurality of servers related to the operation of the service—each server compares the state values of the unit objects causing the failure with predetermined thresholds and then generates a server failure impact determination result based on the first failure determination criteria. Reflecting to the failure state of each server to register in the topology map; And (b) generating service failure impact determination results based on a second failure determination criterion and a failure impact search range based on each failure impact determination result of the plurality of servers; Step of establishing fault propagation path between unit objects Service failure monitoring method comprising a. A failure management object registration unit configured to register a failure management object related to service operation, wherein the failure management object includes a service, a server, and a unit object in a database storing the failure management object and registering the same in a topology map; An attribute setting unit for setting a failure impact attribute of the registered failure management object, wherein the failure impact attribute includes a first failure impact determination criterion, a second failure impact determination criterion, and a failure impact search range; And A fault impact degree that sets a fault impact propagation path between a plurality of servers related to the operation of the service and a unit object of each server by generating a fault impact determination result using the fault impact property in the fault management object. Path selector Service failure monitoring device comprising a. The method of claim 7, wherein After comparing the state values of the unit objects causing the failure with preset thresholds, a server failure impact determination result is generated based on the first failure impact determination criterion, and each server failure impact of a plurality of servers is also determined. A failure impact generation unit that generates a service failure impact determination result based on the second failure determination criteria and the failure impact search range. Service failure monitoring device further comprising. The method according to claim 7 or 8, A fault impact level output unit that outputs a fault state, fault impact level, and the generated fault impact level determination result of the fault management object through the topology map. Service failure monitoring device further comprising. The method according to claim 7 or 8, A fault impact propagation path searching unit that searches for a fault propagation path between the service, the server, and the unit object by selecting the fault management object in the fault impact transmission path and the fault impact receiving path. Service failure monitoring device further comprising.

Images