JP2001184281A - System and method for managing event information - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the processing load and traffics of a server part in an event information managing system having a client/server constitution and an event information managing method. SOLUTION: This event information managing system is provided with a server part 1 for accepting event notification from a part to be monitored in a network and a client part 2 having an event processing part 5 and a picture display part 6. The event processing part 5 of the client part 2 is provided with an event accepting part 7 for accepting the event notification from the server part 1 and a hierarchical monitor data holding part 8 for holding warning events in which the event notification indicates the generation of warning, and for deleting them by warning events in which the event notification indicates the release of warning. Then, the information of the warning events from the hierarchical monitor data holding part 8 is transferred to the monitor screen 10 of the picture display part 6, and displayed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an event information management system having a client-server configuration for displaying and monitoring the status of a monitored unit based on various event notifications from the monitored unit in a network. Related to the event information management method.

[0002]

2. Description of the Related Art FIG. 17 is an explanatory diagram of a conventional event information management system. 70 is a monitored unit in a network, 71 is a server unit, 72 is a client unit, and 73 is a local area network (LAN). And an outline of a server unit 71 and a client unit 72; 74, an event reception processing unit; 75, a database; and an operating system (OPS) having a client-server configuration.

The monitored unit 70 indicates switching devices and the like scatteredly arranged on a network, and notifies a server unit 71 of occurrence of various events. The server unit 71 performs processes related to network monitoring, management, operation, and the like.
The client unit 72 is connected to the client unit 72 via the AN 73, and responds to the event notification from the monitored unit 70 by the client unit 7
Second, a display notification related to the event notification is performed. The database 75 includes, for example, nodes node1 to node
For each of the locations 1 to y in Y, the presence or absence of an alarm is stored. For example, when an event notification indicating the occurrence of a failure at the location x of the node nodeX is received,
As shown by hatching, the presence of an alarm can be stored.

The client unit 72 displays an event display screen such as event contents on a screen display unit in accordance with a notification from the server unit 71, manages the monitored unit 70 in a hierarchical structure, and designates a designated The alarm status and the like are displayed according to the selected hierarchy. The illustrated screen display unit shows a case where an upper layer monitoring screen and its lower layer monitoring screens 1 and 2 are displayed as having an alarm and no alarm, and a lower layer monitoring screen 3 of the lower layer monitoring screen 2 is displayed as a server. In accordance with the contents of the database 75 of the unit 71, the presence of an alarm or the like is displayed in a window format at the location x of the node nodeX.

FIG. 18 is a sequence explanatory diagram of a conventional example, which will be described with reference to FIG. From the monitored unit 70,
An event notification such as an alarm is sent to the server unit 71. In response to the event notification, the event reception processing unit 74 of the server unit 71 performs a process of writing to the database 75. Then, the server unit 71 notifies the client unit 72 for real-time display. Thereby, the content of the event notification is displayed on the event display screen of the client unit 72.

When opening the lower layer monitoring screen 3 of the monitoring screen of the client section 72, for example, a screen information read request corresponding to the lower layer monitoring screen 3 is sent to the server section 71. Thereby, the server unit 71 stores the database 75
The information corresponding to the lower layer monitoring screen 3 is read from the client unit 72 as shown in the screen information read response.
To send to. Therefore, the lower layer monitoring screen 3 includes the node n
The presence of an alarm is displayed at the location x of modeX.

[0007]

The server unit 71 performs not only management of event information but also various processes such as network monitoring, management, and operation, and according to a screen information read request from the client unit 72. Since the screen information read from the database 75 or the like is transferred, there is a problem that the processing load on the server unit 71 is large and the traffic between the server unit 71 and the client unit 72 via the LAN 73 or the like is large. An object of the present invention is to reduce the processing load on a server unit and reduce traffic between a server unit and a client unit.

[0008]

According to the present invention, there is provided an event information management system comprising: (1) a server unit 1 for receiving and processing an event notification from a monitored unit; An event information management system including a client unit 2 having a screen display unit 6 for displaying a state of the monitored unit, wherein the server unit 1 receives and processes an event notification from the monitored unit. The client unit 2 includes an event processing unit 5 and a screen display unit 6 having a function of displaying an event display screen 9 and a monitoring screen 10. The event processing unit 5 is configured to perform at least an event notification from the server unit 1. Is provided with a hierarchical monitoring data holding unit 8 for holding an alarm event indicating that an alarm is being generated in accordance with the hierarchical structure of the monitored unit.

(2) The server unit 1 includes an event reception processing unit 3 and an entire event database 4 that stores event information based on the event notification received by the event reception processing unit 3. The unit 5 includes an event receiving unit 7 and a hierarchical monitoring data holding unit 8
The event receiving unit 7 receives an event notification from the server unit 1 and stores the alarm event during which an alarm is occurring in the hierarchical monitoring data holding unit 8.

(3) The server section 1 includes an event reception processing section 3, the client section 2 includes an event processing section 5 and a screen display section 6, and the event processing section 5 includes an event reception section 7, The system includes an entire event data holding unit for holding event information on the event notification received by the event receiving unit 7 and a hierarchical monitoring data holding unit 8 for holding an alarm event during which an alarm is generated by the event notification.

(4) The client section 2 includes an event processing section 5 and a screen display section 6 having a function of displaying an event display screen and a monitoring screen. The event processing section 5 includes an event reception section 7 and an event reception section. An all event data holding unit that holds event information on the event notification received by the receiving unit 7, a hierarchical monitoring data holding unit 8 that holds an alarm event during which an alarm is generated by the event notification,
A screen object holding unit for holding object information corresponding to the open screen in the screen display unit.

(5) The hierarchical monitoring data holding unit 8 stores the highest importance of the lower layer alarm for the alarm event as the comprehensive importance of the upper layer alarm corresponding to the hierarchical structure of the monitored unit. In addition, a configuration is provided in which the alarm event whose alarm has been recovered is deleted, and the comprehensive importance of the upper layer is updated.

[0013] The event information management method of the present invention comprises:
(6) A server unit 1 for receiving and processing an event notification from a monitored unit, and a client unit 2 having a screen display unit 6 for transferring information between the server unit 1 and displaying the state of the monitored unit. An event information management method for managing event information, wherein the server unit 1 processes the event notification from the monitored unit received by the event reception processing unit 3 and sends out the event notification to the client unit 2. When the event notification from the event reception processing unit 5 of the server unit 1 is an alarm event indicating that an alarm has occurred, the event reception unit 7 of the unit 2 stores the alarm event in the hierarchical monitoring data storage unit 8 and releases the alarm. Is displayed, the corresponding alarm event is deleted, and the alarm event held in the hierarchical monitoring data holding unit 8 is displayed on the monitoring screen 10 of the screen display unit 6. It is intended to include a degree.

(7) The client unit 2 includes an event processing unit 5 and a screen display unit 6.
Is an event receiving unit 7 and a hierarchical monitoring data holding unit 8
And an event data holding unit, and a screen object holding unit. When an event notification is received from the server unit 1 by the event receiving unit 7, the event information is sequentially stored in the all event data holding unit. When the alarm event indicates that an alarm has occurred, the alarm event is held in the hierarchical monitoring data holding unit. When the alarm event indicates that the alarm has been canceled, the corresponding alarm event is deleted and the screen display unit 6 is opened. The object information of the middle event display screen 9 and the monitoring screen 10 is held in the screen object holding unit, and the event receiving unit 7 reads out the object information corresponding to the event notification from the screen object holding unit, and It includes the process of displaying on the monitoring screen.

[0015]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is an explanatory diagram of a first embodiment of the present invention, wherein 1 is a server unit, 2 is a client unit,
Reference numeral 3 denotes an event reception processing unit, 4 denotes an entire event database, 5 denotes an event processing unit, 6 denotes a screen display unit, 7 denotes an event reception unit, 8 denotes a hierarchical monitoring data holding unit, 9 denotes an event display screen, and 10 denotes a monitoring screen. Is shown. The screen display unit 6 includes a display unit such as a cathode ray tube or a liquid crystal panel, and a display control processing unit, and can display the event display screen 9 and the monitoring screen 10 in a window format or as two screens.

The server unit 1 also includes an event reception processing unit 3 for receiving an event notification from a monitored unit (not shown).
And an event database 4 for storing received event notifications, and performs processing such as network monitoring, management, and operation. The client unit 2 includes an event processing unit 5 and a screen display unit 6, and the server unit 1 and the client unit 2 are connected by a LAN (not shown) or the like. The event processing unit 5 of the client unit 2 includes an event receiving unit 7 and a hierarchical monitoring data holding unit 8, receives an event notification from the server unit 1 in the event receiving unit 7, and performs a hierarchical type For example, it is stored in the monitoring data holding unit 8 as shown as alarm events 1 to M.

FIG. 2 is a sequence explanatory diagram of the first embodiment of the present invention, which will be described with reference to FIG. When the event notification processing unit 3 of the server unit 1 receives the event notification from the monitored unit, the event information according to the event notification is stored in the entire event database 4 of the server unit 1 as shown as event 1 to event m. In addition, an event notification is sent to the event receiving unit 7 of the client unit 2.

The event receiving unit 7 of the client unit 2
It is determined whether the type of the event notification is a normal event such as start-up or change of the monitored unit or an alarm event due to the occurrence of a failure. 8, the alarm event is held as shown as a hierarchical monitoring data update, and in the case of the alarm event indicating the alarm release, the corresponding alarm event is deleted. Then, a monitoring screen information read request corresponding to the content of the monitoring screen of the screen display unit 6 is sent from the screen display unit 6 to the hierarchical monitoring data holding unit 8.
The monitoring screen read response is sent to the screen display unit 6 and the monitoring screen 1
0 is displayed.

When the event display screen 9 is activated, it sends an all event information read request to the server unit 1, and the server unit 1 sends an all event information read response from the all event database 4, and the event display screen 9 can display the contents of the event.

Therefore, the monitoring screen 10 only needs to be transferred between the monitoring screen reading request and the monitoring screen reading response with the hierarchical monitoring data holding unit 8 of the event receiving unit 5. That is, between the server unit 1 and the client unit 2,
Only the event notification, the all event information read request, and the all event information read response are included, and the monitoring screen information read request and the
Since only the inside of the client unit 2 is sufficient, the processing load on the server unit 1 is reduced, and the server unit 1 and the client unit 2
Can be reduced.

FIG. 3 is an explanatory diagram of an event message.
(A) shows a case of an alarm event, and (B) shows a case of a general event, which is composed of a header part and a data part.
ect Ref. ), And the data section includes an upper node (node), a lower node (node), a location in the node, an event type, an importance of an alarm, and an additional level corresponding to the hierarchical structure of the monitored section. Information, and the importance of the alarm is three of severe maj, mild min, and none
Shows the case of stages. It is to be noted that the degree of importance of the alarm can be set to more stages.

By using such an event message, the alarm event of the hierarchical monitoring data holding unit 8 of the client unit 2 is as shown in FIG. 4, for example. That is,
The event type is only for alarms and the severity is severe m
aj or mild min. It should be noted that the index (INDEX) 1 of the hierarchical monitoring data holding unit 8
The state where the alarm event is held in the region of ~ M. In the case of alarm release, the corresponding alarm event is deleted. Therefore, the hierarchical monitoring data holding unit 8 stores only an alarm event during which an alarm is occurring.

FIG. 5 is a flow chart of the event receiving unit according to the first embodiment of the present invention, in which it is determined whether or not an event has been received (A1). Processing is performed (A2). This storage processing (A2) determines whether the type of the event message is an alarm (A21), and determines whether or not the upper node has alarm data of the same value (importance) only in the case of an alarm (A22). In the case of the same value, it is determined whether or not the lower node has alarm data of the same value (A23), and in the case of the same value, it is determined whether or not there is alarm data of the same value in the location (A24). In this case, it is determined that the alarm has been recovered, and the corresponding notification data is deleted (A25). That is, when an alarm event having the same content is received twice, it is determined that the alarm has been released, and the corresponding alarm event is deleted from the hierarchical monitoring data holding unit 8. In this case, the empty area from which the alarm event has been deleted is sequentially shifted, and the latest alarm event is updated so as to be the last in the index. Note that such processing can be realized by address control.

Steps (A22), (A23), (A
24), if the values are not the same, it is determined that the event is a new alarm event, and as shown in FIG.
If an alarm event is already held in M, M + 1
The data is stored first (A26). For example, when an alarm is displayed as a type of the event message and none is displayed as the importance, and when the warning is canceled, the importance is determined and the alarm event can be deleted from the hierarchical monitoring data holding unit 8. is there.

As described above, the hierarchical monitoring data holding unit 8 stores information on the upper node, lower node, and location of the current alarm state corresponding to the hierarchical structure of the monitored unit. The identification of the alarm event and the control of writing to and reading from the hierarchical monitoring data holding unit 8 may be performed by the event receiving unit 7 or the writing / reading control unit of the hierarchical monitoring data holding unit 8. it can.

FIG. 6 is a diagram for explaining the updating of the importance. The alarm event held in the hierarchical monitoring data holding unit 8 corresponds to the hierarchical structure of the monitored unit and reflects the importance of the lower layer to the upper layer. The event importance,
The importance within the dotted frame is the comprehensive importance. For example, the first layer is the uppermost layer, the node node-A, the Xth layer is the lowermost layer, the locations 1 and 2, and the X-1 layer above it, the node n
In the case of having mode-a and node-b, as shown in (A), in the case where the importance is low at both the points 1 and 2, the comprehensive importance of the X-1 layer and the first layer is set at the minimum level. And

In this state, a new node nod
When an alarm with a severe maj is generated in the lower layer of e-a, that is, at the location 3 in the X-th layer, the comprehensive importance of the node node-a in the upper layer of the location 3 as shown in FIG. , And the inclusive importance of the first-layer node node-A above it is updated to the level of major ma.

In the state (A), the node node
-A for the lower layer part 2 in the step (A2
As described in 5), when the alarm release is indicated,
The alarm event at the lower part 2 of the node node-a is deleted from the hierarchical monitoring data holding unit 8, and the state shown in FIG. In this case, the warning is canceled when the importance is mild and the comprehensive importance is mild, so there is no change in the comprehensive importance. On the other hand, in the state of (B), when the alarm of the point 3 in the lower layer of the node node-a is released, the warning of the importance of the severe maj disappears. ) Is updated.

FIG. 7 shows a flowchart of the update of the comprehensive importance, where the total number of alarms held is M, the number of alarm data searches up to the corresponding lower node is x, and the number of alarm data searches up to the corresponding location is y. First, it is determined whether the type of the event notification is an alarm (B1). In the case of an alarm event, it is determined whether the same upper node (node) exists in the upper monitoring layer information (B2). In the case, for example, FIG.
The alarm event is stored in M + 1 next to the index M in the hierarchical monitoring data holding unit in (B8). If there is the same upper node, the upper comprehensive importance is compared with the importance of the alarm event (B3). If the received alarm event is higher in importance, the upper comprehensive importance is set to the importance of the alarm event. Update (B9).

If the importance of the received alarm event is lower than the comprehensive importance, it is determined whether the same lower node (node) exists in the lower monitoring layer information (B4). If there is no same lower node, the corresponding lower node is determined. Assuming that the number of searches up to x is x, the alarm event is stored at the (x + 1) -th place in the hierarchical monitoring data holding unit (B10). If there is the same lower node, the lower comprehensive importance is compared with the importance of the alarm event (B5). If the lower comprehensive importance is lower than the importance of the alarm event, the lower comprehensive importance is determined by the importance. Update (B11).

If the lower comprehensive importance is higher than the importance of the alarm event, it is determined whether or not the same location exists in the lowest monitoring layer information (B6). Assuming that the number is y, the alarm event is stored in the (y + 1) th of the hierarchical monitoring data holding unit (B1
2). If there is the same location, the corresponding alarm event in the hierarchical monitoring data holding unit is deleted (B7). Also in this case, it is possible to perform control so as to delete the corresponding alarm event from the hierarchical monitoring data holding unit when the importance of the event message is displayed as “none” and the alarm is canceled.

FIG. 8 is an explanatory diagram of the hierarchical monitoring data holding unit, and shows a case where alarm events are held in accordance with a hierarchical structure. That is, upper monitoring layer information, lower monitoring layer information,
The lower monitoring layer information and the event information indicate the case where the upper monitoring layer information is the upper node and the comprehensive importance, the lower monitoring layer information is the lower node and the comprehensive importance, and the lowest monitoring information is the location. The event information includes a host name, a number, and reference information Ref.
And various types of information.

The contents shown in the figure correspond to the upper node node-.
A, lower nodes node-a and node-c of A, lower node node-d of upper node node-B, lowest positions 1 and 9 for lower node node-a, lowest positions 5 for lower node node-c, Lower node no
A case where alarm events are stored as a hierarchical configuration when the lowest places 6 and 2 for de-d transmit alarm events is shown.

Then, the importance of the points 9 and 6 becomes severe maj
, The lower nodes node-a, node
The inclusive importance of −d is set to severe maj, whereby the inclusive importance of the upper nodes node-A and node-B is set to severe maj. Such hierarchical monitoring data holding unit 8
Can be easily realized by referring to the node information of the event message by the event receiving unit 7 or the not-shown alarm event writing control unit.

FIG. 9 is an explanatory diagram of the second embodiment of the present invention, in which 11 is a server unit, 12 is a client unit, 13
Is an event reception processing unit, 15 is an event processing unit, 16 is a screen display unit, 17 is an event reception unit, 18 is a hierarchical monitoring data storage unit, 19 is an event display screen, 20 is a monitoring screen, and 21 is all event data storage Indicates a part.

In this embodiment, the event processing unit 15 of the client unit 12 includes an event receiving unit 17, a hierarchical monitoring data holding unit 18, and an all event data holding unit 21.
Is provided, and the entire event data holding unit 21
Is a configuration corresponding to the entire event database 4 provided in the server unit 1 in FIG. The following sequence will be described with reference to FIG. The event notification from the monitored unit (not shown) is received by the event reception processing unit 13 of the server unit 11, and the event notification is performed to the event reception unit 17 of the client unit 12. The event receiving unit 17 sequentially stores the events in the event data holding unit 21 as shown as events 1 to m, determines the event type, and, for the alarm event, the hierarchical monitoring data holding unit 18 Update data.

The processing between the hierarchical monitoring data holding unit 18 and the monitoring screen 20 of the screen display unit 16 is the same as that between the hierarchical monitoring data holding unit 8 and the monitoring screen 10 in FIG. Thereby, a screen of a desired monitoring layer can be displayed. While the event display screen 19 is running, the server 11
, Without making an access to the event processing unit 15, an all event information reading request is made to the all event data holding unit 21 of the event processing unit 15, and an event display can be enabled by an all event data reading response to the request.

FIG. 11 is a flowchart showing the operation of storing data in all the event data holding units. It is determined whether or not an event has been received (C1). It is determined whether or not the event notification is an alarm event. If the event notification is an alarm event, the alarm event is stored in the hierarchical monitoring data holding unit 18 (C3). The storage of the alarm event in the hierarchical monitoring data holding unit 18 is performed by the step (B) in FIG.
1) to (B12).

The storage of the event information in the all event data holding unit 21 (C2) is performed in steps (C21) to (C21).
First, as shown in (C23), it is determined whether or not a cycle is present (C21). That is, the all event data holding unit 2
In the case where 1 has the first to n-th areas, the event is stored in order from the first, and when the event is stored in the n-th area, it is determined that the event is cyclic.
= 0 (C23), the event information is stored in the (m + 1) th, that is, the first area. Otherwise, the event information is stored in the (m + 1) th area, with the area before storing the event as the mth area (C22).

In this case, the event information is stored sequentially from the first area, and the next event information having the event information stored in the last n-th area is stored so as to overwrite the first first area. The event information after writing the event information in the last n-th area is deleted by deleting the event information in the oldest first area, and sequentially shifted in the direction of the first area. It is also possible to make the n-th area empty and perform control to write to the empty area.

FIG. 12 is an explanatory diagram of the entire event data holding unit, showing a case where event information in the form of an event message is sequentially stored in the areas of the indexes index1 to indexm. The index index1 is the oldest event information and the index indexm is used. Is the newest event information. Various known means can be applied to the memory control means for cyclically storing the information thus received.

FIG. 13 is an explanatory diagram of the third embodiment of the present invention, in which 31 is a server unit, 32 is a client unit,
3 is an event reception processing unit, 35 is an event processing unit, 36
Denotes a screen display unit, 37 denotes an event receiving unit, 38 denotes a hierarchical monitoring data holding unit, 39 denotes an event display screen, 40 denotes a monitoring screen, 41 denotes an entire event data holding unit, and 42 denotes a screen object holding unit.

In this embodiment, the event processing unit 35
In addition, a screen object holding unit 42 is provided together with a hierarchical monitoring data holding unit 38 and an all event data holding unit 41,
Event information can be displayed automatically and in real time on the event display screen 39 and the monitoring screen 40. The screen object holding unit 42 stores, for example, an open event display screen, monitoring screens a, b,... H, and object information as shown in FIG.

The hierarchical monitoring data holding unit 38 and the all event data holding unit 41 have the same configuration as the hierarchical monitoring data holding unit 18 and the all event data holding unit 21 in FIG. The event notification processing unit 33 of the server unit 31 receives the event notification from the monitored unit (not shown), notifies the event reception unit 37 of the client unit 32, and the event reception unit 37 stores all event data. When the event information is stored in the section 41 and the event type is identified, and the alarm event indicating that the alarm is occurring is stored in the hierarchical monitoring data holding 38.

FIG. 15 is an explanatory diagram of a sequence according to the third embodiment of the present invention.
This will be described with reference to FIG. The event display screen 39 of the screen display unit 36 issues an all event information read request to the all event data storage unit 41, and the all event data storage unit 41 returns an all event information read response to the event display screen 39. , An event display is performed, the screen object holding unit 42 is notified of the event display screen open, and the object information of the event display screen is held.

The monitoring screen 40 sends a monitoring screen information reading request to the hierarchical monitoring data holding unit 38, and the hierarchical monitoring data holding unit 38 returns a monitoring screen information reading response to the monitoring screen 40, and Is displayed, the screen object holding unit 42 is notified of the opening of the monitoring screen, and the object information of the monitoring screen is held.

In response to an event notification from a monitored unit (not shown), the event reception processing unit 33 of the server unit 31 transmits the event reception unit 37 of the client unit 32.
Then, an event notification is performed. The event receiving unit 37 stores all event data in the all event data holding unit 41. If the event type of the event notification indicates an alarm event, the event receiving unit 37 stores the event data in the hierarchical monitoring data holding unit 38.
(A) Store hierarchical monitoring data.

The event receiving unit 37 makes a (b) screen object information read request to the screen object storage unit 42. In response to this, the screen object storage unit 42 transmits (c) a screen object information read response. As
Returns the object information of the open screen. The event receiving unit 37 can recognize the screen during opening, and performs (d) real-time display notification on the event display screen 39 and (e) real-time display notification on the monitoring screen 40. . Thereby, the event display screen 39 and the monitoring screen 40 can be displayed automatically and in real time according to the event notification.

FIG. 16 is a flowchart of the event receiving unit according to the third embodiment of the present invention. It is determined whether or not an event notification has been received from the server unit 31 (D1). The data is stored in the holding unit 41 (D2). This storage processing is performed in step (C2) of FIG.
1) to (C23).

When the event type indicates an alarm event, it is stored in the hierarchical monitoring data holding unit 38 (D
3). This storage processing is performed in steps (B1) to (B1) of FIG.
12). Then, the screen object holding unit 4
2, a screen object information read request is made and read out (D 4).
A real-time display notification is performed (D5), and a real-time display notification is performed on the monitoring screen 40 (D6).

The present invention is not limited to only the above-described embodiments, but can be variously combined, and can be applied to a system in which a server is provided with a plurality of clients. is there.

[0052]

As described above, according to the present invention, the event notification from the monitored unit is received by the event reception processing unit 3 of the server unit 1, and the event notification is transmitted to the event reception unit 7 of the client unit 2. When the client unit 2 identifies that the event is an alarm event indicating the occurrence of an alarm in the event receiving unit 7, the client unit 2 stores the alarm event in the hierarchical monitoring data holding unit 8, and responds when indicating the cancellation of the alarm. Therefore, only the alarm event during which an alarm is occurring is stored in the hierarchical monitoring data holding unit 8. Then, based on the alarm event information from the hierarchical monitoring data holding unit 8, the screen display unit 6
Can be displayed on the monitoring screen 10. Therefore, there is an advantage that the processing load on the server unit 1 can be reduced and the traffic between the server unit 1 and the client unit 2 can be reduced.

Further, the event display screen 9 of the screen display unit 6
By providing the event processing unit with an event data holding unit for holding all event information to be displayed on the server unit, the processing load on the server unit 1 and the traffic can be further reduced. Also, by providing a screen object holding unit in accordance with the open event display screen and the monitoring screen on the screen display unit, an alarm can be automatically and in real time according to the event notification without increasing the processing load and traffic of the server unit 1. There is an advantage that the occurrence state can be displayed.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram of a first embodiment of the present invention.

FIG. 2 is an explanatory diagram of a sequence according to the first embodiment of this invention.

FIG. 3 is an explanatory diagram of an event message.

FIG. 4 is an explanatory diagram of a hierarchical monitoring data holding unit.

FIG. 5 is a flowchart of an event receiving unit according to the first embodiment of this invention.

FIG. 6 is an explanatory diagram of updating importance.

FIG. 7 is a flowchart of comprehensive importance update.

FIG. 8 is an explanatory diagram of a hierarchical monitoring data holding unit.

FIG. 9 is an explanatory diagram of a second embodiment of the present invention.

FIG. 10 is an explanatory diagram of a sequence according to the second embodiment of this invention.

FIG. 11 is a flowchart of a storing operation to all event data holding units.

FIG. 12 is an explanatory diagram of an all event data holding unit.

FIG. 13 is an explanatory diagram of a third embodiment of the present invention.

FIG. 14 is an explanatory diagram of a screen object holding unit.

FIG. 15 is a sequence explanatory diagram of the third embodiment of the present invention.

FIG. 16 is a flowchart of an event receiving unit according to the third embodiment of this invention.

FIG. 17 is an explanatory diagram of a conventional event information management system.

FIG. 18 is a sequence explanatory diagram of a conventional example.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Server part 2 Client part 3 Event reception processing part 4 All event database 5 Event processing part 6 Screen display part 7 Event reception part 8 Hierarchical monitoring data holding part 9 Event display screen 10 Monitoring screen

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Mitsuyoshi Matsuzawa 1-5-2 Honcho, Kanazawa City, Ishikawa Prefecture Inside Fujitsu Hokuriku Communication System Co., Ltd. (72) Inventor Naoki Araki 1-5-2, Honmachi Kanazawa City, Ishikawa Prefecture Fujitsu Hokuriku Communication System Co., Ltd. (72) Inventor Shigeki Kado 1-5-2 Honcho, Kanazawa City, Ishikawa Prefecture Inside Fujitsu Hokuriku Communication System Co., Ltd. (72) Tomoyo Fukuoka 1-5-2, Honcho Kanazawa City, Ishikawa Prefecture F-term in Fujitsu Hokuriku Communication System Co., Ltd. (reference) 5B089 GA11 GA21 GB09 JA35 KA06 KA08 KC28 KC39 KC51 LB14 5K035 AA02 JJ03 KK04 MM03 MM07

Claims (7)

[Claims] 1. A server unit for receiving and processing an event notification from a monitored unit, and information transfer between the server unit and the server unit.
And a client unit having a screen display unit for displaying the state of the monitored unit. The server unit receives an event notification from the monitored unit and processes the event notification. The client unit includes an event processing unit, and a screen display unit having a function of displaying an event display screen and a monitoring screen, and the event processing unit generates an alarm in at least an event notification from the server unit. An event information management system, comprising: a hierarchical monitoring data holding unit that holds an alarm event indicating the inside in accordance with the hierarchical structure of the monitored unit. 2. The server unit includes: the event reception processing unit; and an entire event database that stores event information based on an event notification received by the event reception processing unit. The event processing unit of the client unit includes: A configuration having an event receiving unit and a hierarchical monitoring data holding unit, receiving an event notification from the server unit by the event receiving unit, and holding an alarm event during which an alarm is occurring in the hierarchical monitoring data holding unit. The event information management system according to claim 1, further comprising: 3. The server unit includes an event reception processing unit, the client unit includes an event processing unit and a screen display unit, and the event processing unit receives an event by the event reception unit and the event reception unit 2. The storage device according to claim 1, further comprising: an entire event data holding unit that holds event information about the event notification, and a hierarchical monitoring data holding unit that holds an alarm event during which an alarm is generated by the event notification. Event information management system. 4. The client unit includes an event processing unit and a screen display unit having a function of displaying an event display screen and a monitoring screen, wherein the event processing unit receives an event received by the event reception unit. An all event data holding unit for holding event information about an event notification, a hierarchical monitoring data holding unit for holding an alarm event during the occurrence of an alarm by the event notification, and an object corresponding to an open screen in the screen display unit The event information management system according to claim 1, further comprising: a screen object holding unit that holds information. 5. The hierarchical monitoring data holding unit stores, according to the hierarchical structure of the monitored unit, the highest importance of the lower layer alarm for the alarm event as the comprehensive importance of the upper layer alarm. The event information management system according to any one of claims 1 to 4, further comprising a configuration for deleting the alarm event from which the alarm has been recovered and updating the comprehensive importance of the upper layer. 6. A server unit for receiving and processing an event notification from a monitored unit, and information transfer between the server unit and the server unit.
And a client unit having a screen display unit for displaying the state of the monitored unit. In the event information management method for managing event information, the server unit receives the monitored unit received by an event reception processing unit. And sends the event notification to the client unit.When the event notification from the event reception processing unit of the server unit is an alarm event indicating that an alarm has occurred, The alarm event is held in the hierarchical monitoring data holding unit, and when the alarm event indicates that the alarm is released, the corresponding alarm event is deleted, and the alarm event held in the hierarchical monitoring data holding unit is displayed on the screen display unit. A method for managing event information, comprising the step of displaying on the monitoring screen. 7. The client unit includes an event processing unit and a screen display unit, wherein the event processing unit includes an event receiving unit, a hierarchical monitoring data holding unit, an all event data holding unit, a screen object A storage unit, and when event notification from the server unit is received by the event reception unit, event information is sequentially stored in the all event data storage unit, and when the event notification is an alarm event indicating that an alarm has occurred, The alarm event is held in the hierarchical monitoring data holding unit, and when the alarm event indicates that the alarm has been canceled, the corresponding alarm event is deleted, and the open event display screen and the monitoring screen of the screen display unit are displayed. The object information is stored in the screen object storage unit, and the event reception unit stores the event information from the screen object storage unit. 7. The event information management method according to claim 6, further comprising reading object information corresponding to the notification and displaying the object information on the event display screen and the monitoring screen.