Timed task execution record monitoring method and device, computer equipment and storage medium
By loading custom configuration parameters in the timing task, performing pre-checks and post-checks, and recording logs, the monitoring and handling of timing task execution exceptions is solved, and the effect of timely discovering and troubleshooting exceptions is achieved.
Patent Information
- Application Number
- CN202411530183.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2025-02-07
AI Technical Summary
The existing technology is difficult to monitor and handle abnormal execution of timing tasks, which leads to the need to manually repair abnormal data, which consumes labor, and imperfect log printing, making it inconvenient to troubleshoot production problems.
By loading custom configuration parameters, record the timing task starts execution log, and perform pre-checking, process timing tasks, and perform post-checking. If it is passed, record the processing end log and generate a log record document.
It realizes the correct completion of business logic processing of timing tasks, timely discovers abnormalities, facilitates problem investigation, and reduces manual intervention and investigation time.
Smart Images
Figure CN119396656A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a timed task monitoring technology, and more specifically to a timed task execution record monitoring method, device, computer equipment and storage medium. Background Art
[0002] Scheduled tasks are mainly responsible for scheduling. Many existing frameworks only monitor the success and failure of scheduling, and lack monitoring of the execution of business logic. To troubleshoot problems, you can only look at the error log, which makes it difficult to discover problems in a timely manner. A few scheduled tasks have monitoring, but the process is not perfect, the reusability is not strong, and it is difficult to promote.
[0003] When encountering an abnormal scenario, such as a network anomaly, which causes the scheduled task to execute abnormally, after the anomaly is recovered or resolved, the next scheduled task execution is expected to automatically continue from the point where it failed last time, without too much manual intervention. Currently, many scheduled tasks cannot handle such abnormal scenarios. When encountering an exception, the abnormal data needs to be manually repaired, which is very labor-intensive. In addition, the log printing is not perfect, and some scheduled task stacks are not printed, which is very inconvenient for troubleshooting production problems.
[0004] Therefore, it is necessary to design a new method to ensure that scheduled tasks can correctly complete business logic processing, detect anomalies in a timely manner, and facilitate problem troubleshooting. Summary of the invention
[0005] The present invention provides a scheduled task execution record monitoring method, device, computer equipment and storage medium to solve the technical problems that the abnormal execution of scheduled tasks requires manual repair of abnormal data, wastes manpower, and the log printing is incomplete, which is very inconvenient for troubleshooting production problems.
[0006] In the first aspect, a method for monitoring the execution record of a scheduled task is provided, including:
[0007] Load custom configuration parameters to obtain configuration information;
[0008] Record the start execution log of the scheduled task, and perform a pre-check on the scheduled task according to the configuration information;
[0009] If the pre-check passes, the scheduled task is processed to obtain a processing result;
[0010] Performing post-check on the processing result according to the configuration information;
[0011] If the post-check passes, the scheduled task processing end log is recorded to obtain a log record document.
[0012] In a second aspect, a scheduled task execution record monitoring device is provided, including:
[0013] A loading unit, used to load custom configuration parameters to obtain configuration information;
[0014] A recording execution unit, used to record the start execution log of the scheduled task and perform a pre-check on the scheduled task according to the configuration information;
[0015] A processing unit, configured to process the scheduled task if the pre-check passes, to obtain a processing result;
[0016] An execution unit, configured to perform a post-check on the processing result according to the configuration information;
[0017] The recording unit is used to record the end log of the scheduled task processing if the post-check passes, so as to obtain a log record document.
[0018] In a third aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned scheduled task execution record monitoring method when executing the computer program.
[0019] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned scheduled task execution record monitoring method are implemented.
[0020] The above-mentioned scheduled task execution record monitoring method loads custom configuration parameters to obtain configuration information, records the scheduled task start execution log, and performs a pre-check on the scheduled task according to the configuration information. If the pre-check passes, the scheduled task is processed to obtain the processing result, and a post-check is performed on the processing result according to the configuration information. If the post-check passes, the scheduled task processing end log is recorded to obtain a log record document. By using the scheduled task execution record monitoring, it is ensured that the scheduled task correctly completes the business logic processing, and anomalies can be discovered in time, which is convenient for problem troubleshooting.
[0021] The present invention is further described below in conjunction with the accompanying drawings and specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.
[0023] Figure 1 A schematic diagram of an application scenario of the scheduled task execution record monitoring method provided by an embodiment of the present invention;
[0024] Figure 2 A flowchart of a method for monitoring the execution records of scheduled tasks provided by an embodiment of the present invention;
[0025] Figure 3 A schematic block diagram of a scheduled task execution record monitoring device provided by an embodiment of the present invention;
[0026] Figure 4 It is a schematic diagram of the structure of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION
[0027] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0028] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.
[0029] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.
[0030] It should be further understood that the term "and / or" used in the present description and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.
[0031] See also Figure 1 and Figure 2 , Figure 1 A schematic diagram of an application scenario of the scheduled task execution record monitoring method provided in an embodiment of the present invention. Figure 2A schematic flow chart of a scheduled task execution record monitoring method provided in an embodiment of the present invention. The scheduled task execution record monitoring method is applied in a server. The server interacts with a terminal, and a processing framework is integrated on the terminal. Custom configuration parameters can be loaded to obtain configuration information, record the start execution log of the scheduled task, and perform a pre-check on the scheduled task according to the configuration information. If the pre-check passes, the scheduled task is processed to obtain a processing result, and a post-check is performed on the processing result according to the configuration information. If the post-check passes, the scheduled task processing end log is recorded to obtain a log record document, which ensures that the scheduled task correctly completes the business logic processing, can detect anomalies in time, and facilitates problem troubleshooting.
[0032] Figure 2 FIG. 1 is a flow chart of a method for monitoring the execution record of a scheduled task provided by an embodiment of the present invention. Figure 2 As shown, the method includes the following steps S110 to S150.
[0033] S110: Load custom configuration parameters to obtain configuration information.
[0034] In this embodiment, scheduled tasks include data backup, data update, website update, script execution, etc. The configuration parameters include pre-verifier, scheduling processor, post-verifier, scheduling type, task execution result table, task execution detail table, database name, execution step length, and maximum number of loops.
[0035] Specifically, the processing framework can be used to customize configuration parameters and load them to obtain configuration information, which includes:
[0036] The pre-verifier is used for pre-verification of task execution. It mainly checks the input parameters or data by writing verification rules or logic to ensure that they meet specific conditions or standards. It can also use regular expressions, logical judgments, database queries, etc. for verification.
[0037] The scheduling processor is used for task execution control. It can decide when and how to execute tasks based on preset scheduling strategies or algorithms. The scheduling processor may include different levels of scheduling, such as job scheduling (high-level scheduling), intermediate scheduling (memory scheduling) and process scheduling (low-level scheduling). In the data processing platform, the scheduling processor can be responsible for task allocation, resource scheduling and determination of execution order.
[0038] The post-verifier is used for post-verification of task execution. After the task is completed, the output data or results are verified to ensure that they meet the expected standards or requirements. The post-verifier includes data integrity verification, result accuracy verification, performance evaluation and other aspects.
[0039] Scheduling types include single scheduling and cyclic scheduling. For example, some tasks process a small amount of data and are executed in one go; some tasks process a large amount of data, with millions of data to be processed, and need to be processed in batches and cyclically.
[0040] The task execution result table is used to record the entire task execution result, such as success, failure, exception, etc.
[0041] The task execution details table is used to record the results of each cycle processing, such as the execution time of each cycle, the amount of data processed, etc.
[0042] Database name. A system may have multiple data sources. You need to configure which database table the task execution record is stored in.
[0043] Execution step length: for loop scheduling, how long to query data each time.
[0044] Maximum number of loops, for loop scheduling, defines the maximum number of times or loops a task can be executed.
[0045] Whether the post-check is turned on, each cycle is used to check whether the result meets the expectation.
[0046] Whether the global check is enabled, and whether the result meets expectations after the entire cycle is completed.
[0047] S120, recording a log of the start of execution of the scheduled task, and performing a pre-check on the scheduled task according to the configuration information.
[0048] Specifically, when a scheduled task is about to start executing, the system will record a log in the log system, indicating that the task has started executing. The pre-verification of the scheduled task is performed by checking whether the latest task exists in the scheduled task through the pre-verifier. In other words, first obtain the scheduled task list, and then filter out the latest task from the task list according to the definition of the latest task (such as creation time, update time, etc.), and then check the filtering results. If the latest task exists, continue to execute the subsequent pre-verification logic; if it does not exist, the scheduled task may end execution.
[0049] In this embodiment, after recording the start execution log of the scheduled task and performing a pre-check on the scheduled task according to the configuration information, the method further includes:
[0050] If there is no latest task in the scheduled task, the pre-verification fails, the scheduled task processing ends, and the pre-verification result is generated and recorded in the task execution result table. That is to say, in the pre-verification stage, the system will determine whether there is a latest task in the scheduled task based on the configuration information and business logic, which usually involves querying the database, accessing the cache or calling other services to obtain the task list, and determining whether the latest task exists based on the creation time, update time or specific mark of the task. If the system determines that there is no latest task in the scheduled task, the pre-verification will fail. At this time, the system will generate a result of pre-verification failure, which may contain key information such as the cause of failure, timestamp, task ID, etc. Once the pre-verification fails, the system will not continue to execute other processing logic of the scheduled task, which means that the execution process of the task is interrupted here and will not proceed to the subsequent steps. The system will record the results of the pre-verification in the task execution result table, which is a data structure for storing various results and states generated during the execution of the task, which may include database tables, log files or message queues, etc. The recorded results may include the specific cause of the pre-verification failure, task ID, execution time, etc., for subsequent analysis and auditing.
[0051] S130: If the pre-check passes, process the scheduled task to obtain a processing result.
[0052] In this embodiment, if the pre-check passes, processing the scheduled task to obtain a processing result includes:
[0053] If there is a latest task in the scheduled tasks, the pre-check passes, and the latest task in the scheduled tasks is processed to obtain the processing result.
[0054] Specifically, before executing a scheduled task, a pre-verification is performed first. The latest task information can be obtained by querying the database, accessing the memory cache, or calling other services. Once the latest task is determined, the system will start processing this task. The processing process may include executing specific business logic, calling external services, updating the database, etc.
[0055] S140: Perform a post-check on the processing result according to the configuration information.
[0056] In this embodiment, performing post-check on the processing result according to the configuration information includes:
[0057] The post-verifier is used to verify whether the processing result corresponds to the scheduled task.
[0058] Specifically, the post-verifier is a tool or component specifically used to verify whether the processing result meets the expectations. The post-verifier may also be a class, function or module, which contains specific verification logic and algorithms. The system obtains the processing results of the scheduled task, which may be data, status code or message returned after the task is executed. The processing results are usually stored in temporary variables, database tables or message queues, and the system will read them according to the actual situation. The system passes the processing results to the post-verifier and calls its verification method. The post-verifier verifies the processing results according to the configuration information and specific verification logic to determine whether the processing results correspond to the scheduled task. The verification process may involve operations such as data comparison, status check, and rule matching. If the verification passes, the system may record success information or proceed to the next step; if the verification fails, the system may record error information, trigger an alarm or execute other exception handling processes. The verification results are usually recorded in log files, database tables or message queues for subsequent analysis and auditing.
[0059] In this embodiment, after performing post-check on the processing result according to the configuration information, the method further includes:
[0060] If the post-verification fails, the reason for the verification failure is recorded.
[0061] Specifically, the system first performs post-check on the processing result of the scheduled task according to the configuration information. The post-check may involve checking multiple aspects of the processing result, such as data integrity, business logic consistency, whether the state change is in line with expectations, etc. After the post-check is completed, the system will determine whether the check result is passed. The check result is usually a Boolean value (true / false) or an object containing detailed information to indicate whether the check is successful. If the post-check fails (that is, the check result is false or contains error information), the system will record the reason for the check failure. The failure reason may be a string, an error code, or an object containing detailed error information. The way to record the failure reason may include writing a log file, updating a database record, or sending an alarm message. The recorded content usually includes the time when the check failed, the task ID, the processing result summary, the failure reason, and possible solutions. This information is helpful for subsequent troubleshooting, fault analysis, and system optimization. In addition, recording the reason for the check failure helps developers or operation and maintenance personnel quickly locate the problem. By analyzing the failure reason, you can quickly understand the specific cause of the check failure and take corresponding repair measures. In addition, by recording the reasons for verification failure, the system can promptly detect and handle potential problems to prevent them from expanding or affecting other system components, which helps improve the stability and reliability of the system. In addition, by analyzing the reasons for verification failure, enterprises can understand the bottlenecks or deficiencies that may exist in the execution of scheduled tasks, which helps optimize business processes and improve the efficiency and accuracy of task execution. In addition, in some industries or enterprises, recording the reasons for verification failure may be part of the compliance requirements. By recording this information, it can ensure that the system complies with the requirements of relevant regulations and standards.
[0062] S150: If the post-check passes, a scheduled task processing end log is recorded to obtain a log record document.
[0063] In this embodiment, if the post-check passes, a scheduled task processing end log is recorded to obtain a log record document, including:
[0064] If the processing result corresponds to the scheduled task, the post-check passes, and the scheduled task processing end log is recorded to obtain a log record document, which includes the task execution result table and the task execution detail table.
[0065] Specifically, the system first performs a post-check on the processing result of the scheduled task according to the configuration information and the verification rules. If the processing result meets the expected output of the scheduled task, that is, the processing result corresponds to the scheduled task, then the post-check is judged to be passed. Once the post-check is passed, the system is ready to record the log of the end of the scheduled task processing. The system builds a log record document, which includes a task execution result table and a task execution detail table. The task execution result table usually contains the overall execution status of the task (such as success, failure, partial success, etc.), key output data or status code, etc. The task execution detail table records in detail each step of the task execution process, input data, output data, execution timestamp and other detailed information. The constructed log record document is stored in a specified log storage system, such as a file system, database or log management system. The system provides a log access interface or tool so that developers, operation and maintenance personnel or auditors can easily query and analyze log records. In addition, by recording the log of the end of the scheduled task processing, the system can fully track the execution process of the task, which helps to understand when the task starts, when it ends, what operations are performed, and what the final result is. When a problem occurs during task execution, developers or operation and maintenance personnel can quickly locate the problem by viewing the task execution details in the log record document. Detailed log information helps analyze the root cause of the problem and take appropriate repair measures. In addition, by analyzing the task execution time and resource consumption in the log record document, enterprises can understand the performance bottleneck of scheduled tasks, which helps optimize the task execution process, improve system performance and reduce operating costs.
[0066] In the above-mentioned scheduled task execution record monitoring method, the pre-verification ensures that the task meets the execution conditions. When the task execution does not meet the conditions and is mistakenly executed, it is easy to cause production accidents or generate dirty data. In the past, if a task has similar business requirements, the developers usually write the pre-verification code themselves. Due to the different ability levels of developers, developers with poorer abilities simply add a judgment condition and return directly if the condition is not met, lacking log records. If there are problems later, it is difficult to find the problem when troubleshooting why the task is not executed. In the previous code, the verification logic and the business execution logic are put together, the logic is complex, and it is difficult to test and read. The pre-verifier in this embodiment is a pluggable component that is added only when the user needs it. It is interface-oriented programming and introduced in the form of configuration items. It is less invasive and convenient for testing and dynamic adjustment.
[0067] The post-validator ensures that the business logic is executed according to the expected results. For example, if a scheduled task synchronizes the data of table A to table B, if a data processing exception causes the synchronization to fail, the data of tables A and B will be inconsistent. Such a small number of exceptions are generally difficult to detect. With the post-validator, the validation logic is to compare the number of data in tables A and B to see if they are consistent, and detect problems in advance.
[0068] Logging is very important for troubleshooting and monitoring. Logging is divided into two dimensions: one is whether the execution of the entire task is successful, and the other is whether the pre-check and post-check are successful. The execution status is recorded in the database table. SQL statements can be written to allow operation and maintenance to configure monitoring alarms. For records of abnormal execution, they can be discovered in advance through email alarms.
[0069] To facilitate understanding of the scheduled task execution record monitoring method, the following example is provided:
[0070] For example, the A database synchronizes data to the B database, and the data volume is several million. The requirement is to synchronize the latest data from the A database to the B database. In the middle, some processing is required and finally written into the B database. There may be some processing exceptions in the middle, which causes some data to fail to be synchronized to the B database. Before this, data synchronization failures are difficult to detect, resulting in production data being confirmed, affecting user experience. After using this scheduled task execution record monitoring method, configure the pre-verifier. Before the task is executed, check whether there is the latest data of the day in the A database. If there is no latest data, the task execution ends and the verification result is recorded in the task execution table for easy monitoring. During the task execution, there may be some data processing exceptions, resulting in synchronization failure, which will be recorded in the task results and detailed tables. Monitoring can check the failure records and find problems in time. After the data synchronization is completed, the post-verifier verifies again whether the number of records that need to be synchronized in the A database is consistent with the data that has been synchronized in the B database to avoid data leakage. Because the data volume is large and cannot be processed at one time, it is necessary to use a cyclic processing method to synchronize data in batches.
[0071] The above-mentioned scheduled task execution record monitoring method obtains configuration information by loading custom configuration parameters, records the start execution log of the scheduled task, and performs pre-verification on the scheduled task according to the configuration information. If the pre-verification passes, the scheduled task is processed to obtain the processing result, and the post-verification is performed on the processing result according to the configuration information. If the post-verification passes, the scheduled task processing end log is recorded to obtain a log record document. The use of scheduled task execution record monitoring ensures that the scheduled task correctly completes the business logic processing, can detect anomalies in time, and facilitates problem troubleshooting. At the code level, pre-verifiers, post-verifiers, and log records are provided, and a unified processing flow is provided to allow developers to focus on business logic processing, reduce development time, and make the code more concise, easy to test and maintain. Verifiers are connected in a configured manner, and the access and shutdown of verifiers can be controlled without the need for new versions.
[0072] Figure 3 FIG. 3 is a schematic block diagram of a timed task execution record monitoring device 300 provided in an embodiment of the present invention. Figure 3 As shown, corresponding to the above scheduled task execution record monitoring method, the present invention also provides a scheduled task execution record monitoring device 300. The scheduled task execution record monitoring device 300 includes a unit for executing the above scheduled task execution record monitoring method, and the device can be configured in a server. Figure 3 , the scheduled task execution record monitoring device 300 includes a loading unit 301, a record execution unit 302, a processing unit 303, an execution unit 304 and a recording unit 305;
[0073] The loading unit 301 is used to load the custom configuration parameters to obtain configuration information;
[0074] The recording and executing unit 302 is used to record the start execution log of the scheduled task and perform a pre-check on the scheduled task according to the configuration information;
[0075] The processing unit 303 is used to process the scheduled task to obtain a processing result if the pre-check passes;
[0076] An execution unit 304 is used to perform a post-check on the processing result according to the configuration information;
[0077] The recording unit 305 is used to record the scheduled task processing end log if the post-check passes, so as to obtain a log record document.
[0078] In one embodiment, the configuration parameters include a pre-verifier, a scheduling processor, a post-verifier, a scheduling type, a task execution result table, a task execution detail table, a database name, an execution step length, and a maximum number of loops.
[0079] In one embodiment, the record execution unit 302 uses the pre-verifier to verify whether there is a latest task in the scheduled tasks.
[0080] In one embodiment, in the processing unit 303, if there is a latest task in the scheduled tasks, the pre-check passes, and the latest task in the scheduled tasks is processed to obtain a processing result.
[0081] In one embodiment, the scheduled task execution record monitoring device 300 also includes a record generation unit, which is used to generate a pre-verification result and record it in the task execution result table if there is no latest task in the scheduled task, the pre-verification fails, the scheduled task processing ends.
[0082] In one embodiment, the execution unit 304 verifies whether the processing result corresponds to the scheduled task by using the post-verifier.
[0083] In one embodiment, in the recording unit 305, if the processing result corresponds to the scheduled task, the post-verification passes, and the scheduled task processing end log is recorded to obtain a log record document, which includes the task execution result table and the task execution details table.
[0084] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the above-mentioned scheduled task execution record monitoring device 300 and each unit can refer to the corresponding description in the aforementioned method embodiment, and for the convenience and brevity of description, it will not be repeated here.
[0085] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 4 As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client via a network connection. When the computer program is executed by the processor, it implements the functions or steps on the server side of a scheduled task execution record monitoring method.
[0086] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:
[0087] Load custom configuration parameters to obtain configuration information; record the start execution log of the scheduled task, and perform a pre-check on the scheduled task according to the configuration information; if the pre-check passes, process the scheduled task to obtain a processing result; perform a post-check on the processing result according to the configuration information; if the post-check passes, record the end log of the scheduled task processing to obtain a log record document.
[0088] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
[0089] Load custom configuration parameters to obtain configuration information; record the start execution log of the scheduled task, and perform a pre-check on the scheduled task according to the configuration information; if the pre-check passes, process the scheduled task to obtain a processing result; perform a post-check on the processing result according to the configuration information; if the post-check passes, record the end log of the scheduled task processing to obtain a log record document.
[0090] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can refer to the relevant descriptions on the server side and the client side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.
[0091] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
[0092] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.
[0093] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.
Claims
1. A method for monitoring the execution record of a scheduled task, characterized in that: include: Load custom configuration parameters to obtain configuration information; Record the start execution log of the scheduled task, and perform a pre-check on the scheduled task according to the configuration information; If the pre-check passes, the scheduled task is processed to obtain a processing result; Performing post-check on the processing result according to the configuration information; If the post-check passes, the scheduled task processing end log is recorded to obtain a log record document.
2. The method for monitoring the execution record of scheduled tasks according to claim 1, characterized in that: The configuration parameters include a pre-verifier, a scheduling processor, a post-verifier, a scheduling type, a task execution result table, a task execution detail table, a database name, an execution step length, and a maximum number of loops.
3. The method for monitoring the execution record of scheduled tasks according to claim 2, characterized in that: The recording of the start of execution of the scheduled task log and performing a pre-check on the scheduled task according to the configuration information include: The pre-verifier is used to verify whether there is a latest task in the scheduled tasks.
4. The method for monitoring the execution record of scheduled tasks according to claim 3, characterized in that: If the pre-check passes, processing the scheduled task to obtain a processing result includes: If there is a latest task in the scheduled tasks, the pre-check passes, and the latest task in the scheduled tasks is processed to obtain the processing result.
5. The method for monitoring the execution record of scheduled tasks according to claim 3, characterized in that: After recording the start execution log of the scheduled task and performing a pre-check on the scheduled task according to the configuration information, the method further includes: If there is no latest task in the scheduled tasks, the pre-verification fails, the scheduled task processing ends, and the pre-verification result is generated and recorded in the task execution result table.
6. The method for monitoring the execution record of scheduled tasks according to claim 2, characterized in that: The performing post-check on the processing result according to the configuration information comprises: The post-verifier is used to verify whether the processing result corresponds to the scheduled task.
7. The method for monitoring the execution record of scheduled tasks according to claim 6, characterized in that: If the post-check passes, the scheduled task processing end log is recorded to obtain a log record document, including: If the processing result corresponds to the scheduled task, the post-check passes, and the scheduled task processing end log is recorded to obtain a log record document, which includes the task execution result table and the task execution detail table.
8. A timed task execution record monitoring device, characterized in that: include: A loading unit, used to load custom configuration parameters to obtain configuration information; A recording execution unit, used to record the start execution log of the scheduled task and perform a pre-check on the scheduled task according to the configuration information; A processing unit, configured to process the scheduled task if the pre-check passes, to obtain a processing result; An execution unit, configured to perform a post-check on the processing result according to the configuration information; The recording unit is used to record the end log of the scheduled task processing if the post-check passes, so as to obtain a log record document.
9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the scheduled task execution record monitoring method as described in any one of claims 1 to 7 are implemented.
10. A storage medium, wherein the computer-readable storage medium stores a computer program, characterized in that: When the computer program is executed by a processor, the steps of the scheduled task execution record monitoring method as described in any one of claims 1 to 7 are implemented.