CN116257405A - Task monitoring method and device and task abnormality analysis method and device - Google Patents

Task monitoring method and device and task abnormality analysis method and device Download PDF

Info

Publication number
CN116257405A
CN116257405A CN202310126623.2A CN202310126623A CN116257405A CN 116257405 A CN116257405 A CN 116257405A CN 202310126623 A CN202310126623 A CN 202310126623A CN 116257405 A CN116257405 A CN 116257405A
Authority
CN
China
Prior art keywords
task
thread
function
target
monitored
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310126623.2A
Other languages
Chinese (zh)
Inventor
李惠惠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Eswin Computing Technology Co Ltd
Original Assignee
Beijing Eswin Computing Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Eswin Computing Technology Co Ltd filed Critical Beijing Eswin Computing Technology Co Ltd
Priority to CN202310126623.2A priority Critical patent/CN116257405A/en
Publication of CN116257405A publication Critical patent/CN116257405A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
    • G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G06F11/3476—Data logging
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The application discloses a task monitoring method and device and a task abnormality analysis method and device, relates to the technical field of computers, and aims to reduce positioning difficulty of task abnormality problems; the main technical scheme comprises the following steps: when each target thread of a task to be monitored is executed, monitoring thread execution conditions of the target threads and function call conditions of each function of the target threads to form corresponding thread execution information and function call information; and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored.

Description

Task monitoring method and device and task abnormality analysis method and device
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a task monitoring method and apparatus, and a task anomaly analysis method and apparatus.
Background
In an operating system such as nuttx, there are tasks that multiple threads execute. In such task execution, the threads involved therein affect each other and depend on each other, and the threads need to be switched based on the execution order. Once the task has abnormal problems such as task performance damage or task breakdown, it is difficult to locate where the task abnormal problem occurs.
Disclosure of Invention
In view of this, the present application provides a task monitoring method and apparatus, and a task anomaly analysis method and apparatus, which mainly aims to reduce the difficulty in positioning task anomalies.
In order to achieve the above purpose, the present application mainly provides the following technical solutions:
in a first aspect, the present application provides a task monitoring method, where the task monitoring method includes:
when each target thread of a task to be monitored is executed, monitoring thread execution conditions of the target threads and function call conditions of each function of the target threads to form corresponding thread execution information and function call information;
and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored.
According to the task monitoring method, when each target thread of a task to be monitored is executed, thread execution conditions of the target threads and function call conditions of each function of the target threads are monitored, and corresponding thread execution information and function call information are formed. And generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored. The thread execution information and the function call information recorded in the monitoring log are the basis for locating the task abnormality problem. Based on the monitoring log, not only can the abnormality of which threads of the task occur, but also which functions cause the abnormality of the corresponding threads can be positioned. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
In some embodiments, the task monitoring method further comprises: determining a macro definition switch which is triggered currently; wherein, task monitoring granularities corresponding to different macro definition switches are different; if the task monitoring granularity corresponding to the macro definition switch which is triggered currently is the function granularity, when each target thread of the task to be monitored is executed, the thread execution condition of the target thread and the function call condition of each function of the target thread are monitored, and corresponding thread execution information and function call information are formed.
In some embodiments, monitoring the thread execution condition of the target thread to form corresponding thread execution information includes: monitoring the thread name, the start execution time, the end execution time and the name of an occupied processor of the target thread; and forming corresponding thread execution information based on the monitored thread name, the start execution time, the end execution time and the name of the occupied processor.
In some embodiments, monitoring the function call condition of each function of the target thread to form corresponding function call information includes: monitoring the starting calling time and ending calling time of the functions, the calling sequence of the functions in all functions of the target thread and the calling stack address information of the functions when each function of the target thread is called; the call stack address information is used for acquiring a function name corresponding to the function; and forming corresponding function call information based on the monitored start call time, end call time, call sequence of the function in all functions of the target thread and call stack address information of the function.
In some embodiments, the task monitoring method further comprises: determining all threads of the task to be monitored as target threads; or determining the threads with the corresponding identifiers in the preset list in all the threads of the task to be monitored as target threads; the corresponding threads with the identifiers in the preset list bring the risk of task abnormality to the task to be monitored.
In some embodiments, the task monitoring method further comprises: detecting whether the duration of the currently executed target thread exceeds a first duration; if the target thread is beyond the target thread, terminating the task to be monitored, and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored.
In some embodiments, the task monitoring method further comprises: detecting whether the continuous calling duration of the function of the currently called target thread exceeds a second duration; if the target thread is beyond the target thread, terminating the task to be monitored, and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored.
In a second aspect, the present application provides a task anomaly analysis method, including:
acquiring a monitoring log corresponding to a task to be analyzed; the monitoring log comprises thread execution information corresponding to each target thread of the task to be analyzed when the task to be analyzed is executed and function call information corresponding to the function of each target thread;
and carrying out exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to the function of each target thread.
According to the task abnormality analysis method, the monitoring log corresponding to the task to be analyzed is obtained, wherein the monitoring log comprises thread execution information corresponding to each target thread and function call information corresponding to the function of each target thread when the task to be analyzed is executed. And carrying out exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to the function of each target thread. Because the monitoring log comprises thread execution information corresponding to each target thread and function call information corresponding to the function of each target thread when the task to be analyzed is executed, when the task to be analyzed is analyzed and processed abnormally, the monitoring log can be used for locating which threads of the task are abnormal and locating which functions cause the corresponding threads to be abnormal. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
In some embodiments, performing exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to a function of each target thread includes: based on the thread name, the start execution time, the end execution time and the names of occupied processors included in the thread execution information, displaying the occupied time length of the occupied processor of each target thread in sequence according to the execution sequence of the target threads in the task to be analyzed; when any target thread is selected, analyzing the function names of the functions based on call stack address information included in the function call information of the functions of the selected target thread; displaying the function names and the calling sequence of the functions of the selected target threads and the occupation time of each function occupying the processor based on the starting calling time, the ending calling time and the calling sequence of the functions in all the functions of the corresponding target threads, which are included in the function calling information of the selected target threads; and when any function is selected, displaying the code file identifier corresponding to the selected function and the code row related to the selected function in the code file corresponding to the code file identifier.
In some embodiments, the task anomaly analysis method further comprises: selecting a target thread with the occupied time length longer than the third time length; and/or selecting a function with the occupied time period longer than the fourth time period.
In a third aspect, the present application provides a task monitoring device, including:
the monitoring module is used for monitoring the thread execution condition of each target thread and the function call condition of each function of the target thread when each target thread of the task to be monitored is executed, so as to form corresponding thread execution information and function call information;
and the generating module is used for generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored.
In a fourth aspect, the present application provides a task abnormality analysis device including:
the acquisition module is used for acquiring a monitoring log corresponding to the task to be analyzed; the monitoring log comprises thread execution information corresponding to each target thread of the task to be analyzed when the task to be analyzed is executed and function call information corresponding to the function of each target thread;
And the analysis module is used for carrying out exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to the function of each target thread.
In a fifth aspect, the present application provides a computer readable storage medium, where the storage medium includes a stored program, where the program, when executed, controls a device in which the storage medium is located to perform the task monitoring method of the first aspect, and/or the task abnormality analysis method of the second aspect.
In a sixth aspect, the present application provides an electronic device, including: a memory for storing a program; a processor coupled to the memory for executing the program to perform the task monitoring method of the first aspect and/or the task anomaly analysis method of the second aspect.
The foregoing description is only an overview of the technical solutions of the present application, and may be implemented according to the content of the specification in order to make the technical means of the present application more clearly understood, and in order to make the above-mentioned and other objects, features and advantages of the present application more clearly understood, the following detailed description of the present application will be given.
Drawings
In order to more clearly illustrate the embodiments of the present application 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, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 illustrates a flow chart of a method for task monitoring provided in one embodiment of the present application;
FIG. 2 illustrates a flow chart of a method of task anomaly analysis provided by one embodiment of the present application;
FIG. 3 is a schematic diagram of a task monitoring device according to an embodiment of the present application;
FIG. 4 is a schematic structural diagram of a task monitoring device according to another embodiment of the present application;
FIG. 5 is a schematic structural diagram of a task anomaly analysis device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a task anomaly analysis device according to another embodiment of the present application.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In an operating system such as nuttx, there are tasks that multiple threads execute. In such task execution, the threads involved therein affect each other and depend on each other, and the threads need to be switched based on the execution order. Once the task has abnormal problems such as task performance damage or task breakdown, it is difficult to locate where the task abnormal problem occurs.
The inventors have found that, in general, when a task has an abnormal problem, the abnormal problem is usually caused by a thread execution abnormality, and the abnormal thread execution abnormality is caused by a function abnormality related to the thread. Therefore, the inventor considers that when each thread of the task to be monitored is executed, the thread execution condition of the thread and the function call condition of each function of the thread can be monitored to form corresponding thread execution information and function call information. And generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each thread of the task to be monitored. The thread execution information and the function call information recorded in the monitoring log are the basis for locating the task abnormality problem. Based on the monitoring log, not only can the abnormality of which threads of the task occur, but also which functions cause the abnormality of the corresponding threads can be positioned. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
The inventors have also found that, because the monitoring log includes thread execution information corresponding to each thread and function call information corresponding to a function of each thread when a task is executed. Therefore, the task can be subjected to abnormality analysis processing based on the thread execution information corresponding to each thread of the task and the function call information corresponding to the function of each thread. During exception analysis processing, based on the monitoring log, not only can the exception of which threads of the task occur, but also which functions cause the exception of the corresponding threads can be positioned. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
Based on the above considerations, the embodiments of the present application provide a task monitoring method and apparatus, and a task anomaly analysis method and apparatus, and the task monitoring method and apparatus, and the task anomaly analysis method and apparatus provided in the embodiments of the present application are specifically described below.
As shown in fig. 1, the embodiment of the present application provides a task monitoring method, which mainly includes the following steps 101-102:
101. When each target thread of the task to be monitored is executed, the thread execution condition of the target thread and the function call condition of each function of the target thread are monitored, and corresponding thread execution information and function call information are formed.
In practical applications, in an operating system such as nuttx, there may be tasks that need to be executed by multiple threads, so that the threads of the tasks have a certain execution order, and for any thread in the execution order, the input of the thread is the output of the next-to-last thread. In the task execution process, related threads are mutually influenced and mutually dependent, the threads are required to be switched based on the execution sequence, and once the task has abnormal problems such as task performance damage or task breakdown, the abnormal problem of which thread is difficult to locate, so that in order to accurately and quickly locate the task abnormal problem, the task which needs to be executed by a plurality of threads is determined to be the task to be monitored.
After the task to be monitored is determined, a target thread needs to be selected from threads of the task to be monitored, so that the target thread can be monitored in a targeted manner in the process of executing the task to be monitored. The following describes a method for determining a target thread, which may include two methods:
First, all threads of the task to be monitored are determined as target threads.
In consideration of the problem that each thread of the task to be monitored possibly causes the abnormal problems of breakdown or performance damage of the task to be monitored in the execution process of the task to be monitored, all threads of the task to be monitored are determined to be target threads, so that thread execution information and function call information corresponding to each thread of the task to be monitored can be monitored, and the thread execution information and the function call information provide a comprehensive data basis for positioning the abnormal problems of the task to be monitored.
Secondly, determining the threads with the corresponding identifiers in a preset list in all threads of the task to be monitored as target threads; the corresponding threads with the marks in the preset list bring the risk of task abnormality to the task to be monitored.
Considering that the probability of causing the abnormal problem of the task to be monitored is not high when some threads are executed, and the probability of causing the abnormal problem of the task to be monitored is high when some threads are executed. In order to reduce the monitoring workload, only the threads which have high probability of causing abnormal problems of the task to be monitored can be determined as target threads, so that the target threads are monitored in a targeted manner only when the task to be monitored is executed.
In order to facilitate the determination of the target thread, a preset list is preset, the preset list comprises at least one identifier, and the thread corresponding to the identifier brings abnormal risks to the task to be monitored. When a thread of a task to be monitored is executed, detecting whether the identification of the thread exists in a preset list; if the thread identification is detected to exist in the preset list, the thread is determined to be a target thread. If the mark of the thread is detected not to exist in the preset list, the thread is indicated to have small abnormal risk to the task to be monitored, and the thread is not determined to be the target thread in order to reduce the monitoring workload.
After determining the target thread of the task to be monitored, monitoring the target when the target thread is executed
The thread execution condition of the thread and the function call condition of each function of the target thread form corresponding thread execution information and function call information, so that when the task to be monitored is abnormally positioned, which functions in which threads are positioned to cause the abnormality of the task to be monitored are positioned through the thread execution information and the function call information.
The following describes a specific execution process of forming corresponding thread execution information according to the thread execution condition of the monitoring target thread, and the process includes the following steps: monitoring the thread name, the start execution time, the end execution time and the name of an occupied processor of a target thread; and forming corresponding thread execution information based on the monitored thread name, the start execution time, the end execution time and the name of the occupied processor.
The thread execution information records the thread name, the start execution time, the end execution time and the name of the occupied processor corresponding to the target thread. The start and end times of the corresponding target thread and which processor, i.e., CPU, is executing can be known from the content recorded in the thread execution information.
The following describes a specific execution procedure for forming corresponding function call information for each function call condition of the monitoring target thread, the procedure comprising the steps of: monitoring the starting calling time and ending calling time of the functions, the calling sequence of the functions in all functions of the target thread and the calling stack address information of the functions when each function of the target thread is called; the call stack address information is used for obtaining function names corresponding to the functions. And forming corresponding function call information based on the monitored start call time, end call time, call sequence of the function in all functions of the target thread and call stack address information of the function.
Typically, a thread is completed by the invocation of a plurality of functions, which have a certain order of invocation. Generally, when a task is abnormal, the abnormal execution of the thread is usually caused by the abnormal execution of the function related to the thread, so that the abnormal problem of the function needs to be fundamentally solved in order to solve the task abnormal problem.
In order to locate the function causing the task abnormality in time and accurately when the task has the task abnormality, when each function of the target thread is called, the starting call time, the ending call time, the call sequence of the function in all functions of the target thread and the call stack address information of the function are monitored. The starting call time, the ending call time, the call sequence of the function in all functions of the target thread and the call stack address information of the function are all judging bases for judging whether the task abnormality occurs to the corresponding function. The function call information records the start call time and the end call time of the corresponding functions, the call sequence of the functions in all functions of the target thread and the call stack address information of the functions.
102. And generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored.
The monitoring log of the task to be monitored is the basis for locating the task abnormality problem, and comprises thread execution information and function call information corresponding to each target thread of the task to be monitored. The timing of generating the monitoring log includes the following:
Firstly, detecting whether all target threads of a task to be monitored are executed; and if the execution is completed, generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored.
And when all the target threads of the task to be monitored are detected to be executed, the fact that the task to be monitored does not have threads needing to be monitored currently is indicated, and therefore a monitoring log of the task to be monitored is generated based on thread execution information and function call information corresponding to all the target threads of the task to be monitored.
Secondly, detecting whether the duration of the currently executed target thread exceeds a first duration; if the target thread is beyond the target thread, terminating the task to be monitored, and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored.
If the continuous execution duration of the currently executed target thread exceeds the first duration, the current executed target thread is indicated to have the abnormal problem that the task to be monitored is crashed, so that the task to be monitored is terminated in order to remove the abnormality in time, and a monitoring log of the task to be monitored is generated based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored. The target thread of the task to be monitored which has been executed here includes a target thread which is currently executed and a target thread which has been executed before the target thread which is currently executed.
Thirdly, detecting whether the continuous calling duration of the function of the currently called target thread exceeds a second duration; if the target thread is beyond the target thread, terminating the task to be monitored, and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored.
If the continuous calling time length of the function of the currently called target thread exceeds the second time length, the problem that the currently called function has an abnormal problem of causing the breakdown of the task to be monitored is described, so that the task to be monitored is terminated in order to be able to eliminate the abnormality in time, and a monitoring log of the task to be monitored is generated based on thread executing information and function calling information corresponding to the executed target thread of the task to be monitored. The target thread of the task to be monitored which has been executed here includes a target thread which is currently executed and a target thread which has been executed before the target thread which is currently executed.
In this embodiment of the present application, the following content is recorded in the monitoring log: the task identification of the task to be monitored, the thread name, the start execution time, the end execution time and the name of the occupied processor of the executed target thread of the task to be monitored, the start calling time, the end calling time, the calling sequence of the function in all functions of the target thread and the calling stack address information of the function of each executed target thread.
The content recorded in the monitoring log is the basis for locating task abnormality problems. Based on the monitoring log, not only can the abnormality of which threads of the task occur, but also which functions cause the abnormality of the corresponding threads can be positioned. Therefore, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed by service personnel from the granularity of the function.
According to the task monitoring method, when each target thread of a task to be monitored is executed, thread execution conditions of the target threads and function call conditions of each function of the target threads are monitored, and corresponding thread execution information and function call information are formed. And generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored. The thread execution information and the function call information recorded in the monitoring log are the basis for locating the task abnormality problem. Based on the monitoring log, not only can the abnormality of which threads of the task occur, but also which functions cause the abnormality of the corresponding threads can be positioned. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
In some embodiments of the present application, the task monitoring method further includes the following steps: determining a macro definition switch which is triggered currently; wherein, task monitoring granularities corresponding to different macro definition switches are different; if it is determined that the task monitoring granularity corresponding to the currently triggered macro definition switch is the function granularity, executing the step 101 monitors the thread execution condition of the target thread and the function call condition of each function of the target thread when each target thread of the task to be monitored is executed, so as to form corresponding thread execution information and function call information.
In order to meet the requirements of different monitoring granularities, a plurality of macro-defined switches can be preset, and task monitoring granularities corresponding to different macro-defined switches are different. For example, a macro definition switch 1 and a macro definition switch 2 are provided, the task monitoring granularity of the macro definition switch 1 is a function call condition of which the function granularity is to be monitored, and the task monitoring granularity of the macro definition switch 2 is a thread execution condition of which only the thread granularity is to be monitored.
Business personnel can flexibly trigger macro definition switches meeting the requirements based on specific monitoring requirements. If the task monitoring granularity corresponding to the macro definition switch which is triggered currently is judged to be the function granularity, the function calling condition of the function granularity to be monitored is indicated, and when each target thread of the task to be monitored is executed, the thread executing condition of the target thread and the function calling condition of each function of the target thread are monitored to form corresponding thread executing information and function calling information. If the task monitoring granularity corresponding to the macro definition switch which is triggered currently is judged to be the thread granularity, the thread execution condition of the thread granularity to be monitored is indicated, and when each target thread of the task to be monitored is executed, the thread execution condition of the target thread is monitored, so that corresponding thread execution information is formed.
As shown in fig. 2, the embodiment of the present application provides a task anomaly analysis method, which mainly includes the following steps 201 to 202:
201. acquiring a monitoring log corresponding to a task to be analyzed; the monitoring log comprises thread execution information corresponding to each target thread and function call information corresponding to the function of each target thread when the task to be analyzed is executed.
The tasks to be analyzed are in two cases: firstly, a task to be analyzed is a task with obvious abnormal problems in the execution process; secondly, the task to be analyzed is a task which has no obvious abnormal problem in the execution process, but needs to be subjected to abnormal research and judgment. The task to be analyzed can be the task monitored by the task monitoring method no matter what condition the task to be analyzed is.
The task to be analyzed is a task realized by a plurality of threads, regardless of whether the task to be analyzed is a task in either of the above two cases. The threads of such tasks have a certain execution order, and the input of any one of the threads in the execution order is the output of the immediately preceding thread adjacent thereto. In the task execution process, related threads are mutually influenced and mutually dependent, the threads are required to be switched based on the execution sequence, and once the task has abnormal problems such as task performance damage or task breakdown, the abnormal problem is difficult to locate to which thread, so that in order to accurately and quickly locate the task abnormal problem, the embodiment of the application acquires the monitoring log corresponding to the task to be analyzed, and locates the abnormal problem through the monitoring log.
The obtained monitoring log records thread execution information corresponding to each target thread and function call information corresponding to the function of each target thread when the task to be analyzed is executed. The thread execution information here includes the thread name of the corresponding target thread, the start execution time, the end execution time, and the name of the occupied processor. The function call information here includes start call time, end call time, call order of the function in all functions of the corresponding target thread, and call stack address information of the function.
It can be seen that the above-mentioned content recorded in the monitoring log is the basis for locating task abnormality problems. Based on the monitoring log, not only can the abnormality of which threads of the task occur, but also which functions cause the abnormality of the corresponding threads can be positioned. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
202. And carrying out exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to the function of each target thread.
Based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to a function of each target thread, a specific process of performing exception analysis processing on the task to be analyzed includes the following steps 202A to 202C:
202A, based on the thread name, the start execution time, the end execution time and the names of occupied processors included in the thread execution information, displaying the occupied time of the processor occupied by each target thread in turn according to the execution sequence of the target threads in the task to be analyzed.
After the execution of one thread of the task to be analyzed is completed, the next thread is switched to continue the execution. The execution order of each target thread of the task to be analyzed can thus be determined based on the thread name, start execution time, end execution time included in the thread execution information.
After determining the execution sequence of each target thread of the task to be analyzed, determining the processor occupied by each target thread based on the name of the occupied processor included in the thread execution information, and then determining the occupied time length of the processor occupied by the corresponding target thread based on the difference between the ending execution time and the starting execution time included in the thread execution information.
According to the execution sequence of the target threads in the task to be analyzed, the purpose of displaying the occupied time length of the processor occupied by each target thread in sequence is as follows: business personnel can more intuitively judge whether the task to be analyzed is abnormal in the target thread based on the occupied time length of the processor occupied by the target thread, and the difficulty of locating the abnormal problem is reduced.
202B, when any target thread is selected, analyzing the function names of the functions based on call stack address information included in the function call information of the functions of the selected target thread; and displaying the function names, the calling sequence and the occupied duration of each function occupying the processor of the selected target thread based on the starting calling time, the ending calling time and the calling sequence of the function in all functions of the corresponding target thread, which are included in the function calling information of each function of the selected target thread.
The target thread may be selected in two cases: first, when the target thread is selected by the selection instruction, it is indicated that the target thread is selected. The selection instruction is issued by service personnel based on own abnormality analysis requirements; and secondly, selecting a target thread with the occupied time longer than the third time. The longer than the third length of time indicates that the thread is busy for a long period of time with the processor and fails to complete execution on time, which indicates that the thread may be abnormal.
When any target thread is selected, in order to locate which functions of the target thread cause abnormality, function names of the selected functions are resolved based on call stack address information included in function call information of the selected functions of the target thread so as to determine which functions the selected target thread relates to. And then displaying the function names, the calling sequence and the occupied duration of each function occupying the processor of the selected target thread based on the starting calling time, the ending calling time and the calling sequence of the function in all functions of the corresponding target thread, which are included in the function calling information of each function of the selected target thread. The occupation time is determined based on the difference between the corresponding ending calling time and starting calling time.
The purpose of displaying the function names, the calling sequence and the occupied time length of each function occupying the processor of the selected target thread is as follows: the business personnel can intuitively know which functions are related to the selected target thread, and the occupied duration of the occupied processor of each function is what, so that the business personnel can judge whether the task to be analyzed is abnormal in the function or not based on the occupied duration of the occupied processor of the function.
202C, when any function is selected, displaying the code file identification corresponding to the selected function and the code row related to the selected function in the code file corresponding to the code file identification.
The function may be selected in two cases: and firstly, when the function is selected by the selection instruction, the description function is selected. The selection instruction is issued by service personnel based on own abnormality analysis requirements; and secondly, selecting a function with the occupied time longer than the fourth time. The occupation time is longer than the fourth time, which indicates that the function occupies the processor for a long time and fails to be completed in time, which indicates that the function may have an exception.
When any function is selected, in order to enable service personnel to know whether the problem of task abnormality exists in the codes of the functions, the code file identification corresponding to the selected function is displayed. The code file identifier is the identifier of the code file corresponding to the function, so that the service personnel can know in which file the code corresponding to the function is recorded. And displaying the code file identifier corresponding to the selected function, and displaying the code line related to the selected function in the code file corresponding to the code file identifier, so that a service person can conveniently and quickly find the code corresponding to the function in the code file, and whether the abnormality of the task to be analyzed is caused by the function or not is required to be determined based on the code of the function.
According to the task abnormality analysis method provided by the embodiment of the application, the monitoring log corresponding to the task to be analyzed is obtained, wherein the monitoring log comprises thread execution information corresponding to each target thread and function call information corresponding to the function of each target thread when the task to be analyzed is executed. And carrying out exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to the function of each target thread. Because the monitoring log comprises thread execution information corresponding to each target thread and function call information corresponding to the function of each target thread when the task to be analyzed is executed, when the task to be analyzed is analyzed and processed abnormally, the monitoring log can be used for locating which threads of the task are abnormal and locating which functions cause the corresponding threads to be abnormal. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
Further, an embodiment of the present application further provides a task monitoring device, as shown in fig. 3, where the task monitoring device includes:
The monitoring module 31 is configured to monitor, when each target thread of a task to be monitored is executed, a thread execution condition of the target thread and a function call condition of each function of the target thread, so as to form corresponding thread execution information and function call information;
the generating module 32 is configured to generate a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored.
According to the task monitoring device provided by the embodiment of the application, when each target thread of a task to be monitored is executed, the thread execution condition of the target thread and the function call condition of each function of the target thread are monitored, and corresponding thread execution information and function call information are formed. And generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored. The thread execution information and the function call information recorded in the monitoring log are the basis for locating the task abnormality problem. Based on the monitoring log, not only can the abnormality of which threads of the task occur, but also which functions cause the abnormality of the corresponding threads can be positioned. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
In some embodiments of the present application, as shown in fig. 4, the task monitoring device further includes:
a first determining module 33, configured to determine a macro definition switch that is currently triggered; wherein, task monitoring granularities corresponding to different macro definition switches are different; if it is determined that the task monitoring granularity corresponding to the currently triggered macro definition switch is the function granularity, the trigger monitoring module 31 monitors the thread execution condition of each target thread and the function call condition of each function of the target thread when each target thread of the task to be monitored is executed, so as to form corresponding thread execution information and function call information.
In some embodiments of the present application, as shown in fig. 4, the monitoring module 31 includes:
a first monitoring unit 311, configured to monitor a thread name, a start execution time, an end execution time, and a name of an occupied processor of the target thread; and forming corresponding thread execution information based on the monitored thread name, the start execution time, the end execution time and the name of the occupied processor.
In some embodiments of the present application, as shown in fig. 4, the monitoring module 31 includes:
a second monitoring unit 312, configured to monitor, when each function of the target thread is called, a start call time, an end call time, a call sequence of the function in all functions of the target thread, and call stack address information of the function; the call stack address information is used for acquiring a function name corresponding to the function; and forming corresponding function call information based on the monitored start call time, end call time, call sequence of the function in all functions of the target thread and call stack address information of the function.
In some embodiments of the present application, as shown in fig. 4, the task monitoring device further includes:
and the second determining module 34 is configured to determine all threads of the task to be monitored as target threads.
In some embodiments of the present application, as shown in fig. 4, the task monitoring device further includes:
a third determining module 35, configured to determine, as a target thread, a thread corresponding to all threads of the task to be monitored, where the threads are identified as being located in a preset list; the corresponding threads with the identifiers in the preset list bring the risk of task abnormality to the task to be monitored.
In some embodiments of the present application, as shown in fig. 4, the task monitoring device further includes:
a first detecting unit 36, configured to detect whether a duration of execution of a currently executed target thread exceeds a first duration; if the target thread is beyond the target thread, terminating the task to be monitored, and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored.
In some embodiments of the present application, as shown in fig. 4, the task monitoring device further includes:
a second detecting unit 37, configured to detect whether a duration of continuous calling of a function of a currently called target thread exceeds a second duration; if the target thread is beyond the target thread, terminating the task to be monitored, and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored.
In the task monitoring device provided in the embodiment of the present application, a detailed description of a method adopted in the operation process of each functional module may be referred to a detailed description of a corresponding method of the above task monitoring method embodiment, which is not repeated herein.
Further, an embodiment of the present application further provides a task anomaly analysis device, as shown in fig. 5, including:
the acquisition module 41 is configured to acquire a monitoring log corresponding to a task to be analyzed; the monitoring log comprises thread execution information corresponding to each target thread of the task to be analyzed when the task to be analyzed is executed and function call information corresponding to the function of each target thread;
and the analysis module 42 is configured to perform exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to a function of each target thread.
The task exception analysis device provided by the embodiment of the application acquires a monitoring log corresponding to a task to be analyzed, wherein the monitoring log comprises thread execution information corresponding to each target thread and function call information corresponding to a function of each target thread when the task to be analyzed is executed. And carrying out exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to the function of each target thread. Because the monitoring log comprises thread execution information corresponding to each target thread and function call information corresponding to the function of each target thread when the task to be analyzed is executed, when the task to be analyzed is analyzed and processed abnormally, the monitoring log can be used for locating which threads of the task are abnormal and locating which functions cause the corresponding threads to be abnormal. Therefore, the positioning difficulty of the task abnormal problems can be reduced, the positioning efficiency of the task abnormal problems can be improved, and the task abnormal problems can be removed from the granularity of the function by service personnel more conveniently.
In some embodiments of the present application, as shown in fig. 6, the analysis module 42 includes:
a first analysis unit 421, configured to sequentially display, based on a thread name, a start execution time, an end execution time, and a name of an occupied processor included in the thread execution information, an occupied duration of the processor occupied by each target thread according to an execution order of the target threads in the task to be analyzed;
a second analyzing unit 422, configured to, when any one of the target threads is selected, analyze a function name of each function based on call stack address information included in function call information of each function of the selected target thread; displaying the function names and the calling sequence of the functions of the selected target threads and the occupation time of each function occupying the processor based on the starting calling time, the ending calling time and the calling sequence of the functions in all the functions of the corresponding target threads, which are included in the function calling information of the selected target threads;
and the third analysis unit 423 is configured to display, when any one of the functions is selected, a code file identifier corresponding to the selected function and a code line related to the selected function in the code file corresponding to the code file identifier.
In some embodiments of the present application, as shown in fig. 6, the second analyzing unit 422 is further configured to select a target thread whose occupied time period is longer than the third time period.
In some embodiments of the present application, as shown in fig. 6, the third analysis unit 423 is further configured to select a function with a occupation time period longer than the fourth time period.
In the task anomaly analysis device provided in the embodiment of the present application, a detailed description of a method adopted in the operation process of each functional module may be referred to a detailed description of a corresponding method of the task anomaly analysis method embodiment, which is not repeated herein.
Further, according to the above embodiment, another embodiment of the present application further provides a computer readable storage medium, where the storage medium includes a stored program, and when the program runs, the device where the storage medium is controlled to execute the task monitoring method described above.
Further, according to the above embodiment, another embodiment of the present application further provides a computer readable storage medium, where the storage medium includes a stored program, and when the program runs, the device where the storage medium is controlled to execute the task anomaly analysis method described above.
Further, according to the above embodiment, another embodiment of the present application further provides an electronic device, including: a memory for storing a program; and a processor, coupled to the memory, for executing the program to perform the task monitoring method described above.
Further, according to the above embodiment, another embodiment of the present application further provides an electronic device, including: a memory for storing a program; and the processor is coupled to the memory and is used for running the program to execute the task abnormality analysis method.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
It will be appreciated that the relevant features of the methods and apparatus described above may be referenced to one another. In addition, the "first", "second", and the like in the above embodiments are for distinguishing the embodiments, and do not represent the merits and merits of the embodiments.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with the teachings herein. The required structure for a construction of such a system is apparent from the description above. In addition, the present application is not directed to any particular programming language. It should be appreciated that the contents of the present application described herein can be implemented using a variety of programming languages, and that the above description of specific languages is provided for disclosure of preferred embodiments of the present application.
Furthermore, the memory may include volatile memory, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM), in a computer readable medium, the memory including at least one memory chip.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data tapping device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data tapping device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data cutting apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data-cutting apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises an element.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims (10)

1. A method of task monitoring, the method comprising:
when each target thread of a task to be monitored is executed, monitoring thread execution conditions of the target threads and function call conditions of each function of the target threads to form corresponding thread execution information and function call information;
And generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored.
2. The method according to claim 1, wherein the method further comprises:
determining a macro definition switch which is triggered currently; wherein, task monitoring granularities corresponding to different macro definition switches are different;
if the task monitoring granularity corresponding to the macro definition switch which is triggered currently is the function granularity, when each target thread of the task to be monitored is executed, the thread execution condition of the target thread and the function call condition of each function of the target thread are monitored, and corresponding thread execution information and function call information are formed.
3. The method of claim 1, wherein monitoring the thread execution of the target thread to form corresponding thread execution information comprises:
monitoring the thread name, the start execution time, the end execution time and the name of an occupied processor of the target thread;
forming corresponding thread execution information based on the monitored thread name, the start execution time, the end execution time and the name of the occupied processor;
And/or the number of the groups of groups,
monitoring the function call condition of each function of the target thread to form corresponding function call information, wherein the method comprises the following steps:
monitoring the starting calling time and ending calling time of the functions, the calling sequence of the functions in all functions of the target thread and the calling stack address information of the functions when each function of the target thread is called; the call stack address information is used for acquiring a function name corresponding to the function;
and forming corresponding function call information based on the monitored start call time, end call time, call sequence of the function in all functions of the target thread and call stack address information of the function.
4. A method according to any one of claims 1-3, characterized in that the method further comprises:
determining all threads of the task to be monitored as target threads;
or determining the threads with the corresponding identifiers in the preset list in all the threads of the task to be monitored as target threads; the corresponding threads with the identifiers in the preset list bring the risk of task abnormality to the task to be monitored.
5. A method according to any one of claims 1-3, characterized in that the method further comprises:
Detecting whether the duration of the currently executed target thread exceeds a first duration;
if the target thread is beyond the target thread, terminating the task to be monitored, and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored;
and/or the number of the groups of groups,
the method further comprises the steps of:
detecting whether the continuous calling duration of the function of the currently called target thread exceeds a second duration;
if the target thread is beyond the target thread, terminating the task to be monitored, and generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to the executed target thread of the task to be monitored.
6. A method of task anomaly analysis, the method comprising:
acquiring a monitoring log corresponding to a task to be analyzed; the monitoring log comprises thread execution information corresponding to each target thread of the task to be analyzed when the task to be analyzed is executed and function call information corresponding to the function of each target thread;
and carrying out exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to the function of each target thread.
7. The method according to claim 6, wherein performing exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to a function of each target thread, comprises:
based on the thread name, the start execution time, the end execution time and the names of occupied processors included in the thread execution information, displaying the occupied time length of the occupied processor of each target thread in sequence according to the execution sequence of the target threads in the task to be analyzed;
when any target thread is selected, analyzing the function names of the functions based on call stack address information included in the function call information of the functions of the selected target thread; displaying the function names and the calling sequence of the functions of the selected target threads and the occupation time of each function occupying the processor based on the starting calling time, the ending calling time and the calling sequence of the functions in all the functions of the corresponding target threads, which are included in the function calling information of the selected target threads;
and when any function is selected, displaying the code file identifier corresponding to the selected function and the code row related to the selected function in the code file corresponding to the code file identifier.
8. A task monitoring device, the device comprising:
the monitoring module is used for monitoring the thread execution condition of each target thread and the function call condition of each function of the target thread when each target thread of the task to be monitored is executed, so as to form corresponding thread execution information and function call information;
and the generating module is used for generating a monitoring log of the task to be monitored based on thread execution information and function call information corresponding to each target thread of the task to be monitored.
9. A task anomaly analysis device, the device comprising:
the acquisition module is used for acquiring a monitoring log corresponding to the task to be analyzed; the monitoring log comprises thread execution information corresponding to each target thread of the task to be analyzed when the task to be analyzed is executed and function call information corresponding to the function of each target thread;
and the analysis module is used for carrying out exception analysis processing on the task to be analyzed based on thread execution information corresponding to each target thread of the task to be analyzed and function call information corresponding to the function of each target thread.
10. A computer-readable storage medium, characterized in that the storage medium includes a stored program, wherein the program, when run, controls a device in which the storage medium is located to perform the task monitoring method according to any one of claims 1 to 5, and/or the task abnormality analysis method according to any one of claims 6 to 7.
CN202310126623.2A 2023-02-16 2023-02-16 Task monitoring method and device and task abnormality analysis method and device Pending CN116257405A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310126623.2A CN116257405A (en) 2023-02-16 2023-02-16 Task monitoring method and device and task abnormality analysis method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310126623.2A CN116257405A (en) 2023-02-16 2023-02-16 Task monitoring method and device and task abnormality analysis method and device

Publications (1)

Publication Number Publication Date
CN116257405A true CN116257405A (en) 2023-06-13

Family

ID=86678844

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310126623.2A Pending CN116257405A (en) 2023-02-16 2023-02-16 Task monitoring method and device and task abnormality analysis method and device

Country Status (1)

Country Link
CN (1) CN116257405A (en)

Similar Documents

Publication Publication Date Title
CN105207806A (en) Monitoring method and apparatus of distributed service
CN110661659A (en) Alarm method, device and system and electronic equipment
CN110650036A (en) Alarm processing method and device and electronic equipment
CN108599977B (en) System and method for monitoring system availability based on statistical method
US20190340106A1 (en) Debugging support apparatus and debugging support method
CN109344046B (en) Data processing method, device, medium and electronic equipment
CN104639346A (en) Method and device for detecting network management equipment of communication operator
CN107783879B (en) Method and equipment for analyzing workflow execution path
CN111147313A (en) Message abnormity monitoring method and device, storage medium and electronic equipment
CN105843675B (en) Thread exit method and device
CN111478792B (en) Cutover information processing method, system and device
CN104461847B (en) Data processor detection method and device
CN114691445A (en) Cluster fault processing method and device, electronic equipment and readable storage medium
CN116257405A (en) Task monitoring method and device and task abnormality analysis method and device
CN112596938A (en) Abnormity monitoring method and device
CN111858244A (en) Hard disk monitoring method, system, device and medium
CN112363893B (en) Method, equipment and device for detecting time sequence index abnormity
CN111475394A (en) Application testing method and device
CN113886342A (en) File format conversion method and device, storage medium and processor
CN110647419A (en) Fault detection method and device, computer storage medium and terminal
CN110908866A (en) Software monitoring method and related equipment
JP2007249490A (en) Automatic failure log selection/collection method and apparatus
CN111917602B (en) Method and device for detecting availability of IP address and electronic equipment
CN115604135B (en) Service monitoring method and device
CN109656776B (en) Completeness inspection method and equipment for abnormal monitoring of computer system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination