Program monitoring method, device, equipment, computer program product and system

Abstract

The invention discloses a program monitoring method, device and equipment and a computer program product and system, and is applied to the technical field of computers. A monitoring agent device reads an application program database, screens out state information of a to-be-processed application program, and sends the state information to a server; monitoring operation matched with the state information of the application program to be processed is executed in the application program server, and a monitoring result is obtained. The application program monitoring function is added for the TUMS, the monitoring agent device directly reads the application program database, the application program database serves as a configuration carrier for program monitoring, independent operation and large-area operation can be achieved, the time for starting and stopping the program in a large area is shortened, the application program monitoring efficiency is greatly improved, and therefore the application program monitoring efficiency is improved. And the maintenance difficulty and cost of the TUMS can be reduced.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular, relates to a program monitoring method, device, equipment, computer program product and system. Background Art

[0002] With the vigorous development of the civil aviation industry, civil aviation information technology has become increasingly mature and complete.

[0003] Type B message is a standardized information transmission protocol that can encode various flight information into standardized telegrams and transmit them reliably and efficiently through dedicated air lines, thus ensuring the transmission efficiency and security of flight information.

[0004] TUMS (Travelsky Uninformed Message Bus) can be used as an automatic forwarding platform for typeb messages. The maintenance of the TUMS system mainly relies on manual participation. With the continuous expansion of TUMS system applications and the growth of server scale, the difficulty and cost of TUMS system maintenance are also increasing. Once an application fails, manual participation is required to recover, and the failure recovery time is too long and the efficiency is low. Summary of the invention

[0005] In view of this, the present application provides a program monitoring method, apparatus, device, computer program product and system to solve the problem of long fault recovery time and low efficiency of the TUMS system.

[0006] To solve the above problems, this application provides the following solutions:

[0007] A program monitoring method is applied to a message bus interface system TUMS, wherein the TUMS includes an application database, multiple application servers and multiple monitoring agent devices, wherein the application servers correspond to the monitoring agent devices one by one, and the method includes:

[0008] The monitoring agent device reads the application database and filters out the status information of the application to be processed;

[0009] The monitoring agent device executes a monitoring operation matching the status information of the application to be processed in the application server to obtain a monitoring result.

[0010] A program monitoring device, comprising:

[0011] A reading unit and a monitoring unit; wherein:

[0012] A reading unit, used for monitoring the agent device to read the application database and filter out the status information of the application to be processed;

[0013] The monitoring unit is used for monitoring the agent device in the application server, executing the monitoring operation matching the status information of the application to be processed, and obtaining the monitoring result.

[0014] A program monitoring device, comprising a memory and a processor;

[0015] The memory is used to store instructions;

[0016] The processor is used to execute the instructions stored in the memory to implement any of the above program monitoring methods.

[0017] A computer program product comprises a computer program / instruction, wherein when the computer program / instruction is executed by a processor, the computer program / instruction implements the monitoring method of any of the above programs.

[0018] A message bus interface system TUMS, comprising:

[0019] Front-end, application database, and application server; where:

[0020] The front end is used to generate control instructions and send the control instructions to the application database;

[0021] The application database receives the control instruction and updates the status information of the application in the monitoring table matching the control instruction according to the control instruction;

[0022] The application server includes a monitoring agent device, and the monitoring agent device implements the monitoring method of any of the above programs.

[0023] It can be seen from the above scheme that the monitoring method, device, equipment, computer program product and system of the program disclosed in the present application, the monitoring agent device reads the application database, screens out the status information of the application to be processed, and executes the monitoring operation matching the status information of the application to be processed in the application server to obtain the monitoring result. The present application adds the monitoring function of the application to TUMS, and the monitoring agent device directly reads the application database, and uses the application database as the configuration carrier of the program monitoring. It can be operated individually or in a large area, which reduces the time of starting and stopping the program in a large area, greatly improves the monitoring efficiency of the application, and thus can also reduce the difficulty and cost of TUMS maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0025] Figure 1 It is a flow chart of a monitoring method of a program provided by the present application;

[0026] Figure 2 This is an example diagram of the management interface of the AOS front end provided by this application;

[0027] Figure 3 is the system architecture diagram of the TUMS monitoring system provided by this application;

[0028] Figure 4 This is an example flow chart of the monitoring method of the program provided by this application;

[0029] Figure 5 This is an example flow chart of the monitoring method of the program provided by this application;

[0030] Figure 6 It is another example flow chart of the monitoring method of the program provided by the present application;

[0031] Figure 7 It is a structural diagram of the monitoring device of the program provided by this application;

[0032] Figure 8 It is a hardware structure block diagram of the monitoring device of the program provided by this application;

[0033] Fig. 9 It is a composition structure diagram of the computer program product provided by this application. DETAILED DESCRIPTION

[0034] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0035] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0036] It should be noted that the concepts such as "first" and "second" mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0037] It should be noted that the modifications of "one" and "plurality" mentioned in the present application are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0038] Type B message is a standardized information transmission protocol, which can encode various flight information into standardized messages, mainly through manual operation to forward messages, and air lines to reliably and efficiently transmit messages. Although telegrams may be delayed or blocked for some reason during line transmission, there is almost no loss of information.

[0039] With the increase in the number of flights and the surge in message volume, it is becoming increasingly difficult to forward messages solely through manual operations. The civil aviation information system urgently needs to establish an automated type b message forwarding platform to achieve intelligent analysis, routing selection and rapid delivery of messages.

[0040] TUMS (Travelsky Uninformed Message Bus) can be used as an automatic forwarding platform for typeb messages. TUMS adopts a new overall system design concept, integrates the typeb message forwarding function, and achieves unification with the SMS platform. However, TUMS does not have an automatic monitoring and scheduling mechanism for applications, and maintenance work is mainly completed by manual participation. With the continuous expansion of TUMS system applications and the growth of server scale, the maintenance difficulty and cost of TUMS are increasing. Once an application fails, manual participation is required to recover, and the failure recovery time is too long.

[0041] In order to solve the above problems, the present application provides a program monitoring method, apparatus, device, computer program product and system.

[0042] The TUMS provided in this application includes an application database, multiple application servers and multiple monitoring agent devices.

[0043] The application database, the application server, and the monitoring agent are associated with each other.

[0044] The application database stores the application information of the monitored application servers and each application in the application servers.

[0045] The monitoring agent device can also be called TUMS Monitor Agent. The monitoring agent device corresponds to an application server one by one, and is responsible for monitoring and managing all applications in the corresponding application server, regularly polling each application, and starting and stopping abnormal applications.

[0046] It should be noted that TUMS controls existing programs mainly through script start and stop, and the guardian is set in the configuration file, which means that each time the program changes, the configuration file needs to be manually configured and restarted, which is difficult to adapt to the needs of frequent changes. Therefore, this application provides a flexible and controllable application monitoring method that does not rely on configuration files. It is controlled through a simple front-end interface, which greatly simplifies the maintenance and management process of the TUMS system. It is understandable that when a problem occurs in the TUMS system, the monitoring system will monitor the abnormal situation and automatically execute the application start and stop script for recovery, which can realize intelligent monitoring, fault location and automatic restart of the application, reduce manual maintenance costs, and improve the ability to quickly recover from faults.

[0047] See also Figure 1 , a flow chart of a program monitoring method provided by the present application. Figure 1 As shown, the program monitoring method includes the following steps:

[0048] Step 101: The monitoring agent reads the application database and filters out the status information of the application to be processed.

[0049] It should be noted that the application database includes a monitoring table, which records the status information of the application. The monitoring agent needs to read the content corresponding to the application to be monitored in the application server corresponding to the monitoring agent from the monitoring table.

[0050] Specifically, the monitoring agent reads the process configuration related to the corresponding application service program server from the monitoring table. The monitoring table of the application database records the application information of the application corresponding to each application server. Therefore, the monitoring agent needs to poll all process configurations in the monitoring table to obtain the relevant process configuration of the corresponding application server. The polling time of the monitoring agent can be set on TUMS.

[0051] Optionally, the monitoring agent device polls the status information of all applications in the monitoring table of the application database at a preset time to obtain the status information of the to-be-processed application related to the application server corresponding to the monitoring agent device.

[0052] It should be noted that, in the process of polling the monitoring table of the application database, the monitoring agent device mainly reads the status information of the application managed by the application server corresponding to the monitoring agent device. It can be understood that the status information of the application to be processed is the status information of the application managed by the application server corresponding to the monitoring agent device.

[0053] For the application database, an update will be performed, which updates the status information of the application in the monitoring table. The update process is as follows:

[0054] The TUMS front end sends control instructions to the application database;

[0055] After receiving the control instruction, the application database updates the status information of the application in the monitoring table that matches the control instruction.

[0056] Specifically, the front end of TUMS can be the AOS (Application Operation System) front end of TUMS. The AOS front end can provide a good management interface and can send control instructions to the application database. The control instructions sent by the AOS front end can change the value of the application database. The control instructions can be process processing instructions for abnormal applications, application status query instructions, and application process start and stop instructions.

[0057] For example, see Figure 2 , an example diagram of the management interface of the AOS front-end provided in this application.

[0058] like Figure 2 As shown in the figure, one of the functions of the AOS front-end is system management, which can monitor the application status of multiple application servers at the same time. The AOS front-end system management page will display the server IP, application name and current status of the application.

[0059] Step 102: The monitoring agent device executes a monitoring operation matching the status information of the application to be processed in the application server to obtain a monitoring result.

[0060] Different status information of the application to be processed will correspond to different monitoring operations. For example, when the status of the application to be processed is normal: CONTROLSTATUS=0 or CONTROLSTATUS=1, the monitoring agent device needs to write APPSTATUS=1, ISERROR=0, DEALNUM=0, UPDATETIME=sysdate to the monitoring table; if CONTROLSTATUS=2, that is, the status of the application to be processed is abnormal, the monitoring agent device executes the stop process script of the application to be processed, and writes APPSTATUS=1, ISERROR=1, DEALNUM=DEALNUM+1, UPDATETIME=sysdate to the monitoring table.

[0061] Optionally, a monitoring operation is determined based on the status information of the application to be processed, and the corresponding application status information is processed according to the monitoring operation.

[0062] It should be noted that monitoring operations include application process start operations, application process stop operations, error prompt operations, and the like.

[0063] Optional, see Figure 3 , the system architecture diagram of the TUMS monitoring system provided in this application.

[0064] like Figure 3 As shown in Figure 1, the TUMS monitoring system mainly consists of three parts: AOS front-end page, TUMS application database and TUMS server. These parts are interrelated, and the transmission of all data between the AOS front-end and the TUMS application database is realized through the application status recorded in the TUMS application database.

[0065] The AOS front end obtains monitoring data by querying the application status information in the TUMS application database. The application status information in the TUMS application database is real-time. The AOS front end sends control instructions to the TUMS application database, and modifies the value of the TUMS application database through the control instructions. The modified value of the TUMS application database corresponds to the required operation on the application.

[0066] There are multiple TUMS servers, and each TUMS server deploys a monitoring agent MonitorAgent, which is responsible for monitoring and managing all applications in the TUMS server. MonitorAgent will periodically poll the application status information stored in the TUMS application database and start and stop abnormal applications. For example, the polling time is pre-set, and can be obtained every 30 seconds.

[0067] Specifically, the main tasks of MonitorAgent are as follows:

[0068] MonitorAgent starts a separate thread: the folder of the startup program to call the startup script of the corresponding program;

[0069] Poll the corresponding field information in the MonitorConfig table of the TUMS application database and perform corresponding processing;

[0070] Process the abnormal processes in the MonitorConfig table.

[0071] The application status and value recorded in the TUMS application database can also be understood as the configuration information of the monitored application. It should be noted that the configuration information of the monitored application is stored in the MonitorConfig table of the TUMS application database. During the entire monitoring process, the monitored status information will be synchronized to the MonitorConfig table in a timely manner.

[0072] For example, see Figure 4 , a flow chart showing an example of a method for monitoring a program provided in this application.

[0073] This example mainly shows the process of Monitoragent receiving application status and returning application status information.

[0074] Monitoragent receives the query command, reads all processes to be monitored on the local machine from the MonitorConfig table, checks the status information of all processes, and returns the process status information to the application database.

[0075] It should be noted that Monitoragent will check the process name in the database, and Monitoragent will automatically monitor the process status and control status, and compare the monitored process status with the control status.

[0076] For example, see Figure 5 , a flow chart showing an example of a method for monitoring a program provided in this application.

[0077] This example mainly describes the process in which the application database receives process control commands from the AOS front end and processes the process according to the commands.

[0078] The application database receives the control command. When the control command is a startup command, it determines whether the process has been started. If the process has been started, it only needs to update the MonitorConfig table, set CONTROLSTATUS=1, and return the execution result information; if the process has not been started, update the MonitorConfig table, set CONTROLSTATUS=1, execute the startup script, and finally, return the execution result information.

[0079] When the control command is a stop command, determine whether the process has stopped. If the process has stopped, just update the MonitorConfig table, set CONTROLSTATUS=2, and return the execution result information; if the process is in the start state, update the MonitorConfig table, set CONTROLSTATUS=2, and then execute the stop script. Finally, return the execution result information

[0080] When the control command is other commands, an error message is prompted.

[0081] It should be noted that after receiving all commands, Monitoragent will first verify whether the format of the command itself is legal and whether the operation process is configured.

[0082] In summary, the monitoring method of the program disclosed in the present application is that the monitoring agent device reads the application database, screens out the status information of the application to be processed, and executes the monitoring operation matching the status information of the application to be processed in the application server to obtain the monitoring result. The present application adds the monitoring function of the application to TUMS, uses the application database as the configuration carrier of the application process, cancels the configuration file, and directly operates the application database by the front end to monitor the application. The application database is directly read by the monitoring agent device, which can be operated individually or in a large area, reducing the time of starting and stopping the program in a large area, greatly improving the monitoring efficiency of the application, and thus, can also reduce the difficulty and cost of TUMS maintenance.

[0083] Although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.

[0084] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0085] For example, see Figure 6 , another flow chart of an example of a method for monitoring a program provided in this application.

[0086] Step 1: Read all processes to be monitored on this machine from the MonitorConfig table:

[0087] MonitorAgent reads all process configurations related to the local machine from the MonitorConfig table.

[0088] Step 2: Check if all processes have been completed:

[0089] Determine whether all process configurations have been polled; if all processes have been polled, sleep for a while and jump to step 1 to continue the next round of processing; if all processes have not been polled, go to step 3 to continue processing.

[0090] Step 3: Check the status of the next process to determine whether the process is in the startup state:

[0091] Read the configuration of the next process, query the status information of the process, and determine whether the process is in the startup state. If the process is in the startup state, go to step 4; if the process is not in the startup state, go to step 5.

[0092] Step 4: Determine whether CONTROLSTATUS=0 or CONTROLSTATUS=1:

[0093] When the condition of CONTROLSTATUS=0 or CONTROLSTATUS=1 is met, it means that the program status is normal and no processing is required. Only the MonitorConfig table needs to be modified, that is, APPSTATUS=1, ISERROR=0, DEALNUM=0, and UPDATETIME=sysdate need to be written to the MonitorConfig table;

[0094] When the condition of CONTROLSTATUS=0 or CONTROLSTATUS=1 is not met, it may be CONTROLSTATUS=2, which means that the program status is abnormal and needs to be processed. MonitorAgent executes the stop process script of the process stored in the TUMS server, and writes APPSTATUS=1, ISERROR=1, DEALNUM=DEALNUM+1, UPDATETIME=sysdate to the MonitorConfig table; it should be noted that the stop process script is stored in a separate folder. It is understandable that all process scripts can be stored in the form of separate folders in the TUMS application server. After completing step 4, go to step 2 to continue processing the next process.

[0095] Step 5: Check if CONTROLSTATUS=0 or CONTROLSTATUS=2;

[0096] When the condition of CONTROLSTATUS=0 or CONTROLSTATUS=2 is met, it means that the program status is normal and no processing is required. Only the MonitorConfig table needs to be modified, that is, APPSTATUS=2, ISERROR=0, DEALNUM=0, and UPDATETIME=sysdate need to be written to the MonitorConfig table;

[0097] When the condition of CONTROLSTATUS=0 or CONTROLSTATUS=2 is not met, it means that the program status is abnormal and needs to be processed. MonitorAgent executes the startup process script of the process stored in the TUMS server, and writes APPSTATUS=2, ISERROR=1, DEALNUM= DEALNUM+1, UPDATETIME=sysdate to the MonitorConfig table; after completing step 5, go to step 2 to continue processing the next process.

[0098] It should be noted that CONTROLSTATUS is a TUMS application database field, and APPSTATUS / ISERROR / DEALNUM / UPDATETIME are database fields.

[0099] Take the router application on the production server as an example. The initial configuration is as follows:

[0100]

[0101] Note: CONTROLSTATUS=1 indicates that the router needs to remain started.

[0102] MonitorAgent performs the first polling. At this time, the router is in the startup state. The monitoring program does not perform any special processing after the inspection. The status after the inspection is as follows:

[0103]

[0104] Note: APPSTATUS=1 indicates that the router is currently in startup state and no exception handling is required. ISERROR=0, DEALNUM=0, and UPDATETIME is set to the current time.

[0105] MonitorAgent performs the second polling. At this time, the router has exited abnormally. The monitoring program will start the router after detecting the abnormality. The status after processing is as follows:

[0106]

[0107] Note: APPSTATUS=0 means that the router is currently in a stopped state and requires exception handling. ISERROR=1 indicates a program exception. DEALNUM=1 indicates that the exception is being handled for the first time and UPDATETIME is updated.

[0108] MonitorAgent performs the third polling. At this time, the router remains in the exit state. The monitoring program will continue to start the router after detecting the abnormality. The status after processing is as follows:

[0109]

[0110] Note: DEALNUM=2 means that the exception is processed for the first time and UPDATETIME is updated. MonitorAgent performs the fourth polling. At this time, the router has been started. After the monitoring program is checked, it will restore the status. The status after processing is as follows:

[0111]

[0112] Note: APPSTATUS=1 means the program has been started, ISERROR=0, DEALNUM=0, and UPDATETIME is updated.

[0113] At this time, the command to stop the router is sent through the AOS front end. After receiving the command, the monitoring program will stop the router and modify the record information corresponding to the router in the database. The status after processing is as follows:

[0114]

[0115] Note: CONTROLSTATUS=2 means the router needs to be set to stopped state, APPSTATUS=2 means the program has been stopped, update UPDATETIME.

[0116] MonitorAgent performs the fifth poll. At this time, the router has stopped and the scheduled state is also stopped. The status of the monitoring program after the inspection is as follows:

[0117]

[0118] MonitorAgent performs the sixth polling. At this time, the router has been started. Since the router's scheduled state is stopped, the monitoring program will stop the router and modify the record information corresponding to the router in the database. The status after processing is as follows:

[0119]

[0120] MonitorAgent performs the seventh poll. At this time, the router has stopped and the scheduled state is also stopped. The monitoring program will resume the state after checking. The state after processing is as follows:

[0121]

[0122] At this time, the command to start the router is sent through the AOS front end. After receiving the command, the monitoring program will start the router and modify the record information corresponding to the router in the database. The status after processing is as follows:

[0123]

[0124] It should be noted that the present application optimizes the existing system monitoring method, adopts a database as the configuration carrier of the program, cancels the program's configuration file, and directly operates the database's values ​​by the front end to start and stop the program. It can be operated individually or on a large scale, reducing the steps of adding new configurations to restart the program and reducing the time for starting and stopping programs on a large scale. It is easy to operate and highly secure.

[0125] For the above-mentioned program monitoring method, the present application also provides a program monitoring device, the composition of which is as follows: Figure 7 shown.

[0126] Reading unit 10 and monitoring unit 20; wherein:

[0127] The reading unit 10 is used for monitoring the agent device to read the application database and filter out the status information of the application to be processed;

[0128] The monitoring unit 20 is used for monitoring the agent device in the application server, performing a monitoring operation matching the status information of the application to be processed, and obtaining a monitoring result.

[0129] In one implementation, the reading unit 10 is specifically configured to:

[0130] The monitoring agent device polls the status information of all applications in the monitoring table in the application database according to the preset time to obtain the status information of the application to be processed.

[0131] In one embodiment, the reading unit 10 includes an application database updating subunit;

[0132] The application database updating subunit is used for the application database to receive control instructions sent by the front end of TUMS;

[0133] According to the control instruction, the status information of the application program in the monitoring table matching the control instruction is updated.

[0134] In one embodiment, the control instructions in the application database update subunit include abnormal application process processing instructions, application status query instructions, and application process start and stop instructions.

[0135] In one embodiment, the monitoring unit 10 is specifically configured to:

[0136] Determine the corresponding monitoring operations according to the status information of each application to be processed;

[0137] The status information of each pending application is processed according to the corresponding monitoring operation.

[0138] In one embodiment, the monitoring operation in the monitoring unit 10 includes an application process start operation, an application process stop operation, and an error prompt operation.

[0139] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses".

[0140] Optionally, the present application also provides a program monitoring device, such as Figure 8 The hardware structure block diagram of the monitoring device of the program provided by the present application shown mainly includes a processor 1 and a memory 3, and at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4.

[0141] The memory 3 is used to store instructions;

[0142] The processor 1 is used to execute instructions stored in the memory to implement various processing flows of the program monitoring method.

[0143] Optionally, the present application also provides a computer program product, including a computer program / instruction, which implements various processing flows of the program monitoring method when executed by a processor.

[0144] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. Fig. 9 , a composition structure diagram of a computer program product provided by the present application. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 609, or installed from a storage device 606, or installed from a ROM 602. When the computer program is executed by the processing device 601, the above functions defined in the method of the embodiment of the present disclosure are executed.

[0145] In addition, the embodiment of the present application also provides a message bus interface system TUMS, including:

[0146] Front-end, application database, and application server; where:

[0147] The front end is used to generate control instructions and send the control instructions to the application database;

[0148] The application database receives the control instruction and updates the status information of the application in the monitoring table matching the control instruction according to the control instruction;

[0149] The application server includes a monitoring agent device, and the monitoring agent device implements each processing flow of the program monitoring method.

[0150] According to one or more embodiments disclosed in the present application, Example 1 provides a program monitoring method, including:

[0151] The monitoring agent device reads the application database and filters out the status information of the application to be processed;

[0152] The monitoring agent device executes a monitoring operation matching the status information of the application to be processed in the application server to obtain a monitoring result.

[0153] According to one or more embodiments disclosed in the present application, Example 2 provides a monitoring method for the program of Example 1, wherein a monitoring agent reads an application database and filters out status information of an application to be processed, including:

[0154] The monitoring agent device polls the status information of all applications in the monitoring table in the application database according to the preset time to obtain the status information of the application to be processed.

[0155] According to one or more embodiments disclosed in the present application, Example 3 provides a monitoring method for the program of Example 1, and an update process of an application database includes:

[0156] The application database receives control instructions sent by the front end of TUMS;

[0157] According to the control instruction, the status information of the application program in the monitoring table matching the control instruction is updated.

[0158] According to one or more embodiments disclosed in the present application, Example 4 provides a monitoring method for the program of Example 3, wherein the control instructions include process handling instructions for abnormal applications, application status query instructions, and application process start and stop instructions.

[0159] According to one or more embodiments disclosed in the present application, Example 5 provides a monitoring method for the program of Example 1, wherein a monitoring agent device performs a monitoring operation matching the status information of the application to be processed in an application server, and obtains a monitoring result, including:

[0160] Determine the corresponding monitoring operations according to the status information of each application to be processed;

[0161] The status information of each pending application is processed according to the corresponding monitoring operation.

[0162] According to one or more embodiments disclosed in the present application, Example 6 suggests a method for monitoring the program of Example 1, wherein the monitoring operations include an application process start operation, an application process stop operation, and an error prompt operation.

[0163] According to one or more embodiments disclosed in the present application, Example 7 provides a program monitoring device, including:

[0164] A reading unit and a monitoring unit; wherein:

[0165] A reading unit, used for monitoring the agent device to read the application database and filter out the status information of the application to be processed;

[0166] The monitoring unit is used for monitoring the agent device in the application server, executing the monitoring operation matching the status information of the application to be processed, and obtaining the monitoring result.

[0167] According to one or more embodiments disclosed in the present application, Example 9 provides a program monitoring device, including a memory and a processor;

[0168] The memory is used to store instructions;

[0169] The processor is used to execute instructions stored in the memory to implement a program monitoring method such as any one of the above examples.

[0170] According to one or more embodiments disclosed in the present application, Example 9 provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements a monitoring method for a program as in any of the above examples.

[0171] According to one or more embodiments disclosed in the present application, Example 10 provides a message bus interface system TUMS, including:

[0172] Front-end, application database, and application server; where:

[0173] The front end is used to generate control instructions and send the control instructions to the application database;

[0174] The application database receives the control instruction and updates the status information of the application in the monitoring table matching the control instruction according to the control instruction;

[0175] The application server includes a monitoring agent device, and the monitoring agent device implements the program monitoring method as any one of the above examples.

[0176] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0177] For the convenience of description, the above system or device is described by dividing it into various modules or units according to its functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0178] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

[0179] Finally, it should be noted that, in this article, relational terms such as first, second, third and fourth are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0180] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A program monitoring method, characterized in that: Applied to a message bus interface system TUMS, the TUMS includes an application database, multiple application servers and multiple monitoring agent devices, the application servers correspond to the monitoring agent devices one by one, and the method includes: The monitoring agent device reads the application database and filters out the status information of the application to be processed; The monitoring agent device executes a monitoring operation matching the status information of the application to be processed in the application server to obtain a monitoring result.

2. The program monitoring method according to claim 1, characterized in that: The monitoring agent device reads the application database and filters out the status information of the application to be processed, including: The monitoring agent device polls the status information of all the applications in the monitoring table in the application database at a preset time to obtain the status information of the application to be processed.

3. The program monitoring method according to claim 1, characterized in that: The updating process of the application database includes: The application database receives control instructions sent by the front end of the TUMS; According to the control instruction, the status information of the application in the monitoring table matching the control instruction is updated.

4. The program monitoring method according to claim 3, characterized in that: The control instructions include abnormal application process processing instructions, application status query instructions and application process start and stop instructions.

5. The program monitoring method according to claim 1, characterized in that: The monitoring agent device executes a monitoring operation matching the status information of the application to be processed in the application server to obtain a monitoring result, including: Determine the corresponding monitoring operations according to the status information of each application to be processed; The status information of each of the to-be-processed application programs is processed according to the corresponding monitoring operations.

6. The program monitoring method according to claim 1, characterized in that: The monitoring operation includes an application process start operation, an application process stop operation and an error prompt operation.

7. A program monitoring device, characterized in that: include: A reading unit and a monitoring unit; wherein: The reading unit is used to monitor the proxy device to read the application database and filter out the status information of the application to be processed; The monitoring unit is used for the monitoring agent device to perform a monitoring operation matching the status information of the application to be processed in the application server to obtain a monitoring result.

8. A program monitoring device, characterized in that: including memory and processor; The memory is used to store instructions; The processor is used to execute instructions stored in the memory to implement the program monitoring method described in any one of claims 1-6.

9. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instruction is executed by a processor, the monitoring method of the program as described in any one of claims 1 to 6 is implemented.

10. A message bus interface system TUMS, characterized in that: include: Front-end, application database, and application server; where: The front end is used to generate control instructions and send the control instructions to the application database; The application database receives the control instruction, and updates the status information of the application in the monitoring table matching the control instruction according to the control instruction; The application server includes a monitoring agent device, and the monitoring agent device implements the program monitoring method as described in any one of claims 1-6.

Images