CN111984454B

CN111984454B - Task timeout monitoring method, device and storage medium

Info

Publication number: CN111984454B
Application number: CN202010894974.4A
Authority: CN
Inventors: 殷昊
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2020-08-31
Filing date: 2020-08-31
Publication date: 2023-08-22
Anticipated expiration: 2040-08-31
Also published as: CN111984454A

Abstract

The embodiment of the specification provides a task timeout monitoring method, a device and a storage medium, wherein the method comprises the following steps: collecting the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime, thereby ensuring that the problem of overtime of the running task is found out early.

Description

Task timeout monitoring method, device and storage medium

Technical Field

Embodiments of the present disclosure relate to the field of data processing technologies, and in particular, to a task timeout monitoring method, device, and storage medium.

Background

Batch processing is the most important technical form of the whole information background in banking industry, and is also an important technical means for sharing, transmitting and evolving bank core information asset data. The banking industry has been informationized for many years to build tens or even hundreds of information systems gradually, wherein most of system backrests have work batch processing with different scales, and the total batch work number has developed into a huge scale of thousands to tens of thousands. With the advent of the big data age, especially under the drive of data warehouse and big data platform, the scale will develop rapidly, and the scale of batch operation will also have to produce an order of magnitude increase.

Typically the system takes some time to complete the batch process. However, due to slow system storage, false progress, etc., batch processing time-out may occur. Once timeout occurs, system resources are occupied for a long time, so that the system resources cannot be released. In the prior art, a timeout threshold can be set, the time of batch processing by the system is monitored, and if the time exceeds the set timeout threshold, alarm information is sent to prompt that the batch processing is overtime.

Each job in the batch is required to be processed in the batch processing, wherein each job in the batch processing corresponds to a task, and when all the tasks are processed, the completion of the batch processing is indicated. A batch processing timeout may be when a job in a batch has timed out during processing, resulting in subsequent job processing also timed out. In the prior art, besides the time of batch processing by a monitoring system, the operation with overtime history can be monitored.

The method for setting batch overtime monitoring points aiming at batch overall operation conditions is insufficient in precision, and once overtime occurs, certain service influences are likely to be unavoidable. If some job timeouts are not completed by the initial stage of the batch, rather than by a history of timeout, the impact time may be long.

Disclosure of Invention

The embodiment of the specification aims to provide a task timeout monitoring method, device and storage medium so as to ensure that a task operation timeout problem is discovered early.

In order to solve the above problem, an embodiment of the present disclosure provides a task timeout monitoring method, including: collecting the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime.

To solve the above problem, embodiments of the present disclosure further provide a task timeout monitoring device, which includes: the acquisition module is used for acquiring the running time of the running task at a preset frequency; the selection module is used for selecting a baseline corresponding to the current date from the baseline set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and the determining module is used for determining that the running task is overtime if the exceeding part is larger than a preset threshold under the condition that the running duration exceeds the base line corresponding to the current date.

To solve the above problem, embodiments of the present disclosure further provide an electronic device, including: a memory for storing a computer program; a processor for executing the computer program to implement: collecting the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime.

To solve the above problems, the embodiments of the present specification further provide a computer-readable storage medium having stored thereon computer instructions that, when executed, implement: collecting the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime.

As can be seen from the technical solutions provided in the embodiments of the present disclosure, the running duration of the running task may be collected at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime. According to the method provided by the embodiment of the specification, each task is comprehensively monitored in an automatic mode, so that the problem of task operation overtime is guaranteed to be found early, enough processing windows are provided, and normal development of the service is guaranteed not to be influenced.

Drawings

In order to more clearly illustrate the embodiments of the present description or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present description, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flowchart of a task timeout monitoring method according to an embodiment of the present disclosure;

fig. 2 is a schematic functional structural diagram of an electronic device according to an embodiment of the present disclosure;

fig. 3 is a schematic functional structural diagram of a task timeout monitor according to an embodiment of the present disclosure.

Detailed Description

The technical solutions of the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

In this embodiment of the present disclosure, the batch may include a bank backend system running a series of jobs at night to check, count, generate reports, synchronize inter-system data, etc. transaction information, customer information, account information on the same day (or on the same month or on the same season). The job may be a step in a batch process, may be a function point, or may be a small set of function points. Each job in the batch is required to be processed in the batch processing, wherein each job in the batch processing corresponds to a task, and when all the tasks are processed, the completion of the batch processing is indicated.

The existing technical means only can monitor the whole operation timeout of batches or independently set timeout time threshold values for the operation which has problems in the past, and lack of operation level timeout monitoring for covering all the operations of batches, and once timeout occurs, certain service influences are likely to be unavoidable. If some job timeouts are not completed by the initial stage of the batch, rather than by a history of timeout, the impact time may be long. Considering that if each task in the batch is monitored comprehensively, different overtime monitoring mechanisms are set for different dates, the problem of insufficient precision in a mode of setting batch overtime monitoring points for the whole running condition of the batch is hopefully solved, the problem of overtime running of the task is ensured to be found out as soon as possible, enough processing windows are provided, and normal development of the business is ensured not to be influenced.

Please refer to fig. 1. The embodiment of the description provides a task timeout monitoring method. In the embodiment of the present specification, the main body that performs the task timeout monitoring method may be an electronic device having a logical operation function, and the electronic device may be a server. The server may be an electronic device with a certain arithmetic processing capability. Which may have a network communication unit, a processor, a memory, etc. Of course, the server is not limited to the electronic device with a certain entity, and may be software running in the electronic device. The server may also be a distributed server, and may be a system having a plurality of processors, memories, network communication modules, etc. operating in concert. Alternatively, the server may be a server cluster formed for several servers. The method may comprise the following steps.

S110: and collecting the running time of the running task at a preset frequency.

In some embodiments, the run time of the running task may be collected at intervals. The preset frequency range includes each time of 10-100 seconds, the specific frequency may be selected according to the accuracy of the overtime monitoring of the expected task, the higher the expected accuracy is, the higher the acquisition frequency may be selected, and the accuracy expected may be satisfied in the frequency range of each time of 10-100 seconds. Of course, if higher accuracy is desired, higher acquisition frequencies may also be selected, such as 3 seconds each, 5 seconds each, etc.; if the accuracy is desired to be low, a lower acquisition frequency may be selected, such as 120 seconds each time, 150 seconds each time, etc., although the acquisition frequency may be other values, which are not limited in the embodiment of the present disclosure.

In some embodiments, the server may query the running task by querying a data table record, and then obtain the time when the running task starts to run, and take the difference between the current system time and the starting running time of the task as the running duration of the running task. Specifically, the running time of the task can be subtracted from the current system time, and the difference value is the running time of the task.

S120: selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set includes a plurality of different baselines, the different baselines representing different timeout reference values.

In some embodiments, the baseline is a time concept that is calculated based on categorization of task runs in previous daily batches. The baseline may be used to represent a timeout reference value of the task, that is, whether the task runs out, may be determined according to the timeout reference value, and specifically, whether the task runs out may be determined according to whether the running time of the task exceeds the timeout reference value, and how much the running time exceeds the timeout reference value.

In some embodiments, the task execution is different due to different types of date lots. For example, for weekdays and holidays, the total amount of tasks in the batch and the task execution completion time in the period batch are different. Thus, different baselines may be generated depending on the type of date, e.g., the timeout reference value for a baseline for a weekday may be higher and the timeout reference value for a corresponding baseline for a weekday may be lower.

In some embodiments, the type of date may include some special days in addition to workdays, rest days, and in banking areas, special days may be dates that require special treatment for tasks in the batch, such as day of interest, month end, etc. Of course, the type of date may also include some other special days, such as twenty-one, etc., which are not limited by the present embodiments.

In some embodiments, the baseline set may include a plurality of different baselines, such as a baseline for a weekday, a baseline for a special day, and the like. For example, for JOB001, the baseline corresponding to the working day may be calculated according to the running condition of the task on the previous working day, and may be set to 15 minutes, for example; the baseline corresponding to the holiday can be calculated according to the running condition of the task on the previous holiday, for example, the baseline can be set to be 5 minutes; the baselines corresponding to special days (month end, day of interest, twenty, etc.) can be configured by the user according to the characteristics of the server itself, and a few baselines are determined. If the server has special treatment at the end of a month and the task running time in the batch is greatly different from other dates, a baseline corresponding to the end of a month can be set, and then the server calculates the baseline according to the task running condition in the batch at the end of the month, for example, 30 minutes can be set. If the server has special treatment different from the end of month on the date of interest, and the running condition of tasks in the batch is special, a base line corresponding to the date of interest can be set. Of course, the tasks in the special day batch have different characteristics in running, so that the base line corresponding to the special day can be customized, for example, the 'double eleven' of each year is customized as a special day, and a base line corresponding to the double eleven is set.

In some embodiments, the selecting a baseline corresponding to the current date from the baseline set according to the preset rule includes: determining the type of the current date, and selecting a baseline corresponding to the type of the current date from the baseline set.

In some embodiments, the current date may be a work day or a special day such as a month end, a day of interest, etc., since the current date may be of two or more types at the same time. Thus, it is possible to determine which type of date the current date belongs to according to the following priority order: firstly judging whether the current date belongs to a special day, if not, judging whether the current date belongs to a working day or a rest day; of course, if the current date is judged to belong to a special day, it is no longer judged whether the current date belongs to a working day or a rest day.

In some embodiments, the current date may also be the end of the month and the date of the interest, or other special days of the month, etc., as the special days may include the end of the month, the date of the interest, and other special days. Thus, it is possible to determine which type of date the current date belongs to according to the following priority order: firstly judging whether the current date belongs to other special days, if so, determining that the current date is other special days, and not carrying out subsequent judgment; if not, judging whether the current date belongs to the date of interest, if so, judging whether the current date is the date of interest, and if not, judging whether the current date belongs to the end of the month.

S130: and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime.

In some embodiments, the running duration of the running task and the baseline corresponding to the current date can be compared, and if the running duration exceeds the baseline corresponding to the current date, if the exceeding part is greater than a preset threshold, the running timeout of the running task is determined

In some embodiments, the preset threshold may be determined according to a baseline, for example, the preset threshold may be 10%, 20%, 25% of the baseline, or other values, and may be set according to practical situations, where specific values of the preset threshold are not limited in this specification.

In some embodiments, the normal running completion time of the task may increase or decrease with the optimization of the system or the increase of the coupling degree of the system over time, and if it is further determined based on the original baseline whether the running time of the task is overtime, it may not be suitable. Thus, in embodiments of the present description, the step of updating the baseline may also be included: in the current date, after the operation of a plurality of tasks in the batch is completed, updating a baseline corresponding to the current date according to the operation time of the plurality of tasks; the updated baseline is added to the baseline to replace the pre-updated baseline.

In some embodiments, the baseline may be updated using a dynamic weighting method. For example, when the baseline corresponding to the current date of a task job_a is T and the task running completion time of the day job_a is T, after the task running in the batch of the day is finished, the baseline corresponding to the day of the task may be updated to tx (1-a%) +tx a%. Wherein, the value of a can be a default value or can be set by oneself, and the value range is [1,100]. If the value of a is a default value, the following value rule may be used: taking 3 corresponding to the baseline on the working day; taking a baseline corresponding to the rest day 7; taking 15 corresponding to the baseline at the end of the month; taking a base line corresponding to the date of interest 25; the other special day takes 100/d, where d is the number of days in a year for that special day.

The task timeout monitoring method provided by the embodiment of the specification can collect the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime. According to the method provided by the embodiment of the specification, each task is comprehensively monitored in an automatic mode, so that the problem of task operation overtime is guaranteed to be found early, enough processing windows are provided, and normal development of the service is guaranteed not to be influenced.

Fig. 2 is a schematic functional structure diagram of an electronic device according to an embodiment of the present disclosure, where the electronic device may include a memory and a processor.

In some embodiments, the memory may be used to store the computer program and/or module, and the processor implements various functions of task timeout monitoring by running or executing the computer program and/or module stored in the memory, and invoking data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for a function; the storage data area may store data created according to the use of the user terminal. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, memory, plug-in hard disk, smart Media Card (SMC), secure Digital (SD) Card, flash Card (Flash Card), at least one disk storage device, flash memory device, or other volatile solid-state storage device.

The processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (APPlication Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The processor may execute the computer instructions to implement the steps of: collecting the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime.

In the embodiments of the present disclosure, the specific functions and effects of the electronic device may be explained in comparison with other embodiments, which are not described herein.

Fig. 3 is a schematic functional structural diagram of a task timeout monitoring device according to an embodiment of the present disclosure, where the device may specifically include the following structural modules.

The acquisition module 310 is configured to acquire an operation duration of an operating task at a preset frequency;

a selection module 320, configured to select, from the baseline set, a baseline corresponding to the current date according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values;

and the determining module 330 is configured to determine that the running task is running out if the running duration exceeds the baseline corresponding to the current date and the exceeding part is greater than a preset threshold.

In some embodiments, the device may further include an updating module, configured to update, after the running of the plurality of tasks on the current date is completed, a baseline corresponding to the current date according to running durations of the plurality of tasks; the updated baseline is added to the baseline to replace the pre-updated baseline.

The embodiments of the present specification also provide a computer readable storage medium of a task timeout monitoring method, the computer readable storage medium storing computer program instructions that when executed implement: collecting the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; and under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime.

In the present embodiment, the storage medium includes, but is not limited to, a random access Memory (Random Access Memory, RAM), a Read-Only Memory (ROM), a Cache (Cache), a Hard Disk (HDD), or a Memory Card (Memory Card). The memory may be used to store the computer program and/or the module, and the memory may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the user terminal, etc. Further, the memory may include a high-speed random access memory, and may also include a nonvolatile memory. In the embodiment of the present disclosure, the functions and effects specifically implemented by the program instructions stored in the computer readable storage medium may be explained in comparison with other embodiments, which are not described herein.

It should be noted that the task timeout monitoring method, device and storage medium provided in the embodiments of the present disclosure may be applied to the technical field of data processing. Of course, the method and the device for monitoring task timeout and the application field of the storage medium are not limited in the embodiments of the present disclosure, and the method and the device may be applied to any field other than the financial field.

It should be noted that, in the present specification, each embodiment is described in a progressive manner, and the same or similar parts of each embodiment are referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments and the apparatus embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments in part.

Those skilled in the art, after reading this specification, will recognize without undue burden that any and all of the embodiments set forth herein can be combined, and that such combinations are within the scope of the disclosure and protection of the present specification.

In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented with "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but HDL is not only one, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog2 are most commonly used at present. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

From the above description of embodiments, it will be apparent to those skilled in the art that the present description may be implemented in software plus a necessary general purpose hardware platform. Based on this understanding, the technical solution of the present specification may be embodied in essence or a part contributing to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present specification.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The specification is operational with numerous general purpose or special purpose computer system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

The description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

Although the present specification has been described by way of example, it will be appreciated by those skilled in the art that there are many variations and modifications to the specification without departing from the spirit of the specification, and it is intended that the appended claims encompass such variations and modifications as do not depart from the spirit of the specification.

Claims

1. A method for monitoring task timeout, the method comprising:

collecting the running time of the running task at a preset frequency;

selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values;

under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime;

wherein, selecting the baseline corresponding to the current date from the baseline set according to the preset rule includes:

determining the type of the current date;

selecting a baseline corresponding to the current date type from the baseline set;

wherein the date types include workdays, rest days and special days; wherein the special day comprises: the day and month ends of the rest.

2. The method of claim 1, wherein the running task is queried by querying a database table record.

3. The method of claim 1, wherein the collecting the run time of the running task comprises:

acquiring the starting running time of a running task;

and taking the difference value between the current system time and the starting running time of the task as the running time of the running task.

4. The method of claim 1, wherein the predetermined range of frequencies comprises 10-100 seconds each.

5. The method according to claim 1, wherein the method further comprises:

after the operation of a plurality of tasks on the current date is completed, updating a baseline corresponding to the current date according to the operation time of the plurality of tasks;

the updated baseline is added to the baseline to replace the pre-updated baseline.

6. The method of claim 5, further comprising, prior to updating the baseline corresponding to the current date according to the run lengths of the plurality of tasks:

removing abnormal tasks according to the running completion conditions of a plurality of tasks on the current date;

and updating the base line corresponding to the current date according to the running time of the plurality of tasks after the abnormal task is removed.

7. The method of claim 6, wherein the abnormal task comprises at least one of a task that runs in error, a task that completes after a timeout of running, and a task that a user marks as abnormal.

8. A task timeout monitoring device, the device comprising:

the acquisition module is used for acquiring the running time of the running task at a preset frequency;

the selection module is used for selecting a baseline corresponding to the current date from the baseline set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values;

the determining module is used for determining that the running task is overtime if the exceeding part is larger than a preset threshold value under the condition that the running duration exceeds the base line corresponding to the current date;

determining the type of the current date;

9. The apparatus of claim 8, wherein the apparatus further comprises:

the updating module is used for updating the base line corresponding to the current date according to the running time of the tasks after the tasks on the current date are run; the updated baseline is added to the baseline to replace the pre-updated baseline.

10. An electronic device, comprising:

a memory for storing a computer program;

a processor for executing the computer program to implement: collecting the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime; wherein, selecting the baseline corresponding to the current date from the baseline set according to the preset rule includes: determining the type of the current date; selecting a baseline corresponding to the current date type from the baseline set; wherein the date types include workdays, rest days and special days; wherein the special day comprises: the day and month ends of the rest.

11. A computer-readable storage medium having stored thereon computer instructions that, when executed, implement: collecting the running time of the running task at a preset frequency; selecting a base line corresponding to the current date from the base line set according to a preset rule; wherein the baseline represents a timeout reference value for task operation; the baseline set comprises a plurality of different baselines, and the different baselines represent different timeout reference values; under the condition that the running time length exceeds the base line corresponding to the current date, if the exceeding part is larger than a preset threshold value, determining that the running task is overtime; wherein, selecting the baseline corresponding to the current date from the baseline set according to the preset rule includes: determining the type of the current date; selecting a baseline corresponding to the current date type from the baseline set; wherein the date types include workdays, rest days and special days; wherein the special day comprises: the day and month ends of the rest.