Aggregated micro-service unified monitoring station and construction and monitoring method thereof

Abstract

The invention belongs to the technical field of micro-service and monitoring, and particularly relates to an aggregation type micro-service unified monitoring station and a construction and monitoring method thereof. The monitoring station comprises a data receiving module, a data distribution module, a data analysis and display module, an alarm module and a micro-service connection configuration module. And the monitoring station realizes deep observability and efficient operation and maintenance management by comprehensively enhancing a visual monitoring interface of the aggregation type unified micro-service platform. The operation and maintenance process is effectively optimized, the system service capability is improved, the user confidence is enhanced, the development speed and the team technical level are improved, and powerful support is provided for technical innovation and business growth of enterprises. The problem that existing micro-service health monitoring only has basic functions and cannot meet advanced requirements of deep performance analysis, large-scale cluster management, refined authority control and the like is solved.

Description

Technical Field

[0001] The present invention belongs to the field of microservices and monitoring technologies, and specifically relates to an aggregated microservice unified monitoring platform and a construction and monitoring method thereof. Background Art

[0002] With the rapid development of big data and cloud computing, monolithic applications are becoming less and less suitable for complex business needs. The emergence of microservice architecture breaks down large-scale applications into small, interconnected services, successfully solving the problems of monolithic applications. The microservice design style has many advantages and challenges, and is in line with the design ideas and management methods for the development of medium and large software systems with ever-expanding and changing needs of enterprises. However, it faces a series of management and technical challenges such as many service instances, complex deployment, complex monitoring, and transactions. At the same time, there are also great challenges in troubleshooting and tracking problems in online systems. In the face of the complexity and challenges brought by the microservice architecture in the era of big data and cloud computing, a set of fully functional, intelligent and efficient integrated microservice monitoring platform is indispensable. The platform should have comprehensive monitoring coverage, intelligent alarm and root cause analysis, automated operation and maintenance management, and good customizability and integration capabilities, aiming to achieve deep observability of the microservice ecosystem, automated operation and maintenance, and cross-team collaboration, thereby improving the stability, operation and maintenance efficiency, and security of the system, and escorting the digital transformation and business innovation of enterprises.

[0003] At present, most of the microservice architecture implementation solutions are based on Spring Cloud. Health monitoring mainly uses the open source Spring Boot Admin component, which has basic functions of status monitoring such as notification, instance monitoring, memory usage, CPU usage, and middleware. Considering the monitoring factors such as system security, robustness, application performance, compliance, and software quality, for advanced requirements such as in-depth performance analysis, large-scale cluster management, and refined permission control, it is necessary to cooperate with other professional tools or conduct customized development. In actual use, it is necessary to pay attention to its resource consumption, security settings, and scalability issues in large-scale environments. Obviously, these basic functions cannot meet the needs of actual use. Summary of the invention

[0004] The present invention solves the problem that the existing microservice health monitoring has only basic functions and cannot meet advanced requirements such as deep performance analysis, large-scale cluster management, and refined authority control, and provides an aggregated microservice unified monitoring platform and its construction and monitoring method.

[0005] The technical solution claimed in the present invention is as follows:

[0006] A unified monitoring platform for aggregated microservices, which is a visual user operation interface for uniformly monitoring and displaying the operation data of each microservice in a microservice architecture and alarming for abnormalities; the monitoring platform comprises a data receiving module for receiving microservice operation data, a data distribution module for reading data from the data receiving module and distributing the data, a data analysis and display module for receiving data distributed by the data distribution module and analyzing and displaying the data, and an alarm module for microservice abnormality alarms, which are connected in sequence; the monitoring platform also comprises a microservice connection configuration module, which provides a pre-buried data interface and is used to establish a connection between the data receiving module and the microservice, and provides a non-intrusive embedding point for the microservice;

[0007] The data analysis and display module includes a user configuration submodule, a microservice display submodule and a microservice data analysis submodule connected in sequence; the user configuration submodule is used to configure the monitored microservices and configure the monitoring functions of each microservice; the microservice display submodule uses components to display all microservices in the microservice architecture, and each displayed microservice component includes multiple subcomponents, each subcomponent corresponds to a monitoring function, and the subcomponent displays the monitoring data of the monitoring function corresponding to the microservice; the microservice data analysis submodule has a built-in threshold for the monitoring data in each microservice, and when the monitoring data exceeds the threshold, the microservice data analysis submodule transmits the information to the alarm module for alarm; the monitoring function is to monitor the operating data corresponding to each microservice.

[0008] Preferably, the user configuration module can increase or decrease the microservices to be monitored according to the needs of the user, and the monitoring functions corresponding to the microservices can also be increased or decreased according to the needs of the user.

[0009] The monitoring functions include: basic functions and enhanced functions; the basic functions include: memory, CPU, disk, network, configuration, cache, log, JVM, version, health, dependent middleware status, metadata; the enhanced functions include: SQL performance monitoring, http request performance monitoring, Spring function performance, reids cache master-slave switching, database db master-slave switching, message queue mq master-slave switching, exception log collection and summary, database connection pool status, dependent lib compliance check, graceful shutdown, online api interface list display, database account status, findbugs defect report display, firewall configuration, related git information display, jmeter stress testing, Exception monitoring, static application security testing.

[0010] In a specific embodiment of the present invention, the SQL performance monitoring is connected to the knowledge base system to give recommended solutions for Exception information and poor performance SQL, and the SQL performance monitoring data is obtained by reading the database connection pool; the http request performance monitoring data, Spring function performance data, and exception log collection and summary data are obtained by reading the JVM agent program; the redis cache master-slave switching is achieved by changing and rewriting RedisTemplate.setConnectionFactory to achieve user-free switching in seconds; the database db master-slave switching is achieved by changing and rewriting datasource to achieve user-free switching in seconds; the message queue mq master-slave switching is achieved by changing and rewriting MqConnectionFactory to achieve user-free switching in seconds; the dependency lib compliance check is completed by reading the information of the dependency extension package and combining it with the custom rule library to complete the detection; the graceful shutdown is achieved by pre-burying the shutdown endpoint, and executing the stop service command according to the business microservice situation, and controlling the stop of the microservice through the monitoring console operation interface to achieve graceful shutdown instead of forcibly terminating the process; the online api interface list display is displayed by sending http RESTful implements online HTTP interface debugging and returns interface data; the database account status is displayed by executing standard SQL with DBA privileges to query the database user account status data and returning it to the monitoring station through tracking points. The database account status includes whether it is locked, expiration time, and tablespace association; the findbugs defect report display integrates the Findbugs scanning plug-in to run code defect scanning during packaging and generate reports and displays; the firewall configuration implements firewall status query and configuration on the application server by executing the iptables command of the Linux system; the associated git information display integrates the git plug-in to display the change record of the current online running version and the git version number; the jmeter stress test runs stress testing anytime and anywhere and generates reports by executing the configured jmeter stress testing script; the Exception monitoring writes key performance and abnormal data into the ITSM operation and maintenance system to realize work order allocation; the static application security test implements static application security testing and displays reports by connecting to SAST.

[0011] Preferably, the alarm module issues an alarm by displaying red; the alarm module can also send the alarm data to relevant personnel via email, DingTalk, SMS or WeChat.

[0012] The present invention also provides a method for constructing and monitoring the aggregated microservice unified monitoring platform, comprising the following steps:

[0013] S1: The monitoring station client builds a visual display interface based on the Spring Boot Admin plug-in for displaying monitoring data. The monitoring station server configures the extension plug-in based on the Spring Boot Admin architecture. The monitoring station extends the monitoring function based on the extension plug-in. The monitoring station client builds and implements the functions of each module on the monitoring station through code.

[0014] S2: The microservice connection configuration module is used to establish a connection between the data receiving module and the microservice, and provide a non-intrusive embedding point for the microservice; after the microservice is connected to the data receiving module, the monitoring station server can obtain the embedding point information of the microservice through the pre-embedded data interface provided by the microservice connection configuration, and the embedding point information includes all the operation data of the microservice;

[0015] S3: The user configuration submodule configures the monitored microservices and configures the monitoring functions of each microservice. The monitoring station server obtains the operating data of the microservice to be monitored through the pre-embedded data interface according to the configuration of the user configuration submodule and transmits the operating data;

[0016] S4: The data receiving module receives the operation data transmitted by the monitoring station server, the data distribution module reads the data of the data receiving module and distributes the data, the data analysis and display module receives the data distributed by the data distribution module and analyzes and displays the data, the microservice data analysis submodule of the data analysis and display module has a built-in threshold for monitoring data in each microservice, when the monitoring data exceeds the threshold, the microservice data analysis submodule transmits the information to the alarm module for alarm; at the same time, the microservice display submodule uses components to display all microservices in the microservice architecture, each microservice component includes multiple subcomponents, the subcomponents are used to display all monitoring functions under the microservice, and the monitoring function data can be viewed by clicking the subcomponent.

[0017] Preferably, the pre-buried data interface in S1 realizes unified management by aggregating swagger api data of multiple microservices.

[0018] Preferably, the microservices monitored by the monitoring station in S1 and the monitoring functions corresponding to the microservices can be freely configured, and the user can increase or decrease the microservices and the monitoring functions in the microservices according to needs.

[0019] Preferably, the configuration of the monitoring station server in S1 includes:

[0020] Step 1: Add Spring Boot Admin Server dependency;

[0021] Step 2: Configure the extension plug-in to Spring Boot Admin;

[0022] Step 3: Configure message notification;

[0023] Step 4: Configure Spring Boot Admin Server authentication and configure the authentication information required in each microservice.

[0024] Preferably, the configuration of the monitoring station client in S1 includes:

[0025] Step 1: Add Spring Boot Admin Client dependency;

[0026] Step 2: Configure the Druid connection pool; the connection pool is used to collect database connection pool data and status;

[0027] Step 3: Configure javamelody to collect JVM running parameters, http requests, exceptions and other data;

[0028] Step 4: Configure the findbugs-maven-plugin plug-in to scan source code defect data and generate XML during packaging;

[0029] Step 5: Configure the Swagger plug-in to provide API data;

[0030] Step 6: Configure the git-commit-id-plugin plug-in to provide git data;

[0031] Step 7: Add simplus-base Maven dependency to provide other information EndPoint;

[0032] Step 8: Load the configuration added in Step 2-Step 7.

[0033] Beneficial effects:

[0034] The present invention provides a unified monitoring station for aggregated microservices and a construction and monitoring method thereof, wherein the monitoring station is a visual user operation interface for uniformly monitoring and displaying the operation data of each microservice in a microservice architecture and alarming for anomalies; the monitoring station includes a microservice connection configuration module, the microservice connection configuration module provides a pre-buried data interface and is used to establish a connection between a data receiving module and a microservice, and provides a non-intrusive buried point for the microservice, through which all the operation data of the microservice can be obtained, and the monitoring station service end can obtain all the operation data of the microservice end through the pre-buried data interface, therefore, through the non-intrusive buried point, the monitoring station can obtain and monitor any data required to be monitored generated by the microservice, realize the refined management and performance analysis of the microservice, and solve the problem that the existing microservice health monitoring only has basic functions and cannot meet the advanced requirements such as deep performance analysis, large-scale cluster management, and refined authority control. If it is necessary to monitor the microservice more deeply, only the microservice connection configuration module in multiple monitoring stations needs to be modified, so as to realize the expansion of the microservice monitoring function, which greatly reduces the development cost. The alarm module provides an alarm service, which is convenient for timely discovering problems existing in the microservice, thereby reducing the frequency of microservice anomalies. The microservice data analysis submodule has built-in thresholds for monitoring data in each microservice. When the monitoring data exceeds the threshold, the microservice data analysis submodule transmits the information to the alarm module for alarm, thereby realizing rapid identification and resolution of microservice anomalies. This can effectively avoid development blockages caused by problem troubleshooting, allowing the team to focus more on innovation and optimization of core business logic, so that the product can respond to market demand in a shorter cycle and maintain competitive advantage.

[0035] The user configuration module can increase or decrease the microservices to be monitored according to the needs of the user, and the monitoring functions corresponding to the microservices can also be increased or decreased according to the needs of the user, which greatly improves the user experience.

[0036] The enhanced functions include: SQL performance monitoring, http request performance monitoring, Spring function performance, reids cache master-slave switching, database db master-slave switching, message queue MQ master-slave switching, exception log collection and summary, database connection pool status, dependency lib compliance check, graceful shutdown, online api interface list display, database account status, findbugs defect report display, firewall configuration, related git information display, jmeter stress testing, which basically covers all monitoring functions in the existing microservices. Operation and maintenance personnel can increase or decrease them according to needs, which improves the work efficiency of operation and maintenance personnel. At the same time, since all monitoring functions of existing microservices are covered, developers no longer need to develop separately for a specific monitoring function, which reduces the development cost. Through the enhanced functions, each microservice can be fully and deeply monitored in real time. It can not only reveal the macro-panorama of the running status of each microservice, but also go deep into each microservice component and even code-level details, realize accurate capture and rapid location of anomalies, greatly shorten the developer's exploration path for the root cause of the problem, and significantly save the time cost of troubleshooting errors; through the enhanced functions, a panoramic insight into project progress, resource allocation, risk warning and other information can be achieved, and managers can accurately control the project rhythm, scientifically allocate resources, and realize the refinement and intelligence of project management. The real-time monitoring and automated response mechanism of the monitoring station ensures the immediate detection and effective intervention of anomalies, and minimizes the risk of service interruption or performance degradation. This strict control of service stability has significantly enhanced users' confidence in our products and services, improved user satisfaction, and won a good market reputation for the company. The deep observability and rich data analysis functions of the monitoring station provide developers with rich learning resources and practical scenarios. By participating in practical operations such as problem location and performance tuning, developers can continuously improve their technical level and enhance their problem-solving capabilities. It also helps the team form a shared knowledge base and promote the improvement of overall technical strength.

[0037] The alarm module can also send alarm data to relevant personnel via email, DingTalk, SMS or WeChat, so that relevant personnel can find and solve problems in time and improve user satisfaction.

[0038] The monitoring station provided by the present invention realizes deep observability and efficient operation and maintenance management by comprehensively enhancing the visual monitoring interface of the aggregated unified microservice platform. It effectively optimizes the operation and maintenance process, improves the system service capability, enhances user confidence, improves the development speed and team technical level, and provides strong support for the company's technological innovation and business growth. Before the deployment of a comprehensive unified microservice monitoring station, the business system usually needs to wait for users to report performance or abnormal problems, and then perform a series of troubleshooting steps for the problem, including checking server resources, code debugging, collaborating with DBA to query SQL status, and recording logs of code embedding points to diagnose the problem. After the deployment of the comprehensive unified microservice monitoring station is completed, the anomalies and root causes of the problem can be quickly located through the intuitive visual interface. Operation and maintenance personnel can quickly solve problems and design optimization plans, thereby significantly reducing the workload of operation and maintenance and greatly improving the user experience on the core business system.

[0039] The present invention also provides a construction method of the monitoring station, which is developed based on the existing Spring Boot Admin, and plug-ins are added to expand the basic functions without affecting the functions of Spring Boot Admin, which has strong flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 This is a typical structure diagram of the microservices in an embodiment of the present invention.

[0041] Figure 2 This is a schematic diagram of a unified monitoring station for aggregated microservices according to an embodiment of the present invention.

[0042] Figure 3 This is a flow chart of the method for building and monitoring a unified monitoring platform for aggregated microservices according to an embodiment of the present invention.

[0043] Figure 4 A code block provided for the microservice connection configuration module of the aggregated microservice unified monitoring platform in an embodiment of the present invention.

[0044] Figure 5 The code implementation of adding Spring Boot AdminServer dependency to pom.xml for the aggregated microservice unified monitoring console server of the embodiment of the present invention.

[0045] Figure 6 The code implementation of configuring the extension plug-in to SpringBoot Admin on the server side of the aggregated microservice unified monitoring platform in the embodiment of the present invention.

[0046] Figure 7 The code implementation of adding Spring Boot AdminClient dependency to pom.xml for the aggregated microservice unified monitoring console client of the embodiment of the present invention.

[0047] Figure 8 The code implementation of configuring the Druid connection pool for the client of the aggregated microservice unified monitoring station in the embodiment of the present invention.

[0048] Fig. 9 The code implementation of configuring javamelody for the client of the aggregated microservice unified monitoring station in the embodiment of the present invention.

[0049] Fig.10 The code implementation of configuring the findbugs-maven-plugin plug-in for the client of the aggregated microservice unified monitoring station in the embodiment of the present invention. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solution and advantages of the present invention more clear, the technical solution is further clearly and completely described below in conjunction with the accompanying drawings of the present invention.

[0051] First group of embodiments: Aggregate microservice unified monitoring platform

[0052] This group of embodiments provides an aggregated microservice unified monitoring platform, such as Figure 2 As shown, the monitoring station is a visual user operation interface for uniformly monitoring and displaying the operation data of each microservice in the microservice architecture and alarming for abnormalities; the monitoring station includes a data receiving module for receiving microservice operation data, a data distribution module for reading data from the data receiving module and distributing the data, a data analysis and display module for receiving data distributed by the data distribution module and analyzing and displaying the data, and an alarm module for microservice abnormal alarm; the alarm module alarms by displaying red. In a specific embodiment of the present invention, the alarm module is equipped with multiple red alarm indicator lights. When a certain data of a microservice is abnormal, the corresponding red alarm indicator light will flash to display the abnormality; the alarm module can also send the alarm data to relevant personnel via email, DingTalk, SMS or WeChat. In a specific embodiment of the present invention, DingTalk, enterprise WeChat and email reminders are implemented by rewriting the doNotify function of Spring AbstractStatusChangeNotifier.

[0053] The monitoring station also includes a microservice connection configuration module, which provides a pre-buried data interface and is used to establish a connection between the data receiving module and the microservice, and provides a non-intrusive embedding point for the microservice, and the non-intrusive embedding point can obtain all the operation data of the microservice. The monitoring station server can obtain the operation data through the pre-buried data interface and transmit it, and transmit the operation data of the microservice to the data receiving module; in a specific embodiment of the present invention, the microservice connection configuration module provides a code block ( Figure 4 ), the microservice establishes a connection with the data receiving module by integrating the code block provided by the microservice connection configuration module; when the monitoring station needs to add a new monitoring function to the microservice, the developer only needs to adjust the code logic of the connection configuration module without adjusting the microservice, so as to realize the increase of the corresponding monitoring function of the microservice.

[0054] The data analysis and display module includes a user configuration submodule, a microservice display submodule and a microservice data analysis submodule connected in sequence; the user configuration submodule is used to configure the monitored microservices and configure the monitoring functions of each microservice; the microservice display submodule uses components to display all microservices in the microservice architecture, and each displayed microservice component includes multiple subcomponents, each subcomponent corresponds to a monitoring function, and the monitoring data of the monitoring function corresponding to the microservice is displayed in the subcomponent; in a specific embodiment of the present invention, the user configuration module can increase or decrease the microservices to be monitored according to user needs, and the monitoring functions corresponding to the microservices can also be increased or decreased according to user needs.

[0055] The microservice data analysis submodule has a built-in threshold for monitoring data in each microservice. When the monitoring data exceeds the threshold, the microservice data analysis submodule transmits the information to the alarm module for alarm; the monitoring function is to monitor the operating data corresponding to each microservice, and the monitoring function of the microservice refers to monitoring different parameters of the operating data. Different parameter data corresponds to different monitoring functions. In a specific embodiment of the present invention, the monitoring function includes: basic functions and enhanced functions; the basic functions include: memory, CPU, disk, network, configuration, cache, log, JVM, version, health, dependent middleware status, metadata; the enhanced functions include: SQL performance monitoring, http request performance monitoring, Spring function performance, reids cache master-slave switching, database db master-slave switching, message queue mq master-slave switching, abnormal log collection and summary, database connection pool status, dependent lib compliance check, graceful shutdown, online api interface list display, database account status, findbugs defect report display, firewall configuration, associated git information display, jmeter stress testing, Exception monitoring, static application security testing.

[0056] In a specific embodiment of the present invention, the SQL performance monitoring is connected to the knowledge base system to give recommended solutions for Exception information and poor performance SQL, and the SQL performance monitoring data is obtained by reading the database connection pool; the http request performance monitoring data, Spring function performance data, and exception log collection summary data are obtained by reading the JVM agent program; the redis cache master-slave switching is achieved by changing and rewriting RedisTemplate.setConnectionFactory to achieve user-free second switching; the database db master-slave switching is achieved by changing and rewriting datasource to achieve user-free second switching; the message queue mq master-slave switching is achieved by changing and rewriting MqConnectionFactory to achieve user-free second switching; the dependency lib compliance check is completed by reading the information of the dependency extension package and combining with the custom rule library to complete the detection; the graceful shutdown is achieved by pre-burying the shutdown endpoint, and executing the stop service command according to the business microservice situation, and controlling the stop of the microservice through the monitoring console operation interface to achieve graceful shutdown instead of forcibly terminating the process; the online api interface list is displayed by sending http RESTful implements online HTTP interface debugging and returns interface data; the database account status is displayed by executing standard SQL with DBA privileges to query the database user account status data and returning it to the monitoring station through tracking points. The database account status includes whether it is locked, expiration time, and tablespace association; the findbugs defect report display integrates the Findbugs scanning plug-in to run code defect scanning during packaging and generate reports and displays; the firewall configuration implements firewall status query and configuration on the application server by executing the iptables command of the Linux system; the associated git information display integrates the git plug-in to display the change record of the current online running version and the git version number; the jmeter stress test runs stress testing anytime and anywhere and generates reports by executing the configured jmeter stress testing script; the Exception monitoring writes key performance and abnormal data into the ITSM operation and maintenance system to realize work order allocation; the static application security test implements static application security testing and displays reports by connecting to SAST.

[0057] Second group of embodiments: Construction and monitoring method of aggregated microservice unified monitoring platform

[0058] This group of embodiments provides a method for constructing and monitoring the aggregated microservice unified monitoring platform described in the first group of embodiments, such as Figure 3 As shown, the following steps are included:

[0059] S1: The monitoring station client builds a visual display interface based on the Spring Boot Admin plug-in for displaying monitoring data. The monitoring station server configures an extension plug-in based on the Spring Boot Admin architecture. The monitoring station extends the monitoring function based on the extension plug-in; the monitoring station client builds and implements the functions of each module on the monitoring station through code; the pre-buried data interface achieves unified management by aggregating swagger api data of multiple microservices; all operating data of microservices can be obtained through non-invasive embedding points. The monitoring station server can obtain all operating data of the microservice end through the pre-buried data interface. The monitoring station server can transmit all the acquired operating data to the data receiving module of the monitoring station. Therefore, through non-invasive embedding points, the monitoring station can obtain and monitor any data generated by the microservice that needs to be monitored.

[0060] In a specific embodiment of the present invention, the client builds a visual interface through vue code, and builds and implements the functions of each module in the monitoring station through code logic.

[0061] The configuration of the monitoring station server includes:

[0062] Step 1: Add Spring Boot Admin Server dependency to pom.xml ( Figure 5 );

[0063] Step 2: Configure the extension plugin to Spring Boot Admin ( Figure 6 );

[0064] Step 3: Configure message notifications, including WeChat, email, DingTalk, and SMS;

[0065] Step 4: Configure Spring Boot Admin Server authentication and the information required for authentication in each microservice. Other security configurations are configured according to actual conditions.

[0066] The configuration of the monitoring station client includes:

[0067] Step 1: Add Spring Boot Admin Client dependencies to pom.xml ( Figure 7 );

[0068] Step 2: Configure Druid connection pool stat-view-servlet; the connection pool is used to collect database connection pool data and status ( Figure 8 );

[0069] Step 3: Configure javamelody to collect jvm running parameters, http requests, exceptions and other data ( Fig. 9 );

[0070] Step 4: Configure the findbugs-maven-plugin plug-in to scan source code defect data and generate XML during packaging ( Fig.10 );

[0071] Step 5: Configure the Swagger plug-in to provide API data;

[0072] Step 6: Configure the git-commit-id-plugin plug-in to provide git data;

[0073] Step 7: Add simplus-base Maven dependency to provide other information EndPoint;

[0074] Step 8: For the front-end VUE display extension code, after compilation, use the extension-resource-locations:classpath: / extui / configuration to complete the loading of the configuration added in steps 2 to 7.

[0075] S2: The microservice connection configuration module is used to establish a connection between the data receiving module and the microservice, and provide a non-intrusive embedding point for the microservice; after the microservice is connected to the data receiving module, the monitoring station server can obtain the embedding point information of the microservice through the pre-embedded data interface provided by the microservice connection configuration, and the embedding point information includes all the operation data of the microservice;

[0076] S3: The user configuration submodule configures the monitored microservices and configures the monitoring functions of each microservice. The monitoring station server obtains the operating data of the microservice to be monitored through the pre-embedded data interface according to the configuration of the user configuration submodule and transmits the operating data;

[0077] S4: The data receiving module receives the operation data transmitted by the monitoring station server, the data distribution module reads the data of the data receiving module and distributes the data, the data analysis and display module receives the data distributed by the data distribution module and analyzes and displays the data, the microservice data analysis submodule of the data analysis and display module has a built-in threshold of the monitoring data in each microservice, when the monitoring data exceeds the threshold, the microservice data analysis submodule transmits the information to the alarm module for alarm; at the same time, the microservice display submodule uses a component to display all microservices in the microservice architecture, each microservice component includes multiple subcomponents, the subcomponents are used to display all monitoring functions under the microservice, click the subcomponent to view the monitoring function data, in the specific embodiment of the present invention In the embodiment, a monitoring station builds multiple microservice display submodules, and the microservice display submodules are displayed through UI components. Each microservice display submodule includes multiple subcomponents, and the subcomponents are displayed through UI components. The UI component corresponding to the microservice display submodule supports clicks, and all subcomponents under the corresponding microservice can be displayed by user clicks; the subcomponent corresponds to the monitoring function of the current microservice, and the UI component corresponding to the monitoring function also supports clicks, and the corresponding data under the current monitoring function can be displayed by clicking; the microservices monitored by the monitoring station and the monitoring functions corresponding to the microservices can be freely configured, and users can increase or decrease the microservices or the UI components corresponding to the monitoring functions of the microservices according to needs, thereby realizing the increase or decrease of microservices and the increase or decrease of monitoring functions in microservices.

[0078] The following is a detailed description of the aggregated microservice unified monitoring platform provided by the present invention in conjunction with the entire microservice architecture. Figure 1 As shown in the figure, N microservices are displayed in the microservice architecture. Each microservice carries different functions. They are independent of each other, but work together to build a powerful and flexible system. Each microservice is deployed and run independently, which means that they can be upgraded, expanded and maintained independently without affecting the normal operation of other services. This independence not only improves the reliability of the system, but also allows each service to use the most suitable technology and framework to implement its functions. Although these microservices work independently, they are not isolated. They use related public resource middleware, such as databases, caches, and message queues, to store and exchange data. These middlewares are like bridges that connect different microservices, enabling them to work together to complete tasks. Microservices call each other through a unified protocol, which ensures unimpeded communication between different services.

[0079] At the same time, the registration center plays a vital role in it. It stores the information of all microservice instances, enabling service callers to quickly find and connect to the correct service instance.

[0080] The monitoring station service periodically obtains the monitoring point data of each microservice. These data include key indicators such as the service's response time, throughput, and error rate. When one of the microservice instances goes down, the monitoring station will immediately reflect this status. The present invention enhances the monitoring function of the monitoring station to meet the existing advanced requirements for microservice monitoring; for example: the monitoring station can be used for service health monitoring: real-time tracking of the status of each microservice instance, including operating status, response time, and error rate, to ensure the stability and availability of the service; the monitoring station can be used for link tracking: providing full-link tracking capabilities, from user requests to each link of the back-end service can be tracked and recorded, which helps to quickly locate call problems and performance bottlenecks between services; the monitoring station can be used for performance analysis: providing performance bottleneck analysis tools to help identify the reasons for slow service responses, such as database query delays, slow external API calls, etc.; the monitoring station can be used for performance analysis: providing performance bottleneck analysis tools to help identify the reasons for slow service responses, such as database query delays, slow external API calls, etc. The console can be used for resource management: it supports traffic control strategies such as service routing, load balancing, and service current limiting to ensure stable operation of services in high-concurrency scenarios; the monitoring console can be used for historical data analysis: it supports querying historical monitoring data, conducting trend analysis, and assisting in capacity planning and performance optimization; the monitoring console can be used for alarm management: setting and managing alarm rules. Once the monitored service indicators deviate from the normal range, alarms can be triggered immediately and displayed on the monitoring console. At the same time, relevant personnel can be notified via email, text messages, etc.; the monitoring console can be used for security and authentication: it provides security functions such as service authentication and access control to ensure the security of communication between microservices.

[0081] In a specific embodiment of the present invention, the registration center, configuration center, several business core services, and the server of the monitoring station in the microservice architecture are started in sequence, and the Spring Boot Admin server is logged in. The extension plug-in enhancement function and basic function menus can be seen, as well as the data indicator interface after each menu is clicked (that is, the monitoring data under the corresponding function of each microservice).

Claims

1. An aggregated microservice unified monitoring platform, characterized in that: The monitoring station is a visual user operation interface for uniformly monitoring and displaying the operation data of each microservice in the microservice architecture and alarming for abnormalities; the monitoring station includes a data receiving module for receiving microservice operation data, a data distribution module for reading data from the data receiving module and distributing the data, a data analysis and display module for receiving data distributed by the data distribution module and analyzing and displaying the data, and an alarm module for microservice abnormality alarms, which are connected in sequence; the monitoring station also includes a microservice connection configuration module, which provides a pre-buried data interface and is used to establish a connection between the data receiving module and the microservice, and provides a non-intrusive embedding point for the microservice; The data analysis and display module includes a user configuration submodule, a microservice display submodule and a microservice data analysis submodule connected in sequence; The user configuration submodule is used to configure the monitored microservices and configure the monitoring functions of each microservice; the microservice display submodule uses components to display all microservices in the microservice architecture, and each displayed microservice component includes multiple subcomponents, each subcomponent corresponds to a monitoring function, and the monitoring data of the monitoring function corresponding to the microservice is displayed in the subcomponent; The microservice data analysis submodule has a built-in threshold for monitoring data in each microservice. When the monitoring data exceeds the threshold, the microservice data analysis submodule transmits the information to the alarm module for alarm. The monitoring function is to monitor the operation data corresponding to each microservice.

2. The aggregated microservice unified monitoring platform according to claim 1, characterized in that: The user configuration module can increase or decrease the microservices to be monitored according to the needs of the user, and the monitoring functions corresponding to the microservices can also be increased or decreased according to the needs of the user.

3. The aggregated microservice unified monitoring platform according to claim 2 is characterized in that: The monitoring functions include: basic functions and enhanced functions; the basic functions include: memory, CPU, disk, network, configuration, cache, log, JVM, version, health, dependent middleware status, metadata; the enhanced functions include: SQL performance monitoring, http request performance monitoring, Spring function performance, reids cache master-slave switching, database db master-slave switching, message queue mq master-slave switching, exception log collection and summary, database connection pool status, dependent lib compliance check, graceful shutdown, online api interface list display, database account status, findbugs defect report display, firewall configuration, related git information display, jmeter stress testing, Exception monitoring, static application security testing.

4. The aggregated microservice unified monitoring platform according to claim 3 is characterized in that: The SQL performance monitoring provides recommended solutions for Exception information and poor performance SQL by connecting to the knowledge base system. The SQL performance monitoring data is obtained by reading the database connection pool; the http request performance monitoring data, Spring function performance data, and exception log collection and summary data are obtained by reading the JVM agent program; the redis cache master-slave switching is achieved by changing and rewriting RedisTemplate.setConnectionFactory to achieve user-free switching in seconds; the database db master-slave switching is achieved by changing and rewriting datasource to achieve user-free switching in seconds; the message queue mq master-slave switching is achieved by changing and rewriting MqConnectionFactory to achieve user-free switching in seconds; The dependency lib compliance check completes the detection by reading the information of the dependency extension package and combining it with the custom rule library; the graceful shutdown is achieved by pre-embedding the shutdown endpoint and executing the stop service command according to the business microservice situation, and controlling the stop of the microservice through the monitoring console operation interface to achieve graceful shutdown instead of forcibly terminating the process; the online api interface list is displayed by sending http RESTful implements online HTTP interface debugging and returns interface data; the database account status is displayed by executing standard SQL with DBA privileges to query the database user account status data and returning it to the monitoring station through tracking points. The database account status includes whether it is locked, expiration time, and tablespace association; the findbugs defect report display integrates the Findbugs scanning plug-in to run code defect scanning during packaging and generate reports and displays; the firewall configuration implements firewall status query and configuration on the application server by executing the iptables command of the Linux system; the associated git information display integrates the git plug-in to display the change record of the current online running version and the git version number; the jmeter stress test runs stress testing anytime and anywhere and generates reports by executing the configured jmeter stress testing script; the Exception monitoring writes key performance and abnormal data into the ITSM operation and maintenance system to realize work order allocation; the static application security test implements static application security testing and displays reports by connecting to SAST.

5. The aggregated microservice unified monitoring platform according to claim 2, characterized in that: The alarm module issues an alarm by displaying red; the alarm module can also send the alarm data to relevant personnel via email, DingTalk, SMS or WeChat.

6. The method for constructing and monitoring the aggregated microservice unified monitoring platform according to any one of claims 1 to 5, characterized in that: The steps include: S1: The monitoring station client builds a visual display interface based on the Spring Boot Admin plug-in for displaying monitoring data. The monitoring station server configures an extension plug-in based on the Spring Boot Admin architecture. The monitoring station extends the monitoring function based on the extension plug-in. The monitoring station client is constructed through code and implements the functions of each module on the monitoring station; S2: The microservice connection configuration module is used to establish a connection between the data receiving module and the microservice, and provide a non-intrusive embedding point for the microservice; After the microservice establishes a connection with the data receiving module, the monitoring station server can obtain the microservice's embedded point information through the pre-embedded data interface provided by the microservice connection configuration. The embedded point information includes all the running data of the microservice; S3: The user configuration submodule configures the monitored microservices and configures the monitoring functions of each microservice. The monitoring station server obtains the operating data of the microservice to be monitored through the pre-embedded data interface according to the configuration of the user configuration submodule and transmits the operating data; S4: The data receiving module receives the operation data transmitted by the monitoring station server, the data distribution module reads the data of the data receiving module and distributes the data, the data analysis and display module receives the data distributed by the data distribution module and analyzes and displays the data, the microservice data analysis submodule of the data analysis and display module has a built-in threshold for monitoring data in each microservice, when the monitoring data exceeds the threshold, the microservice data analysis submodule transmits the information to the alarm module for alarm; at the same time, the microservice display submodule uses components to display all microservices in the microservice architecture, each microservice component includes multiple subcomponents, the subcomponents are used to display all monitoring functions under the microservice, and the monitoring function data can be viewed by clicking the subcomponent.

7. The construction and monitoring method according to claim 6, characterized in that: The embedded data interface described in S1 realizes unified management by aggregating the swagger api data of multiple microservices.

8. The construction and monitoring method according to claim 6, characterized in that: The microservices monitored by the monitoring station described in S1 and the monitoring functions corresponding to the microservices can be freely configured, and users can increase or decrease microservices and monitoring functions in microservices according to their needs.

9. The construction and monitoring method according to claim 6, characterized in that: The configuration of the monitoring station server described in S1 includes: Step 1: Add Spring Boot Admin Server dependency; Step 2: Configure the extension plug-in to Spring Boot Admin; Step 3: Configure message notification; Step 4: Configure Spring Boot Admin Server authentication and configure the authentication information required in each microservice.

10. The construction and monitoring method according to claim 6, characterized in that: The configuration of the monitoring station client described in S1 includes: Step 1: Add Spring Boot Admin Client dependency; Step 2: Configure the Druid connection pool; the connection pool is used to collect database connection pool data and status; Step 3: Configure javamelody to collect JVM running parameters, http requests, exceptions and other data; Step 4: Configure the findbugs-maven-plugin plug-in to scan source code defect data and generate XML during packaging; Step 5: Configure the Swagger plug-in to provide API data; Step 6: Configure the git-commit-id-plugin plug-in to provide git data; Step 7: Add simplus-base Maven dependency to provide other information EndPoint; Step 8: Load the configuration added in Step 2-Step 7.

Images