A service monitoring terminal system based on real-time visualized data analysis

Abstract

The application discloses a service monitoring terminal based on real-time visualized data analysis, which comprises a system management component, a monitoring management component and a log management component. The monitoring management component transmits the received subscribed service detail data packet, service fault log data packet and service combination plan to the system management component for processing. The system management component displays the state of each service, the calling relationship between the services and the performance of the node where each service is located according to the feedback result of the system management component, and transmits the service life cycle change message formulated by the user to the system management component and then publishes the message to the corresponding service, so as to control each service to support the service work according to the prescribed service combination plan in real time. Meanwhile, the system management component stores and exports the real-time data of the service key in the log recording component. The application can accurately grasp the state of the service and guarantee the development and maintenance of the service architecture.

Description

Technical Field

[0001] This invention relates to software service technology, and in particular to a service monitoring terminal system based on real-time visual data analysis for the field of unmanned aerial vehicle (UAV) command and control. Background Technology

[0002] Currently, UAV ground station software adopts a component-based architecture, which will gradually transition to a service-oriented architecture. The advantage of this architecture is that a large monolithic software application can be broken down into a set of independently developed, deployed, tested, and run service modules. Lightweight communication mechanisms are used between services, adhering to the architectural principles of high cohesion and low coupling. With the rapid development of UAV technology in China, the number of services required for UAV flight operations on the ground station is also growing rapidly. Service-oriented applications bring significant challenges to system operation and maintenance. These challenges include difficulties in error localization and troubleshooting, and the difficulty in clarifying service call relationships. These problems become increasingly complex as the number of service modules increases.

[0003] The operating environment of information systems based on service-oriented architecture is constantly changing, and all devices are untrusted, potentially leading to overload or unexpected failures at any time. Therefore, real-time monitoring of the distributed service operating environment under a service-oriented architecture is necessary to quickly grasp the service quality and system performance at any given moment, and to promptly address service quality degradation or failures. Existing service monitoring systems monitor the service quality of a single node of a specific service provider from the perspective of the service user, and can only collect and monitor system performance indicators, but cannot statistically analyze service quality indicators within the service process itself.

[0004] As the operational complexity of drone command and control systems increases, a real-time service monitoring terminal system is urgently needed to monitor the performance of all service modules and trace their call chains in order to meet the requirements of both offline control and efficient online operation of service modules, thereby ensuring their efficient and healthy operation. Summary of the Invention

[0005] The purpose of this invention is to provide a service monitoring terminal system based on real-time visual data analysis, which is mainly used for network topology monitoring, service information statistics, and service lifecycle control, to accurately grasp the status of services and ensure the development and maintenance of service-oriented architecture.

[0006] The objective of this invention is achieved through the following technical solution:

[0007] A service monitoring terminal based on real-time visualization data analysis includes a system management component, a monitoring management component, and a log management component. The monitoring management component transmits the received detailed data packets of each subscribed service, the fault log data packets of each service, and the service combination plan to the system management component for processing. Based on the feedback from the system management component, it displays the status of each service, the calling relationship between each service, and the performance of the node where each service is located. It also transmits the service lifecycle change messages specified by the user to the system management component and publishes them to the corresponding services, thereby controlling each service in real time to support service work with the specified service combination plan.

[0008] Meanwhile, the system management component stores and exports service-critical real-time data in the log recording component.

[0009] Preferably, the system management component includes a main interface management module and a data communication module; the monitoring management component includes a service monitoring module, a service topology display and control module, a service status display and control module, a service lifecycle display and control module, and a service performance indicator display and control module.

[0010] The main interface management module is used to manage the relative position, size, and color scheme of each display interface, create, delete, and save page layouts, and save all page layouts to the database.

[0011] The data communication module processes the detailed data packets, fault log data packets, and service combination plans obtained from the service monitoring module. It extracts the node number, service number, service name, and service status and passes them to the service status display and control module. It also extracts service call information and passes it to the service topology display module. Furthermore, it extracts the CPU utilization, memory utilization, node load, workload, and response latency of each node and provides them to the service performance indicator display and control module. The module periodically interacts with the application server and publishes service lifecycle change messages generated by the service lifecycle display and control module to the corresponding services.

[0012] The service monitoring module periodically sends subscription requests to the service management software through the DDS interface to obtain detailed data packets, fault log data packets, and service combination plans for each service.

[0013] The service status display and control module obtains the node number, service number, service name, service status and other node and service information of each service from the data communication module to generate a list for visual display. Each service in the list provides operation buttons to support users to make service lifecycle change requests for the selected service.

[0014] The service topology display module obtains service call information from the data communication module, classifies it according to nodes and services, obtains the call chain relationship between different services between nodes, and generates a topology display view with service interaction function for display. It also provides service operation buttons for the services displayed on the topology display view, allowing users to indicate service lifecycle change requests for a certain type of service on a selected node.

[0015] The service performance indicator display and control module will construct a real-time and continuous visualization view from the CPU utilization, memory utilization, node load, workload, and response latency obtained from the data communication module, and monitor the real-time data and performance trends of the performance indicators.

[0016] The service lifecycle display and control module displays the service lifecycle change requests submitted by the user in the service status display and control module and the service topology display module. After confirmation, it generates a service lifecycle change message and sends it to the data communication module.

[0017] Preferably, the monitoring and management component also includes a service status restoration module; the log management component includes a log recording module and a fault analysis module.

[0018] The logging module forwards the fault log data packets sent by the data communication module to the fault analysis module. The fault analysis module feeds back the fault analysis results to the data communication module, which then sends the fault analysis results to the service restoration module. Based on the fault analysis results, the service restoration module determines the services that need to be enabled or disabled, generates service lifecycle change requests for these services, and sends them to the service lifecycle display and control module. After confirmation with the user, the service lifecycle display and control module generates a service lifecycle change message.

[0019] Preferably, the log management component also includes a file storage module to export different types of recorded information to a database or text file for categorized storage.

[0020] Preferably, the service monitoring terminal based on real-time visualization data analysis also includes a bridging control component, which includes a service composition and reconstruction module.

[0021] The service component refactoring module displays service composition plans for multiple different scenarios. Users can select a service composition plan as needed in the service component refactoring module, configure it flexibly, and start a custom service composition plan. After the user builds a custom service composition plan, the service component refactoring module will generate a service lifecycle change message based on the service composition plan and send it to the data communication module. The data communication module will then send the service lifecycle change message to the service publisher, waiting for the service to be redeployed.

[0022] Ideally, during solution switching, the service component refactoring module first analyzes the new service composition plan and the old service composition plan, and only generates service lifecycle change messages for services whose status needs to be changed.

[0023] The beneficial effects of this invention are as follows:

[0024] The service monitoring terminal system based on real-time visual data analysis provided by this invention monitors multiple nodes and services in a distributed and complex topology. The monitoring metrics include system performance metrics of service nodes and quality performance metrics of the services themselves. Simultaneously, the service monitoring terminal system's business logic and UI interface collect, store, and display rich, multi-dimensional visual data. Through non-intrusive observation of real-time data such as service network topology and service information, it quickly and accurately grasps the status of services and locates problems in faulty services, ensuring efficient and healthy service operation. Attached Figure Description

[0025] Figure 1 This is the system logic architecture diagram of the present invention;

[0026] Figure 2 This is an exploded view of the system functional modules of the present invention;

[0027] Figure 3 This is the overall cross-linking diagram of the system of the present invention. Detailed Implementation

[0028] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments.

[0029] like Figure 1 As shown in this embodiment, a service monitoring terminal system based on real-time visualization data analysis features high real-time performance, low latency, and strong stability. It adopts a client / server architecture and specifically includes four components: a system management component, a monitoring management component, a log management component, and a bridging control component. Each component employs a layered logical architecture, which can be divided into a view layer, a business logic layer, and a data layer from top to bottom. The view layer primarily serves as the human-computer interaction interface for each component, used for various visualization operations and data display. The business logic layer contains the business logic of each component, supporting the implementation of its functions. The data layer implements various database operations, log file operations, and DDS communication. This architecture enables the monitoring system to perform real-time monitoring of services, status restoration, combined plan refactoring, fault analysis, and other operations.

[0030] The monitoring and management component receives detailed data packets of each subscribed service, fault log data packets of each service, and service composition plans, and passes them to the system management component for processing. Based on the feedback from the system management component, it displays the status of each service, the call relationships between services, and the performance of the nodes where each service is located. It also passes user-defined service lifecycle change messages to the system management component and publishes them to the corresponding services, thereby controlling each service in real time to support the stable and continuous operation of the service according to the specified service composition plan.

[0031] The logging component is mainly used to store and export critical real-time data of the service, and to perform anomaly and fault analysis based on the service information logs, thereby supporting functions such as service composition plan reconstruction and service anomaly state restoration.

[0032] The bridging control component is mainly used to allow users to flexibly replan their service portfolio and control the lifecycle of corresponding services based on the latest service portfolio plan, enabling online switching of service solutions.

[0033] See Figure 2 As shown, the system management components include a main interface management module and a data communication module.

[0034] The monitoring and management components include a service monitoring module, a service status restoration module, a service topology display and control module, a service status display and control module, a service lifecycle display and control module, and a service performance indicator display and control module.

[0035] The log management component includes a file storage module, a log recording module, and a fault analysis module.

[0036] The bridging control component includes a service composition refactoring module.

[0037] like Figure 3 As shown, the main interface management module is used to render the main interface and optimize the page layout. It can manage the relative position, size, and color scheme of the display interfaces of each module in the system management component, monitoring management component, log management component, and bridging control component. It can perform operations such as creating, deleting, and saving page layouts, and save all page layouts to the database to realize the page layout memory function. Modifications to the page layout will not be reset when the software is restarted.

[0038] like Figure 3As shown, the data communication module, acting as the system's data processing center, processes the detailed data packets, fault log data packets, and service combination plans obtained from the service monitoring module of the monitoring and management component. It extracts service status information such as node number, service number, service name, and service status, and transmits it to the service status display and control module. It also extracts service call information and transmits it to the service topology display module. Furthermore, it extracts node performance metrics such as CPU utilization, memory utilization, and node load, as well as service performance metrics such as workload and response latency, and provides them to the service performance metrics display and control module, thereby reducing the operational pressure on the service monitoring module. Further, this data communication module also supports forwarding detailed data packets, fault log data packets, and service combination plans to the log management component for persistent storage. Moreover, this data communication module periodically interacts with the application server, publishing service lifecycle change messages to the corresponding services, ensuring users can perform real-time lifecycle control of services on different nodes, meeting the needs of high-frequency, low-latency data communication.

[0039] like Figure 3 As shown, the service monitoring module periodically sends subscription requests to the service management software via the DDS interface to obtain detailed data packets, fault log data packets, and service combination plans for each service, thereby ensuring real-time tracking of the service status of each node. The service management software manages the services, registers and discovers them, and receives service information reported by the services. The detailed service information, fault log data, and service combination plans that the service monitoring module needs to subscribe to are all stored in the service management software. Furthermore, as the data communication starting point of the service monitoring terminal system, the service monitoring module transmits the detailed service data packets, fault log data packets, and service combination plans obtained from the external interface to the data communication module.

[0040] like Figure 3 As shown, the service status display and control module obtains the necessary node and service information, such as node number, service number, service name, and service status, from the data communication module to generate a list for visual display. Furthermore, the service status display and control module provides operation buttons for each service displayed in the list, supporting user requests to enable or disable selected services, and transmits these service lifecycle change requests to the service lifecycle display and control module for service lifecycle control. Additionally, the service lifecycle change requests and the generated list are sent to the log recording module for persistent storage.

[0041] like Figure 3As shown, the service topology display module obtains service call information from the data communication module, categorizes it according to nodes and services, and obtains the call chain relationship between different services between nodes. This generates a topology display view with service interaction capabilities for display. Furthermore, the service topology display module also provides service operation buttons for the services displayed on the topology display view, allowing users to submit service lifecycle change requests such as enabling or disabling a specific type of service on a selected node. The service topology display and control module transmits the service lifecycle change request to the service lifecycle display and control module, which then controls the service lifecycle. Finally, the service topology display module also sends the service lifecycle change request and the generated topology display view to the log recording module for persistent storage.

[0042] like Figure 3 As shown, the service performance indicator display and control module will use node performance indicators such as CPU utilization, memory utilization, and node load, as well as service performance indicators such as workload and response latency, obtained from the data communication module, to build a real-time and continuous visual view for display, which will facilitate the monitoring of real-time data and performance trends of performance indicators.

[0043] like Figure 3 As shown, the service lifecycle display and control module is a central hub for generating service lifecycle control commands. It displays service lifecycle change requests submitted by users in the service status display and control module and the service topology display module. After confirmation, it generates a service lifecycle change message, which is sent via an internal interface to the data communication module. This module communicates with the external data interface to send the service lifecycle change message to the service publisher. After the service status changes, the service publisher reports the information to the service management software, ultimately updating the service status displayed in the service status display and control module. Furthermore, user-triggered service lifecycle change messages need to be persistently stored in the log recording module.

[0044] like Figure 3 As shown, the service state restoration module is responsible for restoring the state of services that have undergone abnormal changes. First, the log recording module forwards the fault log data packet to the fault analysis module. The fault analysis module then feeds back the fault analysis results to the data communication module, which in turn sends the results to the service restoration module. Based on the fault analysis results, the service restoration module determines which services need to be enabled or disabled, generates service lifecycle change requests for these services, and sends them to the service lifecycle display and control module. After confirmation with the user, the service lifecycle display and control module generates a service lifecycle change message, thus completing the state restoration of the abnormal service. Further, the service lifecycle change requests are sent to the log recording module for persistent storage.

[0045] like Figure 3 As shown, the log recording module is responsible for saving the status and operations of all nodes and services in the service monitoring terminal system. The log management component, as an independent component, manages various types of message records through a visual interface. Furthermore, the component's file storage module can export different types of recorded information to a database or text file for categorized storage. Furthermore, the component's fault analysis module can retrieve or obtain historical message records from the database or text file for service fault analysis and debugging.

[0046] like Figure 3 As shown, the Service Component Refactoring module displays service composition plans for multiple different scenarios. This module provides a scheme-based approach to launching different service composition plans. While a default service composition plan is provided, users can select a service composition plan in the Service Component Refactoring module for flexible configuration and launch a custom service composition plan as needed. Furthermore, after a user builds a custom service composition plan, the Service Component Refactoring module generates a service lifecycle change message based on the plan and sends it to the data communication module. The data communication module then sends the service lifecycle change message to the service publisher, awaiting service redeployment. Moreover, during scheme switching, this module first analyzes the new and old service composition plans, generating lifecycle change messages only for services requiring status changes, thereby avoiding the resource overhead caused by frequent service startup and destruction.

[0047] It is understood that those skilled in the art can make equivalent substitutions or modifications to the technical solution and inventive concept of the present invention, and all such substitutions or modifications should fall within the protection scope of the appended claims.

Claims

1. A service monitoring terminal based on real-time visual data analysis, comprising a system management component, a monitoring management component, and a log management component, characterized in that... The monitoring and management component receives detailed data packets, fault log data packets, and service combination plans for each subscribed service and passes them to the system management component for processing. Based on the feedback from the system management component, it displays the status of each service, the call relationships between services, and the performance of the nodes where each service resides. It also transmits user-defined service lifecycle change messages to the system management component, which then publishes them to the corresponding services. This allows for real-time control of each service to support its operation according to the prescribed service combination plan. The feedback from the system management component includes node number, service number, service name, service status, service call information, and CPU utilization, memory utilization, node load, workload, and response latency for each node, extracted from the detailed data packets, fault log data packets, and service combination plans. Meanwhile, the system management component stores and exports service-critical real-time data in the log recording component.

2. The service monitoring terminal based on real-time visual data analysis according to claim 1, characterized in that... The system management component includes a main interface management module and a data communication module; the monitoring management component includes a service monitoring module, a service topology display and control module, a service status display and control module, a service lifecycle display and control module, and a service performance indicator display and control module. The main interface management module is used to manage the relative position, size, and color scheme of each display interface, create, delete, and save page layouts, and save all page layouts to the database. The data communication module processes the detailed data packets, fault log data packets, and service combination plans obtained from the service monitoring module. It extracts the node number, service number, service name, and service status and passes them to the service status display and control module. It also extracts service call information and passes it to the service topology display module. Furthermore, it extracts the CPU utilization, memory utilization, node load, workload, and response latency of each node and provides them to the service performance indicator display and control module. The module periodically interacts with the application server and publishes service lifecycle change messages generated by the service lifecycle display and control module to the corresponding services. The service monitoring module periodically sends subscription requests to the service management software through the DDS interface to obtain detailed data packets, fault log data packets, and service combination plans for each service. The service status display and control module obtains the node number, service number, service name, and service status of each service from the data communication module to generate a list for visual display. Each service in the list provides operation buttons to support users in submitting requests to change the service lifecycle of the selected service. The service topology display module obtains service call information from the data communication module, classifies it according to nodes and services, obtains the call chain relationship between different services between nodes, and generates a topology display view with service interaction function for display. It also provides service operation buttons for the services displayed on the topology display view, allowing users to indicate service lifecycle change requests for a certain type of service on a selected node. The service performance indicator display and control module will construct a real-time and continuous visualization view from the CPU utilization, memory utilization, node load, workload, and response latency obtained from the data communication module, and monitor the real-time data and performance trends of the performance indicators. The service lifecycle display and control module displays the service lifecycle change requests submitted by the user in the service status display and control module and the service topology display module. After confirmation, it generates a service lifecycle change message and sends it to the data communication module.

3. A service monitoring terminal based on real-time visual data analysis according to claim 2, characterized in that... The monitoring and management component also includes a service status restoration module; the log management component includes a log recording module and a fault analysis module. The logging module forwards the fault log data packets sent by the data communication module to the fault analysis module. The fault analysis module feeds back the fault analysis results to the data communication module, which then sends the fault analysis results to the service restoration module. Based on the fault analysis results, the service restoration module determines the services that need to be enabled or disabled, generates service lifecycle change requests for these services, and sends them to the service lifecycle display and control module. After confirmation with the user, the service lifecycle display and control module generates a service lifecycle change message.

4. A service monitoring terminal based on real-time visual data analysis according to claim 3, characterized in that... The log management component also includes a file storage module, which exports different types of recorded information to a database or text file for categorized storage.

5. A service monitoring terminal based on real-time visual data analysis according to claim 1, characterized in that... It also includes a bridging control component, which contains a service composition refactoring module; The service component refactoring module displays service composition plans for multiple different scenarios. Users can select a service composition plan as needed in the service component refactoring module, configure it flexibly, and start a custom service composition plan. After the user builds a custom service composition plan, the service component refactoring module will generate a service lifecycle change message based on the service composition plan and send it to the data communication module. The data communication module will then send the service lifecycle change message to the service publisher, waiting for the service to be redeployed.

6. A service monitoring terminal based on real-time visual data analysis according to claim 5, characterized in that, When switching solutions, the service component refactoring module first analyzes the new service composition plan and the old service composition plan, and only generates service lifecycle change messages for services that need to change their status.

Images