JP2015082131A - Monitoring system, monitoring method, monitoring program, and monitoring device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily and rapidly acquire a resource state of a monitoring target server by simple structure.SOLUTION: A monitoring system comprises: a monitoring target device which is a target of monitoring; a monitoring server device which remotely logs in to the monitoring target device, acquires a resource state of the monitoring target device at predetermined time intervals, and outputs the acquired resource state; and a monitoring client device which displays the resource state output from the monitoring server device.

Description

  The present invention relates to a monitoring system, a monitoring method, a monitoring program, and a monitoring device, and more particularly to a monitoring system, a monitoring method, a monitoring program, and a monitoring device for monitoring resources of a device to be monitored.

  In order to monitor a plurality of servers, a network management system (NMS) is widely used. The NMS uses the NMS application program installed in the NMS client, the NMS server, and the monitoring target server (hereinafter referred to as “monitoring target server”) constituting the NMS to acquire the usage status of the resources of the monitoring target server. .

  In relation to the present invention, Patent Document 1 describes a component management system for a component management client to manage network components via an EMS (element management system server) application server and an EMS component interface server. doing.

Japanese translation of PCT publication No. 2010-502089 (paragraph [0022]-[0027])

  Whether the NMS application program operates on the monitoring target server generally depends on the OS (operation system) of the NMS and the type of OS of the monitoring target server. For this reason, when the monitoring target server is monitored using the NMS application program, if the monitoring target server is equipped with an OS different from the NMS, the NMS application program may not operate on the monitoring target server. As a result, the NMS may not be able to monitor servers with different OSs.

  Further, the NMS generally used does not have a function of directly confirming the resource state of the monitoring target server. For this reason, in order to know the resource status of the monitored server, the user must log in directly to the server whenever necessary to obtain resource information. The user can check the status of the monitored server resource in real time. Can not be confirmed. As a result, there is also a problem that the user cannot quickly cope with the situation where there is a possibility that a failure may occur due to tight use of server resources.

  On the other hand, the component management system described in Patent Document 1 has a function of managing network components by NMS. However, in the component management system described in Patent Document 1, an EMS application server and an EMS component interface server are arranged between the NMS and the network component. For this reason, the component management system described in Patent Document 1 has a complicated configuration, and there is a problem that the resources of the monitoring target server cannot be quickly grasped with a simple configuration.

(Object of invention)
An object of the present invention is to provide a technique for easily and quickly acquiring resources of a monitoring target apparatus with a simple configuration.

  The monitoring system of the present invention acquires the resource status of the monitoring target device to be monitored and the resource status of the monitoring target device at a predetermined time interval by remotely logging in to the monitoring target device. A monitoring server device for outputting, and a monitoring client device for displaying the resource status output from the monitoring server device.

  The monitoring method of the present invention acquires the resource status of the monitored device at a predetermined time interval by remotely logging in to the monitored device to be monitored, outputs the acquired resource status, and outputs the resource status The resource status is displayed.

The monitoring apparatus of the present invention includes a resource state management unit that acquires and outputs a resource state of the monitoring target device at a predetermined time interval by remotely logging in to the monitoring target device to be monitored, and the output of the output And a screen display unit for displaying a resource state.

  The monitoring program of the present invention is a procedure for acquiring a resource state of the monitoring target device at a predetermined time interval by remotely logging in to a monitoring target device to be monitored, a step of outputting the acquired resource state, A procedure for displaying the output resource state is executed by the computer of the monitoring apparatus.

  The monitoring device of the present invention includes a resource state management unit that acquires the resource state of the monitoring target device at a predetermined time interval by remotely logging in to the monitoring target device to be monitored.

  The present invention has an effect that the resources of the monitoring target device can be easily and quickly acquired with a simple configuration.

It is a block diagram which shows the structure of the monitoring system of 1st Embodiment. It is a flowchart which shows the operation example of the NMS server in 1st Embodiment. It is a flowchart which shows the operation example of the monitoring object server in 1st Embodiment. It is a figure which shows the state transition of the screen of an NMS client in 1st Embodiment. It is a block diagram which shows the structure of the monitoring system of 2nd Embodiment.

(First embodiment)
FIG. 1 is a block diagram illustrating a configuration of a monitoring system 10 according to the first embodiment of this invention. The monitoring system 10 includes an NMS client 100, an NMS server 110, a server 150, and a server 160.

  The NMS client 100 includes a screen display unit 101. The NMS server 110 includes an alarm management function unit 130, a resource monitoring function unit 140, and a resource state management unit 141. The NMS client 100 and the NMS server 110 constitute an NMS 200. The NMS client 100 sets the operation of the NMS 200 by the operation of the operator 20.

  Servers 150 and 160 are monitoring target servers. Servers 150 and 160 are connected to NMS server 110. The connection form between the monitoring target server and the NMS server 110 is not limited to the form shown in FIG. For example, a certain monitoring target server may relay communication between the NMS server 110 and another monitoring target server.

  The resource state management unit 141 of the NMS server 110 can remotely log in to each of the servers 150 and 160 and acquire the resource states of the servers 150 and 160 at predetermined time intervals. The monitored servers may include the NMS client 100 and the NMS server 110 in addition to the servers 150 and 160. The predetermined time interval may not be a fixed interval. For example, the resource state acquisition interval may be changed as needed by setting the NMS 200, or the resource state may be acquired at an arbitrary time by the operation of the operator 20.

  The operator 20 is a user who operates the NMS client 100. The operator 20 confirms the display content of the screen display unit 101 of the NMS client 100 and operates the NMS client 100 to manage the NMS server 110 and the servers 150 and 160. Further, the NMS 200 may provide a general NMS monitoring control function to the operator 20 by an NMS application program installed in the NMS client 100 and the NMS server 110. The NMS application program links the NMS client 100 and the NMS server 110 together.

  The resource state management unit 141 confirms and stores the resource state of the monitored server (hereinafter referred to as “resource state”). When the NMS server is included in the monitoring target server, the resource state management unit 141 confirms the resource state of the NMS server 110 and stores it as the resource state of the NMS server 110. Furthermore, the resource state management unit 141 remotely logs into the servers 150 and 160 and accesses the resource state management units 151 and 161, respectively. Then, the resource state management unit 141 acquires the resource states of the servers 150 and 160 from the resource state management units 151 and 161 at predetermined time intervals, and stores the acquired resource states of the respective monitoring target servers. Here, even when the NMS application program is installed in the NMS 200, the resource state management unit 141 remotely logs into the servers 150 and 160 by a procedure or program independent of the NMS application program. The operator 20 may notify the NMS server 110 via the NMS client 100 of login information for the NMS server to log in remotely to the servers 150 and 160.

  Examples of monitored server resources monitored by the NMS 200 include the CPU (central processing unit) usage rate, the number of active processes, the number of waiting processes, the memory usage, and swap of each monitored server There is usage, disk usage and network traffic. The resource status collected by the resource status management unit 141 includes these values and statuses. However, the monitored resources are not limited to these. Further, the resources to be monitored may be different for each monitoring target server.

  The resource monitoring function unit 140 notifies the alarm management function unit 130 and the NMS client 100 of the resource status acquired by the resource status management unit 141 from the monitoring target server. The alarm management function unit 130 extracts information such as “abnormal state”, “normal state”, and alarm included in the resource state and notifies the NMS client 100 of the information.

  Note that the time interval at which the resource state management unit 141 obtains the resource state from the resource state management units 151 and 161 of the servers 150 and 160, the failure detection threshold value and the failure recovery threshold value that are the criteria for determining the occurrence and recovery of an abnormal state The operator 20 is set by operating the NMS client 100.

  The NMS client 100 is notified of the resource status of the monitoring target server acquired by the resource monitoring function unit 140. The NMS client 100 displays the acquired resource state on the screen display unit 101 through a GUI (graphic user interface) screen. For example, the screen display unit 101 displays the resource value of the monitoring target server, information on whether the resource state is “abnormal state” or “normal state”, and the alarm occurrence state. The operator 20 can check the status of the monitoring target server for each server through the screen display unit 101. Furthermore, the operator 20 can operate the NMS client 100 to instruct the monitoring target server to forcibly stop the process causing the resource depletion or to restart the server.

  When the resource usage increases in any monitored server and the resource usage exceeds a predetermined threshold (hereinafter referred to as “depleted state”), the resource status of each monitored server The management unit adds information indicating that the server resource is in the “abnormal state” to the resource state and stores the information. For example, when the resource is depleted in the server 150, the resource state management unit 151 of the server 150 additionally stores information indicating that the resource state of the server 150 is “abnormal state”. Furthermore, when the resource is in an abnormal state, the resource state management unit 151 of the server 150 adds alarm information according to the degree of resource tightness to the resource state.

  An operation example of the monitoring system 10 according to the first embodiment will be described with reference to the flowcharts of FIGS. 2 and 3. FIG. 2 is a flowchart showing an operation example of the NMS server 110 in the first embodiment.

  First, the NMS server 110 is activated (step S1 in FIG. 2). In step S1, when the NMS server 110 starts normally and the resource state is not in a depleted state, the resource state management unit 141 sets the resource state of the NMS server 110 to “normal state”.

  Next, the resource state management unit 141 acquires the resource state of the monitoring target server at predetermined time intervals (step S2). In the first embodiment, the monitoring target servers are the servers 150 and 160, and the NMS server 110 and the NMS client 100 may be further included in the monitoring target server.

  When the resource status of the monitoring target server can be acquired (step S3: Yes), the resource monitoring function unit 140 notifies the NMS client 100 of the acquired resource status (step S4). The resource status obtained from the monitored server includes the detailed status of each server resource, information on whether the resource is in an abnormal state or normal state, and the degree of resource tightness when the resource is in an abnormal state Alarm information according to the is included. Information such as “abnormal state”, “normal state”, and alarm is output to the NMS client 100 via the alarm function management unit 130.

  If the resource status cannot be acquired from some or all of the monitoring target servers (step S3: No), the resource status management unit 141 notifies the NMS client 100 that the acquisition of the resource status has failed (step S3). S5). Then, when a predetermined time has elapsed, the resource state management unit 141 tries again to acquire the resource state of the monitoring target server (step S2). In this case, the NMS server 110 may acquire the resource status of the monitored server that failed to acquire the resource status in the previous step 2 or may acquire the resource status of all the monitored servers again. May be.

  The above steps S1 to S5 are procedures for the NMS server 110 to acquire the resource state from the monitoring target server. These procedures may be executed at different timings for each monitoring target server, or resource states may be acquired from a plurality of monitoring target servers at the same time.

  FIG. 3 is a flowchart illustrating an operation example of the monitoring target server in the first embodiment. In the following description, the server 150 is described as an example of the monitoring target server. However, the operation described in FIG. 3 is the same for other monitored servers.

  First, the monitoring target server is activated (step S6 in FIG. 3). Subsequently, the values of the threshold excess count and the threshold recovery count are initialized to 0 (step S7). The resource state management unit 151 acquires the resource state of the server 150 (step S8). Then, the resource state is compared with a preset failure detection threshold (step S9).

  When the resource state is less than the failure detection threshold (step S9: No), the resource state management unit 151 holds the latest resource state acquired, returns to step S8, and again after a predetermined time has elapsed. The resource status of the server 150 is acquired.

  If the resource state is equal to or greater than the failure detection threshold (step S9: Yes), the resource state management unit 151 stores the acquired latest resource state and increases the threshold excess count by 1 (step S10). ), The process of step S11 is executed.

  As described above, the resource state includes a plurality of resource states such as a CPU usage rate and a disk usage rate. In step S <b> 9, which resource state is to be compared can be set in advance for the NMS 200 by the operator 20. Further, the resource state management unit 151 compares the plurality of resource states with the corresponding failure detection threshold values in step S9, and if there are more than a predetermined number of resource states exceeding the failure detection threshold values, in step S10 The number of times the threshold is exceeded may be increased by one.

  In step S11, the threshold excess count is compared with a preset failure detection count. When the threshold excess count is less than the failure detection set count (step S11: No), the resource status management unit 151 holds the latest resource status acquired, returns to step S8, and at predetermined time intervals. The resource status is acquired from the server 150.

  If the threshold excess count is equal to or greater than the failure detection set count (step S11: Yes), it indicates that the resource depletion state continues for a certain period of time. In this case, the resource state management unit 151 sets the resource state of the server 150 to “abnormal state”. Information indicating the set state is added to the latest resource state. Furthermore, the resource state management unit 151 calculates an excess amount from the resource threshold of the server 150 based on the latest resource state (step S12). It is determined that the greater the amount of the resource that exceeds the failure detection threshold, the greater the degree of resource tightness. For example, if the CPU usage rate of the server 150 continues to be 70% or higher in steps S9 to S11, it is determined as “abnormal”, and if the CPU usage rate is 80% or higher and lower than 90% in step S12, “warning” is determined. When the CPU usage rate is 90% or more, an alarm such as “danger” with a higher degree of tightness may be issued. Alarms such as “warning” and “danger” issued in step S12 are added to the resource state according to the degree of resource tightness and acquired by the resource state management unit 141 of the NMS server 110 (FIG. 2). Step S2).

  Steps S8 to S11 show a procedure in which the resource state is set to the “abnormal state” when the resource depletion state continues for a predetermined period (until the threshold excess number reaches the failure detection set number).

  In step S13, it is determined whether the resource state of the server 150 has decreased to a predetermined failure recovery threshold. For example, in step S13, a state where the CPU usage rate of the server 150 is 65% is set as a failure recovery threshold, and when the CPU usage rate of the server 150 is less than 65%, it is determined that the resource depletion state has been resolved. May be.

  When the resource state of the server 150 has not decreased to the predetermined failure recovery threshold (step S13: No), the resource state management unit 151 holds the latest resource state, and after the predetermined time has elapsed, The resource state is read again (step S14).

  When the resource status of the server 150 has decreased to a predetermined failure recovery threshold or less (step S13: Yes), the resource status management unit 151 stores the latest resource status and increases the threshold recovery count by 1 (step S15). ), And proceeds to step S16.

  In step S16, it is confirmed whether the threshold restoration count has reached a predetermined restoration detection set count.

  If the threshold restoration count has not reached the predetermined restoration detection preset count (step S16: No), the process returns to step S13.

  When the threshold recovery count has reached the predetermined recovery detection setting count (step S16: Yes), the resource status management unit 151 sets the resource status of the server 150 to “normal status” (step S17), and goes to step S6. Return.

  As described above, steps S13 to S16 are performed when the state in which the resource state is exhausted (for example, the CPU usage rate is 65% or less) continues for a predetermined period (until the threshold recovery count reaches the recovery detection set count). The procedure for setting the resource status to “normal status” is shown.

  The procedure shown in FIGS. 2 and 3 may be executed by a program executed by a CPU included in the NMS client 100 and the NMS server 110. The program may be stored in a memory included in the NMS client 100 and the NMS server 110. Note that when the NMS application program is operating in the NMS 200, the program for executing the procedures of FIGS. 2 and 3 is executed independently of the NMS application program.

  FIG. 4 is a diagram illustrating a state transition of the screen of the NMS client 100 in the first embodiment. The NMS client 100 uses the screen display unit 101 to display the resource status of the monitoring target server acquired by the resource monitoring function unit 140 of the NMS server 110.

  On the screen of the NMS client 100, the resource status of the monitored server cannot be acquired, so the resource status is unknown (status S301), the status indicating that the monitored server is in the normal status (status S302), and the monitored server Is in an abnormal state (state S303).

  When at least one of the NMS server 110 and the monitoring target server is not activated, the NMS client 100 is not notified of the resource status of the monitoring target server. Accordingly, in this case, the screen state of the NMS client 100 is the state S301 (“resource state is unknown”).

  When the NMS server 110 and the monitoring target server are started and the resource state of the monitoring target server is not a depletion state, the screen state transitions from the state S301 to the state S302. After the NMS server 110 and the monitoring target server are activated, when the resource state acquired from the monitoring target server indicates an abnormal state, the screen state transitions from the state S301 to the state S303.

  Here, the screen display unit 101 of the NMS client 100 may display one of the states S301 to S303 for each monitoring target server. Alternatively, the NMS client 100 may display whether the resource status of the monitoring target server is a normal state or an abnormal state as the entire monitoring system 10. Then, a condition for causing a transition between the state S301, the state S302, and the state S303 may be set by the user 20 using the NMS client 100.

  If any of the monitoring target servers in the normal state becomes an abnormal state and the condition for transition from the state S302 to the state S303 is satisfied, the screen of the screen display unit 101 also changes from the screen corresponding to the state S302 to the screen corresponding to the state S303. Transition to. Further, as described in step S12 of FIG. 3, when the monitored server is in an abnormal state, an alarm is issued according to the degree of resource tightness. In the state S303, the NMS client 100 is notified from the resource monitoring function unit 140 of an alarm issued according to the degree of resource tightness in step S12 of FIG. The NMS client 100 displays the notified alarm on the screen display unit 101.

  On the other hand, when the resource state of the monitored server is restored from the abnormal state to the normal state and the condition for transition from the state S303 to the state S302 is satisfied, the screen of the screen display unit 101 also corresponds to the state S302 from the screen corresponding to the state S303. Transition to the screen to do.

  As described above, in the NMS system 10 of the first embodiment, the NMS server 110 remotely logs in to the monitoring target servers such as the servers 150 and 160 and acquires the resource state at predetermined time intervals. For this reason, the NMS system 10 can acquire the resource state of the monitoring target server in real time without the operator 20 logging in directly to each of the monitoring target servers.

  Also, acquisition of the resource state by remote login is performed in a procedure independent of the NMS application program. For this reason, the NMS system 10 can acquire the resource state of the monitoring target server even when the NMS application program is not installed in the monitoring target server. Further, the NMS system 10 can acquire the resource state of the monitoring target server even when the NMS application program cannot be installed in the monitoring target server because the OS of the monitoring target server is different from the OS of the NMS server.

  As a result, the NMS system 10 of the first embodiment makes it possible to quickly grasp the resources of the monitoring target device with a simple configuration.

(Modification of the first embodiment)
The effects of the monitoring system 10 described in the first embodiment can also be obtained by a single monitoring device having the following characteristics. That is, the monitoring apparatus according to the modification of the first embodiment includes a resource monitoring function unit 140 and a screen display unit 101. The resource monitoring function unit 140 obtains and outputs the resource state of the monitoring target device at a predetermined time interval by remotely logging in to the monitoring target device. The screen display unit 101 displays the output resource state.

  By using such a monitoring apparatus, the operator 20 can acquire the resource state of the monitoring target server in real time without directly logging in to each of the monitoring target servers. As a result, the monitoring apparatus according to the modification of the first embodiment can also quickly grasp the resources of the monitoring target apparatus with a simple configuration.

(Second Embodiment)
FIG. 5 is a block diagram illustrating a configuration of a monitoring system 500 according to the second embodiment of this invention. The monitoring system 500 includes a monitoring target device 501, a monitoring server device 502, and a monitoring client device 503. The monitoring target device 501 is a device to be monitored by the monitoring server device 502 and the monitoring client device 503. The monitoring target device 501 is a server device, for example.

  The monitoring server device 502 has a function of remotely logging in to the monitoring target device 501. The monitoring server device 502 acquires the resource state of the monitoring target device 501 at predetermined time intervals by the remote login function. Also, the monitoring server device 502 notifies the acquired resource state of the monitoring target device 501 to the outside.

  The monitoring client device 503 displays the resource state notified from the monitoring server device 502. The display may be a GUI display using an image display unit.

  The monitoring system 500 having such a configuration can easily and quickly acquire the resource state of the monitoring target device 501 with a simple configuration by the remote login function provided in the monitoring server device 502. This is because the monitoring server device 502 can acquire the resource state of the monitoring target device 501 directly and in real time by the remote login function.

(Modification of the second embodiment)
As a modification of the second embodiment, the monitoring apparatus that acquires the resource status of the monitoring target apparatus by remotely logging in to the monitoring target apparatus to be monitored at a predetermined time interval is also used for the monitoring apparatus. Can be obtained easily and quickly with a simple configuration. This is because the monitoring apparatus according to the modification of the second embodiment can acquire the resource state of the monitoring target apparatus directly and in real time by the remote login function.

  Although the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

10, 500 Monitoring system 20 Operator 100 NMS client 101 Screen display unit 110 NMS server 130 Alarm management function unit 140 Resource monitoring function unit 141, 151, 161 Resource status management unit 150, 160 Server 200 NMS
501 Monitoring target device 502 Monitoring server device 503 Monitoring client device

Claims (9)

A monitoring target device to be monitored; and
A monitoring server device that acquires the resource state of the monitoring target device at a predetermined time interval by remotely logging in to the monitoring target device, and outputs the acquired resource state;
A monitoring client device that displays the resource status output from the monitoring server device;
A monitoring system comprising: The monitoring server device
The monitoring target device is monitored by a monitoring control application program that operates in cooperation with the monitoring client device,
The remote login is performed by a procedure independent of the monitoring control application program.
The monitoring system according to claim 1, wherein: The monitoring system according to claim 1, wherein the monitoring target device operates with an operating system different from that of the monitoring server device. Obtaining the resource status of the monitored device at a predetermined time interval by remotely logging in to the monitored device to be monitored,
Output the acquired resource status,
Displaying the output resource status;
A monitoring method characterized by that. A resource status management unit that obtains and outputs the resource status of the monitoring target device at a predetermined time interval by remotely logging in to the monitoring target device to be monitored;
And a screen display unit that displays the output resource state. A procedure for acquiring the resource status of the monitoring target device at a predetermined time interval by remotely logging in to the monitoring target device to be monitored;
A procedure for outputting the acquired resource state;
A monitoring program for causing a computer of a monitoring apparatus to execute a procedure for displaying the output resource state. A monitoring apparatus comprising a resource state management unit that acquires a resource state of the monitoring target apparatus at a predetermined time interval by remotely logging in to the monitoring target apparatus to be monitored. A monitoring method for acquiring a resource state of the monitoring target device at a predetermined time interval by remotely logging in to the monitoring target device to be monitored. On the computer of the monitoring device,
Procedure for remote login to the monitored device to be monitored,
A procedure for acquiring the resource status of the monitoring target device at predetermined time intervals;
Monitoring program to execute

Images