CN115495329A

CN115495329A - Monitoring method, device, equipment and medium

Info

Publication number: CN115495329A
Application number: CN202211193469.2A
Authority: CN
Inventors: 吴千
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Priority date: 2022-09-28
Filing date: 2022-09-28
Publication date: 2022-12-20

Abstract

The application relates to the technical field of data analysis, in particular to a monitoring method, a monitoring device, monitoring equipment and a monitoring medium, which are used for simultaneously monitoring a plurality of tasks and ensuring the timeliness of task monitoring. Periodically acquiring the field value of the target field from the data table; the data table comprises a plurality of fields and a plurality of field values of each field; determining the task state of each task based on the task identity identification field and the field value of the task state field; respectively determining the execution duration of each task in execution aiming at the task in execution with the task state being a non-final state; and if the task in execution is determined to be an abnormal task according to the execution duration of each task in execution, alarming aiming at the abnormal task. By setting the data table, the multiple tasks are monitored simultaneously, whether the tasks are abnormal or not is determined according to the states and the execution duration of the tasks, an alarm is given when the tasks are abnormal, and the timeliness of task monitoring is improved.

Description

Monitoring method, device, equipment and medium

Technical Field

The present application relates to the field of data analysis technologies, and in particular, to a monitoring method, apparatus, device, and medium.

Background

Data processing systems generally have asynchronous data file transmission requirements, so that data file interaction needs to be realized by installing a file transmission component client. In the related technology, the alarm monitoring mode of asynchronous data file transmission is that a single node writes a script by itself to alarm, and the situations of no alarm, false alarm and late alarm often occur, so that active discovery and timely emergency treatment cannot be realized. Usually, when the service personnel urgently need the data file, the abnormal data file transmission transaction is discovered passively.

Disclosure of Invention

The embodiment of the application provides a monitoring method, a monitoring device, monitoring equipment and a monitoring medium, which are used for simultaneously monitoring a plurality of tasks and ensuring the timeliness of task monitoring.

In a first aspect, an embodiment of the present application provides a monitoring method, where the method includes:

periodically acquiring the field value of the target field from the data table; the data table comprises a plurality of fields and a plurality of field values of each field, and each field is used for representing attribute information of each task; the target field comprises a task identity identification field and a task state field;

determining the task state of each task based on the task identity identification field and the field value of the task state field;

respectively determining the execution duration of each task in execution aiming at the task in execution with the task state being a non-final state;

and if the task in execution is determined to be an abnormal task according to the execution duration of each task in execution, giving an alarm aiming at the abnormal task.

According to the method and the device, the data table is set, so that the plurality of tasks can be monitored at the same time, whether the tasks are abnormal or not is determined according to the states and the execution duration of the tasks, an alarm is given when the tasks are abnormal, and the timeliness of task monitoring is improved.

In some possible embodiments, the determining the state of each task based on the values of the task identity field and the task state field includes:

for each task, determining the sequence of the field values corresponding to the identification fields of the task in the field values corresponding to the identification fields;

and taking the state characterized by the sequential field values in the field values corresponding to the task state fields as the state of the task.

In the present application, since a plurality of tasks share one data table, in order to accurately determine the state of each task, the state of the task needs to be determined according to the sequence of the id fields of the tasks.

In some possible embodiments, the target field includes: the step of determining the execution duration of each task in execution respectively comprises the following steps:

determining the triggering time of the query operation according to the field value of the triggering time field of the query operation of this time corresponding to each task in execution;

determining the starting time of the executing task according to the field value of the starting time field corresponding to the executing task;

and taking the difference value between the trigger time and the starting time as the execution duration of the task in execution.

In the method and the device, the execution duration of the task is accurately determined by setting the current query operation trigger time field corresponding to the task and the start time field corresponding to the task, so that the abnormal task can be accurately determined.

In some possible embodiments, the target field includes: a query number field, wherein after the task state of each task is determined based on the field values of the task identity field and the task state field, the method further comprises:

aiming at an executing task with a task state being a non-final state, determining a query frequency state value corresponding to the executing task and determining a query frequency corresponding to the executing task;

and if the query times corresponding to the executing task exceed the preset times, determining that the executing task is an abnormal task, and giving an alarm.

In the method, in order to determine whether the task is abnormal more accurately, the query frequency field is set, and when the query exceeds the preset frequency, the task in execution is determined to be an abnormal task, so that the method for determining the abnormal task is more accurate.

In some possible embodiments, the target field includes: a node field, wherein after the task in execution is determined to be an abnormal task, the method further comprises:

determining the field value of a node field corresponding to the task in execution;

determining a node of which the task becomes an abnormal task in the execution according to the field value of the node field;

and generating and displaying an exception prompt according to the node, wherein the exception prompt is used for informing the node of the task becoming an exception task in execution.

In the application, in order to facilitate timely processing of an abnormal task, a node where the task is abnormal needs to be determined, and then a node field is set.

In a second aspect, the present application provides a task monitoring device, the device comprising:

the field value acquisition module is used for periodically acquiring the field value of the target field from the data table; the data table comprises a plurality of fields and a plurality of field values of each field, and each field is used for representing attribute information of each task; the target field comprises a task identity identification field and a task state field;

the task state determining module is used for determining the task state of each task based on the task identity identification field and the field value of the task state field;

the execution time length determining module is used for respectively determining the execution time length of each task in execution aiming at the task in execution with the task state being a non-final state;

and the warning module is used for warning aiming at the abnormal task if the task in execution is determined to be the abnormal task according to the execution duration of each task in execution.

In some possible embodiments, the task state determination module, when performing the determination of the state of each task based on the task identity field and the field value of the task state field, is configured to:

for each task, determining the sequence of field values corresponding to the identification fields of the task in the field values corresponding to the identification fields;

and taking the state represented by the sequential field values in the field values corresponding to the task state fields as the state of the task.

In some possible embodiments, the target field includes: the query operation comprises a trigger time field and a start time field, and the execution duration determining module is configured to determine the execution duration of each task in execution respectively:

In some possible embodiments, the target field includes: the task state determination module is configured to determine a task state of each task based on the task identity field and a field value of the task state field, and is further configured to:

In some possible embodiments, the target field includes: the alarm module is configured to, after determining that the executing task is an abnormal task:

In a third aspect, the present application provides an electronic device, comprising:

a memory for storing program instructions;

a processor for calling the program instructions stored in the memory and executing the steps comprised in any one of the methods of the first aspect in accordance with the obtained program instructions.

In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program comprising program instructions which, when executed by a computer, cause the computer to perform the method of any of the first aspects.

In a fifth aspect, the present application provides a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the method of any one of the first aspects.

Drawings

Fig. 1 is a schematic view of an application scenario of a monitoring method according to an embodiment of the present application;

fig. 2 is an overall flowchart of a monitoring method according to an embodiment of the present disclosure;

fig. 3 is a schematic flowchart of determining a task execution duration of a monitoring method according to an embodiment of the present application;

fig. 4 is a schematic flowchart of a monitoring method for determining an abnormal task based on query times according to an embodiment of the present application;

fig. 5 is a schematic flowchart of determining a node in a monitoring method according to an embodiment of the present application;

fig. 6 is a schematic diagram of a monitoring method according to an embodiment of the present disclosure;

fig. 7 is a schematic view of an electronic device of a monitoring method according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. In the present application, the embodiments and features of the embodiments may be arbitrarily combined with each other without conflict. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.

The terms "first" and "second" in the description and claims of the present application and the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the term "comprises" and any variations thereof, which are intended to cover non-exclusive protection. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. The "plurality" in the present application may mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.

In the technical scheme, the data acquisition, transmission, use and the like all meet the requirements of relevant national laws and regulations.

Before describing the monitoring method provided by the embodiment of the present application, for ease of understanding, the following detailed description is first provided for the technical background of the embodiment of the present application.

Data processing systems generally have asynchronous data file transmission requirements, so that data file interaction needs to be realized by installing a file transmission component client. In the related technology, the alarm monitoring mode of asynchronous data file transmission is that a single node writes a script for alarming by itself, and the situations of no alarm, false alarm and late alarm often occur, so that active discovery and timely emergency treatment cannot be realized. Often, when business personnel urgently need the data file, the business personnel passively discover the abnormal data file transmission transaction.

In view of the above, the present application provides a monitoring method, an apparatus, an electronic device and a storage medium, which are used to solve the above problems. The inventive concept of the present application can be summarized as follows: periodically acquiring the field value of the target field from the data table; the data table comprises a plurality of fields and a plurality of field values of each field, and each field is used for representing attribute information of each task; the target field comprises a task identity identification field and a task state field; determining the task state of each task based on the task identity identification field and the field value of the task state field; respectively determining the execution duration of each task in execution aiming at the task in execution with the task state being a non-final state; and if the task in execution is determined to be an abnormal task according to the execution duration of each task in execution, alarming aiming at the abnormal task.

In order to facilitate understanding of the monitoring method provided by the embodiment of the present application, the following describes a monitoring method provided by the embodiment of the present application with reference to the accompanying drawings:

fig. 1 is a view of an application scenario of a monitoring method in the embodiment of the present application. The drawing comprises the following steps: server 10, memory 20, terminal device 30; wherein:

the server 10 periodically obtains the field value of the target field from the data table; the data table comprises a plurality of fields and a plurality of field values of each field, and each field is used for representing attribute information of each task; the target field comprises a task identity identification field and a task state field; the data table is stored in a memory, and the task state of each task is determined based on the field values of the task identity identification field and the task state field; respectively determining the execution duration of each task in execution aiming at the task in execution with the task state being a non-final state; if the task in execution is determined to be an abnormal task according to the execution duration of each task in execution, an alarm is given for the abnormal task, and an alarm indication is displayed in the terminal device 30.

The description in this application only details about a single server 10, memory 20, and terminal device 30, but it should be understood by those skilled in the art that the illustrated server 10, memory 20, and terminal device 30 are intended to represent the operations of the server 10, memory 20, and terminal device 30 related to the technical aspects of this application. And is not meant to imply a limitation on the number, type, or location of the servers 10, the memory 20, the terminal devices 30, and so forth. It should be noted that the underlying concepts of the example embodiments of the present application may not be altered if additional modules are added or removed from the illustrated environments. In addition, although fig. 1 shows a bidirectional arrow from the memory 20 to the server 10 for convenience of explanation, it will be understood by those skilled in the art that the above-described data transmission and reception also need to be implemented via a network.

It should be noted that the storage in the embodiment of the present application may be, for example, a cache system, or may also be a hard disk storage, a memory storage, or the like. In addition, the monitoring method provided by the application is not only suitable for the application scene shown in fig. 1, but also suitable for any device with task monitoring requirements.

As shown in fig. 2, an overall flow diagram of a monitoring method provided in the embodiment of the present application is shown, where:

in step 201: periodically acquiring the field value of the target field from the data table; the data table comprises a plurality of fields and a plurality of field values of each field, and each field is used for representing attribute information of each task; the target field comprises a task identity identification field and a task state field;

in step 202: determining the task state of each task based on the task identity identification field and the field value of the task state field;

in step 203: respectively determining the execution duration of each task in execution aiming at the task in execution with the task state being a non-final state;

in step 204: and if the task in execution is determined to be an abnormal task according to the execution duration of each task in execution, alarming aiming at the abnormal task.

In the method and the device, the data table is set, so that the multiple tasks are monitored simultaneously, whether the tasks are abnormal or not is determined according to the states and the execution duration of the tasks, the alarm is given when the tasks are abnormal, and the timeliness of task monitoring is improved.

To facilitate further understanding of a monitoring method provided in the embodiment of the present application, the following steps in fig. 2 are described in detail according to the execution sequence of the embodiment of the present application:

first, a data table provided in the embodiment of the present application is explained, and as shown in table 1, a field name, a length of each field, and a role of each field are expressed as follows:

name of field	Length of field	Field description
			Task identity	21	Uniquely characterizing the identity of each task
Task state	10	Characterizing states of a task
			The time of trigger of this inquiry operation	10	Characterization bookTime to trigger of secondary query operation
Starting time	10	Characterizing first time trigger time of query operation
			Number of queries	10	Characterizing query times for each task
Node point	10	Characterizing a current processing node of a task

TABLE 1

In the embodiment of the present application, in order to determine the task state of each task in time and further determine an abnormal task according to the task state and the execution duration, a field value of a target field needs to be periodically obtained from a data table, which is shown in table 2 and is provided by the embodiment of the present application, where the data table includes:

TABLE 2

Since a plurality of tasks share one data table, in the present application, determining the state of each task based on the field values of the task identity field and the task state field may be implemented as: for each task, determining the sequence of field values corresponding to the identification fields of the tasks in the field values corresponding to the identification fields; and taking the state represented by the sequential field values in the field values corresponding to the task state field as the state of the task.

For example: as shown in table 2, the task identity includes six tasks, where the sequence of the field values of the identity corresponding to the task 3 in the field values corresponding to the identity field is the third, and therefore, the state represented by the third field value "0" in the field values corresponding to the task state field is taken as the state corresponding to the task 3.

In the present application, 1 is used to represent the state of the task as the final state, and 0 is used to represent the state of the task as the non-final state. It should be understood that the present application is only one example, and other identifiers may be used to characterize different states of a task in a specific implementation, and the present application is not limited thereto.

In some possible embodiments, determining the execution duration of each in-execution task may be implemented as the steps shown in FIG. 3, where:

in step 301: determining the triggering time of the query operation according to the field value of the triggering time field of the query operation of the time corresponding to the task;

in step 302: determining the starting time of the task according to the field value of the starting time field corresponding to the task;

in step 303: and taking the difference value of the trigger time and the starting time as the execution time length of the task.

For example: as shown in table 3, the table includes:

TABLE 3

The data table includes a time field for triggering the query operation this time and a start time field corresponding to each task, and for task 3, the start time of task 3 is determined to be 00, and the time field for triggering the query operation this time is 03. If the total execution time set for task 3 is 4 hours, it can be determined that task 3 is a normal task.

In the embodiment of the present application, a user may create a task at any time, so that the start times corresponding to each task are different, and the user may also create multiple tasks at the same time to add into the data table, which is not limited in the present application.

In the present application, in order to further improve the timeliness of task monitoring, a query number field is set, and in the present application, after determining the task status of the task, the steps shown in fig. 4 may be implemented:

in step 401: aiming at an executing task with a task state being a non-final state, determining a query frequency state value corresponding to the executing task and determining the query frequency corresponding to the executing task;

in step 402: and if the query times corresponding to the task in execution exceed the preset times, determining that the task in execution is an abnormal task, and giving an alarm.

For example: as shown in table 4, the table includes:

TABLE 4

The data table comprises a query frequency field, the set query frequency is 6 times for the task 1, and if the current query frequency of the task 1 is determined to be 7 times, the task 1 is determined to be an abnormal task, and an alarm is given; and for the task 3, determining the query times set by the task 3 to be 6 times, and determining the current query times of the task 3 to be 7 times, determining the task 3 to be an abnormal task, and giving an alarm.

In the present application, in order to enable a technician to quickly know a node where an exception occurs in a task, a node field is set, and therefore after the task is determined to be an exception task, steps shown in fig. 5 may be implemented:

in step 501: determining a field value of a node field corresponding to a task in execution;

in step 502: determining a node of which the task becomes an abnormal task in execution according to the field value of the node field;

in step 503: and generating and displaying an abnormal prompt according to the node, wherein the abnormal prompt is used for informing the node of the task becoming an abnormal task in execution.

As shown in table 5, these include:

name of field	Field value
		Identity label	Task 1, task 2, task 3, task 4, task 5, task 6
Task state	0,1,0,1,0,1
		The time of the inquiry operation	03：45
Starting time	00：15,00:45,00:25,01:00,02:00,03:10
		Number of queries	7,6,7,5,3,1
Node point	Node 5, node 4, node 1, node 3, node 2, node 1

TABLE 5

The data table comprises node fields, aiming at the task 3, the query frequency set by the task 3 is determined to be 6 times, the current query frequency of the task 3 is determined to be 7 times, the task 3 is determined to be an abnormal task, the node corresponding to the task 3 is determined to be the node 1, the alarm indication is carried out, the abnormal prompt is generated at the same time, and the alarm indication and the abnormal prompt are displayed to a user at the same time, so that the user can process the abnormal task.

As shown in fig. 6, based on the same inventive concept, there is provided a task monitoring apparatus 600, the apparatus including:

a field value obtaining module 6001, configured to periodically obtain a field value of a target field from a data table; the data table comprises a plurality of fields and a plurality of field values of each field, and each field is used for representing attribute information of each task; the target field comprises a task identity identification field and a task state field;

a task state determining module 6002, configured to determine a task state of each task based on the task identity field and a field value of the task state field;

an execution duration determining module 6003, configured to determine, for the executing task whose task state is a non-final state, an execution duration of each executing task;

the alarming module 6004 is configured to, if it is determined that the executing task is an abnormal task according to the execution duration of each executing task, alarm for the abnormal task.

In some possible embodiments, the task status determining module 6002, when performing determining the status of each task based on the task identity field and the field value of the task status field, is configured to:

In some possible embodiments, the target field includes: the query operation at this time includes a trigger time field and a start time field, and the execution duration determining module 6003 is configured to determine the execution duration of each task in execution, respectively, and is configured to:

In some possible embodiments, the target field includes: the number of queries field, the task status determining module 6002, after determining the task status of each task based on the task identity field and the field value of the task status field, is further configured to:

aiming at an executing task with a task state being a non-final state, determining a query frequency state value corresponding to the executing task, and determining the query frequency corresponding to the executing task;

In some possible embodiments, the target field includes: a node field, after the alarm module 6004 performs determining that the executing task is an exception task, further configured to:

and generating and displaying an exception prompt according to the node, wherein the exception prompt is used for informing the node of the task becoming an exception task in the execution process.

Having described the monitoring method and apparatus of the exemplary embodiments of the present application, an electronic device according to another exemplary embodiment of the present application is next described.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method or program product. Accordingly, various aspects of the present application may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

In some possible implementations, an electronic device according to the present application may include at least one processor, and at least one memory. Wherein the memory stores program code which, when executed by the processor, causes the processor to perform the steps of the monitoring method according to various exemplary embodiments of the present application described above in the present specification.

The electronic device 130 according to this embodiment of the present application is described below with reference to fig. 7. The electronic device 130 shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 7, the electronic device 130 is represented in the form of a general electronic device. The components of the electronic device 130 may include, but are not limited to: the at least one processor 131, the at least one memory 132, and a bus 133 that couples various system components including the memory 132 and the processor 131.

Bus 133 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, or a local bus using any of a variety of bus architectures.

The memory 132 may include readable media in the form of volatile memory, such as Random Access Memory (RAM) 1321 and/or cache memory 1322, and may further include Read Only Memory (ROM) 1323.

Memory 132 may also include a program/utility 1325 having a set (at least one) of program modules 1324, such program modules 1324 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

The electronic device 130 may also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), with one or more devices that enable a user to interact with the electronic device 130, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 130 to communicate with one or more other electronic devices. Such communication may occur via input/output (I/O) interfaces 135. Also, the electronic device 130 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 136. As shown, network adapter 136 communicates with other modules for electronic device 130 over bus 133. It should be understood that although not shown in FIG. 7, other hardware and/or software modules may be used in conjunction with electronic device 130, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

In some possible embodiments, aspects of a monitoring method provided by the present application may also be implemented in the form of a program product, which includes program code for causing a computer device to perform the steps of a monitoring method according to various exemplary embodiments of the present application described above in this specification, when the program product is run on the computer device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The program product for task monitoring of embodiments of the present application may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on an electronic device. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the consumer electronic device, partly on the consumer electronic device, as a stand-alone software package, partly on the consumer electronic device and partly on a remote electronic device, or entirely on the remote electronic device or server. In the case of remote electronic devices, the remote electronic devices may be connected to the consumer electronic device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external electronic device (e.g., through the internet using an internet service provider).

It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, the features and functions of two or more units described above may be embodied in one unit, according to embodiments of the application. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.

Further, while the operations of the methods of the present application are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method of monitoring, the method comprising:

and if the task in execution is determined to be an abnormal task according to the execution time length of each task in execution, alarming aiming at the abnormal task.

2. The method of claim 1, wherein determining the status of each task based on the values of the task identity field and the task status field comprises:

3. The method of claim 1, wherein the target field comprises: the querying operation triggering time field and the starting time field respectively determine the execution duration of each executed task, and the method comprises the following steps:

aiming at each task in execution, determining the triggering time of the query operation according to the field value of the triggering time field of the query operation of this time corresponding to the task in execution;

and taking the difference value of the trigger time and the starting time as the execution duration of the task in execution.

4. The method of claim 1, wherein the target field comprises: a query number field, wherein after the task state of each task is determined based on the field values of the task identity field and the task state field, the method further comprises:

5. The method of any of claims 1-4, wherein the target field comprises: a node field, wherein after the task in execution is determined to be an abnormal task, the method further comprises:

determining a field value of a node field corresponding to the task in execution;

6. A task monitoring device, the device comprising:

the execution duration determining module is used for respectively determining the execution duration of each task in execution aiming at the task in execution with the task state being a non-final state;

7. The apparatus of claim 6, wherein the task state determination module, when performing determining the state of each task based on the task identity field and field values of the task state field, is configured to:

8. The apparatus of claim 6, wherein the target field comprises: the query operation comprises a trigger time field and a start time field, and the execution duration determining module is configured to determine the execution duration of each task in execution respectively:

9. The apparatus of claim 6, wherein the target field comprises: the task state determination module is configured to determine a task state of each task based on the task identity field and a field value of the task state field, and is further configured to:

10. The apparatus of any of claims 6-9, wherein the target field comprises: the alarm module is configured to, after determining that the executing task is an abnormal task:

11. An electronic device, comprising:

a memory for storing program instructions;

a processor for calling program instructions stored in said memory and for executing the steps comprised in the method of any one of claims 1 to 5 in accordance with the obtained program instructions.

12. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a computer, cause the computer to perform the method according to any one of claims 1-5.

13. A computer program product, the computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the method according to any of the preceding claims 1-5.