Abnormal monitoring method, device, electronic equipment and storage medium

Abstract

The present disclosure relates to an exception monitoring method, device, electronic device and storage medium. The method is applied to a domain controller. The method includes: when a process exception is monitored, obtaining exception information corresponding to the abnormal process based on a core dump mechanism; generating an exception log according to the exception information, and uploading the exception information and the exception log to a target device, so that the target device generates an exception statistical graph according to the exception information, and locates the abnormal problem according to the exception log; that is, the embodiment of the present disclosure can obtain the exception information and exception logs of all processes including the container process through the core dump mechanism, effectively ensuring the stable operation of the domain controller system.

Description

Technical Field

[0001] The present disclosure relates to the field of computers, and in particular to an abnormality monitoring method, device, electronic device and storage medium. Background Art

[0002] In the field of vehicle autonomous driving, in order to ensure the safe operation of the vehicle, the running status of the application processes in the domain controller system deployed on the vehicle will be monitored, and abnormal processes will be promptly counted and repaired.

[0003] The current monitoring method used for application processes in the domain controller system, such as running the apport program, only generates exception logs for some host processes and cannot monitor all application process exceptions. Summary of the invention

[0004] The embodiments of the present disclosure provide an abnormality monitoring method, device, electronic device and storage medium to solve the technical problem that the existing domain controller system cannot monitor all application process abnormalities.

[0005] In a first aspect, an embodiment of the present disclosure provides an exception monitoring method, which is applied to a domain controller, and the method includes: when a process exception is monitored, obtaining exception information corresponding to the process where the exception occurs based on a core dump mechanism; generating an exception log according to the exception information, and uploading the exception information and the exception log to a target device, so that the target device generates an exception statistical graph according to the exception information, and locates the exception problem according to the exception log.

[0006] As an optional embodiment of the present disclosure, the obtaining of exception information corresponding to the abnormal process based on the core dump mechanism includes: obtaining the exception information corresponding to the abnormal process by reading the standard input of the core pipeline program.

[0007] As an optional embodiment of the present disclosure, the exception information includes the first process number of the process where the exception occurs in the container and the second process number of the process in the host machine; if the first process number is the same as the second process number, it is determined that the process where the exception occurs is a host machine process; if the first process number is different from the second process number, it is determined that the process where the exception occurs is a container process.

[0008] As an optional embodiment of the present disclosure, the exception information further includes: the absolute path of the executable file of the process where the exception occurs, the execution command and parameters, and the exception time.

[0009] As an optional embodiment of the present disclosure, the method also includes: obtaining the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time; uploading the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time to the target device, so that the target device locates the abnormal problem according to the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time uploaded to the target device and the abnormal log.

[0010] As an optional embodiment of the present disclosure, the uploading of the exception information and the exception log to the target device includes: automatically uploading the exception information and the exception log to the target device.

[0011] As an optional embodiment of the present disclosure, the method further includes: detecting whether there is abnormal information and abnormal log that have not been uploaded; if so, uploading the abnormal information and abnormal log that have not been uploaded.

[0012] In the second aspect, an embodiment of the present disclosure provides a process exception monitoring device, including: a monitoring module, which is used to obtain exception information corresponding to the process where the exception occurs based on a core dump mechanism when a process exception is monitored; an uploading module, which is used to generate an exception log according to the exception information, and upload the exception information and the exception log to a target device, so that the target device generates an exception statistical graph according to the exception information, and locates the exception problem according to the exception log.

[0013] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; the memory is used to store computer programs; and the processor is used to implement the steps of the abnormality monitoring method described in any one of the first aspects when executing the program stored in the memory.

[0014] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the abnormality monitoring method as described in any one of the first aspects.

[0015] The embodiments of the present disclosure provide an abnormality monitoring method, device, electronic device and storage medium, and the method is applied to a domain controller. The method includes: when a process abnormality is monitored, obtaining abnormality information corresponding to the abnormal process based on a core dump mechanism; generating an abnormality log according to the abnormality information, and uploading the abnormality information and the abnormality log to a target device, so that the target device generates an abnormality statistical graph according to the abnormality information, and locates the abnormal problem according to the abnormality log; that is, the embodiments of the present disclosure can obtain the abnormality information and abnormality logs of all processes including the container process through the core dump mechanism, effectively ensuring the stable operation of the domain controller system. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] 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 present disclosure.

[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0018] Figure 1 A flowchart of an abnormality monitoring method provided by an embodiment of the present disclosure;

[0019] Figure 2 A flowchart of another abnormality monitoring method provided by an embodiment of the present disclosure;

[0020] Figure 3 FIG. 1 is a flow chart of another abnormality monitoring method provided by an embodiment of the present disclosure;

[0021] Figure 4 A schematic diagram of the structure of a process abnormality monitoring device provided by an embodiment of the present disclosure;

[0022] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0024] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0025] First, the terms involved in this disclosure are explained:

[0026] Docker: A software virtualization mechanism that can isolate file systems and applications on the same operating system kernel. Each isolated unit is called a "container". Each application can run in a container, just like running in an independent operating system. This "operating system" has installed the complete operating environment that the application software depends on, and does not rely on the software environment of the host machine.

[0027] ROS: A typical system with complex and fragile dependencies. Various libraries have specific version requirements. If the dependencies are damaged and cannot be repaired, you can only spend a whole day reinstalling the operating system and deploying ROS and related development tools again before you can continue to use it. Therefore, we decided to move ROS to Docker to reduce the risk of damaged dependencies.

[0028] In the field of vehicle autonomous driving, in order to ensure the safe operation of the vehicle, the running status of the application process in the domain controller system on the vehicle will be monitored, and when an exception occurs in the application process (process termination, crash, etc.), the exception information and exception log will be reported to the background server to quickly repair online problems, quickly iterate, and ensure the stable operation of the domain controller system.

[0029] The current domain controller system monitors application process exceptions through the deployed Apport program. However, since the current domain controllers generally run the Ubuntu system, and the Ubuntu system integrates the Docker container and the ROS system, the processes in the Docker container and the ROS system run in the container, which increases the complexity of the domain controller system. The Apport program can only generate exception logs when some host processes are abnormal, but cannot generate exception logs when processes in the container are abnormal. In other words, the current domain controller system cannot monitor all application process exceptions, which is not conducive to the stable operation of the system.

[0030] In response to the above technical problems, the technical concept of the present invention is to replace the native Apport program with an exception monitoring method using a core dump mechanism, thereby realizing exception monitoring of all processes including container processes and improving the stability of system operation.

[0031] In addition, the Apport program has the following two problems. First, it cannot automatically upload exception logs. When the Apport program detects an abnormal application process, the user needs to manually upload the abnormal information, which is cumbersome. It is more likely that the user will find the operation troublesome and choose not to upload, resulting in the background server being unable to know which part of the application may still have vulnerabilities and unable to repair them in time. The abnormality may occur again, affecting the user experience. Second, users using the Ubuntu system cannot obtain abnormal information and cannot perform personalized transformation of the system. When the user chooses to upload the abnormal information, the abnormal information is also uploaded to the background server of the Ubuntu system, resulting in only the Ubuntu system R&D personnel being able to see the abnormal message, while the users of the Ubuntu system cannot view it, which is not conducive to the maintenance and personalized transformation of the Ubuntu system by the users.

[0032] In a first aspect, an embodiment of the present disclosure provides an abnormality monitoring method, wherein the abnormality monitoring method applies a domain controller. Figure 1 A flowchart of an abnormal monitoring method provided by an embodiment of the present disclosure is shown in FIG. Figure 1 As shown, the abnormal monitoring method includes:

[0033] Step S101: when a process exception is detected, the exception information corresponding to the abnormal process is obtained based on the core dump mechanism.

[0034] Specifically, the execution subject of the embodiment of the present disclosure is a domain controller deployed with a process abnormality monitoring device. Before executing step S101, it is necessary to pre-set the core file size upper limit, core file storage directory, etc. on the domain controller to enable the core-dump mechanism, that is, when a process is abnormal, the abnormal information corresponding to the abnormal process will be obtained, and the abnormal information can also be called a core file, and the core file is stored in the pre-configured storage directory.

[0035] As an optional embodiment, the step S101 of obtaining the exception information corresponding to the abnormal process based on the core dump mechanism includes: obtaining the exception information corresponding to the abnormal process by reading the standard input of the core pipeline program. Specifically, when an exception occurs in the process, the domain controller obtains the exception information by reading the standard input of the core-pattern pipeline.

[0036] As an optional embodiment, the exception information includes the first process number of the process where the exception occurs in the container and the second process number of the process in the host machine; if the first process number is the same as the second process number, it is determined that the process where the exception occurs is a host machine process; if the first process number is different from the second process number, it is determined that the process where the exception occurs is a container process.

[0037] Specifically, you can obtain the PID of the abnormal process in the container and the PID of the host through core-pattern. If the two process numbers are the same, it means that the process is a host process. If the two process numbers are different, it means that the process is a container process. In other words, users can determine whether the abnormality occurs in the container process or the host process based on the process number in the abnormal information.

[0038] As an optional embodiment, the exception information further includes: the absolute path of the executable file of the process where the exception occurs, the execution command and parameters, and the exception time.

[0039] Step S102: 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 graph according to the exception information and locates the exception problem according to the exception log.

[0040] Specifically, the domain controller can use debugging tools such as gdb to generate an exception log from the exception information, and upload the exception information and the exception log to the target device. After receiving the exception information, the target device will generate an exception statistical graph based on the exception information, such as counting the frequency of exceptions in each process, so as to facilitate R&D personnel to focus on a certain process, etc.; the exception log will also be displayed through the target device, so that the user can locate which program has a problem, and even refine it to the source file name of the code with the problem and the number of lines with errors, etc. Among them, the target device can not only be the background server of the Ubuntu system, but preferably, the target device can also be a device specified by the user using the Ubuntu system, so that the user using the Ubuntu system can smoothly view the exception statistical graph and the exception log, which is conducive to the personalized transformation and maintenance of the Ubuntu system.

[0041] As an optional embodiment, uploading the exception information and exception log to the target device in step S102 includes: automatically uploading the exception information and exception log to the target device. Specifically, in this embodiment, after obtaining the exception log, the exception information and exception log are automatically uploaded to the target device, without the need for manual upload by the user, thereby providing a better user experience.

[0042] The exception monitoring method provided by the embodiment of the present disclosure is applied to a domain controller. When a process exception is monitored, the exception information corresponding to the abnormal process is obtained based on the core dump mechanism; an exception log is generated according to the exception information, and the exception information and the exception log are uploaded to a target device, so that the target device generates an exception statistical graph according to the exception information and locates the abnormal problem according to the exception log; that is, the embodiment of the present disclosure can obtain the exception information and exception logs of all processes including the container process through the core dump mechanism, which effectively ensures the stable operation of the domain controller system, thereby ensuring the safety of the vehicle's automatic driving.

[0043] Based on the above embodiments, Figure 2 A flowchart of another abnormality monitoring method provided by an embodiment of the present disclosure is shown as follows: Figure 2 As shown, the abnormal monitoring method includes:

[0044] Step S201: When a process exception is detected, the exception information corresponding to the abnormal process is obtained based on the core dump mechanism.

[0045] Step S202: 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 graph according to the exception information.

[0046] Step S203: Obtain the system operation log, kernel log, and container engine log corresponding to the domain controller before the abnormal time.

[0047] Step S204: Upload the system operation log, kernel log, and container engine log corresponding to the domain controller before the abnormal time to the target device, so that the target device can locate the abnormal problem according to the system operation log, kernel log, and container engine log corresponding to the domain controller before the abnormal time uploaded to the target device and the abnormal log.

[0048] The implementation methods of step S201 and step S202 in this embodiment are similar to those of step S101 and step S102 in the above embodiment, and are not described again here.

[0049] The difference from the above embodiment is that, in order to locate the specific location of the abnormal problem more accurately and quickly, in this embodiment, the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time are obtained; the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time are uploaded to the target device, so that the target device locates the abnormal problem according to the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time uploaded to the target device and the abnormal log.

[0050] Specifically, in this embodiment, in addition to uploading the exception log to the target device, the domain controller will also capture the system operation log, kernel log, container engine log, and even ROS error log before the exception occurs, and upload these captured logs to the target device to assist in analyzing and solving the exception problem.

[0051] As an optional embodiment, the method further includes: detecting whether there is abnormal information and abnormal log that have not been uploaded; if so, uploading the abnormal information and abnormal log that have not been uploaded.

[0052] Specifically, the domain controller can periodically scan the system to see if there are any abnormal information and abnormal logs that have not been uploaded. If so, upload them. If not or they have been uploaded, continue monitoring. Figure 3 The figure shows a flow chart of another abnormal monitoring method provided by an embodiment of the present disclosure. First, the domain controller detects whether there is any unuploaded crash information and crash log. If so, the unuploaded crash information and crash log are uploaded. If not, or after the upload is completed, the application process is monitored, and when the application process crash is monitored, the crash information and crash log are obtained based on the core-dum mechanism, and the crash information and crash log are automatically uploaded to the target device.

[0053] The abnormality monitoring method provided by the embodiment of the present disclosure obtains the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time; uploads the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time to the target device, so that the target device locates the abnormal problem according to the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time uploaded to the target device and the abnormal log; that is, in addition to uploading the abnormal log, the embodiment of the present disclosure also uploads the system operation log, kernel log and container engine log before the abnormality occurs to the target device, so as to assist the user to comprehensively analyze and solve the abnormal problem according to these logs, so as to accurately and quickly locate the problem.

[0054] In a second aspect, an embodiment of the present disclosure provides a process abnormality monitoring device. Figure 4 A schematic diagram of the structure of a process abnormality monitoring device provided by an embodiment of the present disclosure is shown in FIG. Figure 4 As shown, the process abnormality monitoring device includes:

[0055] The monitoring module 10 is used to obtain the exception information corresponding to the abnormal process based on the core dump mechanism when a process exception is monitored; the uploading module 20 is used 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 can generate an exception statistical chart according to the exception information and locate the abnormal problem according to the exception log.

[0056] As an optional embodiment of the present disclosure, the monitoring module 10 is specifically used to obtain the abnormal information corresponding to the abnormal process by reading the standard input of the core pipeline program.

[0057] As an optional embodiment of the present disclosure, the exception information includes the first process number of the process where the exception occurs in the container and the second process number of the process in the host machine; if the first process number is the same as the second process number, it is determined that the process where the exception occurs is a host machine process; if the first process number is different from the second process number, it is determined that the process where the exception occurs is a container process.

[0058] As an optional embodiment of the present disclosure, the exception information further includes: the absolute path of the executable file of the process where the exception occurs, the execution command and parameters, and the exception time.

[0059] As an optional embodiment of the present disclosure, the monitoring module 10 is also used to: obtain the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time; the uploading module 20 is also used to: upload the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time to the target device, so that the target device can locate the abnormal problem according to the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time uploaded to the target device and the abnormal log.

[0060] As an optional embodiment of the present disclosure, the upload module 20 is specifically used to automatically upload the exception information and the exception log to the target device.

[0061] As an optional embodiment of the present disclosure, the device further includes a detection module 30, which is used to: detect whether there is any abnormal information and abnormal log that has not been uploaded; if so, upload the abnormal information and abnormal log that have not been uploaded through the upload module 20.

[0062] The implementation principle and technical effect of the process abnormality monitoring device provided in the embodiment of the present disclosure are similar to those of the above embodiment and will not be repeated here.

[0063] The process exception monitoring device provided by the embodiment of the present disclosure is used, through the monitoring module, to obtain the exception information corresponding to the abnormal process based on the core dump mechanism when the process exception is monitored; the uploading module is used 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 the exception problem according to the exception log; that is, the embodiment of the present disclosure can obtain the exception information and exception logs of all processes including the container process through the core dump mechanism, which effectively ensures the stable operation of the domain controller system.

[0064] like Figure 5 As shown, an embodiment of the present disclosure provides an electronic device, including a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0065] Memory 113, used for storing computer programs;

[0066] In one embodiment of the present disclosure, the processor 111 is configured to implement the steps of the process exception monitoring method provided by any one of the aforementioned method embodiments when executing a program stored in the memory 113 .

[0067] The implementation principle and technical effects of the electronic device provided by the embodiment of the present disclosure are similar to those of the above embodiment and will not be repeated here.

[0068] The above-mentioned memory 113 can be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk or a ROM. The memory 113 has a storage space for program codes for executing any method steps in the above-mentioned method. For example, the storage space for program codes may include various program codes for implementing the various steps in the above method respectively. These program codes can be read from or written into one or more computer program products. These computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks. Such computer program products are usually portable or fixed storage units. The storage unit may have a storage segment or storage space arranged similarly to the memory 113 in the above-mentioned electronic device. The program code can be compressed, for example, in an appropriate form. Generally, the storage unit includes a program for executing the method steps according to an embodiment of the present disclosure, that is, a code that can be read by a processor such as 111, which, when run by an electronic device, causes the electronic device to execute the various steps in the method described above.

[0069] The embodiment of the present disclosure further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the process abnormality monitoring method described above are implemented.

[0070] The computer-readable storage medium may be included in the device / apparatus described in the above embodiment; or it may exist independently without being assembled into the device / apparatus. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0071] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, such as but not limited to: a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0072] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0073] The foregoing is merely a specific embodiment of the present disclosure, which enables those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features applied herein.

Claims

1. An abnormality monitoring method, characterized in that: Applied to a domain controller, the method comprises: When a process exception is detected, the exception information corresponding to the abnormal process is obtained based on the core dump mechanism; 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 graph according to the exception information and locates the exception problem according to the exception log; The abnormal information includes the first process number of the abnormal process in the container and the second process number of the process in the host machine; If the first process number is the same as the second process number, determining that the abnormal process is a host process; If the first process number is different from the second process number, determining that the abnormal process is a container process; The method further includes: obtaining a system operation log, a kernel log, and a container engine log corresponding to the domain controller before the abnormal time; The system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time are uploaded to the target device, so that the target device can locate the abnormal problem according to the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time and the abnormal log.

2. The method according to claim 1, characterized in that The obtaining of the abnormal information corresponding to the abnormal process based on the core dump mechanism includes: By reading the standard input of the core pipeline program, the exception information corresponding to the process where the exception occurs is obtained.

3. The method according to claim 1, characterized in that The abnormal information also includes: the absolute path of the executable file of the process where the abnormality occurs, the execution command and parameters, and the abnormal time.

4. The method according to any one of claims 1 to 3, characterized in that: The uploading of the abnormal information and abnormal log to the target device includes: Automatically upload the abnormal information and abnormal log to the target device.

5. The method according to claim 4, characterized in that The method further comprises: Check whether there is any abnormal information and abnormal log that has not been uploaded; If yes, upload the abnormal information and abnormal log that have not been uploaded.

6. A process abnormality monitoring device, characterized in that: include: The monitoring module is used to obtain the abnormal information corresponding to the abnormal process based on the core dump mechanism when the monitored process is abnormal; An uploading module is used to generate an abnormality log according to the abnormality information, and upload the abnormality information and the abnormality log to the target device, so that the target device generates an abnormality statistical graph according to the abnormality information and locates the abnormal problem according to the abnormality log; The abnormal information includes a first process number of the abnormal process in the container and a second process number of the process in the host machine; if the first process number is the same as the second process number, it is determined that the abnormal process is a host process; if the first process number is different from the second process number, it is determined that the abnormal process is a container process; The monitoring module is also used to: obtain the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time; The upload module is also used to upload the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time to the target device, so that the target device can locate the abnormal problem according to the system operation log, kernel log and container engine log corresponding to the domain controller before the abnormal time and the abnormal log.

7. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; The processor is used to implement the steps of the abnormality monitoring method described in any one of claims 1 to 5 when executing the program stored in the memory.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the abnormality monitoring method according to any one of claims 1 to 5 are implemented.

Images