CN108427616B - Background program monitoring method and monitoring device - Google Patents
Background program monitoring method and monitoring device Download PDFInfo
- Publication number
- CN108427616B CN108427616B CN201710079400.XA CN201710079400A CN108427616B CN 108427616 B CN108427616 B CN 108427616B CN 201710079400 A CN201710079400 A CN 201710079400A CN 108427616 B CN108427616 B CN 108427616B
- Authority
- CN
- China
- Prior art keywords
- background service
- monitoring
- service program
- program
- background
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/323—Visualisation of programs or trace data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a background program monitoring method, which comprises the following steps: traversing the background service programs, and reading configuration files of all the background service programs; generating a monitoring state table of the background service program according to the configuration file of the background service program; sending first heartbeat signals to all background service programs at set time intervals according to the monitoring state table; and determining to restart the corresponding background service program according to the feedback of the background service program to the first heartbeat signal. The background program monitoring method and the background program monitoring device can judge whether the background service program normally operates or not by sending heartbeat information to the background service program, so that the judgment result is more accurate, the automatic operation capability of the background program monitoring process can be improved, and the condition confirmation of the background service program by manpower is avoided.
Description
Technical Field
The invention relates to the field of internet, in particular to a background program monitoring method and a background program monitoring device.
Background
The TSF (Tencent Server Framework, Tencent service Framework) is a PHP service process monitoring scheme introduced by Tencent corporation, and is used for monitoring a background service program. The service framework is widely used in enterprise services and large client data interface projects. In order to ensure the stable operation of the background service program, the service process monitoring scheme is required to have strong unattended operation and maintenance capability.
However, the process monitoring scheme only identifies the master process in the background service program, and judges whether the background service program normally runs or not by judging whether the master process exists or not. However, a master process may exist in an existing background service program, but all worker processes in the background service program are falsely dead due to blocking, so that whether the background service program normally runs or not cannot be accurately judged by monitoring the master process in the background service program, and an engineer is required to confirm the state of the background service program to judge whether the background service program needs to be restarted or not, so that the process monitoring scheme cannot be unattended when in use.
Disclosure of Invention
The embodiment of the invention provides a background program monitoring method and a background program monitoring device which can improve the automatic operation capability of a background program monitoring process; the background program monitoring method and the background program monitoring device solve the technical problems that the existing background program monitoring method and the background program monitoring device are poor in automatic operation capability and need manpower to confirm the state.
The embodiment of the invention provides a background program monitoring method, which comprises the following steps:
traversing the background service programs, and reading configuration files of all the background service programs;
generating a monitoring state table of the background service program according to the configuration file of the background service program, wherein the monitoring state table comprises position information and identification information of a relevant process in the background service program;
sending first heartbeat signals to all background service programs at set time intervals according to the monitoring state table; and
and determining to restart the corresponding background service program according to the feedback of the background service program to the first heartbeat signal.
The embodiment of the present invention further provides a background program monitoring device, which includes:
the configuration file reading module is used for traversing the background service programs and reading the configuration files of all the background service programs;
the monitoring state table generating module is used for generating a monitoring state table of the background service program according to the configuration file of the background service program, wherein the monitoring state table comprises position information and identification information of a relevant process in the background service program;
the heartbeat signal sending module is used for sending first heartbeat signals to all background service programs at set time intervals according to the monitoring state table; and
and the restarting module is used for determining to restart the corresponding background service program according to the feedback of the background service program to the first heartbeat signal.
Compared with the prior art, the background program monitoring method and the background program monitoring device provided by the invention have the advantages that whether the background service program runs normally or not is judged by sending heartbeat information to the background service program, the judgment result is more accurate, the automatic running capability of the background program monitoring process can be improved, and the condition confirmation of the background service program by manpower is avoided; the technical problems that the existing background program monitoring method and the background program monitoring device are poor in automatic operation capacity and need manpower to confirm the state are solved.
Drawings
FIG. 1 is a flow chart of a first preferred embodiment of a daemon monitoring method of the present invention;
FIG. 2 is a flow chart of a daemon monitoring method according to a second preferred embodiment of the present invention;
FIG. 3 is a flowchart of a third preferred embodiment of the daemon monitor method of the present invention;
FIG. 4 is a schematic flowchart of the daemon control operation of the third preferred embodiment of the monitoring method of the present invention;
FIG. 5 is a second schematic flowchart of the daemon control operation of the third preferred embodiment of the monitoring method of the invention;
FIG. 6 is a schematic structural diagram of a daemon monitoring apparatus according to a first preferred embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a daemon monitoring apparatus according to a second preferred embodiment of the present invention;
FIG. 8 is a schematic structural diagram of a daemon monitoring apparatus according to a third preferred embodiment of the present invention;
FIG. 9 is a schematic structural diagram of an external control module of a third preferred embodiment of the daemon monitoring apparatus according to the present invention;
FIG. 10 is an overall architecture diagram of a server system according to an embodiment of the daemon monitoring method and the daemon monitoring apparatus of the present invention;
FIG. 11 is a flowchart illustrating the use of embodiments of the daemon monitoring method and the daemon monitoring apparatus according to the invention;
fig. 12 is a schematic view of a working environment structure of an electronic device in which the daemon monitoring device of the present invention is located.
Detailed Description
Referring to the drawings, wherein like reference numbers refer to like elements, the principles of the present invention are illustrated as being implemented in a suitable computing environment. The following description is based on illustrated embodiments of the invention and should not be taken as limiting the invention with regard to other embodiments that are not detailed herein.
In the description that follows, embodiments of the invention are described with reference to steps and symbols of operations performed by one or more computers, unless otherwise indicated. It will thus be appreciated that those steps and operations, which are referred to herein several times as being computer-executed, include being manipulated by a computer processing unit in the form of electronic signals representing data in a structured form. This manipulation transforms the data or maintains it at locations in the computer's memory system, which may reconfigure or otherwise alter the computer's operation in a manner well known to those skilled in the art. The data maintains a data structure that is a physical location of the memory that has particular characteristics defined by the data format. However, while the principles of the invention have been described in language specific to above, it is not intended to be limited to the specific details shown, since one skilled in the art will recognize that various steps and operations described below may be implemented in hardware.
The daemon monitoring method and the daemon monitoring apparatus of the invention may be used on various electronic devices for background service monitoring, including but not limited to wearable devices, head-worn devices, medical health platforms, personal computers, server computers, hand-held or laptop devices, mobile devices (such as mobile phones, Personal Digital Assistants (PDAs), media players, etc.), multiprocessor systems, consumer electronics, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The electronic equipment judges whether the background service program normally operates or not by sending heartbeat information to the background service program, so that the accuracy of the operation judgment result of the background service program is improved, the automatic operation capability of the background program monitoring process is improved, and the condition confirmation of the background service program by manpower is avoided.
Referring to fig. 1, fig. 1 is a flowchart illustrating a background program monitoring method according to a first preferred embodiment of the present invention. The background program monitoring method of the preferred embodiment may be implemented using the electronic device, and the background program monitoring method includes:
step S101, traversing background service programs, and reading configuration files of all background service programs;
step S102, generating a monitoring state table of the background service program according to the configuration file of the background service program, wherein the monitoring state table comprises position information and identification information of a relevant process in the background service program;
step S103, sending first heartbeat information to all background service programs at set time intervals according to the monitoring state table;
and step S104, determining to restart the corresponding background service program according to the feedback of the background service program to the first heartbeat signal.
The specific flow of each step of the daemon monitoring method of the preferred embodiment is described in detail below.
In step S101, after the daemon monitoring device starts working, all the daemon service programs in the daemon service group are traversed, where the daemon service programs may be a daemon service program providing a TCP (Transmission Control Protocol) service, a daemon service program providing a UDP (User Datagram Protocol) service, a daemon service program providing an HTTP (HyperText Transfer Protocol) service, and a daemon service program providing a WebSocket (a duplex communication Protocol) service.
And then, the background program monitoring device reads configuration files (Config files) of all background service programs, wherein the configuration files can include process identification information (such as process names and the like), process position information (such as a process entry PHP file position and a process start PHP file position and the like), a monitoring port, a background service program type and the like in the corresponding background service programs. Subsequently, the process goes to step S102.
In step S102, the daemon monitoring device generates a monitoring state table of the daemon according to the configuration file of the daemon acquired in step S101, where the monitoring state table includes, but is not limited to, process location information and process identification information of a relevant process in the daemon. The specific monitoring state table may include background service program information such as process identification information, process location information, a monitoring port, a background service program type, process state information, and process start time, and process information in the background service program.
The information such as the process identification information, the process position information, the monitoring port, the background service program type and the like can be acquired from a configuration file of the background service program, and the information such as the process state information, the process starting time and the like can be acquired from the process feedback of the background service program after the background program monitoring device monitors the background service program. Subsequently, the process goes to step S103.
In step S103, the daemon monitoring device sends the first heartbeat information to all the daemon service programs at a set time interval according to the information of the relevant processes in the monitoring state table generated in step S102.
The background program monitoring device can set first heartbeat information of a corresponding type according to the type of the background service program, and then sends the first heartbeat information to the corresponding background service program at a set time interval (such as 30s), so that whether the corresponding background service program runs normally is judged through the feedback of the background service program to the first heartbeat information. Subsequently, the process goes to step S104.
In step S104, the background service program receives the first heartbeat information, and if the main process (master process) of the background service program does not exist, the background program monitoring device cannot receive the feedback of the first heartbeat signal. Or the main process of the background service program exists, but the work process (worker process) is blocked, so that the background program monitoring device still cannot receive the feedback of the first heartbeat signal. If the main process and the working process of the background service program are normal, the background program monitoring device can normally receive the feedback of the first heartbeat signal.
Therefore, if the background program monitoring device does not receive the feedback of the first heartbeat signal, the corresponding background service program is judged to be abnormal, and the background program monitoring device restarts the background service program.
In order to prevent misoperation of the background program monitoring device, the background program monitoring device does not judge the abnormality of the background service program through a single first heartbeat signal feedback result, but judges the abnormality of the corresponding background service program only if the background service program does not respond to the first heartbeat signal with set times; such as no response or response timeout of the first heartbeat signal for 3 consecutive times, etc. The restarting operation of the background service program can be completed by closing all processes under the background service program.
And if the background program monitoring device can normally receive the feedback of the first heartbeat signal, judging that the background service program is normal. And the background program monitoring device continues to send the first heartbeat signal to the background service program at a set time interval until the background service program finishes running.
In this way, the process monitoring process in the daemon of the daemon monitoring method of the preferred embodiment is completed.
The background program monitoring method of the preferred embodiment judges whether the background service program operates normally by sending heartbeat information to the background service program, so that the judgment result is more accurate, the automatic operation capability of the background program monitoring process can be improved, and the condition confirmation of the background service program by manpower is avoided.
Referring to fig. 2, fig. 2 is a flowchart illustrating a background program monitoring method according to a second preferred embodiment of the present invention. The background program monitoring method of the preferred embodiment may be implemented using the electronic device, and the background program monitoring method includes:
step S201, traversing the background service programs, and reading configuration files of all the background service programs;
step S202, generating a monitoring state table of the background service program according to the configuration file of the background service program, wherein the monitoring state table comprises position information and identification information of a relevant process in the background service program;
step S203, sending first heartbeat information to all background service programs at set time intervals according to the monitoring state table;
step S204, according to the feedback of the background service program to the first heartbeat signal, determining to restart the corresponding background service program;
step S205, receiving a second heartbeat signal of the system process, and performing feedback operation on the second heartbeat signal; and the system process generates a monitoring process reset signal for resetting the monitoring process according to the feedback information of the second heartbeat signal.
The specific flow of each step of the daemon monitoring method of the preferred embodiment is described in detail below.
The specific operation principle of steps S201 to S204 in the present preferred embodiment is the same as or similar to the specific operation principle of steps S101 to S104 in the first preferred embodiment of the daemon monitoring method, and please refer to the related description in the first preferred embodiment of the daemon monitoring method.
In step S205, the daemon monitoring device receives a second heartbeat signal of the system process during monitoring the daemon service program, and performs a feedback operation on the second heartbeat signal. The system process may be a daemon process created by a crond planning task (a periodic planning task). If the background program monitoring function device cannot respond to the second heartbeat signal in time, the system process judges that the background program monitoring process is abnormal, and the system process can restart the background program monitoring process of the background program monitoring device. Therefore, the working stability and the automatic operation capability of the background program monitoring device are further improved.
In this way, the process monitoring process in the daemon of the daemon monitoring method of the preferred embodiment is completed.
On the basis of the first preferred embodiment, the background program monitoring method of the present preferred embodiment determines the state of the background program monitoring process in the background program monitoring device in real time through the system process, and if the background program monitoring process is abnormal, the background program monitoring device is restarted; therefore, the daemon process of the system kernel level is used for monitoring and resetting the background program monitoring process, and the working stability and the automatic operation capability of the background program monitoring process are further improved.
Referring to fig. 3, fig. 3 is a flowchart illustrating a background program monitoring method according to a third preferred embodiment of the present invention. The background program monitoring method of the preferred embodiment may be implemented using the electronic device, and the background program monitoring method includes:
step S301, traversing the background service programs, and reading configuration files of all the background service programs;
step S302, generating a monitoring state table of the background service program according to the configuration file of the background service program, wherein the monitoring state table comprises position information and identification information of a relevant process in the background service program;
step S303, sending first heartbeat information to all background service programs at set time intervals according to the monitoring state table;
step S304, according to the feedback of the background service program to the first heartbeat signal, determining to restart the corresponding background service program;
step S305, receiving an external control command, and performing control operation on a corresponding background service program according to the external control command;
step S306, generating a log file, and updating the log file according to the feedback of the first heartbeat signal and the feedback of the control operation.
The specific flow of each step of the daemon monitoring method of the preferred embodiment is described in detail below.
The specific operation principle of steps S301 to S304 in the present preferred embodiment is the same as or similar to the specific operation principle of steps S101 to S104 in the first preferred embodiment of the daemon monitoring method, and please refer to the related description in the first preferred embodiment of the daemon monitoring method.
In step S305, the daemon monitoring device receives an external control command, which may be a script command or a monitoring process start command. The script command is a command for controlling the background service program to perform script operation. The monitoring process starting command is a command for starting the monitoring process of the background program.
Specifically, referring to fig. 4, fig. 4 is a schematic flowchart of a background service program control operation of a third preferred embodiment of the background program monitoring method of the present invention, where if the external control command is a script command, the step of performing a control operation on the corresponding background service program includes:
step S401, the daemon monitoring device receives the script command and determines whether the script command is a legal command, and if the script command is a legal command, the daemon monitoring device starts a daemon service program for executing the script command.
If the script command is a list command (list command), a list of all background service processes obtained by analyzing the configuration file is listed to be used as a parameter index for other command operations.
If the script command is a status command, the status of all background services is listed, including the information in the memory table.
If the script command is a start command, a certain background service program is run, and a first heartbeat signal is sent to the background service program.
If the script command is a stop command, a stop command is executed for a certain background service program.
If the script command is a restart command, the start command is executed after a set time for executing the stop command for a certain background service program.
If the script command is a start all command (startall command), the start command is executed for all background servers.
If the script command is a close command (shutdown command), executing a stop command on all background service programs, and then executing the stop command on the background program monitoring process.
If the script command is a test command (test command), a certain background service program sends a first heartbeat signal to be tested.
Step S402, after the script command in step S401 is executed, the background program monitoring device closes the background service program and performs recovery operation on the resource of the background service program.
Specifically, referring to fig. 5, fig. 5 is a second schematic flowchart of the background service program control operation of the third preferred embodiment of the background program monitoring method of the present invention, where if the external control command is a monitoring process start command, the step of performing control operation on the corresponding background service program includes:
step S501, receiving a monitoring process starting command, and judging whether a monitoring process in the process of starting exists according to the monitoring process starting command; if the monitoring process in the process of starting exists, the step S502 is carried out; if there is no monitoring process in the process of being started, the process goes to step S503.
Step S502, if there is a monitoring process in the process of starting, the background program monitoring device stops performing the monitoring process starting operation.
In step S503, if there is no monitoring process being started, the background program monitoring device performs a monitoring process starting operation.
In step S306, the daemon monitoring device generates a log file, and updates the log file according to the feedback of the first heartbeat signal and the feedback of the control operation. Namely, the state change of the background service program and the state change of the process in the background service program are recorded in the log file. If serious errors such as failure of starting the background service program occur, the errors can be reported to technicians, so that the technicians can process the errors in time.
In this way, the process monitoring process in the daemon of the daemon monitoring method of the preferred embodiment is completed.
On the basis of the first preferred embodiment, the background program monitoring method according to the preferred embodiment may further control the background service program according to an external control command, and record the state of the background service program through a log file, thereby further extending the function of the background program monitoring process.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a daemon monitoring device according to a first preferred embodiment of the invention. The daemon monitoring device of the preferred embodiment may be implemented by using the above daemon monitoring method, and the daemon monitoring device 60 includes a configuration file reading module 61, a monitoring state table generating module 62, a heartbeat signal sending module 63, and a restarting module 64.
The configuration file reading module 61 is used for traversing the background service programs and reading configuration files of all the background service programs; the monitoring state table generating module 62 is configured to generate a monitoring state table of the background service program according to the configuration file of the background service program, where the monitoring state table includes location information and identification information of a relevant process in the background service program; the heartbeat signal sending module 63 is configured to send a first heartbeat signal to all background service programs at a set time interval according to the monitoring state table; the restart module 64 is configured to determine to restart the corresponding background service program according to the feedback of the background service program on the first heartbeat signal; the specific restarting module is used for restarting the corresponding background service program if the background service program continuously does not respond to the first heartbeat signal with the set times.
When the background program monitoring device 60 of the preferred embodiment is used, first, after the background program monitoring device 60 starts working, the configuration file reading module 61 traverses all background service programs in the background service program group, where the background service programs may be a background service program providing TCP (Transmission Control Protocol) service, a background service program providing UDP (User Datagram Protocol) service, a background service program providing HTTP (HyperText Transfer Protocol) service, a background service program providing WebSocket (a duplex communication Protocol) service, and the like.
Subsequently, the configuration file reading module 61 reads configuration files (Config files) of all background service programs, where the configuration files may include process identification information (such as process names) in corresponding background service programs, process location information (such as a process entry PHP file location and a process start PHP file location), a listening port, a background service program type, and the like.
Then, the monitoring state table generating module 62 generates a monitoring state table of the background service program according to the configuration file of the background service program acquired by the configuration file reading module 61, where the monitoring state table includes, but is not limited to, process location information and process identification information of a relevant process in the background service program. The specific monitoring state table may include background service program information such as process identification information, process location information, a monitoring port, a background service program type, process state information, and process start time, and process information in the background service program.
The information such as the process identification information, the process position information, the monitoring port, the background service program type and the like can be acquired from a configuration file of the background service program, and the information such as the process state information, the process starting time and the like can be acquired from the process feedback of the background service program after the background program monitoring device monitors the background service program.
Then, the heartbeat signal sending module 63 sends the first heartbeat information to all background service programs at a set time interval according to the information of the relevant processes in the monitoring state table generated by the monitoring state table generating module 62.
Here, the heartbeat signal sending module 63 may set the first heartbeat information of the corresponding type according to the type of the background service program, and then send the first heartbeat information to the corresponding background service program at a set time interval (e.g. 30s), so as to determine whether the corresponding background service program normally operates by the feedback of the background service program on the first heartbeat information.
Finally, the background service program receives the information of the first heartbeat, and if the main process (master process) of the background service program does not exist, the background program monitoring device 60 cannot receive the feedback of the first heartbeat signal. Or the main process of the background service program exists, but the work process (worker process) is blocked, so that the background program monitoring device 60 still cannot receive the feedback of the first heartbeat signal. If the main process and the working process of the background service program are normal, the background program monitoring device 60 may normally receive the feedback of the first heartbeat signal.
Therefore, if the feedback of the first heartbeat signal is not received, the restart module 64 determines that the corresponding background service program is abnormal, and therefore the restart module 64 performs a restart operation on the background service program.
In order to prevent the misoperation of the background program monitoring device, the restart module 64 does not judge the abnormality of the background service program according to the single first heartbeat signal feedback result, but if the background service program does not respond to the first heartbeat signal with the set times, the restart module 64 judges the abnormality of the corresponding background service program; such as no response or response timeout of the first heartbeat signal for 3 consecutive times, etc. Here, the restart module 64 may complete the restart operation of the background service program by performing a shutdown operation on all processes under the background service program.
If the background program monitoring device 60 can normally receive the feedback of the first heartbeat signal, it determines that the background service program is normal. The background program monitoring device 60 continues to send the first heartbeat signal to the background service program at the set time interval until the background service program finishes running.
This completes the process monitoring process in the daemon of the daemon monitoring apparatus 60 of the present preferred embodiment.
The background program monitoring device of the preferred embodiment judges whether the background service program normally operates by sending heartbeat information to the background service program, so that the judgment result is more accurate, the automatic operation capability of the background program monitoring process can be improved, and the condition confirmation of the background service program by manpower is avoided.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a daemon monitoring device according to a second preferred embodiment of the present invention. The daemon monitoring device of the preferred embodiment may be implemented by using the above daemon monitoring method, and the daemon monitoring device 70 includes a configuration file reading module 71, a monitoring state table generating module 72, a heartbeat signal sending module 73, a restarting module 74, and a heartbeat signal feedback module 75.
On the basis of the first preferred embodiment, the daemon monitoring device 70 of this preferred embodiment further includes a heartbeat signal feedback module 75, where the heartbeat signal feedback module 75 is configured to receive a second heartbeat signal of the system process, and perform a feedback operation on the second heartbeat signal; and the system process generates a monitoring process reset signal for resetting the monitoring process according to the feedback information of the second heartbeat signal.
When the daemon monitoring device 70 of the preferred embodiment is used, in the process of monitoring the daemon monitoring device 70 on the daemon service program, the heartbeat signal feedback module 75 also receives a second heartbeat signal of the system process, and performs a feedback operation on the second heartbeat signal. The system process may be a daemon process created by a crond planning task (a periodic planning task). If the heartbeat signal feedback module 75 cannot respond to the second heartbeat signal in time, the system process determines that the background program monitoring process is abnormal, and the system process may restart the background program monitoring process of the background program monitoring device 70. Therefore, the working stability and the automatic operation capability of the background program monitoring device are further improved.
This completes the process monitoring process in the daemon of the daemon monitoring apparatus 70 of the present preferred embodiment.
On the basis of the first preferred embodiment, the background program monitoring device of the present preferred embodiment determines the state of the background program monitoring process in the background program monitoring device in real time through the system process, and if the background program monitoring process is abnormal, the background program monitoring device is restarted; therefore, the daemon process of the system kernel level is used for monitoring and resetting the background program monitoring process, and the working stability and the automatic operation capability of the background program monitoring process are further improved.
Referring to fig. 8, fig. 8 is a schematic structural diagram of a daemon monitoring device according to a third preferred embodiment of the present invention. The daemon monitoring device of the preferred embodiment may be implemented by using the above daemon monitoring method, and the daemon monitoring device 80 includes a configuration file reading module 81, a monitoring state table generating module 82, a heartbeat signal sending module 83, a restarting module 84, an external control module 85, and a log file updating module 86.
On the basis of the first preferred embodiment, the daemon monitoring device 80 of this preferred embodiment further includes an external control module 85 and a log file updating module 86, where the external control module 85 is configured to receive an external control command and perform a control operation on a corresponding daemon service program according to the external control command. The log file updating module 86 is configured to generate a log file and perform an updating operation on the log file according to the feedback of the first heartbeat signal.
Referring to fig. 9, fig. 9 is a schematic structural diagram of an external control module of a daemon monitoring device according to a third preferred embodiment of the invention. The external control module 85 includes a program starting unit 91, a program resource recycling unit 92, a monitor process start judging unit 93, and a monitor process start unit 94.
The program starting unit 91 is configured to receive a script command and start a background service program for executing the script command; the program resource recycling unit 92 is configured to close the background service program and recycle the background service program resource after the script command is executed; the monitoring process starting judgment unit 93 is configured to receive a monitoring process starting command, and judge whether a monitoring process in starting exists according to the monitoring process starting command; the monitor process starting unit 94 is configured to perform a monitor process starting operation.
When the daemon monitoring device 80 of the preferred embodiment is in use, the external control module 85 receives an external control command, which may be a script command or a monitoring process start command. The script command is a command for controlling the background service program to perform script operation. The monitoring process starting command is a command for starting the monitoring process of the background program.
Specifically, if the external control command is a script command, the step of the external control module 85 performing control operation on the corresponding background service program includes:
the program starting unit 91 of the external control module 85 receives the script command and determines whether the script command is a legal command, and if the script command is a legal command, starts a background service program for executing the script command.
If the script command is a list command (list command), a list of all background service processes obtained by analyzing the configuration file is listed to be used as a parameter index for other command operations.
If the script command is a status command, the status of all background services is listed, including the information in the memory table.
If the script command is a start command, a certain background service program is run, and a first heartbeat signal is sent to the background service program.
If the script command is a stop command, a stop command is executed for a certain background service program.
If the script command is a restart command, the start command is executed after a set time for executing the stop command for a certain background service program.
If the script command is a start all command (startall command), the start command is executed for all background servers.
If the script command is a close command (shutdown command), executing a stop command on all background service programs, and then executing the stop command on the background program monitoring process.
If the script command is a test command (test command), a certain background service program sends a first heartbeat signal to be tested.
When the script command of the program starting unit is executed, the program resource recycling unit 92 of the external control module 85 closes the background service program and recycles the resources of the background service program.
Specifically, if the external control command is a monitor process start command, the step of the external control module 85 performing control operation on the corresponding background service program includes:
the monitoring process start judging unit 93 of the external control module 85 receives the monitoring process start command, and judges whether there is a monitoring process in start according to the monitoring process start command.
If there is a monitoring process in the process of starting, the external control module 85 stops the monitoring process starting operation.
If there is no monitoring process in the process of starting, the monitoring process starting unit 94 of the external control module 85 performs a monitoring process starting operation.
The log file update module 86 then generates a log file and performs an update operation on the log file according to the feedback of the first heartbeat signal and the feedback of the control operation. Namely, the state change of the background service program and the state change of the process in the background service program are recorded in the log file. If serious errors such as failure of starting the background service program occur, the errors can be reported to technicians, so that the technicians can process the errors in time.
This completes the process monitoring process in the daemon of the daemon monitoring apparatus 80 of the present preferred embodiment.
On the basis of the first preferred embodiment, the daemon monitoring device of the present preferred embodiment may also control the daemon according to an external control command, and record the state of the daemon through a log file, further expanding the function of the daemon monitoring process.
The following describes a specific working principle of the daemon monitoring method and the daemon monitoring device according to the present invention by using a specific embodiment. Referring to fig. 10 and 11, fig. 10 is an overall architecture diagram of a server system in which the embodiments of the daemon monitoring method and the daemon monitoring device of the present invention are located, and fig. 11 is a usage flowchart of the embodiments of the daemon monitoring method and the daemon monitoring device of the present invention.
Referring to fig. 10, fig. 10 is a structural diagram of a server system where the daemon monitoring device is located, where the server system includes a system process, a daemon monitoring device, and a daemon service group. The background service program group comprises a TCP background service program, a UDP background service program, an HTTP background service program and a WEBSOCKET background service program. Each background service program comprises a main process master, a management process manager, a plurality of work process workers and a background service program configuration file config.
The background program monitoring device can record the state of each background service program by reading the configuration file of each background service program. The background program monitoring device can monitor whether each background service program in the background service program group normally runs or not through the first heartbeat signal. And the background program monitoring device can conduct the external control command to the corresponding background service program to execute the operation. And monitoring the monitoring process in the background program monitoring device through the system process by the second heartbeat signal, so as to prevent the monitoring process of the background program monitoring device from being abnormal.
The following describes in detail a specific flow of monitoring by the daemon in this embodiment with reference to fig. 11. The background service program monitoring process comprises the following steps:
step S1101, the daemon monitoring device traverses the daemon service program, and acquires a corresponding configuration file;
step S1102, parsing the configuration file, and generating a monitoring state table of the background service program, where the monitoring state table includes, but is not limited to, attributes of the background service program, such as a process name, a process entry PHP file location, a process start PHP file location, a monitor port, a background service program type, a main process number, a management process number, a process state (such as the number of first heartbeat signal feedback failures), and a background service program start time. The above-mentioned partial attribute can be directly obtained by configuration file, such as process name, etc., and can also be subsequently obtained by feedback of background service program, such as process state, etc. Meanwhile, a log file which is also used for recording the updating and abnormal states of the background service program is generated in the step.
Step S1103, receiving and executing an external control command, where the external control command includes but is not limited to a script command and a monitor process start command.
If the external control command is a script command such as list, the background program monitoring device executes the script command through a corresponding background service program; and closing the corresponding background service program after the operation is executed, and recovering the background service program resources.
If the external control command is a monitoring process opening command, the background program monitoring device can judge whether an opening monitoring process exists or not by carrying out exclusive locking operation on the monitoring process lock file, and if the opening monitoring process exists, the opening operation is finished; and if the monitoring process in the starting process does not exist, starting the monitoring process, namely sending a first heartbeat signal to all the background service programs at a set time interval, such as 30 seconds.
Step S1104, updating the monitoring state table of the background service program according to the execution result of the external control command.
Step S1105, according to the execution result of the external control command, updating the log file, if the external control command execution is abnormal, reporting the abnormality to the technician.
While the background program monitoring device executes the external control command, the background program monitoring device further includes:
step S1106, receiving a second heartbeat signal of the system process, and performing a feedback operation on the second heartbeat signal. If the background program monitoring device cannot respond to the second heartbeat signal in time, the system process judges that the background program monitoring process is abnormal, and the system process can restart the background program monitoring process of the background program monitoring device.
Meanwhile, the background program monitoring device also has the function of automatically monitoring the background service program, and the automatic monitoring step comprises the following steps:
in step S1107, the background program monitoring device sends the first heartbeat signal to all the background service programs at a set time interval.
Step S1108, the background program monitoring device determines to restart the corresponding background service program according to the feedback of the background service program to the first heartbeat signal.
Specifically, if the main process (master process) of the background service program does not exist, the background program monitoring device cannot receive the feedback of the first heartbeat signal. Or the main process of the background service program exists, but the work process (worker process) is blocked, so that the background program monitoring device still cannot receive the feedback of the first heartbeat signal. If the main process and the working process of the background service program are normal, the background program monitoring device can normally receive the feedback of the first heartbeat signal.
Therefore, the background program monitoring device adds 1 to the feedback failure times of the first heartbeat signal each time the background program monitoring device does not receive the feedback of the first heartbeat signal, and if the feedback failure times of the first heartbeat signal reach 3, the background program monitoring device judges that the corresponding background service program is abnormal and restarts the background service program. And if the feedback of the first heartbeat signal is received, resetting the number of times of failure of the feedback of the first heartbeat signal.
Step S1109, updating the monitoring state table of the background service program according to the feedback result of the first heartbeat signal.
In step S1110, the log file is updated according to the feedback result of the first heartbeat signal, and the process returns to step S1107. And if the background service program fails to restart and other exceptions occur, reporting the exceptions to a technical staff.
In this way, the background program monitoring method and the background service program monitoring process of the background program monitoring device of the present embodiment are completed.
The background program monitoring method and the background program monitoring device adopt the crond daemon process of the system kernel to monitor the program monitoring process, thereby ensuring the operation stability of the background program monitoring device. And meanwhile, the first heartbeat signal is circularly and asynchronously sent to all the monitoring background service programs, so that the high performance and the stability of the background service programs are ensured. Therefore, the background program monitoring method and the background program monitoring device have higher stability and automatic operation capability, can realize unattended automatic restart operation on the background service program, and simultaneously cannot damage and influence the performance of the monitored background service program.
The background program monitoring method and the background program monitoring device judge whether the background service program runs normally or not by sending heartbeat information to the background service program, so that the judgment result is more accurate, the automatic running capability of the background program monitoring process can be improved, and the condition confirmation of the background service program by manpower is avoided; the technical problems that the existing background program monitoring method and the background program monitoring device are poor in automatic operation capacity and need manpower to confirm the state are solved.
As used herein, the terms "component," "module," "system," "interface," "process," and the like are generally intended to refer to a computer-related entity: hardware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
FIG. 12 and the following discussion provide a brief, general description of an operating environment of an electronic device in which a daemon monitoring apparatus of the present invention is implemented. The operating environment of FIG. 12 is only one example of a suitable operating environment and is not intended to suggest any limitation as to the scope of use or functionality of the operating environment. Example electronic devices 1212 include, but are not limited to, wearable devices, head-mounted devices, medical health platforms, personal computers, server computers, hand-held or laptop devices, mobile devices (such as mobile phones, Personal Digital Assistants (PDAs), media players, and the like), multiprocessor systems, consumer electronics, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
Although not required, embodiments are described in the general context of "computer readable instructions" being executed by one or more electronic devices. Computer readable instructions may be distributed via computer readable media (discussed below). Computer readable instructions may be implemented as program modules, such as functions, objects, Application Programming Interfaces (APIs), data structures, etc. that perform particular tasks or implement particular abstract data types. Typically, the functionality of the computer readable instructions may be combined or distributed as desired in various environments.
FIG. 12 illustrates an example of an electronic device 1212 that includes one or more embodiments of the daemon monitoring apparatus of the invention. In one configuration, the electronic device 1212 includes at least one processing unit 1216 and memory 1218. Depending on the exact configuration and type of electronic device, memory 1218 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. This configuration is illustrated in fig. 12 by dashed line 1214.
In other embodiments, electronic device 1212 may include additional features and/or functionality. For example, device 1212 may also include additional storage (e.g., removable and/or non-removable) including, but not limited to, magnetic storage, optical storage, and the like. Such additional storage is illustrated in fig. 12 by storage 1220. In one embodiment, computer readable instructions to implement one or more embodiments provided herein may be in storage 1220. Storage 1220 may also store other computer readable instructions to implement an operating system, an application program, and the like. Computer readable instructions may be loaded in memory 1218 for execution by processing unit 1216, for example.
The term "computer readable media" as used herein includes computer storage media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions or other data. Memory 1218 and storage 1220 are examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by electronic device 1212. Any such computer storage media may be part of electronic device 1212.
The term "computer readable media" may include communication media. Communication media typically embodies computer readable instructions or other data in a "modulated data signal" such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" may include signals that: one or more of the signal characteristics may be set or changed in such a manner as to encode information in the signal.
Components of electronic device 1212 may be connected by various interconnects, such as a bus. Such interconnects may include Peripheral Component Interconnect (PCI), such as PCI express, Universal Serial Bus (USB), firewire (IEEE1394), optical bus structures, and the like. In another embodiment, components of electronic device 1212 may be interconnected by a network. For example, memory 1218 may be comprised of multiple physical memory units located in different physical locations interconnected by a network.
Those skilled in the art will realize that storage devices utilized to store computer readable instructions may be distributed across a network. For example, an electronic device 1230 accessible via a network 1228 may store computer readable instructions to implement one or more embodiments provided by the present invention. Electronic device 1212 may access electronic device 1230 and download a part or all of the computer readable instructions for execution. Alternatively, electronic device 1212 may download pieces of the computer readable instructions, as needed, or some instructions may be executed at electronic device 1212 and some at electronic device 1230.
Various operations of embodiments are provided herein. In one embodiment, the one or more operations may constitute computer readable instructions stored on one or more computer readable media, which when executed by an electronic device, will cause the computing device to perform the operations. The order in which some or all of the operations are described should not be construed as to imply that these operations are necessarily order dependent. Those skilled in the art will appreciate alternative orderings having the benefit of this description. Moreover, it should be understood that not all operations are necessarily present in each embodiment provided herein.
Also, although the disclosure has been shown and described with respect to one or more implementations, equivalent alterations and modifications will occur to others skilled in the art based upon a reading and understanding of this specification and the annexed drawings. The present disclosure includes all such modifications and alterations, and is limited only by the scope of the appended claims. In particular regard to the various functions performed by the above described components (e.g., elements, resources, etc.), the terms used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the disclosure. In addition, while a particular feature of the disclosure may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for a given or particular application. Furthermore, to the extent that the terms "includes," has, "" contains, "or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term" comprising.
Each functional unit in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium. The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Each apparatus or system described above may perform the method in the corresponding method embodiment.
In summary, although the present invention has been disclosed in the foregoing embodiments, the serial numbers before the embodiments, such as "first" and "second", are used for convenience of description only, and do not limit the sequence of the embodiments of the present invention. Furthermore, the above embodiments are not intended to limit the present invention, and those skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention, therefore, the scope of the present invention shall be limited by the appended claims.
Claims (15)
1. A background program monitoring method is characterized by comprising the following steps:
traversing the background service programs, and reading configuration files of all the background service programs; the configuration file comprises process identification information, process position information, a monitoring port and a background service program type in a corresponding background service program;
generating a monitoring state table of the background service program according to the configuration file of the background service program, wherein the monitoring state table comprises process position information, process identification information, a monitoring port, a background service program type, process state information, process starting time and process information in the background server program of related processes in the background service program;
sending first heartbeat signals to all background service programs at set time intervals according to the monitoring state table; and
and determining to restart the corresponding background service program according to the feedback of the background service program to the first heartbeat signal.
2. A background program monitoring method as claimed in claim 1, wherein the step of determining, according to the feedback of the background service program to the first heartbeat signal, that the corresponding background service program is to be restarted includes:
and if the background service program does not continuously respond to the first heartbeat signal with the set times, restarting the corresponding background service program.
3. A daemon monitoring method according to claim 1, further comprising:
receiving a second heartbeat signal of a system process, and performing feedback operation on the second heartbeat signal; and the system process generates a monitoring process reset signal for resetting the monitoring process according to the feedback information of the second heartbeat signal.
4. A daemon monitoring method according to claim 1, wherein the daemon monitoring method comprises:
and receiving an external control command, and controlling the corresponding background service program according to the external control command.
5. A daemon monitoring method according to claim 4, wherein the external control command comprises a script command;
the step of receiving an external control command and performing control operation on a corresponding background service program according to the external control command comprises the following steps:
receiving the script command and starting a background service program for executing the script command; and
and after the script command is executed, closing the background service program and recycling the background service program resources.
6. A background program monitoring method according to claim 4, wherein the external control command includes a monitor process start command;
the step of receiving an external control command and performing control operation on a corresponding background service program according to the external control command comprises the following steps:
receiving a monitoring process starting command, and judging whether a monitoring process in the process of starting exists according to the monitoring process starting command;
if the monitoring process in the starting process exists, stopping the starting operation of the monitoring process; and
and if the monitoring process in the starting process does not exist, starting the monitoring process.
7. A daemon monitoring method according to claim 1, wherein the daemon monitoring method comprises:
and generating a log file, and updating the log file according to the feedback of the first heartbeat signal.
8. A daemon monitoring apparatus, comprising:
the configuration file reading module is used for traversing the background service programs and reading the configuration files of all the background service programs; the configuration file comprises process identification information, process position information, a monitoring port and a background service program type in a corresponding background service program;
the monitoring state table generating module is used for generating a monitoring state table of the background service program according to the configuration file of the background service program, wherein the monitoring state table comprises process position information, process identification information, a monitoring port, a background service program type, process state information, process starting time and process information in the background server program of relevant processes in the background service program;
the heartbeat signal sending module is used for sending first heartbeat signals to all background service programs at set time intervals according to the monitoring state table; and
and the restarting module is used for determining to restart the corresponding background service program according to the feedback of the background service program to the first heartbeat signal.
9. A background program monitoring device as claimed in claim 8, wherein the restart module is configured to restart the corresponding background service program if the background service program does not continuously respond to the first heartbeat signal for a set number of times.
10. A daemon monitoring apparatus according to claim 8, further comprising:
the heartbeat signal feedback module is used for receiving a second heartbeat signal of the system process and carrying out feedback operation on the second heartbeat signal; and the system process generates a monitoring process reset signal for resetting the monitoring process according to the feedback information of the second heartbeat signal.
11. A daemon monitoring apparatus according to claim 8, further comprising:
and the external control module is used for receiving an external control command and carrying out control operation on the corresponding background service program according to the external control command.
12. A daemon monitoring apparatus according to claim 11, wherein the external control command comprises a script command;
the external control module includes:
the program starting unit is used for receiving the script command and starting a background service program for executing the script command; and
and the program resource recovery unit is used for closing the background service program and recovering the background service program resources after the script command is executed.
13. A background program monitoring apparatus as claimed in claim 11, wherein the external control command comprises a monitor process start command;
the external control module includes:
the monitoring process starting judging unit is used for receiving a monitoring process starting command and judging whether a monitoring process in starting exists according to the monitoring process starting command;
and the monitoring process starting unit is used for carrying out monitoring process starting operation.
14. A daemon monitoring apparatus according to claim 8, wherein the daemon monitoring apparatus comprises:
and the log file updating module is used for generating a log file and updating the log file according to the feedback of the first heartbeat signal.
15. A storage medium having stored therein processor-executable instructions, the instructions being loaded by one or more processors to perform the daemon monitoring method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710079400.XA CN108427616B (en) | 2017-02-14 | 2017-02-14 | Background program monitoring method and monitoring device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710079400.XA CN108427616B (en) | 2017-02-14 | 2017-02-14 | Background program monitoring method and monitoring device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108427616A CN108427616A (en) | 2018-08-21 |
| CN108427616B true CN108427616B (en) | 2020-12-01 |
Family
ID=63155203
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710079400.XA Active CN108427616B (en) | 2017-02-14 | 2017-02-14 | Background program monitoring method and monitoring device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108427616B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110032487A (en) * | 2018-11-09 | 2019-07-19 | 阿里巴巴集团控股有限公司 | Keep Alive supervision method, apparatus and electronic equipment |
| CN111385651A (en) * | 2018-12-29 | 2020-07-07 | 深圳Tcl数字技术有限公司 | Automatic repair method and device based on middleware, smart television and storage medium |
| CN109788068B (en) * | 2019-02-14 | 2020-11-03 | 腾讯科技（深圳）有限公司 | Heartbeat state information reporting method, device and equipment and computer storage medium |
| CN109787997B (en) * | 2019-02-26 | 2021-06-11 | 上海易点时空网络有限公司 | PHP-based TCP (Transmission control protocol) service method and server |
| CN110221934B (en) * | 2019-05-08 | 2023-09-01 | 惠州市德赛西威汽车电子股份有限公司 | Vehicle-mounted system recovery method |
| CN110471689A (en) * | 2019-08-22 | 2019-11-19 | 北京元安物联技术有限公司 | A kind of application program updating method and device |
| CN110572292B (en) * | 2019-10-30 | 2022-04-15 | 北京永亚普信科技有限责任公司 | High availability system and method based on unidirectional transmission link |
| CN111651323A (en) * | 2020-05-29 | 2020-09-11 | 山东中创软件商用中间件股份有限公司 | Application software monitoring method, device and equipment |
| CN113254305B (en) * | 2021-05-08 | 2022-08-02 | 山东英信计算机技术有限公司 | Method, system, equipment and storage medium for displaying offline state of testing machine |
| CN114020356B (en) * | 2021-11-02 | 2023-11-28 | 北京天融信网络安全技术有限公司 | Method and device for safely closing service |
| CN116032326B (en) * | 2022-12-21 | 2024-03-05 | 苏州恩易浦科技有限公司 | Signal control method suitable for photovoltaic equipment, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103246589A (en) * | 2012-02-03 | 2013-08-14 | 京信通信系统（中国）有限公司 | Multithread monitoring method and device |
| CN103595804A (en) * | 2013-11-20 | 2014-02-19 | 北京京东尚科信息技术有限公司 | Server cluster monitoring system |
| CN105095046A (en) * | 2015-07-14 | 2015-11-25 | 北京奇虎科技有限公司 | Method and device for task monitoring |
| CN105389243A (en) * | 2015-10-26 | 2016-03-09 | 华为技术有限公司 | Container monitoring method and apparatus |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070220375A1 (en) * | 2006-02-24 | 2007-09-20 | Symbol Technologies, Inc. | Methods and apparatus for a software process monitor |
-
2017
- 2017-02-14 CN CN201710079400.XA patent/CN108427616B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103246589A (en) * | 2012-02-03 | 2013-08-14 | 京信通信系统（中国）有限公司 | Multithread monitoring method and device |
| CN103595804A (en) * | 2013-11-20 | 2014-02-19 | 北京京东尚科信息技术有限公司 | Server cluster monitoring system |
| CN105095046A (en) * | 2015-07-14 | 2015-11-25 | 北京奇虎科技有限公司 | Method and device for task monitoring |
| CN105389243A (en) * | 2015-10-26 | 2016-03-09 | 华为技术有限公司 | Container monitoring method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108427616A (en) | 2018-08-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108427616B (en) | Background program monitoring method and monitoring device | |
| KR102268355B1 (en) | Cloud deployment infrastructure validation engine | |
| JP6396887B2 (en) | System, method, apparatus, and non-transitory computer readable storage medium for providing mobile device support services | |
| US9280451B2 (en) | Testing device | |
| US9384114B2 (en) | Group server performance correction via actions to server subset | |
| US10452469B2 (en) | Server performance correction using remote server actions | |
| US7624309B2 (en) | Automated client recovery and service ticketing | |
| US20210311859A1 (en) | Orchestration for automated performance testing | |
| US8489941B2 (en) | Automatic documentation of ticket execution | |
| JP2008191878A (en) | Remote diagnostic-failure responding system, remote diagnostic-failure responding device, remote diagnostic-failure response instruction device, remote diagnostic-falure responding method, and remote diagnostic-failure responding program | |
| US20070074172A1 (en) | Software problem administration | |
| CN106549795B (en) | System for monitoring a plurality of distributed devices | |
| US10432490B2 (en) | Monitoring single content page application transitions | |
| US10462234B2 (en) | Application resilience system and method thereof for applications deployed on platform | |
| CN112395194A (en) | Method and device for accessing test platform | |
| CN111400094A (en) | Method, device, equipment and medium for restoring factory settings of server system | |
| CN112416698A (en) | Monitoring system expansion method and device, storage medium and electronic equipment | |
| CN113010365A (en) | System running state monitoring method, system running state detection device, electronic equipment and storage medium | |
| KR20160112787A (en) | Test system and control method thereof | |
| CN111868693B (en) | Information processing apparatus and information processing method | |
| US11822438B1 (en) | Multi-computer system for application recovery following application programming interface failure | |
| CN111832735B (en) | Method and system for performing a machine learning process based on templates | |
| CN108664366A (en) | Data transmission method, device and server | |
| CN113886215A (en) | Interface test method, device and storage medium | |
| CN116483566A (en) | Resource processing method and device for server, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |