JP2001188726A - Monitor event communication system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system for monitoring the generation of an event on a server, and for properly notifying the generation of the event to a server manager or the like in a server/server system existing on a network system. SOLUTION: This system is constituted of a monitor information registering means for registering monitor information for designating an event to be monitored and the destination of information to be notified when the event is generated in a server processing operation and its state, a monitoring means for monitoring the system based on the monitor information registered by the monitor information registering means and for detecting the generation of the event, and a notifying means for notifying the information of the monitor event detected by the monitoring means based on the destination of notification information. When a mail communication system is used as a notifying means, detail information related with the notified information is transmitted as the attached file of a mail. Also, the notifying means confirms whether or not a client at the destination of notification is connected with the client communication, and it decides a notified configuration using the first notifying means and the second notifying means based on the confirmed connected state.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to the field of monitoring and managing the occurrence of events on a server in a client / server system existing on a network system.

[0002]

2. Description of the Related Art A server user contacts a server administrator by telephone or the like, and a server administrator monitors the status of the server while the server is operating by monitoring messages from the server. Can be known.

[0003]

By notifying the server user of the event that has occurred, a countermeasure against the server event is taken, but the work of the server administrator becomes a heavy load.

[0004] This is because a message or log when an event (abnormal termination, service stop, event) detected by the system for displaying the server status or various monitoring applications is output only to the corresponding server system. . Along with these, the following problems are also derived.

[0005] The server system administrator needs to monitor the server application and the like with a fixed management terminal determined by the server. However, the server administrator cannot always monitor the occurrence of an event with a terminal for monitoring the server which is nearby and can be set freely.

Further, there is no means for responding to the client's free monitoring or management request which may occur suddenly. For monitoring the occurrence of events that occur daily, the client must contact the server administrator, set up the server for that purpose, analyze and notify the message of the occurrence of the event, transfer the log file, etc. .

As described above, it is not possible to freely set the monitoring required by the server administrator and the client.
Also, due to the time required for contact and notification between the server administrator and the client, and the unnecessary monitoring time generated by the server administrator while the server is operating, both the server administrator and the client Very problematic in terms of efficiency.

The present invention solves the above problems by grasping server monitoring event information when an event occurs, notifying a client or server administrator by network communication, and confirming an approved client or server. It is an object of the present invention to enable an administrator to freely register monitoring of occurrence of such an event.

[0009]

In order to solve the above problems, a monitoring event notification system according to the present invention is a monitoring event notification system provided in a server of a client / server system connected via a network. Monitoring information specifying an event to be monitored with respect to the processing operation and state of the system, monitoring information registration means for registering notification destination information to be notified when an event occurs, and monitoring information registered by the monitoring information registration means. Monitoring means for monitoring the system to detect the occurrence of an event, and notification means for notifying information of the monitoring event detected by the monitoring means based on the notification destination information. Things.

[0010] Further, the notifying means is provided for the client /
By performing notification using a mail transmission system independent of client communication using a network connected to the server system, it is possible to notify a server administrator of a monitoring event using a terminal independent of the client.
The “client communication” described above is communication performed by communication means for performing original communication performed between a client and a server in a client / server system.

Further, when a notification is executed by mail transmission, the detailed information related to the notification information is transmitted as an attachment to the mail, whereby the detailed information can be transmitted efficiently.

[0012] Further, the notifying means is provided for the client /
First notification means for notifying a monitoring event by client communication using a network connected to the server system, and second notification for notifying the monitoring event using a mail communication system in which communication is performed independently of the client communication. It is desirable to use two notification means. With such a configuration, the notifying unit checks whether or not the client of the notification destination is connected to the client communication, and based on the checked connection state, the first notifying unit and the second notifying unit. If the notification mode is determined using, for example, the event notification is performed by the client communication if the connection is made to the client communication, and the event notification is performed by the mail communication if the connection is not made to the client communication. Thus, the certainty of notifying the server administrator of the event is increased. It should be noted that the mail communication may be performed even when connected to the client communication to increase the reliability, and conversely, the mail communication may not be performed to reduce traffic. For example, it may be set.

[0013] Further, when an event notified to the client by the client communication using the network connected to the client / server system is a service stop, the service is restarted by a client request. desirable.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention monitors an abnormal termination state of an application, a stop state of a service, and the like occurring in a server of a network system, and sends the detected contents to a designated client or administrator via a LAN or a LAN. This is a network notification system that notifies monitoring event occurrence information by a designated method such as the Internet.

An embodiment of the present invention will be described below.
First, the overall flow and functions will be described with reference to FIGS.

FIG. 1 is a functional block diagram for providing a bird's-eye view of the entire flow of the monitoring event occurrence net notification system according to the embodiment of the present invention.

In FIG. 1, a client 11 and a server 10 are both connected to a network (not shown) such as a LAN.
Normally, information is transmitted and received (client communication) using this network.

The server 10 is also connected to a network 13 such as the Internet or an intranet for sending mail, and the client 10 performs the client communication via the user-side server 14.
It is also possible to transmit information by sending mail to clients 12 other than 11.

The client 12 has a mailer 121 and a notification mail storage means 122, and has a function of receiving mail via the user server 14. The client 12 may be a fixed terminal or a mobile terminal capable of receiving e-mail or the like.

The monitoring event registration unit 111 in the client 11
Is a client-side environment setting device, which registers a monitoring event in the client monitoring environment setting registry 113, and requests the server side for event monitoring and notification destination registration. The server user selects and registers from among those existing as a selection list on the client environment server side. Directory 11
3 is configured using a registry file of the client 11 as shown in FIG. 8, for example.

An event registration unit 101 in the server 10 registers a monitoring event and a notification destination requested by a client in a registry 104. As shown in FIGS. 6 and 7, in the present embodiment, the server 10 is configured using a registry file.

The event monitoring unit 102 activates a monitoring function, that is, a service monitoring function, an application monitoring function, and an event log monitoring function when a client requests monitoring and is registered.

The notification content storage unit 105 stores an application error, a service stop notification, as shown in FIG.
A message corresponding to an occurrence event such as an event log notification is stored. These specific examples will be described in the “notification confirmation function” of the explanation part of “details of each function” described later.

As described above, the corresponding monitoring function is in a state of monitoring the occurrence of a registration event from the system or from the monitoring application, or in a waiting state. To be described later,
In step S201 of FIG. 20, step S211 of FIG. 21, and step S221 of FIG. 22, the state of each monitoring event is monitored or waited, and the monitoring event registered in the registry 104 is monitored.

The event notification unit 103 cancels the event wait,
That is, when a monitoring event occurs, control is transferred to the server event notification. This transmits control to the client communication or mail transmission function according to the registered notification destination information in order to transmit the event occurrence notification. As a result, the notification information is transmitted to the monitoring event receiving unit 112. in the client 1 and the mailer 121 in the client 2.

Although not shown, a program for executing the operations of the server and the client may be configured to be installed on the server and the client, the program being recorded on a recording medium.

[0027] In Fig. 2, "-" indicates the configuration of each function of the present invention. 2 and 3 show server-side functions, and FIG. 2 and FIG. 2 show client-side functions, the outline of which is as follows.

"Service monitoring / activation" in FIG. 2 monitors the end of the service running on the server. Here, the “service” is a program that is resident in the system to operate a database or the like and is always operating. Activation means restarting a service that has been completed in response to an instruction from a client.
When the service to be monitored is stopped, the designated client or mail is notified to that effect, and the client service can be restarted from the client message box as a client function.

The "application monitoring" monitors abnormal termination of an application running on the server.
This application is a program that starts up and operates as needed according to a request from a client or the like.

The “event log monitoring” monitors the event log and detects that a record has been added to the event log.

The "client communication" is a communication between the server and the client that notifies the client of an abnormality and an event log detected by the server and receives a service restart instruction from the client.

The “mail transmission” transmits an abnormality detected by the server to the client.

The "environment setting" sets an operating environment such as an event to be monitored and a client to notify. Set the monitoring event notification target in the server function and save it in the registry.

The "server communication" in FIG. 2 performs communication between the server and the client that receives the notification transmitted from the server and displays the content in a pop-up.

The “environment setting” sets an operation environment such as a server for receiving a notification and an application for displaying a log. Set the monitoring event notification target in the client function and save it in the registry. When a service to be monitored is selected, a list of services currently specified on the server is displayed, and a service to be monitored can be selected.

The details of each function will be described below in the order of (1) registration, (2) monitoring, (3) server / client communication, and (4) notification confirmation. (Note that FIGS. 11 to 18 correspond to FIGS. 2 to 2 described above.) First, with regard to (1) registration, a function of setting and registering a monitoring target environment of the present system will be described.

The objects to be monitored are error monitoring of an application started on the server system, monitoring of the status of a service started on the server system, and monitoring of an event log. These monitoring targets are registered or corrected and stored in a registry.

After the occurrence of each event, each "notification to administrator after detecting abnormal termination of application" (see FIG.
12), "Confirmation of service status monitoring (start / stop) and notification to administrator" (Fig. 11), "Confirmation of event type / content and notification to administrator" (Fig. 13) , Register in the register or save it.

For registration, settings are made for each of the server side and the client side.

FIG. 16 is an explanatory diagram of the function outline of “environment setting (server)”. To set the monitoring event notification target in the server function, the monitoring event notification target is saved in a registry (for example, a registry or an area or a file corresponding to a unique interface with the monitoring application depending on the server OS). Items to be specified include a message transmission destination client, a mail address, a mail server, an event to be monitored, and a type of an event log to be detected, as shown in the example diagrams of the formats F601 to F613 in FIGS. (Note that FIG. 6 and FIG. 7 are examples when the registry is set in the registry.) FIG. 18 is an explanatory diagram of the function outline of “environment setting (client)”.

The monitoring event target is set in the client function, and is stored in a registry (depending on the OS of the client, for example, a registry). Items to be specified include a server name, a port number, a path of an application for displaying a log, and the like as shown in the example of the format F801 in FIG. (Note that FIG. 8 is an example of a case where a registry is set in the registry.) The registration of these monitoring events is listed (selected) as follows.
By making a list (see FIGS. 3, 4, and 5), the client can easily select a list.
Improve operability.

First, as the selection of the service to be monitored,
As shown in FIG. 4, a list of services specified on the server is displayed, and a service to be monitored can be selected from the list.

As for the selection of the event log, FIG.
The event to be monitored and the classification of the event can be designated.

Further, monitoring by a source is also possible by detailed settings. For this purpose, a list of application sources installed on the server can be displayed.
By selecting a source to be monitored from the list, detailed event log monitoring is possible. For example,
The event log information to be monitored is
Can be selected for each warning level.

The information to be collected as described above can be freely selected from warning to audit information. When notifying warning information, by displaying the applications installed in the server as a selection list, it is possible to select only necessary parts.

As for the setting of the notification destination and the setting of the transmission method, as shown in FIG. 3, “Setting of transmission destination (notification destination)”
With this, the destination of the abnormal termination of the application, the service status, and the event information is set. More than one client can be specified and therefore output to more than one client. The client can be set with either an IP address or a computer name, and can also specify a mail address.

As the transmission method, transmission of a message by TCP / IP and transmission of a message by mail are possible. Therefore, this makes it possible to reliably notify the server administrator wherever the server administrator is.

The user who can be registered is an ID approved in advance,
Only client and server administrators with passwords. This can only be set by the server administrator.

Next, (2) the monitoring function will be described. Figure 1
FIG. 1 is an explanatory diagram of a function outline regarding “service monitoring / activation”.

In the figure, the service running on the server is monitored, and when the end of the service is detected, the end of the service is notified to the client communication processing (FIG. 14) or the mail transmission processing (FIG. 15) based on the setting of the registry. I do. After receiving the service start notification from the client communication, the service that has received the start instruction is started.

FIG. 20 is a flowchart showing the processing procedure. It is determined whether or not the service is a monitoring target (S203), whether or not a designated time has elapsed (S204), a notification destination is selected (S205), and a notification is made (S206 or S207). ). After the end of the notification, the process returns to the beginning (S201) and returns to the event occurrence monitoring state.

The service monitoring is started periodically (for example, at intervals of 10 seconds) by a timer. In step S202, the state of the started service (F608 in FIG. 7) is monitored.

In step S203, the determination as to whether or not the service is a monitoring target is performed based on the contents of the registry (F606 in FIG. 7). That is, the determination is made based on the content of the \ SERVICEWATCHER of F606 (a flag indicating whether or not to perform monitoring).

In step S204, it is determined whether or not the designated time has elapsed based on the contents of the registry (F601 in FIG. 6 and F612 in FIG. 7). That is, F601
Judgment is made based on the content of the value name ResendTime of \ SERVER (time to retransmit the same notification message) and the content of \ Service in F612 (previous notification time for each service).

FIG. 12 is a schematic diagram for explaining the function of “application monitoring”.

In the figure, when an abnormal end is detected by an application running on the server, the end of the service is notified to the client communication processing (FIG. 14) or the mail transmission processing (FIG. 15) based on the setting of the registry. The log file created at the time of abnormal termination of the application is passed to the client communication process (FIG. 14) or the mail transmission process (FIG. 15).

FIG. 21 is a flowchart showing the processing procedure. It is determined whether or not the application is a monitoring target (S212), a notification destination is selected (S213), and a notification is made (S214 or S215). After notification, first (S211)
And returns to the event occurrence waiting state again.

FIG. 13 is an explanatory diagram of the function outline of “event log monitoring”.

In the figure, an event log is monitored and an added log is detected. Also, event log information output on the server is collected based on the settings in the registry, and the contents of the event log are notified to the client communication process (FIG. 14) or the mail transmission process (FIG. 15).

FIG. 22 is a flowchart showing the processing procedure. It is determined whether or not the event log is a monitoring target event log (S223), whether or not a specified time has elapsed (S224), a notification destination is selected (S225), and a notification is made (S226 or S227). After the end of the notification, the process returns to the beginning (S221) and returns to the event occurrence monitoring state.

The event log monitoring is performed periodically (for example, 10
A timer is started (at intervals of seconds), and in step S222,
Monitor the status of the event log.

In step S222, the determination as to whether or not the service is a monitoring target is performed based on the contents of the registry (F605 in FIG. 6). That is, according to the contents (the latest event log generation time) of the following values under \ EVENTLOGWATCHER of F605, (1) APPLICATIONLASTTIME (application log), (2) SECURITYLASTTIME (security log) and (3) SYSTEMLASTTIME (system log) to decide.

In step S223, whether or not a new event log has occurred is determined based on the contents of the registry (F602, F603 and F604 in FIG. 6). That is, \ APP of F602
LICATION (application log) and \ SYSTE of F603
The determination is made based on the contents of M (system log) and the contents of \ SECURITY (security log) of F604 (flag indicating whether or not monitoring is performed for each event type).

In step S224, the determination as to whether or not the designated time has elapsed is made based on the contents of the registry (F601 in FIG. 6, and F609, F610 and F611 in FIG. 7). That is, the contents of the value name ResendTime of \ SERVER in F601 (time to retransmit the same notification message) and F609
\ APPLICATION (application log) and \ SECURI
TY (security log) and \ SYSTEM (system log) contents ('Audit success',' Audit failure ',' Information ','
Flag for monitoring whether to monitor for 'warning' and 'error'
Judge by

Next, (3) the server-client communication function will be described. FIG. 9 shows a data flow for communication between the client and the server. The above-described monitoring function executes notification of an event that occurs after activation and transmission / reception of client-side request information in response to the notification.

The communication between the client and the server is processed by a client communication notification or a mail transmission notification to a plurality of clients as desired and specified by the client.

First, FIG. 14 is an explanatory diagram of the function outline regarding “client communication notification”. Service monitoring / startup,
A service or application end notification and an event log notification are received from the application monitoring and event log monitoring processes, and a message is transmitted to the client-side server communication process. Further, it receives a service activation instruction from the server communication processing on the client side and notifies the service monitoring / activation processing.

Also, S205, S206 and S207 in FIG.
21, S213 and S214 and S215, and FIG. 22 S225 and S226 and
S227 is a flowchart showing the processing procedure. These processing contents are the same. S205 and S206 and S2 in FIG. 20
07 will be described as a representative example.

It is determined whether or not the notification destination client is running (S205), and the notification destination is selected and notified (S206).
Or S207).

In step S205, it is determined whether or not the notification destination client is running based on the fact that the state is held by the connection establishment processing between the client and the server.

First, when the notification destination client is activated, that is, when the connection between the client and the server has been established, in step S206, the directory (F60 in FIG. 6) is registered.
1) Acquire the notification destination client from and notify. That is, the contents of WS_NAMEx (x is a serial number from 1) of the value name of \ SERVER in F601 (client name of the notification destination or I
The notification destination is acquired from the (P address) and notified by the client communication. Note that output can be made to a plurality of clients as notification destinations.

When the notification destination client is not activated,
Notify by the following second method. FIG. 15 is an explanatory diagram of a function outline of the “mail transmission notification”, and receives a service or application end notification and an event log notification from each process of service monitoring / startup, application monitoring, or event log monitoring. These notification contents are transmitted to the mail server as e-mail to the designated destination.

The mail transmission notification processing is performed in steps
In S207, a mail transmission notification destination is obtained from the registry (F601 in FIG. 6) and notified. That is, \ SERVE of F601
This is performed by acquiring the notification destination from the contents (mail address of the transmission destination) of the contents of MAIL_ADDRESSx (x is a serial number from 1) of the value name of R and notifying the mail transmission. Note that output can be made to a plurality of mail addresses as notification destinations.

As described above, the output information is notified by the designated client screen or mail.
If an error log file is output, the log file is copied to the designated client, and there is no need to touch the server to collect information. At the time of mail transmission, a log file is transmitted as an attached file.

Finally, (4) the notification confirmation function, that is, the contents of notification to the client or server administrator and the confirmation (client request information) function will be described.

FIG. 17 is an explanatory diagram of the function outline regarding “server communication”. "Server communication" receives various notification messages and detailed information (FIG. 10) from the server, and displays a pop-up on the client screen. "Server communication"
Transmits a service activation instruction or the like to the server in response to a client request. At the start of the connection between the client and the server, a connection establishment process with the server is performed.

FIG. 19 is a flowchart showing the processing procedure of "server communication", that is, the task of receiving the notification of the server on the client side.

The client is normally in a state of waiting for a notification message from the server (S191). The server communication of the client determines whether it is service monitoring information, event log monitoring information, or application monitoring information based on the notification contents (FIG. 10) (S192), displays a service end message box display process (S193), Box display processing (S194) or application abnormal end message box display processing (S195) is performed. The client has steps S194 and S1
After the process of step 95, the process enters the first (S191) waiting state. In the case of service end message box display processing (S193),
When the request from the client is a service restart instruction, a service restart instruction is transmitted to the server (S197).
After the processing in step S197 is completed, the client first (S19
Return to 1), and enter the wait state for receiving the notification message from the next server.

The messages transmitted from the server side and the client side are transmitted and received in the format shown in FIG.
Further, transmission and reception of messages are performed using the TCP / IP protocol, and all messages are transmitted and received in text format.

The messages transmitted from the server and the client are unique messages based on the message numbers. Number-specific messages are linked and transmitted in the order shown in the message list.

Hereinafter, a notification display at the time of occurrence of a monitoring event will be described.

First, FIGS. 23 and 24 show examples of notification display when a message and a log are displayed on a client / mail when an application terminates abnormally.

FIG. 23 shows an example of a screen displayed for notification to the client. The displayed contents are (1) application name: name of the execution module that terminated abnormally, (2) server name: name of the server where the error occurred (or computer name), (3) date and time: date and time of occurrence, and (4) log storage destination: debugger Is the storage location of the log file output by. By clicking the button on this display screen, the contents of the log file can be displayed.

FIG. 24 shows an example of a screen displayed by e-mail notification. The displayed contents are (1) application name: name of the execution module that terminated abnormally, (2) server name: name of the server where the error occurred (or computer name), (3) date and time: date and time of occurrence, and (4) log file: by the debugger This is the output log file. This log file is added and notified as an attached file.

Next, FIG. 25 and FIG. 26 show examples of notification display when the monitoring service is stopped and the notification is made to the designated client or mail address.

FIG. 25 shows an example of a screen displayed for notification to the client. The displayed contents are (1) service name: stopped service name, (2) server name: error occurrence server name (or computer name), and (3) date and time: occurrence date and time. By clicking the button on this display screen, the stopped service can be restarted.

FIG. 26 shows an example of a screen displayed by e-mail notification. The displayed contents are (1) service name: stopped service name, (2) server name: error occurrence server name (or computer name), and (3) date and time: occurrence date and time. Finally, FIGS. 27 and 28 show examples of notification display when a monitoring event occurs.

FIG. 27 shows an example of a screen displayed for notification to the client. The displayed contents are (1) event type: type of sent event, (2) event source: source name output to event log, (3) server name: error occurrence server name (or computer name) and ( 4) Date: Date and time of occurrence. When a button on this display screen is clicked, details such as an event log are displayed.

FIG. 28 shows an example of a screen displayed by e-mail notification. The displayed contents are (1) event type: type of sent event, (2) event source: source name output to event log, (3) server name: error occurrence server name (or computer name), ( 4) Date and time: Date and time of occurrence and (5)
Details: Contents output in the event log. As described above, the server monitoring which can monitor the situation occurring in the server on the network system and notify the content of the detected event to a designated client or a server administrator by a designated method. , An operation management system can be realized.

[0090]

According to the present invention, when a monitoring event registered in the server occurs, the server monitoring event information can be automatically and promptly notified to the client or the server administrator via the network communication in order to grasp the server status. This makes it possible to configure an effective operation management system for the server administrator and the server user (client).

The client or server administrator who has been approved for the monitoring event to be notified by the status monitoring event registration setting function can easily and efficiently register the monitoring event displayed in the list in a selected format. To
It also enables detailed information (monitoring function, log collection function) of monitoring events to be notified to be freely registered in a selection format.

When the monitoring information is notified on the Internet, the detailed information is notified to the server user without any operation of the server by notifying the details of the display contents of the event as an attachment to the mail.

The service can be restarted from the client without operating the server without bothering the server administrator.

The notification destination and the notification method can be freely set and changed. If the notification destination client or the address of the Internet is changed according to the destination of the server administrator, the server administrator can manage the notification. You don't need to stick to the terminal to monitor. Also, E-mai
Since transmission to a mobile phone that can receive 1 is also possible, the server administrator can make it possible to be anywhere as long as the mobile phone can be reached.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating overall functions of the present invention.

FIG. 2 is a diagram illustrating a system configuration of a monitoring event notification system according to the present invention.

[Figure 3] Example of notification destination setting for monitoring target event notification

[Figure 4] Example of display of monitoring target event notification selection (monitoring service)

[Figure 5] Example of selected event notification to be monitored (event log) display

[Figure 6] Example diagram of a directory for monitoring environment settings (server side)
(1/2)

[Figure 7] An example of a directory for monitoring environment settings (server side)
(2/2)

[Figure 8] Example diagram of a directory for monitoring environment settings (client side)

[Figure 9] Client / server data notification flow diagram

[Figure 10] Client notification format diagram

FIG. 11 is a block diagram illustrating a service monitoring / starting function.

FIG. 12 is a block diagram illustrating an application monitoring function.

FIG. 13 is a block diagram illustrating an event log monitoring function.

FIG. 14 is a block diagram illustrating a client communication notification function.

FIG. 15 is a block diagram illustrating a mail transmission notification function.

FIG. 16 is a block diagram illustrating an environment setting (server) function.

FIG. 17 is a block diagram illustrating a server communication function.

FIG. 18 is a block diagram illustrating an environment setting (client) function.

FIG. 19 is a flowchart for explaining reception of a client: server notification.

FIG. 20 is a flowchart illustrating service monitoring.

FIG. 21 is a flowchart illustrating application monitoring.

FIG. 22 is a flowchart illustrating event log monitoring.

[Figure 23] Notification display of abnormal termination of application (client communication) Example diagram

[Fig. 24] Example of notification display at the time of abnormal termination of application (sending mail)

[Fig. 25] Example of service stop notification display (client communication)

[Fig. 26] Example of service stop notification display (e-mail transmission)

[Figure 27] Event occurrence notification display (client communication) Example diagram

[Figure 28] Event occurrence notification display (e-mail transmission) Example diagram

[Explanation of symbols]

 Reference Signs List 10 server 111 server event registration unit 112 server event monitoring unit 113 server event notification unit 114 registry 115 notification content storage unit 11 client 1 111 client monitoring event registration unit 112 client monitoring event reception unit 113 registry 12 client 2 121 mailer 122 notification Mail storage unit 13 Network of mail communication system 14 User server of mail communication system

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Katsumi Yano 2-29-1, Kachidokibashi, Tokushima City, Tokushima Prefecture Inside Fujitsu Tokushima System Engineering Co., Ltd. (72) Kenshin Nakai 2-29, Kachidokibashi, Tokushima City, Tokushima Prefecture No. 1 F-term in Fujitsu Tokushima System Engineering Co., Ltd. (Reference) 5B042 GA12 GC20 JJ17 KK02 MC15 MC19 MC40 NN56 5B089 GA11 GB02 JA35 JB15 KA12 KC59 LA01 LA18 MC01 ME13

Claims (7)

[Claims] 1. A monitoring event notification system provided in a server of a client / server system connected by a network, comprising: monitoring information for specifying an event to be monitored with respect to a processing operation and a state of the server; Monitoring information registration means for registering notification destination information to be notified, monitoring means for monitoring the system based on the monitoring information registered by the monitoring information registration means to detect occurrence of an event, and monitoring detected by the monitoring means A monitoring event notification system, comprising: notification means for notifying event information based on the notification destination information. 2. The monitoring system according to claim 1, wherein the notifying unit performs the notification using a mail communication system in which communication is performed independently of client communication used in the client / server system. Event notification system. 3. The method according to claim 2, wherein when the notification is performed using the mail communication system, detailed information related to the notification information is transmitted as a file attached to the mail.
2. The monitoring event notification system according to 1. 4. The communication system according to claim 1, wherein the notifying unit is a first notifying unit that notifies a monitoring event by a client communication used in the client / server system, and a mail communication system that performs communication independently of the client communication system. 2. The monitoring event notification system according to claim 1, wherein the monitoring event notification system is configured to include a second notification unit that notifies a monitoring event by using the second notification unit. 5. The notifying means checks whether or not a client of a notification destination is connected to the client communication, and based on the checked connection state, the first notifying means and the second notifying means. The monitoring event notification system according to claim 4, wherein the monitoring event notification system is configured to determine a notification mode used. 6. The service according to claim 1, wherein when the event notified to the client by the client communication used in the client / server system is a service stop, the service is restarted at the request of the client. Monitoring event notification system. 7. A computer-readable recording medium on which a program for operating a monitoring event notification system provided in a server of a client / server system connected via a network is recorded, and monitors a processing operation and a state of the server. Monitoring information registering means for registering monitoring information specifying an event to be notified and notification destination information to be notified when an event occurs; and monitoring the system based on the monitoring information registered by the monitoring information registering means to determine whether an event has occurred. A computer-readable program recording medium recording a monitoring event notification program, comprising: a monitoring unit for detecting; and a notifying unit for notifying information of the monitoring event detected by the monitoring unit based on the notification destination information.