CN115129573A - Program operation monitoring method and device, electronic equipment and storage medium - Google Patents
Program operation monitoring method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115129573A CN115129573A CN202211050172.0A CN202211050172A CN115129573A CN 115129573 A CN115129573 A CN 115129573A CN 202211050172 A CN202211050172 A CN 202211050172A CN 115129573 A CN115129573 A CN 115129573A
- Authority
- CN
- China
- Prior art keywords
- program
- branch
- determining
- counting
- track
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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/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/3452—Performance evaluation by statistical analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/865—Monitoring of software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/88—Monitoring involving counting
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Life Sciences & Earth Sciences (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Bioinformatics & Computational Biology (AREA)
- Evolutionary Biology (AREA)
- Probability & Statistics with Applications (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a program operation monitoring method and device, electronic equipment and a storage medium. The program comprises at least one program branch, and the method comprises the following steps: responding to a monitoring instruction of program operation, and determining the current operation position of the program; if the current running position is determined to be the starting point of one program branch in the program, determining a preset track point corresponding to the program branch; the track points are used for representing program branches; counting the track points corresponding to the program branches to obtain counting results of the track points corresponding to the program branches; wherein the counting result is used for indicating the running times of the program branch when the program is monitored. This application carries out the count of track point to the program branch, monitors at any time according to the count result to the program operation process, improves monitoring efficiency.
Description
Technical Field
The present application relates to computer technologies, and in particular, to a method and an apparatus for monitoring program operation, an electronic device, and a storage medium.
Background
With the continuous progress of society and the rapid development of information technology, computer applications have penetrated all aspects of modern society production and life. Software is used as a soul of computer systems, the scale and complexity of the software are continuously increased, and the probability of the software being defective and failing is continuously increased. Therefore, the software program needs to be monitored and debugged to ensure the normal operation of the program.
In the prior art, a program can be monitored by printing a log, and the more detailed the log is, the more the problem of the program is positioned. However, a certain amount of CPU time is consumed for printing the logs, the logs can only be added to the key nodes of the infrequent processing branches for printing, the performance of the product is seriously affected by adding the logs to the frequent processing branches for printing, and the monitoring efficiency and accuracy of the program operation are low.
Disclosure of Invention
The application provides a program running monitoring method and device, electronic equipment and a storage medium, which are used for improving the monitoring efficiency and precision of program running.
In a first aspect, the present application provides a method for monitoring program operation, where a program includes at least one program branch, and the method includes:
responding to a monitoring instruction of program operation, and determining the current operation position of the program;
if the current running position is determined to be the starting point of one program branch in the program, determining a preset track point corresponding to the program branch; wherein the track points are used for representing program branches;
counting the track points corresponding to the program branches to obtain counting results of the track points corresponding to the program branches; wherein the counting result is used for indicating the running times of the program branch when the program is monitored.
In a second aspect, the present application provides an apparatus for monitoring program operation, where the program includes at least one program branch, and the apparatus includes:
the position determining module is used for responding to a monitoring instruction of program operation and determining the current operation position of the program;
a track point determining module, configured to determine a preset track point corresponding to a program branch if it is determined that the current operating position is a starting point of the program branch in the program; wherein the track points are used for representing program branches;
the track point counting module is used for counting the track points corresponding to the program branches to obtain counting results of the track points corresponding to the program branches; wherein the counting result is used for indicating the running times of the program branch when the program is monitored.
In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer execution instructions;
the processor executes the computer-executable instructions stored in the memory to implement the method for monitoring the operation of the program according to the first aspect of the present application.
In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used for implementing the monitoring method for program execution according to the first aspect of the present application.
In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements a method of monitoring the operation of a program as described in the first aspect of the present application.
According to the monitoring method and device for program operation, the electronic equipment and the storage medium, the current operation position of the program is determined in real time in the program operation process by responding to the monitoring instruction for program operation. The program comprises a plurality of program branches, each program branch corresponds to one track point, if the current running position is the starting point of any program branch, the track points of the program branches are counted, the times of the program running to the program branches are recorded, and the monitoring of the program running process is realized. The problem that monitoring information of frequent processing branches cannot be obtained due to the fact that log printing can only be added to infrequent processing branches in the prior art is solved. By counting the track points, the whole program is comprehensively monitored, the continuous execution condition of the program is known, the consumption of a CPU is reduced, and the monitoring efficiency and the monitoring precision of the program operation are improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is a schematic flowchart of a monitoring method for program operation according to an embodiment of the present disclosure;
fig. 2 is a schematic diagram of a program branch in a program according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a monitoring method for program running according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a monitoring method for program operation according to an embodiment of the present disclosure;
fig. 5 is a block diagram of a monitoring apparatus for program operation according to an embodiment of the present disclosure;
fig. 6 is a block diagram of a monitoring apparatus for program operation according to an embodiment of the present disclosure;
fig. 7 is a block diagram of an electronic device according to an embodiment of the present disclosure;
fig. 8 is a block diagram of an electronic device according to an embodiment of the present disclosure.
With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
It should be understood that the embodiments described are only a few embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application, as detailed in the appended claims.
In the description of the present application, it is to be understood that the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not necessarily used to describe a particular order or sequence, nor are they to be construed as indicating or implying relative importance. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as appropriate. Further, in the description of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
It should be noted that the present specification is not intended to exhaust all alternative embodiments for the sake of brevity, and it should be understood by those skilled in the art after reading the present specification that any combination of features may constitute an alternative embodiment as long as the features are not mutually inconsistent. The following examples are described in detail.
With the continuous progress of society and the rapid development of information technology, computer applications have penetrated various aspects and fields of modern society production and life. The software is used as the soul of the computer system, and the automation and the intelligence are higher and higher due to the fact that the software is combined with various service field scenes. Software systems are growing in size and complexity, and the likelihood of software bugs and failures is increasing.
Currently, there are many monitoring and debugging means for software programs, for example, online debugging of a target machine can be performed by means of a debugging device, and debugging of some standard interfaces can also be performed by means of an oscilloscope. The running log of the program can be printed to monitor the running condition of the program and debug the program. The print log can be applied in the running environment of the program, and the more detailed the log is, the more the log is helpful for positioning the problem. However, since the log printing takes a certain amount of CPU time, the log printing can be added only to the key node of the infrequent processing branch, and if the log printing is added to the frequent processing branch, the product performance is seriously affected.
The log printing mode can record the long-term operation of the program, monitor the operation state and help to locate problems to a certain extent. However, due to performance considerations, the applicable logs of the branches can only be called at the key nodes infrequently, the program cannot be monitored comprehensively, and the monitoring precision is low. In addition, when the log is printed, a certain time cost is required, for example, a certain length of time for formatting a character string is required, wherein the character string is used for distinguishing different positions in the program, and the time for streaming and copying the character string is also required. The log printing involves the operations that the business thread sends log information to the log management thread, the log management thread extracts the log information and copies the log information into the cache block, the cache block is full of imported disk files, and the like, and the monitoring efficiency of program operation is low.
The application provides a program running monitoring method and device, an electronic device and a storage medium, and aims to solve the technical problems in the prior art.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 1 is a flowchart illustrating a monitoring method for program operation according to an embodiment of the present application, where the program includes at least one program branch, and the method is performed by a monitoring apparatus for program operation. As shown in fig. 1, the method comprises the steps of:
and S101, responding to a monitoring instruction of program operation, and determining the current operation position of the program.
For example, the user may instruct the program to run, where the running program may be a process or a thread, and the program may include multiple program branches. After the program runs, the user can send out a monitoring instruction, and the program is monitored in the running process of the program. For example, the progress of the execution of each program branch in the program may be monitored. The program branch in the program may be each option branch, or may be a plurality of program blocks obtained by dividing the program in the sequential structure, and each program block may be used as one program branch.
The monitoring of the program operation may depend on a CLI (Command Line Interface) system, and a user may issue a monitoring instruction through the CLI system and check the program operation condition. After the user sends the monitoring instruction, the current running position of the program can be determined in real time or in a timing mode in response to the monitoring instruction. The current running position may refer to a program code statement to which the program is currently running, for example, when the program is currently running to the second sentence of program code, the current running position is the position of the second sentence of program code. The time that the program runs to each current running position can be recorded, for example, when 0.01 second after the monitoring instruction is received, the current running position is the second sentence code of the program; and when 0.02 th second after the monitoring instruction is received, the current running position is the tenth sentence code of the program.
Or numbering each sentence of code in the program, determining the number of the currently operated program when monitoring the program, and determining the current operation position of the program according to the number.
S102, if the current running position is determined to be the starting point of one program branch in the program, determining a preset track point corresponding to the program branch; wherein the trace points are used to represent program branches.
Illustratively, various program branches in a program are predetermined, and program code statements in the program branches are determined. And determining one or more program code statements from each program branch as the starting point of the program branch, namely, if the program runs to the program code statement corresponding to the starting point of one program branch, the program is considered to have run to the program branch.
Each program branch is used as a track point of the program, and the program running process can be a process of passing through each track point. The program branches can be identified according to preset track points, and the track points can be represented in the form of characters or character strings. For example, the trace points are represented by lower case english letters, the program includes three program branches, namely branch one, branch two, and branch three, and then the trace point corresponding to branch one may be a, the trace point corresponding to branch two may be b, and the trace point corresponding to branch three may be c. FIG. 2 is a diagram illustrating a branch of a program. In fig. 2, three program branches are included, a track point of branch one may be represented by "TP 0", a track point of branch two may be represented by "TP 1", and a track point of branch three may be represented by "TP 2".
And after the current running position is obtained, determining whether the current running position is the starting point of any one of the program branches according to the preset starting points of the program branches. If so, it is determined that the program has been run to the program branch. And determining a program branch to which the program currently runs according to the current running position, acquiring a track point corresponding to the program branch, and representing the currently running program branch by the track point.
In this embodiment, determining that the current running position is the starting point of a program branch in the program includes: and if the program code of the first sentence of the program branch, which is currently operated to the program, of the program branch in the program is determined, determining the current operation position of the program as the starting point of the program branch in the program.
Specifically, a program is considered to have been run to a program branch whenever the program has run to the first sentence of program code in the program branch. Thus, the first sentence of program code in each program branch may be taken as the starting point for each program branch. After the current running position is obtained, whether the current running position is the first sentence program code in any program branch is determined, if yes, the program is determined to run to the starting point of the program branch, and the track point corresponding to the program branch can be determined.
The current running position can be obtained in real time, and when one current running position is obtained, the program code of the current running position is compared with the first sentence program code of each program branch, and whether the program runs to each program branch or not is determined in time. The first two program codes of each branch can be determined as the starting point of each program branch, if the program runs to the first program code of the program branch, the program is not judged to run to the program branch, and when the current running position is the second program code, the second program code in the program branch is used for judging, the program is determined to run to the program branch, so that the problem of wrong program branch determination caused by wrong judgment of the first program code is avoided, and the determination precision of the program branch is effectively improved.
The beneficial effect that sets up like this lies in, just can confirm that the program has run to the program branch when the program runs to the first sentence of program branch, improves the definite efficiency of program branch, and then improves the definite efficiency of track point, helps the real-time monitoring to the program operation.
In this embodiment, determining the preset trace point corresponding to the program branch includes: and determining the track point corresponding to the program branch at which the current running position is located according to the association relation between the preset program branch and the track point.
Specifically, track points are set for program branches in advance, an association relationship between the track points and the program branches is set, and one program branch corresponds to a unique track point. After determining the program branch to which the program currently runs, determining the track point corresponding to the program branch to which the program currently runs according to the preset incidence relation between each program branch and the track point, namely determining the track point corresponding to the program branch at which the current running position is located.
The association relationship between the program code statement and the program branch may be set first, and the program branch may be determined according to the program code statement in which the current operating position is located. And determining the track points corresponding to the program branches according to the incidence relation between the program branches and the track points.
The beneficial effect who sets up like this lies in, through the incidence relation of predetermineeing, can obtain the track point fast accurately, is convenient for make statistics of the operational aspect of procedure, improves the efficiency and the precision of procedure monitoring.
S103, counting the track points corresponding to the program branches to obtain counting results of the track points corresponding to the program branches; the counting result is used for indicating the running times of the program branch when the program is monitored.
Illustratively, a count space is allocated to each trace point in the memory in advance, and the count space can be used for storing the times of the program running to each program branch. When the program runs to a program branch, the running times of the track points of the program branch are counted, and the counting result of the track points corresponding to the program branch is obtained. That is, the count result may be used to indicate the number of times of execution to each program branch when the program is monitored. For example, the program includes a branch one, a branch two, and a branch three, where the track point corresponding to the branch one is a, the track point corresponding to the branch two is b, and the track point corresponding to the branch three is c. And (3) sequentially operating a branch I, a branch II and a branch III in the program, operating the program twice, and operating the program to the branch I again at present, wherein the counting result of the track point a is 3, and the counting result of the track point b and the track point c is 2.
In this embodiment, after obtaining the count result of the trace point corresponding to the program branch, the method further includes: and determining a target memory space which is allocated to the program in advance in the memory, and storing the counting result in the target memory space.
Specifically, the memory is divided in advance to obtain a plurality of memory spaces, and a memory space is allocated to each program, for example, a memory space may be allocated to each thread or process, so that each thread or process may store its own monitoring information in the corresponding memory space. Wherein the monitoring information may be a counting result or the like.
Allocating a memory space for the program in advance, determining the memory space allocated for the program in the memory after obtaining the counting result of any trace point in the program, using the memory space as a target memory space, and storing the counting result in the target memory space for subsequent checking.
And in a memory space corresponding to the program, a counting space can be allocated to each track point, and the counting space corresponding to each track point can include a 4-byte or 8-byte counting result. After the counting result is obtained, the counting space of the track point corresponding to the counting result can be determined, and the counting result is stored in the counting space. For a multi-process scene, a memory sharing technology among processes can be utilized, so that monitoring information such as counting results and the like among the processes can be accessed, and a user can conveniently and quickly check the counting results.
The beneficial effect who sets up like this lies in, through allocating memory in advance, is convenient for carry out the statistics in order to the monitoring information of procedure, avoids the information confusion, improves control efficiency and precision.
In this embodiment, count the track point that the procedure branch corresponds, obtain the count result of the track point that the procedure branch corresponds, include: determining the current counting numerical value of the trace point corresponding to the program branch; and adding one to the current counting value to obtain a counting result of the track points corresponding to the program branches.
Specifically, when the program runs to a program branch, the track point corresponding to the program branch is determined. And acquiring a currently stored counting result from the counting space of the track point in the memory to obtain the number of times that the program branch corresponding to the track point has been operated, wherein the currently stored counting result corresponding to the track point is the currently counted numerical value of the track point. For example, if the program branch corresponding to the trace point has been run twice, the current count value for the trace point may be 2.
The trace points corresponding to the program branches are counted, and a counting result of the trace points can be obtained by adding one to the current counting value of the trace points. For example, the value of the current count is obtained as 2, and 2 is incremented by one to obtain a count result of 3. That is, each time a program branch is run, the count of the trace point corresponding to the program branch is increased by one, so that the running times of each program branch can be determined in real time.
The beneficial effect who sets up like this lies in, tracks a track point, only need to correspond the count value of track point plus one can, the performance is higher than log printing far away, is applicable to the tracking of frequently calling branch and fine grit orbit.
According to the monitoring method for program operation, the current operation position of the program is determined in real time in the program operation process by responding to the monitoring instruction for program operation. The program comprises a plurality of program branches, each program branch corresponds to one track point, if the current running position is the starting point of any program branch, the track points of the program branches are counted, the times of the program running to the program branches are recorded, and the monitoring of the program running process is realized. The problem that monitoring information of frequent processing branches cannot be obtained due to the fact that log printing can only be added to infrequent processing branches in the prior art is solved. By counting the track points, the whole program is comprehensively monitored, the continuous execution condition of the program is known, the consumption of a CPU is reduced, and the monitoring efficiency and the monitoring precision of the program operation are improved.
Fig. 3 is a schematic flowchart of a monitoring method for program operation according to an embodiment of the present application, which is an alternative embodiment based on the foregoing embodiment.
In this embodiment, after obtaining the count result of the trace point corresponding to the program branch, the following may be added: responding to the counting query instruction, and determining the current counting result of each track point in the program; if the counting result which does not meet the requirement of the preset numerical value exists, determining the track point corresponding to the counting result which does not meet the requirement of the preset numerical value as a fault point; and determining the program branch corresponding to the fault point as an abnormal branch, displaying the abnormal branch, and prompting a user to check.
As shown in fig. 3, the method comprises the steps of:
and S301, responding to a monitoring instruction of program operation, and determining the current operation position of the program.
For example, this step may refer to step S101 described above, and is not described again.
S302, if the current running position is determined to be the starting point of one program branch in the program, determining a preset track point corresponding to the program branch; wherein the trace points are used to represent program branches.
For example, this step may refer to step S102 described above, and is not described again.
S303, counting the track points corresponding to the program branches to obtain counting results of the track points corresponding to the program branches; the counting result is used for indicating the running times of the program branch when the program is monitored.
For example, this step may refer to step S103 described above, and is not described again.
And S304, responding to the counting inquiry instruction, and determining the current counting result of each track point in the program.
For example, in the process of monitoring the program, the user may send a counting query instruction at any time to query the current counting result of each track point in the program. And after responding to the counting query instruction, acquiring the current counting result of each track point in the program from the memory space allocated to the program in the memory. The current counting result refers to the latest updated counting result stored in the memory space. The current counting result of all track points in the program can be inquired through the counting inquiry instruction.
Counting query instructions can also be issued for one or more program branches in a program, for example, a user can select branch one on a visual interface and only issue counting query instructions for branch one. After responding to a counting query instruction of a user for a certain program branch, only the current counting result of the track point of the program branch can be obtained from the counting space corresponding to the program branch, so that the program branch or the track point can be accurately queried.
S305, if the counting result which does not meet the requirement of the preset numerical value exists, determining the track point corresponding to the counting result which does not meet the requirement of the preset numerical value as a fault point.
Illustratively, a value requirement is preset, and the value requirement is a requirement that the counting result needs to meet when the program runs normally. If the counting result does not meet the preset numerical value requirement, the counting result is considered to have a problem, and the program branch corresponding to the counting result may have a fault.
And comparing the current counting result of each track point with a preset numerical value requirement, and determining whether the current counting result of each track point meets the preset numerical value requirement, namely determining whether a counting result which does not meet the preset numerical value requirement exists. And if the counting result which does not meet the requirement of the preset numerical value exists, determining the track point corresponding to the counting result which does not meet the requirement of the preset numerical value as a fault point. For example, the current count results of the obtained track points in the program are respectively 2, and 10, and if the preset numerical value requirement is that the track point count result cannot exceed 5, the track point with the count result of 10 can be determined as a fault point. And if the counting result which does not meet the numerical requirement does not exist, namely the counting results of all track points meet the numerical requirement, determining that the program has no problem and continuously operating.
In this embodiment, if there is a counting result that does not meet the requirement of the preset value, determining, as a fault point, a track point corresponding to the counting result that does not meet the requirement of the preset value, including: determining a preset numerical value requirement corresponding to each track point according to the incidence relation between the preset track point and the numerical value requirement; comparing the counting result of each track point with the corresponding preset numerical value requirement; and if the counting result of each track point does not meet the preset numerical value requirement, determining the track point as a fault point.
Specifically, different numerical requirements can be preset for different program branches or trace points. For example, the numerical value of the trace point corresponding to the branch one requires that the counting result can only be 0, and the numerical value of the trace point corresponding to the branch two requires that the counting result cannot be 0. And associating and storing each track point and the numerical value requirement in advance.
And after the current counting result of the track point is obtained, acquiring the numerical value requirement corresponding to the track point according to the association relation between the preset track point and the numerical value requirement. And comparing the current counting result of the track points with the corresponding preset numerical value requirement, and judging whether the current counting result of the track points meets the numerical value requirement. If the counting result of each track point does not meet the requirement of a preset numerical value, determining the track point as a fault point; and if the counting result of each track point meets the preset numerical value requirement, determining that the track point has no problem.
The beneficial effect who sets up like this lies in, through the numerical value requirement that sets up each track point, can carry out accurate control to each track point, improves the control accuracy when the program moves.
And S306, determining the program branch corresponding to the fault point as an abnormal branch, displaying the abnormal branch, and prompting a user to check.
For example, if there is a fault point, the program branch corresponding to the fault point is determined as an abnormal branch, that is, it is monitored that there is an abnormality in the program. The abnormal branch can be displayed on an interface, and a user is prompted to view and improve. After the abnormal branch is determined, the reason of the abnormal branch can be determined, and the reason of the abnormal branch is prompted to a user. For example, there is a program branch in the program, and if the program runs to the program branch, it indicates that there is a missing input parameter of the program. When the counting result corresponding to the program branch is greater than 0, the program is considered to run to the program branch, and the reason that the program has the problem can be determined to be that the input parameter is missing. That is, the cause of an abnormality in a problem occurring in a program when the program branches is executed may be set in advance. When prompting is carried out on the user, the abnormal reason related to the abnormal branch is obtained, the abnormal reason can be directly displayed, the workload of the user is reduced, and the debugging efficiency of the program is improved.
By inquiring the counting result, the monitoring information of each track point of each thread and/or process can be obtained, the running condition of the program can be known, the frequency of entering an abnormal branch can be monitored, and continuous optimization and problem positioning are facilitated.
According to the monitoring method for program operation, the current operation position of the program is determined in real time in the program operation process by responding to the monitoring instruction for program operation. The program comprises a plurality of program branches, each program branch corresponds to one track point, if the current running position is the starting point of any program branch, the track points of the program branches are counted, the times of the program running to the program branches are recorded, and the monitoring of the program running process is realized. The problem that in the prior art, log printing can only be added to an infrequent processing branch, and therefore monitoring information of the frequent processing branch cannot be obtained is solved. Through counting the track points, the comprehensive monitoring of the whole program is realized, the continuous execution condition of the program is known, the consumption of a CPU is reduced, and the monitoring efficiency and the monitoring precision of the program operation are improved.
Fig. 4 is a schematic flowchart of a monitoring method for program operation according to an embodiment of the present application, which is an alternative embodiment based on the foregoing embodiment.
In this embodiment, determining the current running position of the program may be refined as: and acquiring the current running positions of the program at least twice within a preset fault positioning time period.
After acquiring the current operating position of the program at least twice within the preset fault location time period, the following steps can be added: and if the current running positions of the program of at least two times are the same, determining that the program fails, and determining the position where the failure occurs as the current running position.
As shown in fig. 4, the method comprises the steps of:
s401, responding to a monitoring instruction of program operation, and acquiring current operation positions of the program at least twice within a preset fault positioning time period.
For example, after responding to the monitoring instruction of the program operation, a plurality of current operation positions may be automatically acquired, or a user may issue a position acquisition instruction to acquire a plurality of current operation positions. A fault location time period is preset, where the fault location time period is a time period for judging whether a fault occurs in program operation, for example, 15 minutes is around the fault location time, and multiple current operation positions can be obtained within 15 minutes. For example, once at the 5 th minute, once at the 10 th minute, and once within the 15 th minute. A plurality of current operating positions can be randomly acquired within a preset fault positioning time period. That is, the query of the current operation position is continuously performed a plurality of times within the fault locating time period.
A position acquisition instruction may be issued by a user, and a plurality of real-time current operating positions may be continuously acquired after responding to the position acquisition instruction. Or a real-time current operating position can be obtained every time a position obtaining instruction is received, and a user continuously sends out a plurality of position obtaining instructions to obtain a plurality of current operating positions.
S402, if the current running positions of the program of at least two times are the same, determining that the program fails, and determining that the position where the failure occurs is the current running position.
For example, after obtaining the plurality of current operating positions, the plurality of current operating positions are compared to determine whether the plurality of current operating positions are the same position. If the current operation positions are different, the program is considered to be normally operated; and if the current operation positions are the same, determining that the program fails before the program is stopped, and determining the position where the failure occurs as the current operation position. Namely, the program can be seen whether to be hung or not by continuously executing position query for many times, the program can be clearly hung at the position, the problem of the program can be easily positioned by matching code walk-through, the problem of on-site hanging can be effectively positioned, the execution condition of the program can be known by checking the position of the track point, and the continuous optimization of the program is facilitated.
In this embodiment, S401 may be executed before or after S102, or may be executed before or after S103, as long as S402 can be executed after S401.
According to the monitoring method for program operation, the current operation position of the program is determined in real time in the program operation process by responding to the monitoring instruction for program operation. The program comprises a plurality of program branches, each program branch corresponds to one track point, if the current running position is the starting point of any program branch, the track points of the program branches are counted, the times of the program running to the program branches are recorded, and the monitoring of the program running process is realized. The problem that monitoring information of frequent processing branches cannot be obtained due to the fact that log printing can only be added to infrequent processing branches in the prior art is solved. Through counting the track points, the comprehensive monitoring of the whole program is realized, the continuous execution condition of the program is known, the consumption of a CPU is reduced, and the monitoring efficiency and the monitoring precision of the program operation are improved.
Fig. 5 is a block diagram of a monitoring apparatus for monitoring program operation according to an embodiment of the present disclosure. For ease of illustration, only portions that are relevant to embodiments of the present disclosure are shown. The program includes at least one program branch. Referring to fig. 5, the apparatus includes: a position determination module 501, a track point determination module 502 and a track point counting module 503.
A position determining module 501, configured to determine a current operating position of the program in response to a monitoring instruction for program operation;
a track point determining module 502, configured to determine a preset track point corresponding to a program branch if it is determined that the current operating position is a starting point of the program branch in the program; wherein the track points are used for representing program branches;
the trace point counting module 503 is configured to count trace points corresponding to the program branch to obtain a count result of the trace points corresponding to the program branch; wherein the counting result is used for indicating the running times of the program branch when the program is monitored.
Fig. 6 is a block diagram of a monitoring apparatus for program operation according to an embodiment of the present application, and based on the embodiment shown in fig. 5, as shown in fig. 6, the track point counting module 503 includes a current value determining unit 5031 and a counting result determining unit 5032.
A current value determining unit 5031, configured to determine a current counted value of the trace point corresponding to the program branch;
a counting result determining unit 5032, configured to add one to the current counted value to obtain a counting result of the trace point corresponding to the program branch.
In one example, the track point determining module 502 includes:
the starting point determining unit is used for determining that the current running position of the program is the starting point of one program branch in the program if the first sentence program code of one program branch in the program currently run by the program is determined.
In one example, the trace point determining module 502 includes:
and the track point searching unit is used for determining the track point corresponding to the program branch at the current running position according to the preset incidence relation between the program branch and the track point.
In one example, the apparatus further comprises:
the counting query module is used for responding to a counting query instruction after obtaining a counting result of the track points corresponding to the program branches and determining the current counting result of each track point in the program;
the fault point determining module is used for determining track points corresponding to the counting results which do not meet the requirement of the preset numerical value as fault points if the counting results which do not meet the requirement of the preset numerical value exist;
and the abnormal branch determining module is used for determining the program branch corresponding to the fault point as an abnormal branch, displaying the abnormal branch and prompting a user to check.
In one example, the failure point determining module is specifically configured to:
determining a preset numerical value requirement corresponding to each track point according to the incidence relation between the preset track point and the numerical value requirement;
comparing the counting result of each track point with the corresponding preset numerical value requirement;
and if the counting result of each track point does not meet the preset numerical value requirement, determining the track point as a fault point.
In one example, the apparatus further comprises:
and the counting result storage module is used for determining a target memory space which is allocated for the program in advance in a memory after the counting result of the trace points corresponding to the program branches is obtained, and storing the counting result in the target memory space.
In one example, the position determining module 501 is specifically configured to:
and acquiring the current running position of the program at least twice within a preset fault positioning time period.
In one example, the apparatus further comprises:
and the fault positioning module is used for determining that the program has a fault if the current running positions of the program at least twice are the same after the current running positions of the program at least twice are obtained within a preset fault positioning time period, and determining the position where the fault occurs as the current running position.
Fig. 7 is a block diagram of an electronic device according to an embodiment of the present application, and as shown in fig. 7, the electronic device includes: a memory 71, a processor 72; a memory 71; a memory for storing instructions executable by processor 72.
Wherein the processor 72 is configured to perform the methods provided in the above embodiments.
The electronic device further comprises a receiver 73 and a transmitter 74. The receiver 73 is used for receiving instructions and data transmitted from other devices, and the transmitter 74 is used for transmitting instructions and data to external devices.
FIG. 8 is a block diagram illustrating an electronic device, which may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like, in accordance with one exemplary embodiment.
The processing component 802 generally controls overall operation of the device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operation at the device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The power component 806 provides power to the various components of the device 800. The power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.
The multimedia component 808 includes a screen that provides an output interface between the device 800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 814 includes one or more sensors for providing various aspects of state assessment for the device 800. For example, the sensor assembly 814 may detect the open/closed state of the device 800, the relative positioning of components, such as a display and keypad of the device 800, the sensor assembly 814 may also detect a change in the position of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, orientation or acceleration/deceleration of the device 800, and a change in the temperature of the device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
In an exemplary embodiment, the device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the device 800 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
A non-transitory computer-readable storage medium, in which instructions are executed by a processor of a terminal device, so that the terminal device can perform a monitoring method of program execution of the terminal device.
The application also discloses a computer program product comprising a computer program which, when executed by a processor, implements the method as described in the embodiments.
Various implementations of the systems and techniques described here above may be realized in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present application may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or electronic device.
In the context of this application, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data electronic device), or that includes a middleware component (e.g., an application electronic device), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include a client and an electronic device. The client and the electronic device are generally remote from each other and typically interact through a communication network. The relationship of client and electronic device arises by virtue of computer programs running on the respective computers and having a client-electronic device relationship to each other. The electronic device may be a cloud electronic device, which is also called a cloud computing electronic device or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and low service extensibility in a conventional physical host and VPS service ("Virtual Private Server", or "VPS" for short). The electronic device may also be a distributed system of electronic devices or an electronic device incorporating a blockchain. It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present application can be achieved, and the present invention is not limited herein.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (12)
1. A method for monitoring the operation of a program, wherein the program includes at least one program branch, the method comprising:
responding to a monitoring instruction of program operation, and determining the current operation position of the program;
if the current running position is determined to be the starting point of one program branch in the program, determining a preset track point corresponding to the program branch; wherein the track points are used for representing program branches;
counting the track points corresponding to the program branches to obtain counting results of the track points corresponding to the program branches; wherein the counting result is used for indicating the running times of the program branch when the program is monitored.
2. The method according to claim 1, wherein counting the trace points corresponding to the program branch to obtain a count result of the trace points corresponding to the program branch comprises:
determining a current counting numerical value of a track point corresponding to the program branch;
and adding one to the current counting numerical value to obtain a counting result of the track points corresponding to the program branches.
3. The method of claim 1, wherein determining that the current running location is a beginning of a branch in the program comprises:
and if the first sentence of the program code of one program branch in the program currently operated by the program is determined, determining the current operation position of the program as the starting point of the one program branch in the program.
4. The method of claim 1, wherein determining the predetermined trajectory points corresponding to the program branches comprises:
and determining the track point corresponding to the program branch at which the current running position is located according to the association relation between the preset program branch and the track point.
5. The method of claim 1, further comprising, after obtaining the result of counting the trace points corresponding to the program branch:
responding to a counting query instruction, and determining the current counting result of each track point in the program;
if the counting result which does not meet the requirement of the preset value exists, determining the track point corresponding to the counting result which does not meet the requirement of the preset value as a fault point;
and determining the program branch corresponding to the fault point as an abnormal branch, displaying the abnormal branch, and prompting a user to check.
6. The method according to claim 5, wherein if there is a counting result that does not meet the requirement of the preset value, determining the trace point corresponding to the counting result that does not meet the requirement of the preset value as a fault point, comprises:
determining a preset numerical value requirement corresponding to each track point according to the incidence relation between the preset track point and the numerical value requirement;
comparing the counting result of each track point with the corresponding preset numerical value requirement;
and if the counting result of each track point does not meet the preset numerical value requirement, determining the track point as a fault point.
7. The method of claim 1, further comprising, after obtaining the result of counting the trace points corresponding to the program branch:
and determining a target memory space which is allocated to the program in advance in the memory, and storing the counting result in the target memory space.
8. The method of any of claims 1-7, wherein determining the current operating position of the program comprises:
and acquiring the current running position of the program at least twice within a preset fault positioning time period.
9. The method of claim 8, further comprising, after obtaining the current operating position of the program at least twice within a preset fault locating time period:
and if the current running positions of the program are the same at least twice, determining that the program fails, and determining the failed position as the current running position.
10. An apparatus for monitoring the operation of a program, the program including at least one program branch, the apparatus comprising:
the position determining module is used for responding to a monitoring instruction of program operation and determining the current operation position of the program;
a track point determining module, configured to determine a preset track point corresponding to a program branch if it is determined that the current operating position is a starting point of the program branch in the program; wherein the track points are used for representing program branches;
the track point counting module is used for counting the track points corresponding to the program branches to obtain counting results of the track points corresponding to the program branches; wherein the counting result is used for indicating the running times of the program branch when the program is monitored.
11. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to implement a method of monitoring the operation of a program as claimed in any one of claims 1 to 9.
12. A computer-readable storage medium, having stored thereon computer-executable instructions for implementing a method of monitoring the operation of a program as claimed in any one of claims 1-9 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211050172.0A CN115129573A (en) | 2022-08-31 | 2022-08-31 | Program operation monitoring method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211050172.0A CN115129573A (en) | 2022-08-31 | 2022-08-31 | Program operation monitoring method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115129573A true CN115129573A (en) | 2022-09-30 |
Family
ID=83387244
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211050172.0A Pending CN115129573A (en) | 2022-08-31 | 2022-08-31 | Program operation monitoring method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115129573A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115755709A (en) * | 2022-11-25 | 2023-03-07 | 北京北方华创微电子装备有限公司 | Operating environment data acquisition method and device, electronic equipment and storage medium |
| CN115794550A (en) * | 2022-11-23 | 2023-03-14 | 广州汽车集团股份有限公司 | Process management method, device, vehicle and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104268081A (en) * | 2014-09-25 | 2015-01-07 | 深圳创维数字技术有限公司 | Software running state monitoring method and device |
| US20170286253A1 (en) * | 2016-03-31 | 2017-10-05 | International Business Machines Corporation | Optimization for application runtime monitoring |
| CN112306788A (en) * | 2019-07-29 | 2021-02-02 | 北京京东振世信息技术有限公司 | Program dynamic monitoring method and device |
| CN113296997A (en) * | 2021-06-16 | 2021-08-24 | 度普(苏州)新能源科技有限公司 | Task monitoring method and device based on watchdog |
| CN113407414A (en) * | 2021-06-24 | 2021-09-17 | 厦门科灿信息技术有限公司 | Program operation monitoring method, device, terminal and storage medium |
| CN113515430A (en) * | 2021-09-14 | 2021-10-19 | 国汽智控(北京)科技有限公司 | Method, device and equipment for monitoring state of process |
| CN114036032A (en) * | 2022-01-10 | 2022-02-11 | 北京搜狐互联网信息服务有限公司 | Real-time program monitoring method and device |
-
2022
- 2022-08-31 CN CN202211050172.0A patent/CN115129573A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104268081A (en) * | 2014-09-25 | 2015-01-07 | 深圳创维数字技术有限公司 | Software running state monitoring method and device |
| US20170286253A1 (en) * | 2016-03-31 | 2017-10-05 | International Business Machines Corporation | Optimization for application runtime monitoring |
| CN112306788A (en) * | 2019-07-29 | 2021-02-02 | 北京京东振世信息技术有限公司 | Program dynamic monitoring method and device |
| CN113296997A (en) * | 2021-06-16 | 2021-08-24 | 度普(苏州)新能源科技有限公司 | Task monitoring method and device based on watchdog |
| CN113407414A (en) * | 2021-06-24 | 2021-09-17 | 厦门科灿信息技术有限公司 | Program operation monitoring method, device, terminal and storage medium |
| CN113515430A (en) * | 2021-09-14 | 2021-10-19 | 国汽智控(北京)科技有限公司 | Method, device and equipment for monitoring state of process |
| CN114036032A (en) * | 2022-01-10 | 2022-02-11 | 北京搜狐互联网信息服务有限公司 | Real-time program monitoring method and device |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115794550A (en) * | 2022-11-23 | 2023-03-14 | 广州汽车集团股份有限公司 | Process management method, device, vehicle and storage medium |
| CN115794550B (en) * | 2022-11-23 | 2024-04-02 | 广州汽车集团股份有限公司 | Process management method, device, vehicle and storage medium |
| CN115755709A (en) * | 2022-11-25 | 2023-03-07 | 北京北方华创微电子装备有限公司 | Operating environment data acquisition method and device, electronic equipment and storage medium |
| CN115755709B (en) * | 2022-11-25 | 2023-08-18 | 北京北方华创微电子装备有限公司 | Method and device for collecting running environment data, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115129573A (en) | Program operation monitoring method and device, electronic equipment and storage medium | |
| JP7289334B2 (en) | Methods and apparatus, electronic devices, storage media and computer programs for testing code | |
| CN111858318B (en) | Response time testing method, device, equipment and computer storage medium | |
| CN112131079B (en) | Data monitoring method, device, electronic equipment and storage medium | |
| CN114721912B (en) | Data analysis method, device, equipment and medium | |
| CN112256563B (en) | Android application stability testing method and device, electronic equipment and storage medium | |
| CN115632928A (en) | Alarm method and device based on system level, electronic equipment and storage medium | |
| CN114020615A (en) | Method, device, equipment and storage medium for testing remote multi-active financial system | |
| CN110347565B (en) | Application program abnormity analysis method and device and electronic equipment | |
| CN114372043A (en) | Data migration method and device, electronic equipment and storage medium | |
| CN114218005A (en) | Equipment fault detection and repair processing method, device and equipment | |
| CN113094225B (en) | Abnormal log monitoring method and device and electronic equipment | |
| CN112486770B (en) | Client dotting reporting method and device, electronic equipment and storage medium | |
| CN116069612A (en) | Abnormality positioning method and device and electronic equipment | |
| CN112416751A (en) | Processing method and device for interface automation test and storage medium | |
| CN111913850A (en) | Data anomaly detection method, device, equipment and storage medium | |
| CN114936040B (en) | Program data processing method, device, electronic equipment and storage medium | |
| CN115563156A (en) | Method, device and equipment for checking stream data information and storage medium | |
| CN115604132A (en) | Remote control method and device for server, electronic equipment and readable storage medium | |
| CN111240927B (en) | Method, device and storage medium for detecting time consumption of method in program | |
| CN114564206A (en) | Data non-empty checking method, device, equipment and readable storage medium | |
| CN118195291B (en) | Table replacement identification method, apparatus, storage medium and device | |
| CN116055292B (en) | Knowledge graph-based information processing method, device and equipment | |
| CN109739763B (en) | Code segment operation method, device, terminal and storage medium | |
| CN114115196A (en) | Method, device, equipment and storage medium for detecting equipment reliability |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220930 |
|
| RJ01 | Rejection of invention patent application after publication |