Fault monitoring system based on embedded Linux operating system

Abstract

The invention belongs to the technical field of computer system software, and particularly relates to a fault monitoring system based on an embedded Linux operating system, which is used for visually monitoring the embedded Linux operating system. The fault monitoring system comprises a monitoring data acquisition module, a fault diagnosis and processing module, a log management module and a visualization module. According to the method, the change of the system state can be captured and fed back in time, rapid fault judgment and processing are realized, and a visual graphical interface is provided, so that the usability is improved.

Description

Technical Field

[0001] The invention belongs to the technical field of computer system software, and in particular relates to a fault monitoring system based on an embedded Linux operating system. Background Art

[0002] With the rapid development of multiple embedded fields such as the Internet of Things, home appliances, and industrial control, embedded systems, as key technologies, are becoming increasingly complex, and the possibility of failures during operation is also increasing. Once an embedded device fails, it will cause economic losses. Therefore, how to monitor system failures in a timely and effective manner, and quickly locate and solve problems has become an important research topic in embedded system development. The current fault monitoring system mainly uses text log records, and problems need to be discovered through manual analysis, which limits the real-time and visualization of fault monitoring. Summary of the invention

[0003] In view of this, the present invention provides a fault monitoring system based on an embedded Linux operating system, which can timely capture and feedback changes in system status, realize rapid fault judgment and processing, and has an intuitive graphical interface to improve ease of use.

[0004] The technical solution of the present invention is:

[0005] A fault monitoring system based on an embedded Linux operating system is used to visually monitor the embedded Linux operating system; the fault monitoring system comprises:

[0006] Monitoring data acquisition module, collecting key data generated during the operation of embedded Linux operating system;

[0007] The fault diagnosis and processing module analyzes the data generated by the system monitoring data acquisition module, determines the current operating status of the embedded Linux operating system, and takes response measures when necessary;

[0008] The log management module effectively classifies and stores the logs generated during the operation of the embedded Linux operating system;

[0009] The visualization module presents the embedded Linux operating system running data, fault information and performance status through an intuitive visualization interface and human-computer interaction.

[0010] Furthermore, the system monitoring data acquisition module includes:

[0011] System monitor, by collecting overall, kernel and log information of hardware and embedded Linux operating system;

[0012] Application performance collector collects information related to the application's running status, start time, end time, exit status, number of open files, used semaphores, timeout status, memory usage, and CPU usage.

[0013] Furthermore, the fault diagnosis and processing module is divided into three processing levels based on the fault classification mechanism in the fault processor:

[0014] Level 1 faults correspond to non-critical application internal errors, non-critical application fatal errors, and non-critical application abnormal exits. When a level 1 fault is detected, the default fault ignore measure is adopted but the fault log is stored;

[0015] Level 2 faults correspond to critical application internal errors, critical application fatal errors, and critical application unresponsiveness. When a level 2 fault is detected, the script in the fault handler is used to resolve the problem and record the fault log.

[0016] The third level fault corresponds to a fatal error of the embedded Linux operating system. When a third level fault is detected, the kernel crash log is saved through kernel dump, and the embedded Linux operating system is restarted immediately.

[0017] Further, the log management module is used to store system events, kernel events, hardware events, application events and system log events;

[0018] System events include basic system information; kernel events include kernel crashes and driver crashes; hardware events include multi-core resource usage, hard disk usage and performance, and network traffic resource usage; application events include application crashes, deadlocks, exceptions, and status during operation; system log events include system startup, restart, shutdown, and application service status;

[0019] The system events, kernel events, hardware events and system log events correspond to the information collected by the system monitoring data collection module; the application events correspond to the information collected by the application performance collector module.

[0020] Furthermore, the system status monitor is used to monitor and collect information of the embedded Linux operating system, track the usage of system resources in real time, and provide basic data support for fault diagnosis.

[0021] Furthermore, the application performance collector is used to collect the operating status and performance data of the business applications running on the system, and analyze the operating status of the applications through data indicators;

[0022] The data buffer configured by the monitoring data acquisition module is used as a temporary data storage area to cache the collected system and application information to maintain the real-time and integrity of the data;

[0023] The data transmission manager configured in the monitoring data acquisition module uses a data compression algorithm to transmit the cached data to a designated location.

[0024] Further, the fault diagnosis and processing module is composed of a fault detector and a fault processor;

[0025] The fault detector uses a preset fault judgment rule base and key performance indicator monitoring to analyze and interpret the collected data in real time and identify abnormal situations. When a fault is detected, it divides the fault into different levels according to the severity and urgency of the fault, and sends warning information in the form of a visual page pop-up window.

[0026] As an execution unit, the fault handler responds quickly and takes appropriate measures when a fault occurs, executing the preset processing script to minimize the impact of the fault.

[0027] Further, the log management module includes: an offline log storage, an online log storage and a log parser;

[0028] The offline log storage is used to store the operation logs with scheduled coverage and to trace back the historical data when necessary;

[0029] The online log storage records the system operation status and fault information in real time, and continuously updates the log data while the system is running, ensuring that the latest system status and operation records can be obtained online at all times;

[0030] Beneficial effects of the present invention:

[0031] The present invention can capture and store the fault information of the embedded Linux operating system in real time locally, use the rule base to quickly identify and locate the fault, and then use the server-side visualized graphical interface to enable users to intuitively monitor the system operation status and take necessary processing measures in time, thereby providing a strong guarantee for the stable operation of the embedded Linux operating system and significantly optimizing the system performance and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0033] Figure 1 System monitoring data collection architecture diagram;

[0034] Figure 2 Fault diagnosis and processing architecture diagram;

[0035] Figure 3 Visual module architecture diagram;

[0036] Figure 4 Schematic diagram of the visual fault monitoring system flow based on embedded Linux operating system. DETAILED DESCRIPTION

[0037] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0038] The following describes the embodiments of the present disclosure through specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present disclosure.

[0039] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present disclosure, it should be understood by those skilled in the art that an aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein can be used to implement this device and / or practice this method.

[0040] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present disclosure. The illustrations only show components related to the present disclosure rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0041] Additionally, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects described may be practiced without these specific details.

[0042] In one embodiment of the present invention, referring to Figure 1-Figure 4, a fault monitoring system based on an embedded Linux operating system is proposed, which is used to visually monitor the embedded Linux operating system; the fault monitoring system includes:

[0043] Monitoring data acquisition module, collecting key data generated during the operation of embedded Linux operating system;

[0044] The fault diagnosis and processing module analyzes the data generated by the system monitoring data acquisition module, determines the current operating status of the embedded Linux operating system, and takes response measures when necessary;

[0045] The log management module effectively classifies and stores the logs generated during the operation of the embedded Linux operating system;

[0046] The visualization module presents the embedded Linux operating system running data, fault information and performance status through an intuitive visualization interface and human-computer interaction.

[0047] In this embodiment, the system monitoring data acquisition module includes:

[0048] System monitor, by collecting overall, kernel and log information of hardware and embedded Linux operating system;

[0049] Application performance collector collects information related to the application's running status, start time, end time, exit status, number of open files, used semaphores, timeout status, memory usage, and CPU usage.

[0050] In this embodiment, the fault diagnosis and processing module is divided into three processing levels based on the fault classification mechanism in the fault processor:

[0051] Level 1 faults correspond to non-critical application internal errors, non-critical application fatal errors, and non-critical application abnormal exits. When a level 1 fault is detected, the default fault ignore measure is adopted but the fault log is stored;

[0052] Level 2 faults correspond to critical application internal errors, critical application fatal errors, and critical application unresponsiveness. When a level 2 fault is detected, the script in the fault handler is used to resolve the problem and record the fault log.

[0053] The third level fault corresponds to a fatal error of the embedded Linux operating system. When a third level fault is detected, the kernel crash log is saved through kernel dump, and the embedded Linux operating system is restarted immediately.

[0054] In this embodiment, the log management module is used to store system events, kernel events, hardware events, application events and system log events;

[0055] System events include basic system information; kernel events include kernel crashes and driver crashes; hardware events include multi-core resource usage, hard disk usage and performance, and network traffic resource usage; application events include application crashes, deadlocks, exceptions, and status during operation; system log events include system startup, restart, shutdown, and application service status;

[0056] The system events, kernel events, hardware events and system log events correspond to the information collected by the system monitoring data collection module; the application events correspond to the information collected by the application performance collector module.

[0057] In this embodiment, the system status monitor is used to monitor and collect information of the embedded Linux operating system, track the usage of system resources in real time, and provide basic data support for fault diagnosis.

[0058] In this embodiment, the application performance collector is used to collect the operating status and performance data of the business application running on the system, and analyze the operating status of the application through data indicators;

[0059] The data buffer configured by the monitoring data acquisition module is used as a temporary data storage area to cache the collected system and application information to maintain the real-time and integrity of the data;

[0060] The data transmission manager configured in the monitoring data acquisition module uses a data compression algorithm to transmit the cached data to a designated location.

[0061] In this embodiment, the fault diagnosis and processing module is composed of a fault detector and a fault processor;

[0062] The fault detector uses a preset fault judgment rule base and key performance indicator monitoring to analyze and interpret the collected data in real time and identify abnormal situations. When a fault is detected, it divides the fault into different levels according to the severity and urgency of the fault, and sends warning information in the form of a visual page pop-up window.

[0063] As an execution unit, the fault handler responds quickly and takes appropriate measures when a fault occurs, executing the preset processing script to minimize the impact of the fault.

[0064] In this embodiment, the log management module includes: an offline log storage, an online log storage, and a log parser;

[0065] The offline log storage is used to store the operation logs with scheduled coverage and to trace back the historical data when necessary;

[0066] The online log storage records the system operation status and fault information in real time, and continuously updates the log data while the system is running, ensuring that the latest system status and operation records can be obtained online at all times;

[0067] The log parser is responsible for classifying, filtering and analyzing the stored log data, classifying the logs according to the event type, filtering out the relevant log information using filtering rules, collecting and parsing the results of the fault diagnosis and processing module analysis, generating structured data, and writing the structured data into a JSON format file for storage.

[0068] In this embodiment, the visualization module includes a status displayer and a configuration manager;

[0069] The status displayer dynamically displays data information in a graphical interface;

[0070] The configuration manager deploys the server IP, establishes network protocol information interaction between the client and the server, and then sets the log storage path to ensure that the logs are stored in the correct location; users can configure to view different types of data information based on specific monitoring needs.

[0071] In this embodiment, the visualization module is deployed on the client host; during the operation of the embedded Linux operating system, the startup port number of the embedded Linux operating system server is configured, and the fault monitoring system starts to collect system status information and application information during the operation;

[0072] The client installs the visualization module plug-in through vscode; the client starts the visualization module plug-in, configures the network IP address and port number of the embedded Linux operating system server, and enters the server embedded Linux operating system platform that needs to be viewed currently;

[0073] The status displayer of the visualization module is used to display the overall configuration interface, system monitoring interface, process monitoring interface, network monitoring interface, hardware monitoring interface, driver monitoring interface, performance monitoring interface, kernel and middleware monitoring interface, log monitoring interface and fault analysis interface; users interact with the interface by clicking the mouse to query the required information.

[0074] In this embodiment, the server of the visual fault monitoring system is deployed in the embedded Linux operating system, and the client of the visual fault monitoring system is deployed in the host. During the operation of the embedded Linux operating system, the server startup port number is configured, and the visual fault monitoring system starts to collect system status information and application information during the operation. The client installs the visualization module plug-in through vscode, starts the plug-in, configures the network IP address and port number of the server, and enters the server embedded operating system platform that needs to be viewed.

[0075] When the visual fault monitoring system starts running, the system status monitor collects the resource usage of the system through the corresponding shell command, and the application performance collector collects the resource usage of the application process through the script. The above collected data is placed in the ring buffer and sent to the fault diagnosis and processing module through the data transmission manager.

[0076] The fault detector uses the expert knowledge base to determine whether fault information is generated. If it is detected that the current system is running normally, the collected information is directly stored in the log module. If a fault is detected, the fault classification mechanism is used to remind the user of the current fault severity. For serious faults, such as kernel crashes that cause system freezes, the fault handler stores the fault site information and restarts the system. For minor faults, such as application timeouts, the application is restarted and the fault information is also stored in the log module.

[0077] The collected data will be processed by offline storage and online log storage. Offline log storage saves data in JSON format so that it can be retrieved at any time when needed; online log storage sends data to the log parser in real time via HTTP protocol, and then parses, classifies and summarizes the data.

[0078] The processed data is sent to the visualization module, and the data is visualized on the user interface. Users can intuitively see various status information of the current system, including ten interfaces: overall configuration, system monitoring, process monitoring, network monitoring, hardware monitoring, driver monitoring, performance monitoring, kernel and middleware monitoring, log monitoring, and fault analysis. Users interact with the interface by clicking the mouse to query the required information.

[0079] The above is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present disclosure should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A fault monitoring system based on an embedded Linux operating system, characterized in that: Used to visually monitor embedded Linux operating systems; The fault monitoring system comprises: Monitoring data acquisition module, collecting key data generated during the operation of embedded Linux operating system; The fault diagnosis and processing module analyzes the data generated by the system monitoring data acquisition module, determines the current operating status of the embedded Linux operating system, and takes response measures when necessary; The log management module effectively classifies and stores the logs generated during the operation of the embedded Linux operating system; The visualization module presents the embedded Linux operating system running data, fault information and performance status through an intuitive visualization interface and human-computer interaction.

2. The fault monitoring system based on embedded Linux operating system according to claim 1, characterized in that: The system monitoring data acquisition module includes: System monitor, by collecting overall, kernel and log information of hardware and embedded Linux operating system; Application performance collector collects information related to the application's running status, start time, end time, exit status, number of open files, used semaphores, timeout status, memory usage, and CPU usage.

3. The fault monitoring system based on embedded Linux operating system according to claim 2 is characterized in that: The fault diagnosis and processing module is divided into three processing levels based on the fault classification mechanism in the fault processor: Level 1 faults correspond to non-critical application internal errors, non-critical application fatal errors, and non-critical application abnormal exits. When a level 1 fault is detected, the default fault ignore measure is adopted but the fault log is stored; Level 2 faults correspond to critical application internal errors, critical application fatal errors, and critical application unresponsiveness. When a level 2 fault is detected, the script in the fault handler is used to resolve the problem and record the fault log. The third level fault corresponds to a fatal error of the embedded Linux operating system. When a third level fault is detected, the kernel crash log is saved through kernel dump, and the embedded Linux operating system is restarted immediately.

4. The fault monitoring system based on embedded Linux operating system according to claim 3 is characterized in that: The log management module is used to store system events, kernel events, hardware events, application events and system log events; System events include basic system information; kernel events include kernel crashes and driver crashes; hardware events include multi-core resource usage, hard disk usage and performance, and network traffic resource usage; application events include application crashes, deadlocks, exceptions, and status during operation; system log events include system startup, restart, shutdown, and application service status; The system events, kernel events, hardware events and system log events correspond to the information collected by the system monitoring data collection module; the application events correspond to the information collected by the application performance collector module.

5. The fault monitoring system based on embedded Linux operating system according to claim 4 is characterized in that: The system status monitor is used to monitor and collect information of the embedded Linux operating system, track the usage of system resources in real time, and provide basic data support for fault diagnosis.

6. The fault monitoring system based on embedded Linux operating system according to claim 5, characterized in that: The application performance collector is used to collect the operating status and performance data of business applications running on the system, and analyze the operating status of the applications through data indicators; The data buffer configured by the monitoring data acquisition module is used as a temporary data storage area to cache the collected system and application information to maintain the real-time and integrity of the data; The data transmission manager configured in the monitoring data acquisition module uses a data compression algorithm to transmit the cached data to a designated location.

7. The fault monitoring system based on embedded Linux operating system according to claim 6, characterized in that: The fault diagnosis and processing module consists of a fault detector and a fault processor; The fault detector uses a preset fault determination rule base and key performance indicator monitoring to analyze and interpret the collected data in real time and identify abnormal situations; When a fault is detected, different fault levels are classified according to the severity and urgency of the fault, and warning information is sent in the form of a pop-up window on the visualization page; As an execution unit, the fault handler responds quickly and takes appropriate measures when a fault occurs, executing the preset processing script to minimize the impact of the fault.

8. The fault monitoring system based on embedded Linux operating system according to claim 7, characterized in that: The log management module includes: offline log storage, online log storage and log parser; The offline log storage is used to store the operation logs with scheduled coverage and to trace back the historical data when necessary; The online log storage records the system operation status and fault information in real time, and continuously updates the log data while the system is running, ensuring that the latest system status and operation records can be obtained online at all times; The log parser is responsible for classifying, filtering and analyzing the stored log data, classifying the logs according to the event type, filtering out the relevant log information using filtering rules, collecting and parsing the results of the fault diagnosis and processing module analysis, generating structured data, and writing the structured data into a JSON format file for storage.

9. The fault monitoring system based on embedded Linux operating system according to claim 1, characterized in that: The visualization module includes a status displayer and a configuration manager; The status displayer dynamically displays data information in a graphical interface; The configuration manager deploys the server IP, establishes network protocol information interaction between the client and the server, and then sets the log storage path to ensure that the logs are stored in the correct location; users can configure to view different types of data information based on specific monitoring needs.

10. The fault monitoring system based on embedded Linux operating system according to claim 9, characterized in that: The visualization module is deployed on the client host; during the operation of the embedded Linux operating system, the startup port number of the embedded Linux operating system server is configured, and the fault monitoring system starts to collect system status information and application information during the operation; The client installs the visualization module plug-in through vscode; the client starts the visualization module plug-in, configures the network IP address and port number of the embedded Linux operating system server, and enters the server embedded Linux operating system platform that needs to be viewed currently; The status displayer of the visualization module is used to display the overall configuration interface, system monitoring interface, process monitoring interface, network monitoring interface, hardware monitoring interface, driver monitoring interface, performance monitoring interface, kernel and middleware monitoring interface, log monitoring interface and fault analysis interface; Users interact with the interface by clicking the mouse to query the required information.

Images