CN114328158A - Abnormity monitoring method and device, electronic equipment and storage medium - Google Patents
Abnormity monitoring method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114328158A CN114328158A CN202111655001.6A CN202111655001A CN114328158A CN 114328158 A CN114328158 A CN 114328158A CN 202111655001 A CN202111655001 A CN 202111655001A CN 114328158 A CN114328158 A CN 114328158A
- Authority
- CN
- China
- Prior art keywords
- abnormal
- log
- exception
- information
- uploading
- 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
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The present disclosure relates to an anomaly monitoring method, apparatus, electronic device, and storage medium, the method being applied to a domain controller, the method comprising: when the process is monitored to be abnormal, acquiring abnormal information corresponding to the abnormal process based on a core dump mechanism; generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to target equipment, enabling the target equipment to generate an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log; namely, the embodiment of the present disclosure can obtain the exception information and the exception log of all processes including the container process through the core dump mechanism, thereby effectively ensuring the stable operation of the domain controller system.
Description
Technical Field
The present disclosure relates to the field of computers, and in particular, to an anomaly monitoring method and apparatus, an electronic device, and a storage medium.
Background
In the field of automatic driving of vehicles, in order to ensure safe operation of the vehicles, the running state of an application process in a domain controller system deployed on the vehicles is monitored, and abnormal processes are counted and repaired in time.
In the monitoring method adopted by the application process in the current domain controller system, for example, by running an aport program, only an exception log of a part of host processes is generated, and all application process exceptions cannot be monitored.
Disclosure of Invention
The embodiment of the disclosure provides an anomaly monitoring method and device, electronic equipment and a storage medium, so as to solve the technical problem that the existing domain controller system cannot monitor all application processes to be anomalous.
In a first aspect, an embodiment of the present disclosure provides an anomaly monitoring method applied to a domain controller, where the method includes: when the process is monitored to be abnormal, acquiring abnormal information corresponding to the abnormal process based on a core dump mechanism; and generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to target equipment, so that the target equipment generates an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log.
As an optional embodiment of the present disclosure, the obtaining, based on the core dump mechanism, exception information corresponding to the process in which the exception occurs includes: and acquiring abnormal information corresponding to the abnormal process by reading the standard input of the core pipeline program.
As an optional embodiment of the present disclosure, the exception information includes a first process number of the exception-occurring process in the container and a second process number of the process in the host; if the first process number is the same as the second process number, determining the abnormal process as a host process; and if the first process number is different from the second process number, determining that the abnormal process is a container process.
As an optional embodiment of the present disclosure, the exception information further includes: absolute path of executable file, execution command and parameter, and exception time of the process in which the exception occurred.
As an optional embodiment of the present disclosure, the method further comprises: acquiring a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time; and uploading a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time to a target device, so that the target device uploads the system running log, the kernel log and the container engine log corresponding to the domain controller before the abnormal time to the target device according to the system running log, the kernel log and the container engine log before the abnormal time, and the abnormal log locates abnormal problems.
As an optional embodiment of the present disclosure, the uploading the exception information and the exception log to a target device includes: and automatically uploading the abnormal information and the abnormal log to a target device.
As an optional embodiment of the present disclosure, the method further comprises: detecting whether the abnormal information and the abnormal log which are not uploaded exist or not; and if so, uploading the non-uploaded abnormal information and the abnormal log.
In a second aspect, an embodiment of the present disclosure provides a process exception monitoring apparatus, including: the monitoring module is used for acquiring abnormal information corresponding to the abnormal process based on a core dump mechanism when the abnormal process is monitored; and the uploading module is used for generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to the target equipment, so that the target equipment generates an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete mutual communication through the communication bus; a memory for storing a computer program; a processor configured to implement the steps of the abnormality monitoring method according to any one of the first aspect when executing the program stored in the memory.
In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the steps of the anomaly monitoring method according to any one of the first aspect.
The embodiment of the disclosure provides an anomaly monitoring method, an anomaly monitoring device, an electronic device and a storage medium, wherein the method is applied to a domain controller, and comprises the following steps: when the process is monitored to be abnormal, acquiring abnormal information corresponding to the abnormal process based on a core dump mechanism; generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to target equipment, enabling the target equipment to generate an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log; namely, the embodiment of the present disclosure can obtain the exception information and the exception log of all processes including the container process through the core dump mechanism, thereby effectively ensuring the stable operation of the domain controller system.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the related art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
Fig. 1 is a schematic flow chart of an anomaly monitoring method according to an embodiment of the present disclosure;
fig. 2 is a schematic flow chart of another anomaly monitoring method provided in the embodiment of the present disclosure;
fig. 3 is a schematic flow chart of another anomaly monitoring method according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a process anomaly monitoring apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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 an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The nouns to which this disclosure relates will be explained first:
docker: a software virtualization mechanism can realize the isolation of a file system and an application program on the same operating system kernel. Each isolated unit is referred to as a "Container". Each application may run in a container, just as it would in a separate operating system. This "operating system" has installed a complete operating environment on which the application software depends, and is not dependent on the host's software environment.
ROS: a typical system has complex and fragile dependencies. Various libraries have specific versioning requirements, and if dependent on items that are damaged and cannot be repaired, it can eventually only take a full day to reinstall the operating system and re-deploy the ROS and associated development tools for continued use. We therefore decided to transfer ROS to Docker for operation, reducing the risk of damaging dependent items.
In the field of automatic driving of vehicles, in order to ensure safe operation of vehicles, the operating state of an application process in a domain controller system on a vehicle is monitored, and when the application process is abnormal (process termination, crash and the like), abnormal information and an abnormal log are reported to a background server, so that online problems can be quickly repaired, fast iteration is performed, and stable operation of the domain controller system is ensured.
The existing domain controller system monitors the application process exception through a deployed application program, but because the existing domain controller generally runs an Ubuntu system, the Ubuntu system also integrates a Docker container, an ROS system and the like, and processes in the Docker container and the ROS system run in the container, the complexity of the domain controller system is increased, and the application program can only generate an exception log when part of host machine processes are abnormal, and cannot generate an exception log when the processes in the container are abnormal, that is, the existing domain controller system cannot monitor all application processes exception, which is not beneficial to the stable operation of the system.
In view of the above technical problem, the technical idea of the present disclosure is as follows: by adopting an exception monitoring method of a core dump (core-dump) mechanism to replace a native Apport program, exception monitoring of all processes including a container process is realized, and the running stability of the system is improved.
In addition, the Apport program suffers from the following two problems. One is that unusual log can't automatic upload, when the application process is unusual in the application program monitoring, need the manual abnormal information of uploading of user, complex operation is more likely, and the user can feel the troublesome poeration and choose not to upload, leads to that backend server can't know which part of application program probably still has the leak, can't in time repair, and the possibility appears unusually again, influences user experience. Secondly, a user using the Ubuntu system cannot acquire abnormal information and cannot perform personalized transformation on the system, and when the user selects to upload the abnormal information, the abnormal information is uploaded to a background server of the Ubuntu system, so that only research personnel of the Ubuntu system can see the abnormal information, and the user using the Ubuntu system cannot view the abnormal information, which is not beneficial to maintenance and personalized transformation of the Ubuntu system by the user.
In a first aspect, an embodiment of the present disclosure provides an anomaly monitoring method, which applies a domain controller. Fig. 1 is a schematic flow chart of an anomaly monitoring method according to an embodiment of the present disclosure, and as shown in fig. 1, the anomaly monitoring method includes:
step S101, when the process is monitored to be abnormal, acquiring abnormal information corresponding to the abnormal process based on a core dump mechanism.
Specifically, the execution subject of the embodiment of the present disclosure is a domain controller in which a process exception monitoring apparatus is deployed. Before step S101 is executed, a core (core) file size upper limit, a core file storage directory, and the like need to be preset on the domain controller to start the core-dump mechanism, that is, when a process is abnormal, abnormal information corresponding to the abnormal process is obtained, where the abnormal information may be referred to as a core file, and the core file is stored in a preset storage directory.
As an alternative embodiment, the obtaining of the exception information corresponding to the process in which the exception occurs based on the core dump mechanism in step S101 includes: and acquiring abnormal information corresponding to the abnormal process by reading the standard input of the core pipeline program. Specifically, when a process is abnormal, the domain controller obtains abnormal information by reading the standard input of the core-pattern pipeline.
As an optional embodiment, the exception information includes a first process number of the exception-occurring process in the container and a second process number of the exception-occurring process in the host; if the first process number is the same as the second process number, determining the abnormal process as a host process; and if the first process number is different from the second process number, determining that the abnormal process is a container process.
Specifically, the PID of the abnormal process in the container and the PID of the abnormal process in the host may be obtained simultaneously through the core-pattern, and if the two process numbers are the same, the process is indicated as the host process, and if the two process numbers are different, the process is indicated as the container process. That is, the user can determine whether the container process or the host process occurs an exception according to the process number in the exception information.
As an optional embodiment, the exception information further includes: absolute path of executable file, execution command and parameter, and exception time of the process in which the exception occurred.
And S102, generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to target equipment, enabling the target equipment to generate an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log.
Specifically, the domain controller may generate an exception log from the exception information by using a debugging tool, such as gdb, and upload the exception information and the exception log to the target device, and after receiving the exception information, the target device may generate an exception statistical chart according to the exception information, for example, count the frequency of exception occurring in each process, so as to facilitate a research and development staff to perform an emphasis detection on a certain process; and the abnormal log is displayed through the target device, so that a user can conveniently locate which program has a problem, and even refine the source file name of the code with the problem, the error line number and the like. The target device can be a background server of the Ubuntu system, and preferably, the target device can also be a device designated by a user using the Ubuntu system, so that the user using the Ubuntu system can conveniently and smoothly check the abnormal statistical chart and the abnormal log, and personalized modification and maintenance of the Ubuntu system are facilitated.
As an optional embodiment, the uploading the exception information and the exception log to the target device in step S102 includes: and automatically uploading the abnormal information and the abnormal log to a target device. Specifically, after the exception log is obtained, the exception information and the exception log are automatically uploaded to the target device, and the user experience is provided without manually uploading by the user.
The anomaly monitoring method provided by the embodiment of the disclosure is applied to a domain controller, and acquires anomaly information corresponding to an abnormal process based on a core dump mechanism when the process is monitored to be abnormal; generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to target equipment, enabling the target equipment to generate an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log; namely, according to the embodiment of the disclosure, the abnormal information and the abnormal log of all processes including the container process can be acquired through the core dump mechanism, so that the stable operation of the domain controller system is effectively ensured, and further the safety of the automatic driving of the vehicle is ensured.
On the basis of the foregoing embodiment, fig. 2 is a schematic flowchart of another anomaly monitoring method provided in the embodiment of the present disclosure, and as shown in fig. 2, the anomaly monitoring method includes:
step S201, when the process is monitored to be abnormal, acquiring abnormal information corresponding to the abnormal process based on a core dump mechanism.
Step S202, generating an abnormal log according to the abnormal information, and uploading the abnormal information and the abnormal log to a target device so that the target device generates an abnormal statistical chart according to the abnormal information.
Step S203, obtaining a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time.
Step S204, uploading a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time to a target device, so that the target device uploads the system running log, the kernel log and the container engine log corresponding to the domain controller before the abnormal time to the target device according to the system running log, the kernel log and the container engine log, and the abnormal log locates abnormal problems.
Step S201 and step S202 in this embodiment are similar to the implementation manners of step S101 and step S102 in the above embodiments, and are not described again here.
The difference from the above embodiment is that, in order to more accurately and quickly locate the specific position of the abnormal problem, in this embodiment, a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time are obtained; and uploading a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time to a target device, so that the target device uploads the system running log, the kernel log and the container engine log corresponding to the domain controller before the abnormal time to the target device according to the system running log, the kernel log and the container engine log before the abnormal time, and the abnormal log locates abnormal problems.
Specifically, in this embodiment, in addition to uploading the exception log to the target device, the domain controller may also capture a system operation log, a kernel log, and a container engine log before the exception occurs, or even an ROS error log, and upload the captured logs to the target device to assist in analyzing and solving the exception problem.
As an optional embodiment, the method further comprises: detecting whether the abnormal information and the abnormal log which are not uploaded exist or not; and if so, uploading the non-uploaded abnormal information and the abnormal log.
Specifically, the domain controller may periodically scan whether the system has the non-uploaded abnormal information and the abnormal log, if so, upload the information, and if not, continue to monitor the system. As shown in fig. 3, which is a schematic flow diagram of another exception monitoring method provided in the embodiment of the present disclosure, first, a domain controller detects whether there is unported crash information and crash logs, if there is, uploads the unported crash information and crash logs, if there is no, or after uploading is completed, starts monitoring an application process, and when monitoring that the application process crashes, obtains the crash information and crash logs based on a core-dum mechanism, and automatically uploads the crash information and crash logs to a target device.
According to the anomaly monitoring method provided by the embodiment of the disclosure, a system running log, a kernel log and a container engine log corresponding to a domain controller before the anomaly time are obtained; uploading a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time to a target device, so that the target device uploads the system running log, the kernel log and the container engine log corresponding to the domain controller before the abnormal time to the target device according to the system running log, the kernel log and the container engine log, and the abnormal log locates abnormal problems; in other words, in the embodiment of the present disclosure, in addition to the abnormal log, the system running log, the kernel log, the container engine log, and the like before the abnormal event are also uploaded to the target device, so as to assist the user in comprehensively analyzing and solving the abnormal problem according to the logs, and thus, the problem is accurately and quickly located.
In a second aspect, an embodiment of the present disclosure provides a process exception monitoring apparatus. Fig. 4 is a schematic structural diagram of a process exception monitoring apparatus according to an embodiment of the present disclosure, and as shown in fig. 4, the process exception monitoring apparatus includes:
the monitoring module 10 is configured to, when it is monitored that a process is abnormal, obtain abnormal information corresponding to the abnormal process based on a core dump mechanism; and the uploading module 20 is configured to generate an exception log according to the exception information, and upload the exception information and the exception log to the target device, so that the target device generates an exception statistical chart according to the exception information, and locates an exception problem according to the exception log.
As an optional embodiment of the present disclosure, the monitoring module 10 is specifically configured to: and acquiring abnormal information corresponding to the abnormal process by reading the standard input of the core pipeline program.
As an optional embodiment of the present disclosure, the exception information includes a first process number of the exception-occurring process in the container and a second process number of the process in the host; if the first process number is the same as the second process number, determining the abnormal process as a host process; and if the first process number is different from the second process number, determining that the abnormal process is a container process.
As an optional embodiment of the present disclosure, the exception information further includes: absolute path of executable file, execution command and parameter, and exception time of the process in which the exception occurred.
As an alternative embodiment of the present disclosure, the monitoring module 10 is further configured to: acquiring a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time; the upload module 20 is further configured to: and uploading a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time to a target device, so that the target device uploads the system running log, the kernel log and the container engine log corresponding to the domain controller before the abnormal time to the target device according to the system running log, the kernel log and the container engine log before the abnormal time, and the abnormal log locates abnormal problems.
As an optional embodiment of the present disclosure, the upload module 20 is specifically configured to: and automatically uploading the abnormal information and the abnormal log to a target device.
As an alternative embodiment of the present disclosure, the apparatus further includes a detection module 30, where the detection module 30 is configured to: detecting whether the abnormal information and the abnormal log which are not uploaded exist or not; if yes, the non-uploaded exception information and the exception log are uploaded through the uploading module 20.
The implementation principle and technical effect of the process anomaly monitoring device provided by the embodiment of the present disclosure are similar to those of the above embodiments, and are not described herein again.
The process exception monitoring device provided by the embodiment of the disclosure is used for acquiring exception information corresponding to an exception process based on a core dump mechanism when the process exception is monitored through the monitoring module; the uploading module is used for generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to the target equipment, so that the target equipment generates an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log; namely, the embodiment of the present disclosure can obtain the exception information and the exception log of all processes including the container process through the core dump mechanism, thereby effectively ensuring the stable operation of the domain controller system.
As shown in fig. 5, an embodiment of the present disclosure provides an electronic device, which includes a processor 111, a communication interface 112, a memory 113, and a communication bus 114, where the processor 111, the communication interface 112, and the memory 113 complete mutual communication through the communication bus 114,
a memory 113 for storing a computer program;
in an embodiment of the present disclosure, the processor 111 is configured to implement the steps of the process exception monitoring method provided in any one of the foregoing method embodiments when executing the program stored in the memory 113.
The electronic device provided by the embodiment of the present disclosure has the similar implementation principle and technical effect to those of the above embodiments, and is not described herein again.
The memory 113 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable and programmable read only memory), an EPROM, a hard disk, or a ROM. The memory 113 has a storage space for program code for performing any of the method steps of the above-described method. For example, the memory space for the program code may comprise respective program codes for implementing respective steps in the above method, respectively. The program code can be read from or written to one or more computer program products. These computer program products comprise a program code carrier such as a hard disk, a Compact Disc (CD), a memory card or a floppy disk. Such computer program products are typically portable or fixed storage units. The storage unit may have a storage section or a storage space or the like arranged similarly to the memory 113 in the electronic device described above. The program code may be compressed, for example, in a suitable form. Typically, the memory unit comprises a program for performing the steps of the method according to embodiments of the present disclosure, i.e. code that can be read by a processor, such as 111 for example, which when run by an electronic device causes the electronic device to perform the individual steps of the method described above.
Embodiments of the present disclosure also provide a computer-readable storage medium. The computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the process anomaly monitoring method as described above.
The computer-readable storage medium may be contained in the apparatus/device described in the above embodiments; or may be present alone without being assembled into the device/apparatus. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: 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), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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 an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present disclosure, which enable those skilled in the art to understand or practice the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. An anomaly monitoring method applied to a domain controller, the method comprising:
when the process is monitored to be abnormal, acquiring abnormal information corresponding to the abnormal process based on a core dump mechanism;
and generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to target equipment, so that the target equipment generates an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log.
2. The method of claim 1, wherein the obtaining exception information corresponding to the process in which the exception occurs based on the core dump mechanism comprises:
and acquiring abnormal information corresponding to the abnormal process by reading the standard input of the core pipeline program.
3. The method of claim 2, wherein the exception information comprises a first process number of the exception-occurring process in a container and a second process number of a process in a host;
if the first process number is the same as the second process number, determining the abnormal process as a host process;
and if the first process number is different from the second process number, determining that the abnormal process is a container process.
4. The method of claim 3, wherein the exception information further comprises: absolute path of executable file, execution command and parameter, and exception time of the process in which the exception occurred.
5. The method of claim 4, further comprising: acquiring a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time;
and uploading a system running log, a kernel log and a container engine log corresponding to the domain controller before the abnormal time to a target device, so that the target device uploads the system running log, the kernel log and the container engine log corresponding to the domain controller before the abnormal time to the target device according to the system running log, the kernel log and the container engine log before the abnormal time, and the abnormal log locates abnormal problems.
6. The method according to any one of claims 1-5, wherein uploading the exception information and exception log to a target device comprises:
and automatically uploading the abnormal information and the abnormal log to a target device.
7. The method of claim 6, further comprising:
detecting whether the abnormal information and the abnormal log which are not uploaded exist or not;
and if so, uploading the non-uploaded abnormal information and the abnormal log.
8. A process exception monitoring apparatus, comprising:
the monitoring module is used for acquiring abnormal information corresponding to the abnormal process based on a core dump mechanism when the abnormal process is monitored;
and the uploading module is used for generating an abnormal log according to the abnormal information, uploading the abnormal information and the abnormal log to the target equipment, so that the target equipment generates an abnormal statistical chart according to the abnormal information, and positioning abnormal problems according to the abnormal log.
9. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the steps of the anomaly monitoring method of any one of claims 1-7 when executing a program stored on a memory.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the anomaly monitoring method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111655001.6A CN114328158A (en) | 2021-12-30 | 2021-12-30 | Abnormity monitoring method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111655001.6A CN114328158A (en) | 2021-12-30 | 2021-12-30 | Abnormity monitoring method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114328158A true CN114328158A (en) | 2022-04-12 |
Family
ID=81018519
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111655001.6A Pending CN114328158A (en) | 2021-12-30 | 2021-12-30 | Abnormity monitoring method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114328158A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116089563A (en) * | 2022-07-28 | 2023-05-09 | 荣耀终端有限公司 | Log processing method and related device |
-
2021
- 2021-12-30 CN CN202111655001.6A patent/CN114328158A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116089563A (en) * | 2022-07-28 | 2023-05-09 | 荣耀终端有限公司 | Log processing method and related device |
| CN116089563B (en) * | 2022-07-28 | 2024-03-26 | 荣耀终端有限公司 | Log processing method and related device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10915204B2 (en) | Systems and methods for identifying faulty touch panel having intermittent field failures | |
| US9489292B2 (en) | Devices and methods for acquiring abnormal information | |
| CN110764945B (en) | Crash log processing method, device, equipment and storage medium | |
| US8156475B2 (en) | Device and method for testing embedded software using emulator | |
| US9170921B2 (en) | Application testing automation | |
| US20210064518A1 (en) | Methods Circuits Devices Systems and Functionally Associated Machine Executable Code For Automatic Failure Cause Identification in Software Code Testing | |
| US11327742B2 (en) | Affinity recommendation in software lifecycle management | |
| CN111274154A (en) | Automatic testing method, device, equipment and storage medium | |
| US20210342217A1 (en) | System and method for remotely diagnosing and repairing a computing device | |
| US8745600B2 (en) | Inserting test scripts | |
| CN110865944A (en) | Data analysis method and device for test case, storage medium and test equipment | |
| CN114328158A (en) | Abnormity monitoring method and device, electronic equipment and storage medium | |
| CN111949488A (en) | Hard disk fault prediction method and system, electronic equipment and storage medium | |
| US20170344461A1 (en) | Automated exception resolution during a software development session based on previous exception encounters | |
| US20210019253A1 (en) | Methods Circuits Devices Systems and Functionally Associated Machine Executable Code For Enhanced Automated Software Code Testing | |
| US20120310849A1 (en) | System and method for validating design of an electronic product | |
| CN110008074B (en) | Method, device and equipment for automatically testing and inquiring upper-layer interface of hardware information | |
| JP6747161B2 (en) | Software quality judgment method | |
| US9632879B2 (en) | Disk drive repair | |
| US9696986B2 (en) | Managing a code load | |
| CN102023916B (en) | Computer system detection method | |
| JP2009223714A (en) | Arithmetic circuit and failure analysis method of arithmetic circuit | |
| CN114218001A (en) | Fault repairing method and device, electronic equipment and readable storage medium | |
| US10380000B2 (en) | Multi environment aware debugger | |
| CN111026715A (en) | Data processing method and device, computer storage medium and electronic equipment |
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 |