JP4892260B2 - Event notification device and event notification program - Google Patents

Description

  The present invention relates to an event notification device and an event notification program, and more particularly to an event notification device and an event notification program that detect an event to be monitored and notify the event.

  In recent years, computers have come to provide users with a multitasking environment in which a plurality of tasks are simultaneously performed using the functions of the OS. In a multitasking environment, computers perform task scheduling based on priority and fairness.

  An example of a task executed in such a multitasking environment is, for example, one or more monitoring tasks for monitoring whether or not the monitoring target is operating normally, and a notification when the monitoring target is not operating normally There are one or more notification tasks to perform.

Patent Document 1 discloses a technique related to software monitoring means for monitoring the normality of software processing. Patent Document 2 discloses that monitoring is performed by a plurality of monitoring threads that are sequentially activated from the monitoring process for the monitoring target.
JP-A-7-98667 JP 2001-5694 A

  However, in a multitasking environment, consideration is not given to the task execution environment (especially resource status). For example, when a memory exhaustion (insufficiency) occurs during execution of a task, a memory depletion is avoided by using a function for forcibly terminating a task, such as an OOM (out-of-memory) killer, in a multitasking environment.

  Therefore, if resource depletion occurs during the execution of the monitoring task and notification task as described above, the monitoring task and the notification task may also be forcibly terminated, and the executability of notification performed when the monitoring target is abnormal There was a problem of lowering. Considering the roles of the monitoring task and the notification task as described above, some kind of contrivance that does not decrease the executability of the notification even when the resource is exhausted has been desired.

  The present invention has been made in view of the above points, and an object of the present invention is to provide an event notification device and an event notification program that improve the performance of event notification when resources are depleted.

In order to solve the above-described problem, the present invention provides an event notification device that detects an event to be monitored and notifies the event, and includes at least one monitoring unit that detects the event to be monitored; and One or more reporting means for reporting an event based on the detected event, and switching between the normal mode and the degeneration mode based on the resource consumption state, and there is a resource allocation request to the monitoring means and the reporting means during the normal mode And a resource arbitration unit that allocates a pool area on a kernel space when a resource allocation request is made to the monitoring unit and the reporting unit during the degeneration mode. The means is configured to switch from normal mode to degenerate mode while resources are in short supply. When there is a resource allocation request during the normal mode, and a degradation management unit that manages the degradation mode, a shared area on the user space is allocated as a resource dynamically consumed by the monitoring unit and the reporting unit, and the degradation is performed. When there is a resource allocation request during the mode, a resource control unit that allocates a pool area on the kernel space as a resource dynamically consumed by the monitoring unit and the reporting unit, and a plurality of the reporting units are reporting an event or an event when a report waiting, and a notification control means for executing said notification means of the event notification during or event notification waiting order of priority, the resource mediation section, sometimes the reduction mode, the user as the resource said notification means is assigned a common area in space, the through after notification said event Allocates a pool area on the kernel space as a resource unit consumes dynamically, the monitoring means is assigned a shared area in the user space as the resource, after notification success of the event, degenerate mode the monitoring means It is characterized by restarting .

  The degeneration management unit may allocate a shared area on the user space as a resource dynamically consumed by the monitoring unit and the notification unit after the normal mode is restored.

In order to solve the above problems, the present invention provides an event notification program executed in an event notification device including a storage device and an arithmetic processing device, wherein the storage device is on a shared area and a kernel space on a user space. A pool area, wherein the arithmetic processing unit includes one or more monitoring means for detecting an event to be monitored, and one or more notification means for reporting an event based on the event detected by the monitoring means; The normal mode and the degeneration mode are switched based on the resource consumption state, and when there is a resource allocation request to the monitoring unit and the notification unit during the normal mode, a shared area on the user space is allocated, and during the degeneration mode When there is a resource allocation request to the monitoring unit and the reporting unit, a pool area in the kernel space is allocated. The resource arbitration unit is configured to manage the normal mode and the degeneration mode so as to switch from the normal mode to the degeneration mode while resources are insufficient, and during the normal mode When there is a resource allocation request, the monitoring unit and the reporting unit allocate a shared area on the user space as a resource that is dynamically consumed, and when there is the resource allocation request during the degeneration mode, the monitoring unit and the Resource control means for allocating a pool area in the kernel space as a resource dynamically consumed by the reporting means, and when the plurality of reporting means are reporting an event or waiting for an event report, Let the notification means function as a notification control means for executing in descending order of priority, Resource mediation section, sometimes the degenerate mode, the notification means is assigned a common area on the user space as the resource pool area on the kernel space as a resource which the notification means is consumed dynamically after notification said event And an event notification program for causing the monitoring unit, which is assigned a shared area on the user space as the resource, to function so as to restart the monitoring unit in a degenerate mode after successful reporting of the event. It is characterized by that.

  As described above, according to the present invention, it is possible to provide an event notification device and an event notification program that improve the performance of event notification when resources are depleted.

  Next, the best mode for carrying out the present invention will be described based on the following embodiments with reference to the drawings. In this embodiment, the monitoring agent-equipped device 1 will be described as an example of the event notification device. However, any device, device, or computer that can detect an event and notify the event may be a board or an expansion card. Also good.

  FIG. 1 is a configuration diagram of an example of a system including a monitoring agent mounting device. The monitoring agent mounting apparatus 1 includes a monitoring agent 10 and a resource arbitration unit 20. The monitoring agent 10 is configured to include monitoring tasks 11a to 11c and reporting tasks 12a to 12c. In addition, when any of the monitoring tasks 11a to 11c may be used, it is simply referred to as the monitoring task 11. When any of the notification tasks 12a to 12c is acceptable, it is simply referred to as the notification task 12.

  The monitoring tasks 11a to 11c are associated with the monitoring objects 2a to 2c on a one-to-one basis, and detect events of the monitoring objects 2a to 2c associated with the monitoring tasks 11a to 11c. The monitoring targets 2 a to 2 c are connected to the monitoring agent mounting apparatus 1 directly or via the network 3. Although FIG. 1 shows an example in which the monitoring targets 2a to 2c are outside the own device, they may be inside the own device. The notification tasks 12a to 12c are associated with the monitoring tasks 11a to 11c on a one-to-one basis, and perform an event notification to the network 4, for example, based on the events detected by the monitoring tasks 11a to 11c.

  The resource arbitration unit 20 manages the resource consumption state of its own device as the normal mode or the degeneration mode. Normal mode refers to a state where resources are not exhausted. Degeneration mode refers to a state where resources are exhausted. The resource arbitration unit 20 switches from the normal mode to the degeneration mode while the resource of the own device is exhausted. The resource arbitration unit 20 allocates a shared area on the user space or a pool area on the kernel space as a resource dynamically consumed by the monitoring task 11 and the notification task 12 based on the normal mode or the degeneration mode.

  Details of processing performed by the monitoring agent mounting apparatus 1 will be described later. Next, the hardware configuration of the monitoring agent mounting apparatus 1 will be described. FIG. 2 is a hardware configuration diagram of an example of the monitoring agent mounting apparatus. The monitoring agent mounting device 1 includes an input device 31, an output device 32, a drive device 33, an auxiliary storage device 34, a memory device 35, an arithmetic processing device 36, and an interface device 37 that are mutually connected by a bus B. .

  The input device 31 includes a keyboard and a mouse, and is used for inputting various signals. The output device 32 includes a display device and is used to display various windows, data, and the like. The interface device 37 includes a modem, a LAN card, and the like, and is used for connecting to the networks 3 and 4.

  The event notification program of the present invention is at least a part of various programs for controlling the monitoring agent mounting apparatus 1. The event notification program is provided by, for example, distribution of the recording medium 38 or downloading from the network 4 or the like. The recording medium 38 on which the event report program is recorded is information such as a CD-ROM, a flexible disk, a magneto-optical disk, etc., a recording medium for recording information optically, electrically or magnetically, a ROM, a flash memory, etc. Various types of recording media, such as a semiconductor memory that electrically records data, can be used.

  When the recording medium 38 on which the event notification program is recorded is set in the drive device 33, the event notification program is installed from the recording medium 38 to the auxiliary storage device 34 via the drive device 33. The event notification program downloaded from the network 4 or the like is installed in the auxiliary storage device 34 via the interface device 37.

  The monitoring agent loading device 1 stores the installed event report program and also stores necessary files, data, and the like. The memory device 35 reads and stores the event notification program from the auxiliary storage device 34 when the computer is activated. The arithmetic processing unit 36 implements various processes as will be described later in accordance with the event notification program stored in the memory device 35.

  FIG. 3 is a functional configuration diagram of an embodiment of the monitoring agent loading apparatus. The monitoring agent loading apparatus 1 is provided with a kernel space 100 and a user space 200 as memory spaces. The kernel space 100 is a memory space used by the kernel. In the kernel space 100, an operating system (OS) 101 and a pool area 102 are arranged.

  The user space 200 is a memory space used by applications and the like. In the user space 200, a monitoring agent 10, a resource switcher 201, a shared area 202, and a resource monitoring unit 203 are arranged. The resource switcher 201 corresponds to the resource arbitration unit 20 described above. Further, the resource monitoring unit 203 may be provided outside the monitoring agent mounting apparatus 1 and linked externally.

  The pool area 102 of the kernel space 100 is an area reserved in advance in order to avoid resource acquisition competition when resources are exhausted. The pool area 102 is an area locked on a RAM as an example of the memory device 35 on the kernel space 100. The pool area 102 is an area that can retain data and can be reused even after the monitoring task 11 and the reporting task 12 are completed.

  A shared area 202 of the user space 200 is an area that the OS 101 allocates to tasks including the monitoring task 11 and the notification task 12. The shared area 202 is a target of swap, there is competition for acquisition among tasks, and is a target of the OOM killer described above. Therefore, the task to which the shared area 202 is assigned may be forcibly terminated by the OOM killer.

  The resource switcher 201 is configured to include an abnormality degree preemption function unit 211, a resource control unit 212, and a degeneration management function unit 213. The resource control unit 212 includes a resource dynamic allocation unit 221 and a task switch 222.

  The resource switcher 201 hooks the resource allocation request from the monitoring task 11 and the notification task 12, and performs processing in the normal mode and the degeneration mode in a resource driven manner. The resource switcher 201 uses the pool area 102 as a resource to be dynamically consumed regardless of the normal mode or the degeneration mode in order to improve the executability when resources are exhausted.

  The degeneration management function unit 213 of the resource switcher 201 performs task control including degeneration mode management and task execution management. In the degeneration mode management, for example, a depletion notification from the resource monitoring unit 203 such as external resource management software is captured, and the normal mode and the degeneration mode are switched. The task execution management controls the degeneration of the monitoring task 11 and the notification task 12 and the recovery from the degeneration based on the normal mode or the degeneration mode managed by the degeneration mode management. Degeneration is determined based on a resource allocation request notified when the monitoring task 11 and the notification task 12 are activated.

  Here, degeneration from the normal mode to the degeneration mode will be described. The monitoring task 11 is always activated in order to detect events of the monitoring targets 2a to 2c. Since the monitoring task 11 needs to notify the detected event immediately, the event is detected and restarted in the order in which the event notification was successful, so that the monitoring task 11 is gradually switched to the degenerate mode. The notification task 12 is switched from the newly executed one to the degenerate mode. The notification task 12 during event notification or waiting for event notification is managed in the notification waiting queue, and is switched to the degeneration mode after event notification.

  Next, recovery from the degenerate mode to the normal mode will be described. The monitoring task 11 restarts and returns to the normal mode. If there is a notification task 12 corresponding to the monitoring task 11, the monitoring task 11 needs to acquire the event notification result, so that after the completion of the notification task 12, the monitoring task 11 is sequentially restarted to recover to the normal mode. The notification task 12 is restored from the newly executed task to the normal mode. Note that the reporting task 12 that is reporting an event or is waiting for an event report recovers to the normal mode after successful event reporting.

  When there is a resource allocation request from the monitoring task 11 and the notification task 12, the resource control unit 212 of the resource switcher 201 allocates the pool area 102 on the kernel space 100 as a resource in the degenerate mode, and the user space 200 in the normal mode. Shared area 202 is allocated as a resource.

  The resource dynamic allocation unit 221 of the resource control unit 212 performs resource allocation in the degenerate mode and resource allocation in the normal mode. The allocation of resources in the degeneration mode is performed by exclusively allocating the pool area 102 of the kernel space 100 to the monitoring task 11 and the reporting task 12, thereby securing resources that are dynamically consumed by the monitoring task 11 and the reporting task 12 when resources are depleted. However, the monitoring task 11 and the notification task 12 are sequentially switched to execution.

  The resource dynamic allocation unit 221 performs round-robin allocation while switching over a predetermined time in order to maintain fairness of event detection between the monitoring tasks 11. Further, the resource dynamic allocation unit 221 allocates the abnormality degree preemption function unit 211 from the newly executed notification task 12. The notification task 12 during event notification or waiting for event notification is assigned after event notification. Note that the resource allocation in the normal mode relays the shared area 202 of the user space 200 allocated by the OS 101 to the monitoring task 11 and the notification task 12.

  The task switch 222 of the resource control unit 212 performs switching in the degenerate mode and switching in the normal mode. Switching in the degeneration mode realizes task switching by resource allocation in the degeneration mode performed by the resource dynamic allocation unit 221. Switching in the normal mode depends on the scheduler of the OS 101.

  The abnormality degree preemption function unit 211 of the resource switcher 201 controls the order of event notification according to the priority of event notification. The abnormality level preemption function unit 211 sorts the notification waiting queue in descending order of the degree of abnormality, and causes the notification task 12 to be executed in descending order of priority in response to resource acquisition (resource allocation request) of the notification task 12. The abnormality degree preemption function unit 211 is an example of a notification control unit.

  Next, a switch table created and managed by the resource switcher 201 for degeneration control of the monitoring task 11 and the notification task 12 will be described. FIG. 4 is a configuration diagram of an example of a switch table. The switch table shown in FIG. 4 includes monitoring task information and report task information. The monitoring task information is composed of fields "monitoring task", "status", and "pool". The report task information is composed of fields “report task”, “status”, “abnormality”, and “pool”. That is, the switch table is composed of seven fields.

  The field “monitoring task” of the monitoring task information represents the identifier of the monitoring task 11. The field “status” of the monitoring task information represents information for determining whether the monitoring task 11 is in the normal mode or the degenerate mode.

  When the field “status” of the monitoring task information is “normal”, the monitoring task 11 is monitoring in the normal mode. When the field “status” of the monitoring task information is “degenerated”, the monitoring task 11 is monitoring in the degenerated mode. When the field “status” of the monitoring task information is “abnormal”, the monitoring task 11 has ended abnormally.

  Further, the field “pool” of the monitoring task information represents the usage status of the pool area 102 by the monitoring task 11. When the field “pool” of the monitoring task information is “used”, the monitoring task 11 has acquired the pool area 102 and is in use. When the monitoring task information field “pool” is “waiting for acquisition”, the monitoring task 11 is waiting for acquisition of the pool area 102. When the field “pool” of the monitoring task information is “no space”, there is no area that can be allocated to the monitoring task 11 in the pool area 102. When the field “pool” of the monitoring task information is “−”, the monitoring task 11 does not use the pool area 102.

  The field “report task” of the report task information represents an event identifier during event report in the report task 12. When the field “report task” of the report task information is “−”, there is no report task 12 that is reporting an event. The field “state” of the notification task information represents information for determining whether the notification task 12 is in the normal mode or the degenerate mode.

  When the field “status” of the report task information is “normal”, the report task 12 is communicating in the normal mode. When the field “status” of the report task information is “degenerate”, the report task 12 is communicating in the degenerate mode.

  When the field “status” of the report task information is “completed”, the report task 12 has ended normally. When the field “status” of the report task information is “abnormal”, the report task 12 has ended abnormally. When the field “status” of the report task information is “−”, the report task 12 does not exist.

  The field “abnormality” of the notification task information represents the degree of abnormality of the event reported from the notification task 12 as the priority of event notification. The field “abnormality” of the notification task information represents the priority of event notification by a numerical value (for example, 0 to 100). When the report task information field “abnormality” is “−”, the report task 12 does not exist.

  Further, the field “pool” of the notification task information represents the usage status of the pool area 102 by the notification task 12. When the field “pool” of the report task information is “used”, the report task 12 has acquired the pool area 102 and is currently using it. When the notification task information field “pool” is “waiting for acquisition”, the notification task 12 is waiting for acquisition of the pool area 102. When the field “pool” of the report task information is “no space”, there is no area that can be allocated to the report task 12 in the pool area 102. When the field “pool” of the report task information is “−”, the report task 12 does not use the pool area 102.

  Next, the procedure of processing performed by the monitoring agent mounting apparatus 1 will be described with reference to the flowchart of FIG. FIG. 5 is a flowchart illustrating an example of a processing procedure performed by the monitoring agent mounting apparatus.

  The degeneration management function unit 213 of the resource switcher 201 captures the depletion notification from the resource monitoring unit 203 that is externally linked, and switches between the normal mode and the degeneration mode as described above. The degeneration management function unit 213 proceeds to step S1 in response to a resource allocation request from the monitoring task 11 and the notification task 12, and determines whether the mode is the normal mode or the degeneration mode.

  In the normal mode, the resource dynamic allocation unit 221 proceeds to step S2 and relays the shared area 202 of the user space 200 allocated by the OS 101 to the monitoring task 11 and the notification task 12. If the mode is the degeneration mode, the resource dynamic allocation unit 221 proceeds to step S3, and the degeneration management function unit 213 controls degeneration of the monitoring task 11 and the notification task 12 based on the switch table described above.

  In step S 4, the resource control unit 212 allocates the pool area 102 on the kernel space 100 as a resource for the monitoring task 11 and the notification task 12. Further, the degeneration management function unit 213 reflects the pool area 102 on the kernel space 100 in the switch table of the pool area 102 when the pool area 102 is allocated as a resource for the monitoring task 11 and the notification task 12. In step S5, the abnormality degree preemption function unit 211 controls the order of event notification according to the priority of event notification.

  In step S6 following step S2 or S5, the monitoring task 11 and the notification task 12 perform processing by dynamically consuming the pool area 102 or the shared area 202 allocated as resources.

  Hereinafter, a procedure of processing performed by the monitoring agent mounting apparatus 1 will be described with reference to a switch table transition. FIG. 6 and FIG. 7 are transition diagrams showing the switch table immediately after degeneration and during degeneration. FIG. 8 is a transition diagram showing a switch table in recovery from degeneration. 6 to 8 show examples in which the monitoring tasks are an SNMP monitoring task, a syslog monitoring task, and an IO monitoring A task.

  First, referring to FIGS. 6 and 7, an example of the transition of the switch table immediately after degeneration and during degeneration will be described. 6 and 7, it is assumed that time has passed in the order of FIGS. 6 (a) to 6 (e), FIG. 7 (f), and FIG. 7 (g).

  FIG. 6A shows that the SNMP monitoring task, the syslog monitoring task, and the IO monitoring A task in the normal mode are activated in the normal mode before the degeneration, and the X event that is the notification task in the normal mode is being reported. Represents.

  FIG. 6B shows that the SNMP monitoring task in the normal mode is degenerated after completion of the X event as the notification task, and the pool area 102 is being used. FIG. 6B shows that the syslog monitoring task in the normal mode detects an event, the Y event that is the report task in the degenerate mode is being reported, and the pool area 102 is being used.

  In FIG. 6C, the IO monitoring A task in the normal mode detects an event. Since the Z event, which is a report task in the degenerate mode, has a higher degree of abnormality than the Y event and has a higher priority than the Y event, an event notification is performed instead of the Y event. The Y event is in a waiting state.

  FIG. 6D shows that the IO monitor A task in the normal mode is degenerated after completion of the Z event, which is the report task in the degenerated mode, and the pool area 102 is being used. The degenerated SNMP monitoring task and IO monitoring A task are switched at a predetermined time. Note that the Y event resumes event reporting in place of the completed Z event.

  In FIG. 6E, the syslog monitoring task in the normal mode is degenerated after the completion of the Y event that is the reporting task in the degenerated mode. The degenerated SNMP monitoring task, the syslog monitoring task, and the IO monitoring A task are switched at a predetermined time.

  FIG. 7F shows that the SNMP monitoring task in the degenerate mode detects an event, the W event that is the report task in the degenerate mode is being reported, and the pool area 102 is being used.

  In FIG. 7G, the IO monitoring A task in the degenerate mode has detected an event. Since the V event, which is a report task in the degenerate mode, has a higher degree of abnormality than the W event and has a higher priority than the W event, an event notification is performed instead of the W event. The W event is in a waiting state.

  Next, switch table transition in recovery from degeneration will be described as an example with reference to FIG. In FIG. 8, it is assumed that time elapses in the order of FIGS. 8 (a) to 8 (d).

  FIG. 8A is the same as FIG. 7G described above. In FIG. 8A, the SNMP monitoring task and the IO monitoring A task in the degeneration mode detect events before recovery from the degeneration. Since the V event, which is a report task in the degenerate mode, has a higher priority than the W event, event notification is performed instead of the W event. The W event is in a waiting state.

  In FIG. 8B, the syslog monitoring task in the degenerate mode without the notification task is restarted to recover to the normal mode. Note that the SNMP monitoring task and the IO monitoring A task in the degenerate mode with the report task wait for the completion of the report task W event and V event in the degenerate mode.

  In FIG. 8C, the IO monitoring A task in the degenerate mode is restarted after the completion of the V event as the notification task, and is restored to the normal mode. Further, in FIG. 8D, the SNMP monitoring task in the degenerate mode is restarted after completion of the W event as the notification task, and is restored to the normal mode.

  Since the monitoring agent loading device 1 switches resources allocated to the monitoring task 11 and the notification task 12 from the shared area 202 to the pool area 102 when the resource is depleted, there is no possibility of being forcibly terminated like the shared area 202. It is possible to improve the execution performance.

  As described above, the monitoring agent-equipped device 1 according to the present invention is not a mechanism for automatically adjusting necessary resources and avoiding exhaustion as in the scale-out operation of an autonomous system, but the exhaustion is resolved after detecting the exhaustion of resources. It is possible to improve the executability of tasks that are executed in the meantime.

The present invention may have the following configurations as described below.
(Appendix 1)
An event notification device that detects an event to be monitored and reports an event,
One or more monitoring means for detecting the monitored event;
One or more reporting means for reporting an event based on the event detected by the monitoring means;
Switching between the normal mode and the degeneration mode based on the resource consumption state, and when there is a resource allocation request to the monitoring unit and the notification unit during the normal mode, a shared area on the user space is allocated, and during the degeneration mode An event notification device, comprising: a resource arbitration unit that allocates a pool area in a kernel space when there is a resource allocation request to the monitoring unit and the notification unit.
(Appendix 2)
The resource arbitration means includes a degeneration management means for managing the normal mode and the degeneration mode so as to switch from the normal mode to the degeneration mode while resources are insufficient.
When there is the resource allocation request during the normal mode, the monitoring unit and the notification unit allocate a shared area on the user space as a resource that is dynamically consumed, and when there is the resource allocation request during the degeneration mode, The event notification device according to claim 1, further comprising resource control means for allocating a pool area in a kernel space as resources dynamically consumed by the monitoring means and the notification means.
(Appendix 3)
After the degeneration management means is switched to the degeneration mode, the monitoring means and the reporting means are dynamically activated when the monitoring means assigned a shared area on the user space as the resource detects the event. The event notification device according to appendix 2, wherein a pool area on the kernel space is allocated as a resource to be consumed.
(Appendix 4)
The event report according to appendix 2 or 3, wherein the degeneration management unit allocates a shared area on the user space as a resource dynamically consumed by the monitoring unit and the reporting unit after recovering to the normal mode. apparatus.
(Appendix 5)
The resource arbitration unit further includes a report control unit that executes the reporting unit that is reporting the event or is waiting for the event reporting in descending order of priority when the plurality of reporting units are reporting an event or waiting for an event report. The event notification device according to any one of appendices 2 to 4, characterized in that:
(Appendix 6)
The resource control means is a resource dynamic allocation means for allocating a shared area on the user space or a pool area on the kernel space as resources dynamically consumed by the monitoring means and the reporting means,
6. The appendix according to any one of claims 2 to 5, further comprising: a switching unit that switches between the monitoring unit and the reporting unit to which a shared area in a user space or a pool area in a kernel space is allocated as the resource. Event reporting device.
(Appendix 7)
The resource arbitration unit stores a table indicating whether the monitoring unit and the reporting unit are in a normal mode or a degenerate mode in a pool area in a kernel space. The event notification device according to any one of the above.
(Appendix 8)
An event notification program executed in an event notification device including a storage device and a processing unit,
The storage device is provided with a shared area on the user space and a pool area on the kernel space,
The arithmetic processing unit;
One or more monitoring means for detecting the monitored event;
One or more reporting means for reporting an event based on the event detected by the monitoring means;
Switching between the normal mode and the degeneration mode based on the resource consumption state, and when there is a resource allocation request to the monitoring unit and the notification unit during the normal mode, a shared area on the user space is allocated, and during the degeneration mode An event notification program for functioning as resource arbitration means for allocating a pool area in a kernel space when there is a resource allocation request to the monitoring means and the notification means.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

It is a block diagram of an example of the system containing the monitoring agent mounting apparatus. It is a hardware block diagram of an example of the monitoring agent mounting apparatus. It is a function block diagram of one Example of the monitoring agent mounting apparatus. It is a block diagram of an example of a switch table. It is a flowchart of an example showing the procedure of the process which the monitoring agent mounting apparatus performs. FIG. 10 is a transition diagram (1/2) showing a switch table immediately after degeneration and during degeneration. FIG. 10 is a transition diagram (2/2) showing a switch table immediately after degeneration and during degeneration. It is a transition diagram showing the switch table in the recovery from degeneration.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Monitoring agent mounting apparatus 2a-2c Monitoring object 3, 4 Network 10 Monitoring agent 11, 11a-11c Monitoring task 12, 12a-12c Notification task 20 Resource arbitration part 31 Input apparatus 32 Output apparatus 33 Drive apparatus 34 Auxiliary storage apparatus 35 Memory Device 36 Arithmetic processing device 37 Interface device 38 Recording medium 100 Kernel space 101 OS
DESCRIPTION OF SYMBOLS 102 Pool area | region 200 User space 201 Resource switcher 202 Shared area 203 Resource monitoring part 211 Abnormality preemption function part 212 Resource control part 213 Degeneration management part 221 Resource dynamic allocation part 222 Task switch

Claims (3)

An event notification device that detects an event to be monitored and reports an event,
One or more monitoring means for detecting the monitored event;
One or more reporting means for reporting an event based on the event detected by the monitoring means;
Switching between the normal mode and the degeneration mode based on the resource consumption state, and when there is a resource allocation request to the monitoring unit and the notification unit during the normal mode, a shared area on the user space is allocated, and during the degeneration mode When there is a resource allocation request to the monitoring unit and the reporting unit, the resource arbitration unit allocates a pool area on the kernel space,
The resource arbitration means includes a degeneration management means for managing the normal mode and the degeneration mode so as to switch from the normal mode to the degeneration mode while resources are insufficient.
When there is the resource allocation request during the normal mode, the monitoring unit and the notification unit allocate a shared area on the user space as a resource that is dynamically consumed, and when there is the resource allocation request during the degeneration mode, Resource control means for allocating a pool area on a kernel space as resources dynamically consumed by the monitoring means and the reporting means;
When a plurality of the reporting means are in an event report or waiting for an event report, the report control means for executing the notification means in the event report or waiting for an event report in order of priority,
The resource arbitration means, in the degeneration mode , the reporting means assigned a shared area on the user space as the resource, and a pool on the kernel space as a resource that the reporting means dynamically consumes after the event notification An event notification device characterized by allocating an area and restarting the monitoring means, which is assigned a shared area on a user space as the resource, in the degenerate mode after the notification of the event. 2. The event notification device according to claim 1, wherein the resource arbitration unit allocates a shared area on a user space as a resource dynamically consumed by the monitoring unit and the notification unit after recovery to the normal mode. . An event notification program executed in an event notification device including a storage device and a processing unit,
The storage device is provided with a shared area on the user space and a pool area on the kernel space,
The arithmetic processing unit;
One or more monitoring means for detecting the monitored event;
One or more reporting means for reporting an event based on the event detected by the monitoring means;
Switching between the normal mode and the degeneration mode based on the resource consumption state, and when there is a resource allocation request to the monitoring unit and the notification unit during the normal mode, a shared area on the user space is allocated, and during the degeneration mode When there is a resource allocation request to the monitoring unit and the reporting unit, it functions as a resource arbitration unit that allocates a pool area on the kernel space,
The resource arbitration means includes a degeneration management means for managing the normal mode and the degeneration mode so as to switch from the normal mode to the degeneration mode while resources are insufficient.
When there is the resource allocation request during the normal mode, the monitoring unit and the notification unit allocate a shared area on the user space as a resource that is dynamically consumed, and when there is the resource allocation request during the degeneration mode, Resource control means for allocating a pool area on a kernel space as resources dynamically consumed by the monitoring means and the reporting means;
When a plurality of the reporting means are in the event report or waiting for an event report, the reporting means in the event report or waiting for the event report is made to function as a report control means for executing in descending order of priority,
The resource arbitration means, in the degeneration mode , the reporting means assigned a shared area on the user space as the resource, and a pool on the kernel space as a resource that the reporting means dynamically consumes after the event notification An area is allocated , and the monitoring means to which a shared area on the user space is allocated as the resource is made to function so as to restart the monitoring means in a degenerate mode after the successful reporting of the event . Event report program.

Images