A method, device, system and medium for alarming work performance timeliness

By acquiring the target achievement time and historical execution data of the work project, and combining the upstream and downstream relationships to perform timeliness iteration calculations, the problem of inaccurate work alarm thresholds in existing technologies is solved, and the reliability of work timeliness alarms is improved.

CN115934485BActive Publication Date: 2026-11-17PING AN BANK CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202211542811.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-12-02
Publication Date
2026-11-17
Estimated Expiration
2042-12-02

AI Technical Summary

Technical Problem

Existing job failure alarm methods struggle to accurately determine alarm thresholds for job timeliness, resulting in low alarm reliability.

Method used

By acquiring the target achievement time and historical execution data of the task projects, and performing timeliness iteration calculations based on the upstream and downstream relationships between tasks, the timeliness configuration of each task is determined, and precise alarm thresholds are set.

Benefits of technology

This allows for more precise and effective configuration of alarm times for each job, improving the reliability of job timeliness alarms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115934485B_ABST
    Figure CN115934485B_ABST
Patent Text Reader

Abstract

This invention discloses a method, apparatus, system, and medium for job timeliness alarms. The method includes: acquiring a job item with a timeliness to be configured and its target achievement time, wherein the job item includes multiple jobs; confirming the upstream and downstream relationships between the multiple jobs based on their execution links; acquiring historical execution data of the job item; performing timeliness iterative calculations based on the target achievement time and historical execution data, according to the upstream and downstream relationships between the jobs, to obtain a timeliness configuration for each job; setting an alarm timeliness for each job according to the timeliness configuration, and issuing a job timeliness alarm. By confirming the relationships between multiple jobs and historical execution data, and iteratively calculating the accurate timeliness configuration for each job, the alarm time configured for each job is more accurate and effective, effectively improving the reliability of job timeliness alarms.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method, apparatus, system, and medium for alarming on work timeliness. Background Technology

[0002] Currently, thousands of jobs are running on the bank's big data platform. Many of these jobs have time requirements, so the platform usually integrates timeliness monitoring and alarm components, allowing platform users to easily configure timeliness monitoring and alarms for the corresponding jobs. When an alarm is triggered, the relevant personnel are notified to handle it.

[0003] However, existing methods typically rely on single monitoring alarms. For example, if a task requires completion by 9 AM, only a single 9 AM monitoring alarm is configured. By the time the alarm is triggered, it is already quite delayed. Alternatively, some methods include monitoring all upstream tasks and configuring a baseline time for each task. However, this approach has high development and maintenance costs, and the fixed baseline time configured for each task often leads to false alarms. For instance, if task A depends on upstream task B, and task B's baseline time is 1 AM, and task A's time requirement is 8 AM, if task B's time requirement changes to 2 AM on a certain day, an alarm will be triggered. This alarm would then be a false alarm for task A.

[0004] Therefore, existing job failure alarm methods are still unable to accurately determine the alarm threshold for job timeliness, which reduces the reliability of job timeliness alarms. Summary of the Invention

[0005] In view of the shortcomings of the prior art, the purpose of this invention is to provide a method, device, system and medium for work timeliness alarm that can be applied to financial technology or other related fields, aiming to achieve accurate confirmation of work timeliness alarm threshold and improve the reliability of work timeliness alarm.

[0006] The technical solution of the present invention is as follows:

[0007] A method for alarming on work deadlines includes:

[0008] Obtain the job items to be configured with time limits and the target achievement time of the job items, wherein the job items include multiple jobs;

[0009] Based on the execution chain of the multiple jobs, confirm the upstream and downstream relationships between each job;

[0010] Obtain the historical execution data of the aforementioned job item;

[0011] Based on the target achievement time and historical execution data, the timeliness is iteratively calculated according to the upstream and downstream relationships between each job to obtain the timeliness configuration for each job;

[0012] According to the timeliness configuration, the alarm timeliness of each job is set accordingly, and job timeliness alarms are issued.

[0013] In one embodiment, determining the upstream and downstream relationships between the various jobs based on their execution chains specifically includes:

[0014] Obtain the full-link information of the job project and analyze it to obtain the execution link of the multiple jobs;

[0015] The upstream and downstream jobs of each job in the job project are identified based on the execution chain.

[0016] In one embodiment, obtaining the historical execution data of the job project includes:

[0017] Obtain historical execution data for each job in the job project, including job start time and job end time;

[0018] The historical execution time of each task is obtained according to preset statistical indicators.

[0019] In one embodiment, the step of performing timeliness iterative calculations based on the target achievement time and historical execution data, according to the upstream and downstream relationships between various jobs, to obtain the timeliness configuration for each job includes:

[0020] The time when the target is achieved is used as the end time alarm threshold for the last task;

[0021] Based on the historical execution duration of each job, the timeliness configuration of upstream jobs is calculated iteratively upwards to obtain the start time alarm threshold and end time alarm threshold for each job.

[0022] In one embodiment, the step of iteratively calculating the timeliness configuration of upstream jobs based on the historical execution duration of each job to obtain the start time alarm threshold and end time alarm threshold for each job includes:

[0023] The alarm threshold for the start time of the last job is calculated based on the historical execution duration of the last job.

[0024] Use the start time alarm threshold of the last job as the end time alarm threshold of its upstream job;

[0025] Based on the historical execution duration of upstream jobs, the start time alarm threshold for upstream jobs is calculated. Similarly, the start time alarm threshold and end time alarm threshold for each job are calculated iteratively upwards.

[0026] In one embodiment, setting the alarm timeout for each job according to the timeout configuration and issuing job timeout alarms includes:

[0027] According to the aforementioned timeliness configuration, set the start time alarm threshold and end time alarm threshold for each job accordingly;

[0028] If the job has not started execution when the start time alarm threshold is reached, or the job has not finished execution when the end time alarm threshold is reached, then a job timeout alarm message will be output.

[0029] In one embodiment, after outputting job timeliness alarm information when the job has not started execution when the start time alarm threshold is reached, or when the job has not finished execution when the end time alarm threshold is reached, the method further includes:

[0030] Locate problematic tasks based on the aforementioned task timeliness alarm information.

[0031] A work performance timeliness alarm device, comprising:

[0032] The acquisition module is used to acquire the job items to be configured with time limits and the target achievement time of the job items, wherein the job items include multiple jobs;

[0033] The association confirmation module is used to confirm the upstream and downstream association relationships between the multiple jobs based on their execution links.

[0034] The historical data acquisition module is used to acquire the historical execution data of the job project;

[0035] The timeliness calculation module is used to perform timeliness iterative calculation based on the target achievement time and historical execution data, according to the upstream and downstream correlation between each job, to obtain the timeliness configuration of each job;

[0036] The alarm configuration module is used to set the alarm time limit for each job according to the time limit configuration and to issue job time limit alarms.

[0037] A job performance timeliness alarm system, the system comprising at least one processor; and,

[0038] A memory communicatively connected to the at least one processor; wherein,

[0039] The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the aforementioned job timeout alarm method.

[0040] A non-volatile computer-readable storage medium storing computer-executable instructions, which, when executed by one or more processors, cause the one or more processors to perform the above-described job timeout alarm method.

[0041] Beneficial effects: This invention discloses a method, device, system, and medium for job timeliness alarms. Compared with the prior art, the embodiments of this invention confirm the correlation between multiple jobs and historical execution data, and iteratively calculate the accurate timeliness configuration of each job, making the alarm time configured for each job more accurate and effective, and effectively improving the reliability of job timeliness alarms. Attached Figure Description

[0042] The present invention will be further described below with reference to the accompanying drawings and embodiments. In the accompanying drawings:

[0043] Figure 1 A flowchart of a job performance alarm method provided in an embodiment of the present invention;

[0044] Figure 2 A flowchart of step S200 in the job performance alarm method provided in this embodiment of the invention;

[0045] Figure 3 This is a flowchart of step S300 in the job performance alarm method provided in an embodiment of the present invention;

[0046] Figure 4 A flowchart of step S400 in the job performance alarm method provided in this embodiment of the invention;

[0047] Figure 5 This is a flowchart of step S402 in the job performance alarm method provided in the embodiment of the present invention;

[0048] Figure 6 A flowchart of step S500 in the job performance alarm method provided in this embodiment of the invention;

[0049] Figure 7 A schematic diagram of the functional modules of the work timeliness alarm device provided in an embodiment of the present invention;

[0050] Figure 8 This is a schematic diagram of the hardware structure of the job performance alarm system provided in an embodiment of the present invention. Detailed Implementation

[0051] To make the objectives, technical solutions, and effects of this invention clearer and more explicit, the invention is further described in detail below. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. The embodiments of the invention are described below in conjunction with the accompanying drawings.

[0052] Please see Figure 1 , Figure 1 This is a flowchart of an embodiment of the job timeliness alarm method provided by the present invention. The job timeliness alarm method provided in this embodiment is applied to a system comprising terminal devices, a network, and a server. The network is the medium providing a communication link between the terminal devices and the server, and can include various connection types, such as wired, wireless communication links, or fiber optic cables. The operating system on the terminal device can include a handheld device operating system (iPhone operating system, iOS system), Android system, or other operating systems. The terminal device connects to the server through the network to achieve interaction, thereby performing operations such as receiving or sending data. Specifically, it can be various electronic devices with a display screen and supporting web browsing, including but not limited to smartphones, tablets, portable computers, and desktop servers. Figure 1 As shown, the method specifically includes the following steps:

[0053] S100: Obtain the job items to be configured with time limits and the target achievement time of the job items, wherein the job items include multiple jobs.

[0054] In this embodiment, the jobs running on the big data platform can be divided into projects. When issuing timeliness alarms, the alarm time needs to be configured for each job project. Each job project further includes multiple jobs executed in sequence. Before configuring the timeliness, the target achievement time of the job project is obtained as the benchmark for timeliness configuration to ensure that the overall execution timeliness of the job project meets the requirements of the target achievement time.

[0055] S200. Based on the execution chain of the multiple jobs, confirm the upstream and downstream relationships between each job.

[0056] In this embodiment, the upstream and downstream relationships between each job are determined based on the execution chain of multiple jobs in the job project, that is, the execution order of each job in the job project. This allows the impact of upstream and downstream jobs on the current configuration object to be considered when configuring alarm time, thereby achieving accurate alarm time configuration for each job.

[0057] In one embodiment, see Figure 2 This is a flowchart of step S200 in the job performance alarm method provided in the embodiment of the present invention, as follows: Figure 2 As shown, step S200 includes:

[0058] S201. Obtain the full-link information of the job project and analyze it to obtain the execution link of the multiple jobs;

[0059] S202. Based on the execution chain, confirm the upstream and downstream jobs of each job in the job project.

[0060] In this embodiment, the full-link information of the job project can be obtained from the database, that is, the full-link tracking record obtained during the historical execution of the job project. Then, the execution link of multiple jobs contained therein can be analyzed. Based on the execution link, the upstream and downstream jobs of each job can be identified, providing a reliable job association relationship for the configuration of alarm time.

[0061] S300: Obtain the historical execution data of the job project.

[0062] In this embodiment, based on the target achievement time of the task project, its historical execution data is further obtained as the data basis for configuring the alarm time of each task in the task project, so as to realize the alarm time configuration that is more in line with the actual execution situation and avoid false alarms caused by invalid time configuration.

[0063] In one embodiment, see Figure 3 This is a flowchart of step S300 in the job performance alarm method provided in the embodiment of the present invention, as follows: Figure 3 As shown, step S300 includes:

[0064] S301. Obtain historical execution data for each job in the job project, wherein the historical execution data includes job start time and job end time;

[0065] S302. Obtain the historical execution time of each job according to the preset statistical indicators.

[0066] In this embodiment, by obtaining the start and end times of each job's historical execution, multiple historical execution durations for each job are obtained. Since the time spent on each execution may be different, in order to reduce the amount of data and filter out irregular situations in historical execution, this embodiment analyzes the historical execution data of each job using preset statistical indicators to obtain the historical execution duration of each job. Specifically, the preset statistical indicator is the P95 duration within a preset time period (e.g., within 3 months, 6 months, etc.). The P95 duration is the historical execution duration of 95% of the total historical execution times of each job. That is, in 95% of the historical execution times, each job completes the execution process with the corresponding historical execution duration. The P95 duration can accurately reflect the actual execution duration of each job, thereby enabling subsequent accurate and effective alarm time settings.

[0067] S400. Based on the target achievement time and historical execution data, perform timeliness iteration calculations according to the upstream and downstream relationships between each job to obtain the timeliness configuration for each job.

[0068] In this embodiment, the target achievement time and historical execution data of the work project are used as the basis, and the timeliness iterative calculation is performed according to the upstream and downstream relationship between each work. That is, according to the historical execution order and the time requirement of the downstream work, the time requirement of each other work in the work project is iteratively calculated in sequence through the upstream and downstream relationship to deduce the timeliness configuration of each work, and thus obtain the accurate alarm time configuration of each work that meets its target achievement time and time execution status.

[0069] In one embodiment, see Figure 4 This is a flowchart of step S400 in the job performance alarm method provided in the embodiment of the present invention, as follows: Figure 4 As shown, step S400 includes:

[0070] S401. Use the target achievement time as the end time alarm threshold for the last task;

[0071] S402. Based on the historical execution duration of each job, iteratively calculate the timeliness configuration of the upstream jobs to obtain the start time alarm threshold and end time alarm threshold for each job.

[0072] In this embodiment, the target achievement time is used as the end time alarm threshold for the last task. That is, the last task must be completed before the alarm threshold is reached to ensure the timeliness of the entire task project. Based on the historical execution time of each task, the timeliness configuration of the upstream tasks is calculated sequentially from the last task. This timeliness configuration includes the start time alarm threshold and the end time alarm threshold until the timeliness configuration of each task is calculated, so as to realize the precise time threshold setting for each task in the task project.

[0073] In one embodiment, see Figure 5 This is a flowchart of step S402 in the job performance alarm method provided in the embodiment of the present invention, as follows: Figure 5 As shown, step S402 includes:

[0074] S4021. Calculate the alarm threshold for the start time of the last job based on the historical execution duration of the last job.

[0075] S4022. Use the start time alarm threshold of the last job as the end time alarm threshold of its upstream job.

[0076] S4023. Based on the historical execution duration of upstream jobs, calculate the start time alarm threshold of upstream jobs. Similarly, iterate upwards to calculate the start time alarm threshold and end time alarm threshold of each job.

[0077] In this embodiment, during the specific iterative calculation, the start time alarm threshold for the last job is calculated based on its historical execution duration. Specifically, the start time alarm threshold is the end time alarm threshold minus the historical execution duration of the last job. Then, the start time alarm threshold of the last job is iteratively used as the end time alarm threshold for its upstream jobs. Similarly, based on the historical execution duration of its upstream jobs, the start time alarm threshold for those upstream jobs is calculated. This process continues iteratively upstream until the start and end time alarm thresholds for each job are obtained. This embodiment is based on the timeliness requirements of each job's downstream jobs, meaning that the end time alarm threshold for each job is equal to the start time alarm threshold for the downstream job. Furthermore, it automatically determines the start and end alarm times for each job by combining the historical execution duration of each job, making the alarm times configured for each job more accurate and effective.

[0078] S500. Set the alarm time limit for each job according to the time limit configuration, and issue a job time limit alarm.

[0079] In this embodiment, the alarm time limit for each job is set according to the calculated time limit configuration. Based on the alarm time limit for each job, the job time limit alarm is performed during the actual operation. The reliability of the job time limit alarm is effectively improved through accurate time limit configuration.

[0080] In one embodiment, see Figure 6 This is a flowchart of step S500 in the job performance alarm method provided in the embodiment of the present invention, as follows: Figure 6 As shown, step S500 includes:

[0081] S501. Set the start time alarm threshold and end time alarm threshold for each job according to the timeliness configuration.

[0082] S502. If the job has not started execution when the start time alarm threshold is reached, or the job has not finished execution when the end time alarm threshold is reached, then output job timeliness alarm information.

[0083] In this embodiment, the timeliness configuration for each job is specifically configured with a start time alarm threshold and an end data alarm threshold. When a job timeliness alarm is triggered, the execution status of each job is monitored. If the job has not started execution when the start time alarm threshold is reached, or the job has not finished execution when the end time alarm threshold is reached, the job timeliness alarm information is output. By setting the thresholds for the two time nodes, timeliness alarms for timely jobs can be set more accurately and effectively.

[0084] In one embodiment, after step S502, the method further includes:

[0085] Locate problematic tasks based on the aforementioned task timeliness alarm information.

[0086] In this embodiment, when the execution time of a job fails to meet the corresponding time alarm threshold requirements, the problematic job can be located based on the job time alarm information, thereby enabling rapid location of the problematic job and facilitating quick problem resolution.

[0087] Specifically, if the job time alarm information indicates that a job has not started execution when the start time alarm threshold is reached, then it is further determined whether the upstream job of the job has ended on time, that is, whether the upstream job outputs a job alarm information indicating that the job has not finished execution when the end time alarm threshold is reached. If the upstream job has a job timeliness alarm information, then the problematic job is identified as the upstream job; if the upstream job does not have a job timeliness alarm information, then the problematic job is identified as the current job. If the job time alarm information indicates that a job has not finished execution when the end time alarm threshold is reached, then the problematic job is identified as the current job.

[0088] Another embodiment of the present invention provides a work timeliness alarm device, such as Figure 7 As shown, device 1 includes:

[0089] The acquisition module 11 is used to acquire the job items to be configured with timeliness and the target achievement time of the job items, wherein the job items include multiple jobs;

[0090] The association confirmation module 12 is used to confirm the upstream and downstream association relationships between the multiple jobs based on the execution chain of the multiple jobs;

[0091] Historical data acquisition module 13 is used to acquire historical execution data of the job project;

[0092] The timeliness calculation module 14 is used to perform timeliness iterative calculation based on the target achievement time and historical execution data, according to the upstream and downstream correlation between each job, to obtain the timeliness configuration of each job;

[0093] The alarm configuration module 15 is used to set the alarm time limit for each job according to the time limit configuration and to issue job time limit alarms.

[0094] The module referred to in this invention is a series of computer program instruction segments that can perform specific functions. It is more suitable than a program for describing the execution process of job timeliness alarms. For the specific implementation of each module, please refer to the corresponding method embodiments above, which will not be repeated here.

[0095] In one embodiment, the association confirmation module 12 includes:

[0096] The link analysis unit is used to obtain the full link information of the job project and analyze the execution link of the multiple jobs;

[0097] The association confirmation unit is used to confirm the upstream and downstream jobs of each job in the job project according to the execution link.

[0098] In one embodiment, the historical data acquisition module 13 includes:

[0099] The acquisition unit is used to acquire historical execution data for each job in the job project, wherein the historical execution data includes job start time and job end time;

[0100] The statistical filtering unit is used to obtain the historical execution time of each job according to preset statistical indicators.

[0101] In one embodiment, the timeliness calculation module 14 includes:

[0102] An initial configuration unit is used to set the target achievement time as the end time alarm threshold for the last job;

[0103] The iterative calculation unit is used to iteratively calculate the timeliness configuration of upstream jobs based on the historical execution duration of each job, and obtain the start time alarm threshold and end time alarm threshold for each job.

[0104] In one embodiment, the iterative calculation unit includes:

[0105] The calculation unit is used to calculate the alarm threshold for the start time of the last job based on the historical execution duration of the last job.

[0106] An iterative unit is used to take the start time alarm threshold of the last job as the end time alarm threshold of its upstream job.

[0107] The calculation unit is used to calculate the start time alarm threshold of the upstream job based on the historical execution time of the upstream job, and so on, iteratively calculating the start time alarm threshold and end time alarm threshold of each job.

[0108] In one embodiment, the alarm configuration module 15 includes:

[0109] The configuration unit is used to set the start time alarm threshold and end time alarm threshold for each job according to the timeliness configuration.

[0110] The alarm notification unit is used to output job timeliness alarm information if the job has not started when the start time alarm threshold is reached, or if the job has not finished when the end time alarm threshold is reached.

[0111] In one embodiment, the alarm configuration module 15 further includes:

[0112] The positioning unit is used to locate problematic tasks based on the task timeliness alarm information.

[0113] Another embodiment of the present invention provides a job performance timeliness alarm system, such as Figure 8 As shown, system 10 includes:

[0114] One or more processors 110 and memory 120, Figure 8 The following description uses a processor 110 as an example. The processor 110 and the memory 120 can be connected via a bus or other means. Figure 8 Taking the example of a connection between China and Israel via a bus.

[0115] Processor 110 is used to perform various control logics of system 10, and can be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), microcontroller, ARM (Acorn RISC Machine) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. Furthermore, processor 110 can also be any conventional processor, microprocessor, or state machine. Processor 110 can also be implemented as a combination of computing devices, such as a combination of DSP and microprocessor, multiple microprocessors, one or more microprocessors combined with DSP and / or any other such configuration.

[0116] The memory 120, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions corresponding to the job timeliness alarm method in the embodiments of the present invention. The processor 110 executes various functional applications and data processing of the system 10 by running the non-volatile software programs, instructions, and units stored in the memory 120, thereby implementing the job timeliness alarm method in the above method embodiments.

[0117] The memory 120 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created according to the use of the system 10. Furthermore, the memory 120 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 120 may optionally include memory remotely located relative to the processor 110, and these remote memories may be connected to the system 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0118] One or more units are stored in memory 120, and when executed by one or more processors 110, perform the following steps:

[0119] Obtain the job items to be configured with time limits and the target achievement time of the job items, wherein the job items include multiple jobs;

[0120] Based on the execution chain of the multiple jobs, confirm the upstream and downstream relationships between each job;

[0121] Obtain the historical execution data of the aforementioned job item;

[0122] Based on the target achievement time and historical execution data, the timeliness is iteratively calculated according to the upstream and downstream relationships between each job to obtain the timeliness configuration for each job;

[0123] According to the timeliness configuration, the alarm timeliness of each job is set accordingly, and job timeliness alarms are issued.

[0124] In one embodiment, determining the upstream and downstream relationships between the various jobs based on their execution chains specifically includes:

[0125] Obtain the full-link information of the job project and analyze it to obtain the execution link of the multiple jobs;

[0126] The upstream and downstream jobs of each job in the job project are identified based on the execution chain.

[0127] In one embodiment, obtaining the historical execution data of the job project includes:

[0128] Obtain historical execution data for each job in the job project, including job start time and job end time;

[0129] The historical execution time of each task is obtained according to preset statistical indicators.

[0130] In one embodiment, the step of performing timeliness iterative calculations based on the target achievement time and historical execution data, according to the upstream and downstream relationships between various jobs, to obtain the timeliness configuration for each job includes:

[0131] The time when the target is achieved is used as the end time alarm threshold for the last task;

[0132] Based on the historical execution duration of each job, the timeliness configuration of upstream jobs is calculated iteratively upwards to obtain the start time alarm threshold and end time alarm threshold for each job.

[0133] In one embodiment, the step of iteratively calculating the timeliness configuration of upstream jobs based on the historical execution duration of each job to obtain the start time alarm threshold and end time alarm threshold for each job includes:

[0134] The alarm threshold for the start time of the last job is calculated based on the historical execution duration of the last job.

[0135] Use the start time alarm threshold of the last job as the end time alarm threshold of its upstream job;

[0136] Based on the historical execution duration of upstream jobs, the start time alarm threshold for upstream jobs is calculated. Similarly, the start time alarm threshold and end time alarm threshold for each job are calculated iteratively upwards.

[0137] In one embodiment, setting the alarm timeout for each job according to the timeout configuration and issuing job timeout alarms includes:

[0138] According to the aforementioned timeliness configuration, set the start time alarm threshold and end time alarm threshold for each job accordingly;

[0139] If the job has not started execution when the start time alarm threshold is reached, or the job has not finished execution when the end time alarm threshold is reached, then a job timeout alarm message will be output.

[0140] In one embodiment, after outputting job timeliness alarm information when the job has not started execution when the start time alarm threshold is reached, or when the job has not finished execution when the end time alarm threshold is reached, the method further includes:

[0141] Locate problematic tasks based on the aforementioned task timeliness alarm information.

[0142] This invention provides a non-volatile computer-readable storage medium storing computer-executable instructions that are executed by one or more processors, for example, to perform the operations described above. Figure 1 The method steps S100 to S500.

[0143] As examples, non-volatile storage media can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) as external cache memory. By way of illustration and not limitation, RAM can be obtained in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The memory components or memories disclosed in the operating environment described herein are intended to include one or more of these and / or any other suitable types of memory.

[0144] In summary, the job timeliness alarm method, apparatus, system, and medium disclosed in this invention involve the following steps: The method obtains the job item whose timeliness needs to be configured and its target achievement time, where each job item includes multiple jobs; it confirms the upstream and downstream relationships between the jobs based on their execution chains; it obtains historical execution data for the job item; it performs iterative timeliness calculations based on the target achievement time and historical execution data, according to the upstream and downstream relationships between the jobs, to obtain the timeliness configuration for each job; it sets the alarm timeliness for each job according to the timeliness configuration and issues a job timeliness alarm. By confirming the relationships between multiple jobs and using historical execution data, the accurate timeliness configuration for each job is iteratively calculated, making the alarm time configured for each job more precise and effective, thus significantly improving the reliability of job timeliness alarms.

[0145] Of course, those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware (such as a processor, controller, etc.). The computer program can be stored in a non-volatile, computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The storage medium can be a memory, magnetic disk, floppy disk, flash memory, optical storage, etc.

[0146] It should be understood that the application of the present invention is not limited to the examples above. Those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

Claims

1. A work time limit warning method characterized by comprising: include: Obtain the job items to be configured with time limits and the target achievement time of the job items, wherein the job items include multiple jobs; Based on the execution chain of the multiple jobs, confirm the upstream and downstream relationships between each job; Obtain the historical execution data of the aforementioned job item; Based on the target achievement time and historical execution data, the timeliness is iteratively calculated according to the upstream and downstream relationships between each job to obtain the timeliness configuration for each job; According to the timeliness configuration, the alarm timeliness of each job is set accordingly, and job timeliness alarms are issued; The acquisition of historical execution data for the job project includes: Obtain historical execution data for each job in the job project, including job start time and job end time; The historical execution time of each job is obtained according to a preset statistical indicator; the preset statistical indicator is the P95 duration within a preset time period, and the P95 duration is the historical execution time of 95% of the total historical execution times of each job. The step of performing timeliness iterative calculations based on the target achievement time and historical execution data, according to the upstream and downstream relationships between each job, to obtain the timeliness configuration for each job includes: The time when the target is achieved is used as the end time alarm threshold for the last task; Based on the historical execution duration of each job, the timeliness configuration of upstream jobs is calculated iteratively upwards to obtain the start time alarm threshold and end time alarm threshold for each job.

2. The work timeliness alarm method according to claim 1, characterized in that, The step of confirming the upstream and downstream relationships between the various jobs based on their execution chains specifically includes: Obtain the full-link information of the job project and analyze it to obtain the execution link of the multiple jobs; The upstream and downstream jobs of each job in the job project are identified based on the execution chain.

3. The work timeliness alarm method according to claim 1, characterized in that, The process involves iteratively calculating the timeliness configuration of upstream jobs based on the historical execution duration of each job, to obtain the start time alarm threshold and end time alarm threshold for each job, including: The alarm threshold for the start time of the last job is calculated based on the historical execution duration of the last job. Use the start time alarm threshold of the last job as the end time alarm threshold of its upstream job; Based on the historical execution duration of upstream jobs, the start time alarm threshold for upstream jobs is calculated. Similarly, the start time alarm threshold and end time alarm threshold for each job are calculated iteratively upwards.

4. The work timeliness alarm method according to claim 1, characterized in that, The step of setting the alarm time limit for each job according to the time limit configuration and issuing job time limit alarms includes: According to the aforementioned timeliness configuration, set the start time alarm threshold and end time alarm threshold for each job accordingly; If the job has not started execution when the start time alarm threshold is reached, or the job has not finished execution when the end time alarm threshold is reached, then a job timeout alarm message will be output.

5. The work timeliness alarm method according to claim 4, characterized in that, After outputting a job timeliness alarm message when the start time alarm threshold is reached or the end time alarm threshold is reached, the method further includes: Locate problematic tasks based on the aforementioned task timeliness alarm information.

6. A work performance timeliness alarm device, characterized in that, include: The acquisition module is used to acquire the job items to be configured with time limits and the target achievement time of the job items, wherein the job items include multiple jobs; The association confirmation module is used to confirm the upstream and downstream association relationships between the multiple jobs based on their execution links. The historical data acquisition module is used to acquire the historical execution data of the job project; The timeliness calculation module is used to perform timeliness iterative calculation based on the target achievement time and historical execution data, according to the upstream and downstream correlation between each job, to obtain the timeliness configuration of each job; The alarm configuration module is used to set the alarm duration for each job according to the timeliness configuration and to issue job timeliness alarms. The historical data acquisition module includes: The acquisition unit is used to acquire historical execution data for each job in the job project, wherein the historical execution data includes job start time and job end time; The statistical filtering unit is used to obtain the historical execution time of each job according to a preset statistical indicator; the preset statistical indicator is the P95 duration within a preset time period, and the P95 duration is the historical execution time of 95% of the total historical execution times of each job. The timeliness calculation module includes: An initial configuration unit is used to set the target achievement time as the end time alarm threshold for the last job; The iterative calculation unit is used to iteratively calculate the timeliness configuration of upstream jobs based on the historical execution duration of each job, and obtain the start time alarm threshold and end time alarm threshold for each job.

7. A work performance timeliness alarm system, characterized in that, The system includes at least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the job timeliness alarm method according to any one of claims 1-5.

8. A non-volatile computer-readable storage medium, characterized in that, The non-volatile computer-readable storage medium stores computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the job timeout alarm method according to any one of claims 1-5.

Citation Information

Patent Citations

  • Batch processing task time monitoring method and device, electronic equipment and storage medium

    CN111737095A

  • Batch job monitoring method and device, equipment and medium

    CN114500318A