CN115629903A - Task delay monitoring method, device, equipment and storage medium - Google Patents
Task delay monitoring method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115629903A CN115629903A CN202211327884.2A CN202211327884A CN115629903A CN 115629903 A CN115629903 A CN 115629903A CN 202211327884 A CN202211327884 A CN 202211327884A CN 115629903 A CN115629903 A CN 115629903A
- Authority
- CN
- China
- Prior art keywords
- task
- execution
- current
- delay
- upstream
- 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.)
- Pending
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 309
- 238000000034 method Methods 0.000 title claims abstract description 72
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 234
- 230000003111 delayed effect Effects 0.000 claims description 73
- 238000004590 computer program Methods 0.000 claims description 16
- 238000012806 monitoring device Methods 0.000 abstract description 7
- 230000008569 process Effects 0.000 description 12
- 230000001419 dependent effect Effects 0.000 description 11
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 3
- 238000013024 troubleshooting Methods 0.000 description 3
- 238000012935 Averaging Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000007619 statistical method Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
- G06F11/0754—Error or fault detection not based on redundancy by exceeding limits
- G06F11/0757—Error or fault detection not based on redundancy by exceeding limits by exceeding a time limit, i.e. time-out, e.g. watchdogs
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses a task delay monitoring method, a task delay monitoring device, a task delay monitoring equipment and a task delay monitoring storage medium. The method determines each upstream execution task corresponding to the current monitoring task under the condition of determining the execution start time delay of the current monitoring task, further determines the upstream delay task causing the delay of the current monitoring task from each upstream execution task, further determines the current delay deviation of each upstream execution task according to the current execution information and the average execution information of each upstream execution task, determines the upstream delay task causing the delay of the current monitoring task according to each current delay deviation, realizes the determination of the upstream task causing the delay of the current monitoring task, further realizes the determination of the task delay reason, can immediately determine the task delay reason during the delay execution of the task, solves the technical problem that the task delay reason can not be determined in real time, does not need to manually search the delay reason subsequently, and improves the determination efficiency of the task delay reason.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a task delay monitoring method, a task delay monitoring device, task delay monitoring equipment and a storage medium.
Background
In the existing big data scheduling tasks, the scheduling tasks are also monitored in multiple aspects, multiple dimensions and multiple indexes, one of the monitoring is task execution delay monitoring, namely whether the scheduling tasks are executed at preset time or not and whether the scheduling tasks are executed at the preset time or not are monitored, and after the task execution delay, a task responsible person is notified in a short message or mail mode.
In the process of implementing the present invention, the inventor finds that at least the following technical problems exist in the prior art: the reason for the task delay cannot be determined in real time when the task is delayed, and the real-time performance for determining the reason for the task delay is poor.
Disclosure of Invention
The embodiment of the invention provides a task delay monitoring method, a task delay monitoring device, a task delay monitoring equipment and a task delay monitoring storage medium, and aims to solve the technical problem that the reason of task delay cannot be determined in real time.
According to an aspect of the embodiments of the present invention, a task delay monitoring method is provided, including:
under the condition that the execution starting time delay of the current monitoring task is determined, determining each upstream execution task corresponding to the current monitoring task;
determining current execution information and average execution information respectively corresponding to each upstream execution task, wherein the current execution information comprises current start time and current end time, and the average execution information comprises average start time and average end time;
and determining current delay deviations corresponding to the upstream execution tasks according to the current execution information and the average execution information, and determining the upstream delay task causing the delay of the current monitoring task from the upstream execution tasks based on the current delay deviations corresponding to the upstream execution tasks.
According to another aspect of the embodiments of the present invention, there is provided a task delay monitoring apparatus, including:
the upstream task determining module is used for determining each upstream execution task corresponding to the current monitoring task under the condition of determining the execution starting time delay of the current monitoring task;
an execution information determining module, configured to determine current execution information and average execution information corresponding to each upstream execution task, where the current execution information includes a current start time and a current end time, and the average execution information includes an average start time and an average end time;
and the delay task determining module is used for determining current delay deviation corresponding to each upstream execution task according to each current execution information and each average execution information, and determining an upstream delay task causing the delay of the current monitoring task from each upstream execution task based on the current delay deviation corresponding to each upstream execution task.
According to another aspect of the embodiments of the present invention, there is provided an electronic apparatus, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the method for task delay monitoring according to any of the embodiments of the invention.
According to another aspect of the embodiments of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement the task delay monitoring method according to any one of the embodiments of the present invention when the computer instructions are executed.
According to the technical scheme of the embodiment of the invention, under the condition of determining the execution starting time delay of the current monitoring task, the upstream execution tasks corresponding to the current monitoring task are determined, so that the upstream delay task causing the delay of the current monitoring task is further determined from the upstream execution tasks, the current delay deviation of each upstream execution task is further determined according to the current execution information and the average execution information of each upstream execution task, the upstream delay task causing the delay of the current monitoring task is determined according to each current delay deviation, the determination of the upstream task causing the delay of the current monitoring task is realized, and the determination of the task delay reason is further realized.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a task delay monitoring method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of another task delay monitoring method according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of another task delay monitoring method according to an embodiment of the present invention;
fig. 4A is a schematic structural diagram of a task delay monitoring apparatus according to an embodiment of the present invention;
fig. 4B is a schematic structural diagram of another task delay monitoring apparatus according to an embodiment of the present invention
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Fig. 1 is a schematic flowchart of a task delay monitoring method according to an embodiment of the present invention, where the embodiment is applicable to monitoring whether each task is executed in a delayed manner and determining a reason for delayed execution of the task, and the method may be executed by a task delay monitoring apparatus, where the task delay monitoring apparatus may be implemented in a hardware and/or software form, and the task delay monitoring apparatus may be configured in an electronic device such as a computer, a smart phone, or a smart tablet. As shown in fig. 1, the method includes:
and S110, under the condition that the execution starting time delay of the current monitoring task is determined, determining each upstream execution task corresponding to the current monitoring task.
The current monitoring task may be a task that needs to monitor whether there is a delay currently. Specifically, the current monitoring task may be a task that generates service data required by other service systems after being executed.
For example, the information such as the identification information of all tasks, the priority of the tasks, and whether the tasks are flag bits of the monitoring tasks may be stored in the task information table, and the monitoring tasks may be determined according to whether each task in the task information table is a flag bit of the monitoring task. Or, the preset start time corresponding to the monitoring task may be stored in the task information table, a task with the preset start time in all the tasks in the task information table is detected, and the task with the preset start time is determined as the monitoring task.
Specifically, for the current monitoring task, it needs to be determined whether the execution start time of the current monitoring task is delayed, that is, whether the execution of the current monitoring task is delayed. For example, when the preset start time corresponding to the current monitoring task is reached, whether the current monitoring task starts to be executed is detected, if yes, it is determined that the execution start time of the current monitoring task is not delayed, and if not, it is determined that the execution start time of the current monitoring task is delayed. Or, when it is detected that the current monitoring task starts to be executed, the actual start time corresponding to the current monitoring task is acquired, and whether the execution start time of the current monitoring task is delayed or not is judged based on the actual start time and the preset start time.
In a specific embodiment, a plurality of timing tasks may be set, so that delayed monitoring of each monitoring task is initiated by the timing tasks. As such, the method provided by this embodiment further includes: determining preset starting time corresponding to the current monitoring task according to a task information table, wherein the task information table comprises the preset starting time corresponding to each monitoring task; starting a preset timing monitoring task when the preset starting time is reached, detecting whether the current monitoring task starts to be executed or not through the preset timing monitoring task, and if not, determining that the execution starting time of the current monitoring task is delayed.
The preset starting time may be a preset time at which the current monitoring task starts to be executed, that is, a set starting time. Specifically, the preset start time may be set manually; or may be determined based on the historical execution record of the current monitoring task, i.e., based on the historical start time of the monitoring task within a historical period of time (e.g., one month).
That is, the preset start time corresponding to each monitoring task may be determined according to the task information table, and each preset start time is set to each start time of the preset timing monitoring task, so as to determine whether to start execution of each monitoring task by starting the preset timing monitoring task at each preset start time, and further determine whether to delay the execution start time of each monitoring task.
In the above embodiment, the preset timing monitoring task is started at the preset starting time, so that whether the current monitoring task starts to be executed or not is detected by the preset timing monitoring task, the judgment on whether the current monitoring task is delayed to be executed or not is automatically initiated at the set starting time of the current monitoring task, the delay reason is immediately judged when the initial time of the delayed execution of the task is determined, a user can conveniently solve the delay problem in time, and the influence of the task delay on other service systems is reduced.
Further, when it is determined that the execution start time of the current monitoring task is delayed, it is necessary to determine each upstream execution task corresponding to the current monitoring task. The upstream execution task may be a task that has a task dependency relationship with the current monitoring task and is executed before the current monitoring task starts to be executed.
Specifically, the current task and the dependent task corresponding to the current task may be stored in the task dependent information table in advance for each task in an associated manner; and searching a dependent task corresponding to the current monitoring task through the task dependent information table, and determining the upstream tasks in all the dependent tasks as each upstream execution task corresponding to the current monitoring task.
Illustratively, the task dependency information table may store the dependent tasks corresponding to the tasks in the following manner: and task C: task A, task E, task F, task G, task K, and task D: task B, task E, task H and task I; the task-dependent information table may store identification information of each task.
It should be noted that, in the present embodiment, when determining that the execution start time of the current monitoring task is delayed, the reason for determining each upstream execution task corresponding to the current monitoring task is that: if the execution start time of the current monitoring task is delayed, it indicates that the delayed execution of the current monitoring task is caused by the delay of the upstream task, so that each upstream execution task of the current monitoring task can be determined, and the upstream delay task causing the delayed execution of the current monitoring task is determined from each upstream execution task.
And S120, determining current execution information and average execution information respectively corresponding to each upstream execution task, wherein the current execution information comprises current start time and current end time, and the average execution information comprises average start time and average end time.
The current execution information may be information of a previous execution of the upstream execution task, and includes a current start time and a current end time, that is, a time when the execution is actually started and a time when the execution is actually ended. The average execution information may be average information of the upstream execution task executed within the historical period of time, including an average start time and an average end time.
In this embodiment, the execution information of each task may be recorded in the task execution record table, and the current execution information of each upstream execution task may be read from the task execution record table. Furthermore, historical execution information of each upstream execution task can be read from the task execution record table, and average execution information can be determined according to the historical execution information.
For example, the determining of the current execution information and the average execution information respectively corresponding to each upstream execution task may be: acquiring historical execution information and current execution information which respectively correspond to each upstream execution task based on a task execution record table, wherein the task execution record table comprises the historical execution information and the current execution information which correspond to each task, and the historical execution information comprises historical start time and historical end time which correspond to each task; and respectively determining average execution information corresponding to the upstream execution tasks based on the historical execution information corresponding to the upstream execution tasks.
The historical execution information may be execution information of tasks in a historical time period, such as execution information within a month and a week. The historical execution information of each task comprises historical start time and historical end time of the task, so that the average start time can be determined according to the historical start time, and the average end time can be determined according to the historical end time.
By the method, the average execution information of each upstream execution task and the current execution information are accurately acquired; and the average execution information is determined through the historical execution information, so that the reasonable determination of the starting time and the ending time of the task is realized, the starting time and the ending time of the task do not need to be specified manually, and the condition that the determination is wrong due to the delay caused by unreasonable manual time specification is avoided.
Of course, in addition to the manner of determining the current execution information and the average execution information according to the task execution record table, the average execution information of each task may be calculated in advance, the average execution information of each task is stored in the task information table, and the average execution information of each upstream execution task is queried from the task information table.
Specifically, the process of determining the average execution information according to the historical execution information may adopt an averaging method, a clustering method or a K-nearest neighbor method.
Illustratively, the determining the average execution information corresponding to each upstream execution task respectively based on the historical execution information corresponding to each upstream execution task includes: aiming at each upstream execution task, calculating historical average starting time according to each historical starting time corresponding to the current upstream execution task, calculating historical average ending time according to each historical ending time corresponding to the current upstream execution task, and determining the historical average starting time and the historical average ending time as average execution information corresponding to the current upstream execution task; or clustering the historical start time corresponding to the current upstream execution task aiming at each upstream execution task, determining the average start time corresponding to the current upstream execution task based on the core point in the clustering result, clustering the historical end time corresponding to the current upstream execution task, and determining the average end time corresponding to the current upstream execution task based on the core point in the clustering result.
That is, the historical average start time may be calculated from each historical start time, and the historical average end time may be calculated from the historical end time as the average execution information. Alternatively, for each upstream execution task, the respective historical start times of the upstream execution tasks may be clustered, the clustered core point may be determined as the average start time, the historical end times may be clustered, and the clustered core point may be determined as the average end time.
By means of the statistical analysis methods such as averaging or clustering, accurate determination of the average execution time of each upstream execution task is achieved, the reasonability of the average start time and the average end time of each upstream execution task is improved, and the situation that determination of delay reasons is wrong due to unreasonable manual appointed time is avoided. Moreover, even if the upstream execution task is not configured with delay monitoring, whether the upstream execution task is delayed or not can be counted, so that the delayed upstream execution task can be determined when the current monitoring task is delayed, the delay reason of the current monitoring task can be quickly positioned, and the problem troubleshooting efficiency is improved.
And S130, determining current delay deviations corresponding to the upstream execution tasks respectively according to the current execution information and the average execution information, and determining the upstream delay task causing the delay of the current monitoring task from the upstream execution tasks based on the current delay deviations corresponding to the upstream execution tasks respectively.
Wherein, the current delay deviation may be a delay time length of last execution of the upstream execution task. Specifically, the current execution duration may be calculated according to the current start time and the current end time in the current execution information, the average execution duration may be calculated according to the average start time and the average end time of the average execution information, and the current delay skew of the upstream execution task may be calculated according to the current execution duration and the average execution duration.
Specifically, after the current delay deviation of each upstream execution task is calculated, the upstream execution task causing the delayed execution of the current monitoring task, that is, the upstream delay task, may be screened out from each upstream execution task according to each current delay deviation, so as to determine the delay reason of the current monitoring task.
For example, the upstream execution task with the largest current delay deviation may be determined as the upstream delay task. Or, the upstream execution tasks may be sorted in order from large to small according to the current delay deviation corresponding to each upstream execution task, and at least one upstream delay task may be determined based on the sorting result.
It should be noted that, this embodiment may not only monitor whether the execution start time of the task is delayed and determine the upstream task causing the delayed execution of the task, but also monitor whether the execution end time of the task is delayed. For example, the method provided by this embodiment may further include: and under the condition that the execution starting time of the current monitoring task is not delayed and the execution ending time of the current monitoring task is delayed, determining the current monitoring task as a monitoring delay task.
That is, if the execution start time of the current monitoring task is not delayed and the execution end time of the current monitoring task is delayed, it indicates that each upstream execution task corresponding to the current monitoring task is not delayed and the current monitoring task has a delay, and at this time, the current monitoring task may be determined as a monitoring delayed task.
Specifically, the upstream task causing the delayed execution of the current monitoring task can be determined when the initial time of the delayed execution of the current monitoring task is determined, and after the delayed execution of the current monitoring task is determined, whether the delayed completion of the current monitoring task is determined, so that the delayed monitoring of the starting execution and the ending execution of the task is realized.
In the above process, it may be determined whether the execution end time of the current monitoring task is delayed by:
determining a preset ending time corresponding to the current monitoring task according to a task information table, wherein the task information table comprises the preset ending time corresponding to each monitoring task; and starting the preset timing monitoring task when the preset ending time is reached, detecting whether the current monitoring task is finished executing or not through the preset timing monitoring task, and if not, determining that the execution ending time of the current monitoring task is delayed.
The preset end time may be a preset end time for the current monitoring task to be executed. The preset end time may be set manually or determined according to a historical execution record of the current monitoring task, that is, according to the historical end time of the monitoring task in a historical time period (e.g., one month or three months).
That is, the preset end time corresponding to each monitoring task may be determined according to the task information table, and each preset end time is set to each start time of the preset timing monitoring task, so as to determine whether each monitoring task ends execution or not by starting the preset timing monitoring task at each preset end time, and further determine whether the execution end time of each monitoring task is delayed or not.
By the method, whether the current monitoring task is delayed to be executed or not is judged at the set finishing time of the current monitoring task, and the delay reason is immediately judged at the initial time of determining the delayed finishing of the task, so that a user can conveniently and timely solve the delay problem.
According to the technical scheme of the embodiment, under the condition that the execution starting time delay of the current monitoring task is determined, the upstream delay tasks corresponding to the current monitoring task are determined, so that the upstream delay tasks causing the delay of the current monitoring task are further determined from the upstream execution tasks, the current delay deviation of the upstream execution tasks is further determined according to the current execution information and the average execution information of the upstream execution tasks, the upstream delay tasks causing the delay of the current monitoring task are determined according to the current delay deviations, the determination of the upstream tasks causing the delay of the current monitoring task is realized, and the determination of the task delay reasons is further realized.
Fig. 2 is a schematic flow chart of another task delay monitoring method according to an embodiment of the present invention, and this embodiment provides a supplementary description on a process of determining an upstream delayed task according to a current delay deviation of each upstream executed task based on the above embodiment. As shown in fig. 2, the method includes:
s210, under the condition that the execution starting time delay of the current monitoring task is determined, each upstream execution task corresponding to the current monitoring task is determined.
S220, determining current execution information and average execution information corresponding to each upstream execution task, wherein the current execution information comprises current starting time and current ending time, and the average execution information comprises average starting time and average ending time.
And S230, determining the current delay deviation corresponding to each upstream execution task according to each current execution information and each average execution information.
S240, determining at least one delay task to be screened from each upstream execution task based on a preset deviation threshold and the current delay deviation corresponding to each upstream execution task, and determining at least one upstream delay task from each delay task to be screened according to the current delay deviation corresponding to each delay task to be screened.
Wherein the preset deviation threshold value may be a preset deviation allowable maximum value. Specifically, the current delay deviation corresponding to each upstream execution task may be compared with a preset deviation threshold, and if the current delay deviation corresponding to the upstream execution task is greater than the preset deviation threshold, the upstream execution task may be determined as the delay task to be screened.
Further, at least one upstream delay task is determined according to the current delay deviation corresponding to each delay task to be screened. For example, all delay tasks to be screened may be taken as upstream delay tasks; or, the delay tasks to be screened may be sorted in the order from large to correct according to the magnitude of the current delay deviation corresponding to each delay task to be screened, and at least one upstream delay task may be determined based on the result of the sorting. For example, the first n delay tasks to be screened in the sequencing result are determined as the upstream delay tasks.
In an embodiment, if the number of the determined upstream delay tasks is multiple, the upstream delay tasks may be sorted according to the current delay deviation of each upstream delay task; the upstream delay tasks can also be sequenced according to the execution sequence of the upstream delay tasks, namely the dependency relationship.
For example, for each upstream delay task, the dependent task corresponding to the current upstream delay task may be determined according to the task dependency information table, whether other upstream delay tasks exist is queried in the dependent task, if so, the other upstream delay tasks may be determined as the associated delay tasks of the current upstream delay task, and the current upstream delay task and the associated delay tasks are sorted according to the dependency relationship.
In this embodiment, after determining the upstream delay task causing the delay of the current monitoring task, alarm information may also be generated and sent to the terminal device of the user.
Illustratively, the method provided by this embodiment further includes: acquiring a first task identifier of a current monitoring task and a second task identifier of each upstream delay task according to a task information table, and generating alarm information based on the first task identifier and each second task identifier; and acquiring a relevant user identifier corresponding to the current monitoring task based on a task information table, and sending the alarm information to a user terminal corresponding to the relevant user identifier, wherein the task information table comprises the task identifiers of all the tasks and the relevant user identifiers corresponding to all the monitoring tasks.
The first task identifier may be a task identifier corresponding to a current monitoring task, and the second task identifier may be a task identifier corresponding to an upstream delay task. The associated user identifier corresponding to the current monitoring task may be a user identifier responsible for processing the current monitoring task.
Specifically, the associated user identifier corresponding to the current monitoring task may be queried from the task information table, the first task identifier of the current monitoring task and the second task identifiers of the upstream delay tasks may be queried from the task information table, and then the alarm information generated according to the first task identifier and the second task identifiers may be sent to the user terminal corresponding to the associated user identifier. The alarm information can be sent in the modes of mail, short message, telephone, weChat or application program prompt message and the like.
By the method, the alarm of the delayed execution monitoring task is realized, the delayed execution monitoring task is quickly positioned, the upstream delay task is sent to the user together, the user does not need to manually find the task delay reason, and the efficiency of troubleshooting the task delay problem is improved. And the monitoring task delayed to be executed and the reason for delayed execution of the task can be immediately sent when the initial time of delayed execution of the task is determined, so that the user can conveniently process the task in time, and the practicability of delayed monitoring alarm is improved.
In this embodiment, in addition to sending the task identifier including the task of executing the delayed task and the task identifier of the upstream delayed task causing the task delay, the predicted start time and the predicted end time of the current monitoring task may be sent.
Illustratively, generating alarm information based on the first task identifier and each second task identifier includes: determining the predicted starting time and the predicted ending time of the current monitoring task based on the current delay deviation corresponding to each upstream delay task; and generating alarm information according to the first task identifier, the second task identifiers, the predicted starting time and the predicted ending time.
Specifically, the predicted start time of the current monitoring task may be calculated according to a preset start time of the current monitoring task and a current delay deviation corresponding to each upstream delay task. If, the preset start time is 8:00, the current delay deviations for each upstream delay task are 5 minutes, 20 minutes and 15 minutes, respectively, the expected start time is 8.
The estimated completion time of the current monitoring task can be calculated according to the preset completion time of the current monitoring task and the current delay deviation corresponding to each upstream delay task; or determining a preset execution time length according to the preset starting time and the preset completion time of the current monitoring task, and determining a predicted ending time based on the predicted starting time and the preset execution time length.
Further, after the predicted start time and the predicted end time are determined, alarm information carrying the first task identifier, each second task identifier, the predicted start time and the predicted end time is generated and sent to the user terminal corresponding to the associated user identifier. Of course, the current delay deviation corresponding to each upstream delay task may also be sent to the user terminal corresponding to the associated user identifier.
The method and the device calculate the predicted starting time and the predicted ending time of the current monitoring task through the current delay deviation corresponding to each upstream delay task respectively, and generate alarm information containing the predicted starting time and the predicted ending time of the current monitoring task, so that a user is timely informed of which upstream tasks are delayed when the current monitoring task is delayed, how long the current monitoring task is delayed, the current monitoring task can be predicted to start to be executed at what time, and can be executed at what time, and the practicability of delay monitoring alarm is further improved.
According to the technical scheme of the embodiment, at least one delay task to be screened is determined in each upstream execution task through the preset deviation threshold and the current delay deviation of each upstream execution task, so that the delayed upstream execution task is selected from the upstream execution tasks preliminarily, and at least one upstream delay task is determined according to the current delay deviation of the delay task to be screened, so that the upstream delay task causing the delay of the current monitoring task is determined.
Fig. 3 is a schematic flow chart of another task delay monitoring method according to an embodiment of the present invention, where this embodiment provides supplementary description on a situation that an execution end time of a current monitoring task is delayed after an upstream delay task causing a delay of the current monitoring task is determined from among upstream execution tasks based on the foregoing embodiment. As shown in fig. 3, the method includes:
and S310, under the condition that the execution starting time delay of the current monitoring task is determined, determining each upstream execution task corresponding to the current monitoring task.
And S320, determining current execution information and average execution information respectively corresponding to each upstream execution task, wherein the current execution information comprises current starting time and current ending time, and the average execution information comprises average starting time and average ending time.
S330, determining current delay deviations corresponding to the upstream execution tasks according to the current execution information and the average execution information, and determining the upstream delay tasks causing the delay of the current monitoring task from the upstream execution tasks based on the current delay deviations corresponding to the upstream execution tasks.
And S340, under the condition that the execution ending time delay of the current monitoring task is determined, determining the current execution information corresponding to the current monitoring task.
Specifically, if the execution start time of the current monitoring task is delayed and the execution end time is also delayed, it may be further determined whether there is a delay in the execution process of the current monitoring task. Therefore, the current execution information corresponding to the current monitoring task can be acquired, wherein the current execution information includes the current start time and the current end time.
And S350, determining the actual execution time length corresponding to the current monitoring task based on the current execution information corresponding to the current monitoring task.
Specifically, after the current start time and the current end time corresponding to the current monitoring task are obtained, the actual execution duration may be determined according to the current start time and the current end time.
And S360, acquiring a preset execution time corresponding to the current monitoring task, and determining the current monitoring task as a monitoring delay task if the difference value between the preset execution time and the actual execution time exceeds a preset threshold value.
The preset execution duration can be obtained from the task information table, that is, the preset execution duration corresponding to each monitoring task is stored in the task information table. Alternatively, the preset starting time and the preset ending time may be obtained from the task information table, and the preset execution time may be calculated based on the preset starting time and the preset ending time.
Further, if the difference between the preset execution time length and the actual execution time length exceeds a preset threshold, it may be determined that there is a delay in the execution process of the current monitoring task, and the current monitoring task is determined as a monitoring delay task. The preset threshold may be a preset maximum error of the delay time.
For example, after the current monitoring task is determined as the monitoring delay task, alarm information may be generated based on a task identifier corresponding to the monitoring delay task, and the alarm information may be sent to the user terminal associated with the user identifier corresponding to the monitoring delay task.
According to the technical scheme of the embodiment, after the upstream delay task causing the delay of the current monitoring task is determined, if the delay of the execution ending time of the current monitoring task is determined, the actual execution time length corresponding to the current monitoring task is determined according to the current execution information corresponding to the current monitoring task, and then if the difference value between the actual execution time length and the preset execution time length exceeds the preset threshold value, the current monitoring task is determined as the monitoring delay task, so that the judgment on whether the execution process of the current monitoring task is delayed is realized, a user can timely process the monitoring delay task, and the delay reason of the downstream task can be judged, namely when the downstream task of the current monitoring task is delayed, the reason causing the delay of the downstream task can be directly determined according to the monitoring delay task.
Fig. 4A is a schematic structural diagram of a task delay monitoring apparatus according to an embodiment of the present invention. As shown in fig. 4A, the apparatus includes an upstream task determination module 410, an execution information determination module 420, and a delayed task determination module 430.
An upstream task determining module 410, configured to determine, in a case that it is determined that the execution start time of the current monitoring task is delayed, each upstream execution task corresponding to the current monitoring task;
an execution information determining module 420, configured to determine current execution information and average execution information respectively corresponding to each upstream execution task, where the current execution information includes a current start time and a current end time, and the average execution information includes an average start time and an average end time;
a delay task determining module 430, configured to determine, according to each piece of current execution information and each piece of average execution information, a current delay deviation corresponding to each upstream execution task, and determine, based on the current delay deviation corresponding to each upstream execution task, an upstream delay task causing the delay of the current monitoring task from each upstream execution task.
According to the technical scheme of the embodiment, under the condition that the execution starting time delay of the current monitoring task is determined, each upstream execution task corresponding to the current monitoring task is determined through the upstream task determination module, so that the upstream delay task causing the delay of the current monitoring task is further determined from the upstream execution tasks, the current execution information and the average execution information of each upstream execution task are determined through the execution information determination module, the current delay deviation of each upstream execution task is determined through the delay task determination module, the upstream delay task causing the delay of the current monitoring task is determined according to each current delay deviation, the determination of the upstream task causing the delay of the current monitoring task is realized, and the determination of the task delay reason is further realized.
On the basis of the foregoing embodiment, the upstream task determining module 410 is further configured to determine a preset starting time corresponding to the current monitoring task according to a task information table, where the task information table includes preset starting times corresponding to the monitoring tasks; and starting a preset timing monitoring task when the preset starting time is reached, detecting whether the current monitoring task starts to be executed or not through the preset timing monitoring task, and if not, determining that the execution starting time of the current monitoring task is delayed.
On the basis of the above embodiment, the execution information determination module 420 includes an information acquisition unit and an average information calculation unit; the information acquisition unit is used for acquiring historical execution information and current execution information which respectively correspond to each upstream execution task based on a task execution record table, wherein the task execution record table comprises the historical execution information and the current execution information which correspond to each task, and the historical execution information comprises historical start time and historical end time which correspond to each task; and the average information calculation unit is used for respectively determining the average execution information corresponding to each upstream execution task based on the historical execution information corresponding to each upstream execution task.
On the basis of the foregoing embodiment, the average information calculating unit is specifically configured to:
for each upstream execution task, calculating historical average starting time according to each historical starting time corresponding to the current upstream execution task, calculating historical average ending time according to each historical ending time corresponding to the current upstream execution task, and determining the historical average starting time and the historical average ending time as average execution information corresponding to the current upstream execution task; or clustering, for each upstream execution task, each historical start time corresponding to the current upstream execution task, determining an average start time corresponding to the current upstream execution task based on a core point in a clustering result, clustering each historical end time corresponding to the current upstream execution task, and determining an average end time corresponding to the current upstream execution task based on the core point in the clustering result.
On the basis of the foregoing embodiment, the delay task determining module 430 is specifically configured to:
determining at least one delay task to be screened from each upstream execution task based on a preset deviation threshold and the current delay deviation corresponding to each upstream execution task; and determining at least one upstream delay task from each delay task to be screened according to the current delay deviation corresponding to each delay task to be screened.
On the basis of the above embodiment, the apparatus provided in this embodiment further includes an alarm module; the alarm module is used for acquiring a first task identifier of the current monitoring task and a second task identifier of each upstream delay task according to a task information table, and generating alarm information based on the first task identifier and each second task identifier; and acquiring a relevant user identifier corresponding to the current monitoring task based on the task information table, and sending the alarm information to a user terminal corresponding to the relevant user identifier, wherein the task information table comprises task identifiers of all tasks and relevant user identifiers corresponding to all monitoring tasks.
On the basis of the above embodiment, the alarm module is further configured to determine a predicted start time and a predicted end time of the current monitoring task based on current delay deviations corresponding to the upstream delay tasks, respectively; and generating alarm information according to the first task identifier, each second task identifier, the predicted starting time and the predicted ending time.
On the basis of the foregoing embodiment, the apparatus provided in this embodiment further includes an ending delay determining module, where the ending delay determining module is configured to determine the current monitoring task as the monitoring delay task when it is determined that the execution start time of the current monitoring task is not delayed and the execution end time of the current monitoring task is delayed.
On the basis of the above embodiment, the ending delay determining module is further configured to determine a preset ending time corresponding to the current monitoring task according to a task information table, where the task information table includes the preset ending time corresponding to each monitoring task; and starting a preset timing monitoring task when the preset ending time is reached, detecting whether the current monitoring task is finished executing or not through the preset timing monitoring task, and if not, determining that the execution ending time of the current monitoring task is delayed.
On the basis of the foregoing embodiment, the delay task determining module 430 is further configured to determine current execution information corresponding to the current monitoring task when it is determined that the execution end time of the current monitoring task is delayed; determining actual execution duration corresponding to the current monitoring task based on current execution information corresponding to the current monitoring task; and acquiring a preset execution time corresponding to the current monitoring task, and determining the current monitoring task as a monitoring delay task if the difference value between the preset execution time and the actual execution time exceeds a preset threshold value.
In this embodiment, another task delay monitoring device is further provided, as shown in fig. 4B, and fig. 4B is a schematic structural diagram of another task delay monitoring device according to an embodiment of the present invention. The task delay monitoring device comprises a task module, a monitoring module and an alarm module.
Specifically, the task module is configured to store task information of each task in a task information table, where the task information includes task identifiers, associated user identifiers, task priorities, and the like, and the task information of the monitoring task further includes a preset start time and a preset end time. The task module is also used for storing each task and the dependent task corresponding to each task into a task dependent information table and storing the historical execution information of each task into a task execution record table.
The monitoring module can determine each monitoring task needing to be monitored and delayed from the task information table of the task module, acquire the preset starting time and the preset ending time of each monitoring task, and set the starting time of the preset timing monitoring task according to each preset starting time and each preset ending time so as to start the preset timing monitoring task when each preset starting time and each preset ending time are reached.
If the monitoring module detects that the execution time of the current monitoring task is delayed after the monitoring module starts the preset monitoring task, the upstream execution tasks corresponding to the current monitoring task can be read from the task dependency information table, and the current execution information and the historical execution information of the upstream execution tasks can be read from the task execution record table.
Further, the monitoring module calculates average execution information of the upstream execution tasks based on the historical execution information, determines current delay deviation of the upstream execution tasks according to the average execution information and the current execution information, stores the current delay deviation and the average execution information of the upstream execution tasks into a delay statistical information table, and determines the upstream delay tasks causing the delay of the current monitoring tasks according to the current delay deviation of the upstream execution tasks in the delay statistical information table.
Further, the monitoring module can call the alarm module, and sends alarm information by calling the alarm module, specifically, after the alarm module is called, the alarm module can query the associated user identifier corresponding to the current monitoring task from the task information table in the task module, and then sends the alarm information to the user terminal corresponding to the associated user identifier.
Through the task module, the monitoring module and the alarm module, whether the monitoring task is delayed to be executed or not is determined, and whether the delay of the monitoring task is caused by the delay of an upstream task or not is determined when the big data scheduling task is executed. And the average execution information is calculated by a statistical analysis method, and even if the upstream task is not configured with delay monitoring, whether the upstream task has delay can be counted, so that the delay condition of the upstream task can be clearly provided when the monitoring task is delayed, the reason of the delay of the monitoring task can be quickly positioned, and the efficiency of troubleshooting problems can be improved.
The task delay monitoring device provided by the embodiment of the invention can execute the task delay monitoring method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 5, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as the task delay monitoring method.
In some embodiments, the task delay monitoring method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the task latency monitoring method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the task delay monitoring method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Computer programs for implementing the task delay monitoring methods of embodiments of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
An embodiment of the present invention further provides a computer-readable storage medium, in which computer instructions are stored, and the computer instructions are used to enable a processor to execute a task delay monitoring method, where the method includes:
under the condition that the execution starting time delay of the current monitoring task is determined, determining each upstream execution task corresponding to the current monitoring task;
determining current execution information and average execution information respectively corresponding to each upstream execution task, wherein the current execution information comprises current starting time and current ending time, and the average execution information comprises average starting time and average ending time;
and determining current delay deviations corresponding to the upstream execution tasks according to the current execution information and the average execution information, and determining the upstream delay task causing the delay of the current monitoring task from the upstream execution tasks based on the current delay deviations corresponding to the upstream execution tasks.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the Internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (13)
1. A method for monitoring task delay, comprising:
under the condition that the execution starting time delay of the current monitoring task is determined, determining each upstream execution task corresponding to the current monitoring task;
determining current execution information and average execution information respectively corresponding to each upstream execution task, wherein the current execution information comprises current starting time and current ending time, and the average execution information comprises average starting time and average ending time;
and determining current delay deviation corresponding to each upstream execution task according to each current execution information and each average execution information, and determining an upstream delay task causing the delay of the current monitoring task from each upstream execution task based on the current delay deviation corresponding to each upstream execution task.
2. The method of claim 1, further comprising:
determining preset starting time corresponding to the current monitoring task according to a task information table, wherein the task information table comprises the preset starting time corresponding to each monitoring task;
and starting a preset timing monitoring task when the preset starting time is reached, detecting whether the current monitoring task starts to be executed or not through the preset timing monitoring task, and if not, determining that the execution starting time of the current monitoring task is delayed.
3. The method of claim 1, wherein the determining the current execution information and the average execution information respectively corresponding to each upstream execution task comprises:
acquiring historical execution information and current execution information which respectively correspond to each upstream execution task based on a task execution record table, wherein the task execution record table comprises the historical execution information and the current execution information which correspond to each task, and the historical execution information comprises historical start time and historical end time which correspond to each task;
and respectively determining average execution information corresponding to each upstream execution task based on the historical execution information corresponding to each upstream execution task.
4. The method according to claim 3, wherein the determining average execution information corresponding to each upstream execution task based on the historical execution information corresponding to each upstream execution task respectively comprises:
for each upstream execution task, calculating historical average starting time according to each historical starting time corresponding to the current upstream execution task, calculating historical average ending time according to each historical ending time corresponding to the current upstream execution task, and determining the historical average starting time and the historical average ending time as average execution information corresponding to the current upstream execution task; or,
and clustering the historical start time corresponding to the current upstream execution task aiming at each upstream execution task, determining the average start time corresponding to the current upstream execution task based on the core point in the clustering result, clustering the historical end time corresponding to the current upstream execution task, and determining the average end time corresponding to the current upstream execution task based on the core point in the clustering result.
5. The method of claim 1, wherein determining the upstream delaying task that caused the delay of the current monitoring task from the upstream executing tasks based on the current delay offset corresponding to each upstream executing task comprises:
determining at least one delay task to be screened from each upstream execution task based on a preset deviation threshold and the current delay deviation corresponding to each upstream execution task;
and determining at least one upstream delay task from each delay task to be screened according to the current delay deviation corresponding to each delay task to be screened.
6. The method of claim 5, further comprising:
acquiring a first task identifier of the current monitoring task and a second task identifier of each upstream delay task according to a task information table, and generating alarm information based on the first task identifier and each second task identifier;
and acquiring a relevant user identifier corresponding to the current monitoring task based on the task information table, and sending the alarm information to a user terminal corresponding to the relevant user identifier, wherein the task information table comprises task identifiers of all tasks and relevant user identifiers corresponding to all monitoring tasks.
7. The method of claim 6, wherein generating alert information based on the first task identification and each of the second task identifications comprises:
determining the predicted starting time and the predicted ending time of the current monitoring task based on the current delay deviation corresponding to each upstream delay task;
and generating alarm information according to the first task identifier, each second task identifier, the predicted starting time and the predicted ending time.
8. The method according to any one of claims 1-7, further comprising:
and under the condition that the execution starting time of the current monitoring task is determined not to be delayed and the execution ending time of the current monitoring task is delayed, determining the current monitoring task as a monitoring delay task.
9. The method of claim 8, further comprising:
determining a preset ending time corresponding to the current monitoring task according to a task information table, wherein the task information table comprises the preset ending time corresponding to each monitoring task;
and starting a preset timing monitoring task when the preset ending time is reached, detecting whether the current monitoring task is finished executing or not through the preset timing monitoring task, and if not, determining that the execution ending time of the current monitoring task is delayed.
10. The method of any of claims 1-7, wherein after said determining an upstream delaying task from each of said upstream executing tasks that causes a delay in said current monitoring task, said method further comprises:
under the condition that the execution ending time delay of the current monitoring task is determined, current execution information corresponding to the current monitoring task is determined;
determining actual execution duration corresponding to the current monitoring task based on current execution information corresponding to the current monitoring task;
and acquiring a preset execution time corresponding to the current monitoring task, and determining the current monitoring task as a monitoring delay task if the difference value between the preset execution time and the actual execution time exceeds a preset threshold value.
11. A task delay monitoring apparatus, comprising:
the upstream task determining module is used for determining each upstream execution task corresponding to the current monitoring task under the condition of determining the execution starting time delay of the current monitoring task;
an execution information determining module, configured to determine current execution information and average execution information corresponding to each upstream execution task, where the current execution information includes a current start time and a current end time, and the average execution information includes an average start time and an average end time;
and a delay task determining module, configured to determine, according to each piece of current execution information and each piece of average execution information, a current delay deviation corresponding to each upstream execution task, and determine, based on the current delay deviation corresponding to each upstream execution task, an upstream delay task that causes a delay of the current monitoring task from each upstream execution task.
12. An electronic device, characterized in that the electronic device comprises:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the task delay monitoring method of any one of claims 1-10.
13. A computer-readable storage medium storing computer instructions for causing a processor to perform the method of task delay monitoring of any one of claims 1-10 when executed.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211327884.2A CN115629903A (en) | 2022-10-27 | 2022-10-27 | Task delay monitoring method, device, equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211327884.2A CN115629903A (en) | 2022-10-27 | 2022-10-27 | Task delay monitoring method, device, equipment and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN115629903A true CN115629903A (en) | 2023-01-20 |
Family
ID=84906869
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202211327884.2A Pending CN115629903A (en) | 2022-10-27 | 2022-10-27 | Task delay monitoring method, device, equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN115629903A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117370065A (en) * | 2023-12-01 | 2024-01-09 | 中航信移动科技有限公司 | Abnormal task determining method, electronic equipment and storage medium |
-
2022
- 2022-10-27 CN CN202211327884.2A patent/CN115629903A/en active Pending
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117370065A (en) * | 2023-12-01 | 2024-01-09 | 中航信移动科技有限公司 | Abnormal task determining method, electronic equipment and storage medium |
CN117370065B (en) * | 2023-12-01 | 2024-02-02 | 中航信移动科技有限公司 | Abnormal task determining method, electronic equipment and storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN116661960A (en) | Batch task processing method, device, equipment and storage medium | |
CN115629903A (en) | Task delay monitoring method, device, equipment and storage medium | |
CN115904656A (en) | State control method, device and equipment applied to chip and storage medium | |
CN112860401B (en) | Task scheduling method, device, electronic equipment and storage medium | |
CN116069774B (en) | Data cleaning method, device and medium based on wireless timeout intelligent analysis | |
CN117314068A (en) | Tobacco shred task scheduling method and device, electronic equipment and storage medium | |
CN115426287B (en) | System monitoring and optimizing method and device, electronic equipment and medium | |
CN115458184A (en) | Epidemic prevention detection data pushing method, device, equipment and storage medium | |
CN115509714A (en) | Task processing method and device, electronic equipment and storage medium | |
CN115890684A (en) | Robot scheduling method, device, equipment and medium | |
CN114867050A (en) | Vehicle flow detection method, device, system, equipment and storage medium | |
CN116089499A (en) | Data statistics method, device and medium based on kafka data volume | |
CN116991620B (en) | Solution determining method, device, equipment and medium | |
CN116991683B (en) | Alarm information processing method, device, equipment and medium | |
CN115563015B (en) | Code heat statistics method, device, equipment and storage medium | |
CN112633683B (en) | Resource usage statistics method, device, system, electronic equipment and storage medium | |
CN115599634A (en) | Data processing method, device, equipment and storage medium | |
CN117785403A (en) | Heartbeat task execution device for equipment, electronic equipment and storage medium | |
CN115454847A (en) | Pressure testing method and device, electronic equipment and storage medium | |
CN115601043A (en) | Risk transaction processing method and device, electronic equipment and storage medium | |
CN115408115A (en) | Transaction starting time processing method, device, equipment and storage medium | |
CN118827179A (en) | Distribution network diagram data transmission state detection method, device, equipment and storage medium | |
CN115237561A (en) | Job obtaining method, device, equipment and medium | |
CN117762871A (en) | Document storage method, device, electronic equipment and storage medium | |
CN117376397A (en) | Game duration determining method, device, 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 |