Cloud platform inspection method, device and equipment and storage medium

Abstract

The invention discloses a cloud platform inspection method, device and equipment and a storage medium. Comprising the steps of configuring and issuing an inspection task to an inspection engine through an inspection platform; an inspection engine searches an inspection address corresponding to the product management and control service according to the received inspection task, calls an inspection interface based on the inspection task and the inspection address to obtain an inspection result, and feeds back the inspection result to an inspection platform after cleaning and sorting; and performing intelligent decision analysis through the inspection platform according to the received inspection result. The routing inspection tasks are configured and issued through the routing inspection platform, centralized standardized configuration and efficient distribution of the tasks are achieved, and accurate transmission of the tasks is guaranteed. The corresponding management and control service inspection address is searched through the inspection engine, an interface is called to obtain a result, and feedback is cleaned and arranged, so that multiple products are quickly adapted, the network connection problem is solved, and accuracy and standardization of inspection data are guaranteed. The inspection platform performs intelligent decision analysis according to the result, quickly recognizes abnormity and hidden dangers, reduces the labor cost, and improves the operation and maintenance response efficiency.

Description

Technical Field

[0001] This invention relates to the field of cloud computing, and in particular to a cloud platform inspection method, apparatus, equipment, and storage medium. Background Technology

[0002] Inspection is a core component of IT operations and maintenance. It refers to the routine, route, and standard-based inspection of equipment, facilities, or systems to monitor their operational status and promptly identify anomalies and potential problems. With the development of cloud computing technology, traditional IT architectures are transforming into distributed cloud-native architectures. PaaS cloud platforms, by providing out-of-the-box development and runtime environments for applications, have become crucial carriers for core business operations.

[0003] Currently, PaaS cloud platform inspections in the industry mainly consist of independent self-developed inspection systems for each component, with each component only responsible for checking its own operating status and adapting to its own characteristics and needs; as well as customized solutions built on open-source automated operation and maintenance components, which achieve batch checks of basic indicators by writing scripts.

[0004] In existing inspection solutions, the independent development of components leads to high development costs, and the parallel operation of multiple systems results in a serious waste of computing, storage, and network resources. Open-source component solutions require significant resources for additional development and adaptation when facing heterogeneous underlying environments, and are difficult to implement in special network environments such as firewall isolation. Furthermore, independent inspection lacks a global perspective, failing to correlate the operational status of application systems with that of individual components. This makes it difficult to identify systemic problems at the application level and to trace application failures caused by component anomalies, resulting in low efficiency in problem localization. Summary of the Invention

[0005] This invention provides a cloud platform inspection method, apparatus, equipment, and storage medium, which solves the technical problems of limited architectural scalability, high cost of multi-product adaptation, high pressure of concurrent large-scale inspection tasks, low data processing efficiency, and slow response to anomaly analysis in traditional cloud platform inspection.

[0006] According to one aspect of the present invention, a cloud platform inspection method is provided, applied to an inspection system, the inspection system including: an inspection platform, an inspection engine, and a product management service, the method including:

[0007] Configure and distribute inspection tasks to the inspection engine through the inspection platform;

[0008] The inspection engine finds the inspection address of the corresponding product management service based on the received inspection task, calls the inspection interface based on the inspection task and inspection address to obtain the inspection results, and then cleans and organizes the inspection results and feeds them back to the inspection platform.

[0009] The inspection platform performs intelligent decision analysis based on the received inspection results.

[0010] Optionally, the inspection task can be configured and sent to the inspection engine through the inspection platform, including: obtaining the configuration information input by the user through the inspection platform, and creating the inspection task based on the configuration information, wherein the configuration information includes basic task information, inspection target, inspection indicators, execution method, execution time and inspection report notification settings; and sending the inspection task to the inspection engine in the form of a message queue or database sharing.

[0011] Optionally, the method also includes: acquiring indicator information of each inspection object through product management services by actively collecting or passively receiving information, wherein the inspection object is a specific instance under the inspection target; and temporarily storing each indicator information in its own database after cleaning and sorting, and encapsulating it into a pre-defined format.

[0012] Optionally, the inspection engine can be used to find the inspection address of the corresponding product management service based on the received inspection task, including: obtaining the inspection target contained in the inspection task through the inspection engine, generating a query request based on the inspection target and sending it to the registration center; and receiving the inspection address of the product management service that matches the inspection target returned by the registration center.

[0013] Optionally, the inspection interface is invoked based on the inspection task and inspection address to obtain the inspection results, including: generating a call request based on the inspection target in the inspection task; invoking the inspection interface from the inspection address based on the call request to obtain the target indicator information corresponding to the call request in the product management service; and encapsulating the target indicator information in a specified format to generate the inspection results.

[0014] Optionally, the inspection results are cleaned and organized before being fed back to the inspection platform. This includes: validating the target indicator information in the inspection results, removing outliers from the target indicator information and filling in missing data to generate cleaned inspection results; converting the cleaned inspection results into a preset standard format to generate organized inspection results; and feeding back the organized inspection results to the inspection platform through a message queue or database sharing.

[0015] Optionally, the inspection platform can perform intelligent decision analysis based on the received inspection results, including: comparing the inspection results with the inspection indicators to identify abnormal indicators; connecting the inspection platform to the knowledge base to generate analysis results corresponding to the abnormal indicators; combining the analysis results with the configured report template to generate an inspection report, and sending the inspection report to the designated user according to the sending strategy and notification method in the inspection report notification settings.

[0016] According to another aspect of the present invention, a cloud platform inspection device is provided, the device comprising:

[0017] The inspection task distribution module is used to configure and distribute inspection tasks to the inspection engine through the inspection platform.

[0018] The inspection result feedback module is used to find the inspection address of the corresponding product management service through the inspection engine based on the received inspection task, call the inspection interface based on the inspection task and inspection address to obtain the inspection results, and then clean and organize the inspection results and feed them back to the inspection platform.

[0019] The intelligent decision analysis module is used to perform intelligent decision analysis based on the received inspection results through the inspection platform.

[0020] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0021] At least one processor;

[0022] and a memory communicatively connected to the at least one processor;

[0023] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute a cloud platform inspection method according to any embodiment of the present invention.

[0024] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, the computer instructions being configured to cause a processor to execute and implement a cloud platform inspection method according to any embodiment of the present invention.

[0025] The technical solution of this invention configures and distributes inspection tasks through an inspection platform, achieving centralized and standardized task configuration and efficient distribution, ensuring accurate task delivery. The inspection engine locates the corresponding management service inspection address, calls interfaces to obtain results, cleans and organizes them for feedback, quickly adapting to multiple products, resolving network connectivity issues, and ensuring accurate and standardized inspection data. Based on the results, the inspection platform intelligently analyzes the data to quickly identify anomalies and potential hazards, reducing manual costs and improving operational response efficiency.

[0026] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 This is a flowchart of a cloud platform inspection method provided in Embodiment 1 of the present invention;

[0029] Figure 2 This is a flowchart of another cloud platform inspection method provided according to Embodiment 2 of the present invention;

[0030] Figure 3 This is a schematic diagram of an inspection system architecture provided in Embodiment 2 of the present invention;

[0031] Figure 4 This is a schematic diagram of a cloud platform inspection process provided in Embodiment 2 of the present invention;

[0032] Figure 5 This is a schematic diagram of the structure of a cloud platform inspection device according to Embodiment 3 of the present invention;

[0033] Figure 6 This is a schematic diagram of the structure of an electronic device that implements a cloud platform inspection method according to an embodiment of the present invention. Detailed Implementation

[0034] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0035] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0036] Example 1

[0037] Figure 1 This is a flowchart of a cloud platform inspection method provided in Embodiment 1 of the present invention. This embodiment is applicable to Platform as a Service (PaaS) scenarios. The method can be executed by a cloud platform inspection device, which can be implemented in hardware and / or software. This cloud platform inspection device can be applied to an inspection system, which includes: an inspection platform, an inspection engine, and product management services. Figure 1 As shown, the method includes:

[0038] S110: Configure and send inspection tasks to the inspection engine through the inspection platform.

[0039] Inspection refers to the process of checking the operational status, collecting and analyzing data from applications, middleware, databases, and other products on a cloud platform through a standardized architecture and workflow. The inspection platform is the core of the upper-level interaction and management of the inspection system, responsible for interfacing with users. It includes modules for inspection task management, inspection report management, real-time status monitoring, risk management, intelligent diagnosis and decision-making, and supports inspection task configuration, result analysis, report push, and alarm triggering. It allows users to configure periodic or single-time inspection tasks. The inspection engine is the execution vehicle for inspection tasks, supporting distributed deployment and dynamic scaling. After receiving tasks from the inspection platform, it looks up the inspection address of the corresponding product management service through the registry center, calls the inspection interface to obtain data, cleans and integrates the inspection results, and then feeds them back to the inspection platform. The product management service is the intermediate proxy layer between the inspection engine and the inspection target. It belongs to the PaaS product management plane and is implemented with a microservice architecture, with each PaaS product corresponding to a dedicated management service. It provides a unified Hypertext Transfer Protocol (HTTP) inspection interface to the upper level, and obtains the indicator information of the inspection target through active collection or passive reporting to the lower level, while completing indicator cleaning, sorting and temporary storage. Inspection tasks refer to the specific inspection instructions configured by the inspection platform, which are sent to the inspection engine through message queues or database sharing.

[0040] Optionally, the inspection task can be configured and sent to the inspection engine through the inspection platform, including: obtaining the configuration information input by the user through the inspection platform, and creating the inspection task based on the configuration information, wherein the configuration information includes basic task information, inspection target, inspection indicators, execution method, execution time and inspection report notification settings; and sending the inspection task to the inspection engine in the form of a message queue or database sharing.

[0041] The configuration information includes basic task information, inspection targets, inspection indicators, execution methods, execution time, and inspection report notification settings. Basic task information is entered by the user and must conform to the 1-64 character requirement, supporting Chinese characters, English letters, numbers, hyphens, underscores, colons, and periods. This information is used to clearly name the inspection task for easy identification and management later. Determining the inspection target requires the user to specify the specific object to be inspected, including the type of PaaS cloud product to be inspected, such as middleware, database, or application, as well as the corresponding cluster. This information can be obtained from the Configuration Management Database (CMDB). The user also needs to supplement this information with component type, data center, cloud type, and other related information. Multiple inspection clusters can be added using the cluster addition function to ensure accurate coverage of the target object during the inspection. Configuring inspection metrics requires users to first select the corresponding metric set type, then add specific inspection metrics, and simultaneously set the judgment rules and thresholds for each metric, such as CPU utilization, memory utilization, disk utilization, and network inbound / outbound traffic. Users can flexibly add single metrics or metric groups according to actual operation and maintenance needs, clearly defining the normal range standards for the metrics to provide a basis for subsequent inspection result judgment. The execution method is selected by the user, supporting both periodic execution and single execution modes. If periodic execution is selected, the specific execution day must be selected in the execution time configuration, such as some or all dates from Tuesday to Sunday each week, and the specific execution time must be specified. If single execution is selected, a unique execution time can be directly set to ensure that the inspection task is carried out according to the expected rhythm. Inspection report notification settings require users to specify the notification method, such as email, SMS, or telephone, and select an appropriate sending strategy and corresponding contact group to facilitate timely feedback of results to relevant operation and maintenance personnel after the inspection is completed. After completing the input of all the above configuration information, the inspection platform will integrate and generate a complete inspection task. Finally, the inspection platform will send the created inspection tasks to the inspection engine using either a message queue or a shared database. The message queue enables asynchronous task distribution, ensuring efficient and stable task delivery, while the shared database allows the inspection engine to obtain task information through data synchronization. Both methods ensure that the inspection engine accurately receives the tasks, preparing it for the execution of subsequent inspection tasks.

[0042] Optionally, the method also includes: acquiring indicator information of each inspection object through product management services by actively collecting or passively receiving information, wherein the inspection object is a specific instance under the inspection target; and temporarily storing each indicator information in its own database after cleaning and sorting, and encapsulating it into a pre-defined format.

[0043] It is known that the product management service, as an intermediary agent layer connecting the inspection engine and the inspection target, will obtain the indicator information of each inspection object through two methods: active collection or passive reception. The inspection object is a specific instance under the inspection target, including the actual running instances of applications, middleware, and databases, as well as the software and hardware environment on which the instance runs.

[0044] Specifically, in the active data collection mode, the product management service uses a built-in timer to proactively access the HTTP interfaces of each inspected object at preset intervals, extracting CPU usage, memory usage, disk usage, and network traffic to ensure real-time tracking of the inspected object's operational status. In the passive data collection mode, the inspected object periodically sends its own metric information to the product management service. In some scenarios, an agent can be deployed on the inspected object to collect metric information and proactively report it to the product management service, ensuring comprehensive collection of metric information.

[0045] Furthermore, the product management service first cleanses the indicator information, removing invalid, erroneous, or duplicate data to ensure accuracy and validity. Then, the cleaned data is organized according to a unified standard data format, ensuring consistency and comparability of indicator information across different inspection targets. Finally, the product management service temporarily stores the standardized indicator information in its own database for quick retrieval by the inspection engine. Simultaneously, to meet the data interaction requirements with the inspection engine, the product management service encapsulates the temporarily stored indicator information into a pre-defined JSON format.

[0046] S120: The inspection engine finds the inspection address of the corresponding product management service based on the received inspection task, calls the inspection interface based on the inspection task and inspection address to obtain the inspection results, and then cleans and organizes the inspection results before feeding them back to the inspection platform.

[0047] The inspection address refers to the accessible network address provided by the product management service. It is used by the inspection engine to locate and connect to the management service of the corresponding product, enabling the invocation of the inspection interface and data interaction, thus resolving the network connectivity issue between the inspection engine and the inspection target. The inspection interface is a standardized HTTP interface defined by the product management service. It receives requests from the inspection engine and returns inspection result data in a unified format. Interface parameters include key information such as type, component name, and cluster ID, masking the differences between different products and reducing the development and adaptation costs of the inspection engine. The inspection result refers to the operational status data of the inspection target obtained through the inspection interface, presented in JSON format. It includes metrics such as CPU usage, memory usage, disk usage, and network inbound / outbound traffic. After initial cleaning and processing by the product management service, it is further integrated by the inspection engine, ultimately providing data support for the intelligent decision-making of the inspection platform.

[0048] Optionally, the inspection engine can be used to find the inspection address of the corresponding product management service based on the received inspection task, including: obtaining the inspection target contained in the inspection task through the inspection engine, generating a query request based on the inspection target and sending it to the registration center; and receiving the inspection address of the product management service that matches the inspection target returned by the registration center.

[0049] Specifically, the inspection engine, acting as the execution vehicle for inspection tasks, first extracts the inspection target from the task information after receiving the inspection task from the inspection platform. The inspection target explicitly points to a specific object on the PaaS cloud platform, including the product type to be inspected and the corresponding cluster information. After obtaining the specific information of the inspection target, the inspection engine generates a standardized query request based on the cluster information. The query request clearly includes the product type and cluster ID of the inspection target, ensuring that the registry center can accurately identify the query intent. Then, the inspection engine sends the query request to the registry center. The registry center, as the core hub storing information related to various product management services on the PaaS platform, has pre-collected the inspection addresses of all product management services and their corresponding inspection target relationships. Upon receiving the query request from the inspection engine, the registry center immediately matches and retrieves the inspection target identifier in the request, filtering out the product management service entry that perfectly corresponds to the inspection target from its stored information. Finally, the registration center will return the inspection address of the matched product management service to the inspection engine in the form of a response. After the inspection engine successfully receives the response, it can obtain the product management service inspection address required to execute the current inspection task.

[0050] Optionally, the inspection interface is invoked based on the inspection task and inspection address to obtain the inspection results, including: generating a call request based on the inspection target in the inspection task; invoking the inspection interface from the inspection address based on the call request to obtain the target indicator information corresponding to the call request in the product management service; and encapsulating the target indicator information in a specified format to generate the inspection results.

[0051] Specifically, the inspection engine generates standardized call requests based on the clearly defined inspection goals in the inspection task. The inspection goal is incorporated as a core parameter into the call request, which also adheres to the interface specifications preset by the product management service, ensuring that parameter formats and request methods meet interaction requirements. Required parameters include type, component name, and cluster ID. Based on the generated call request, the inspection engine initiates a call to the unified HTTP inspection interface provided by the product management service through the obtained inspection address. During the call, the inspection engine transmits all parameters in the call request according to the HTTP protocol specifications, ensuring that the product management service can accurately identify the inspection needs. After receiving the call request, the product management service retrieves the corresponding cluster's metric information from its database based on key information such as product type, component name, and cluster ID, and then feeds it back to the inspection engine. Finally, the inspection engine encapsulates the retrieved target metric information in a pre-defined JSON format. The encapsulated result includes a status identifier, the node name of the inspected object, and the corresponding metric data.

[0052] Optionally, the inspection results are cleaned and organized before being fed back to the inspection platform. This includes: validating the target indicator information in the inspection results, removing outliers from the target indicator information and filling in missing data to generate cleaned inspection results; converting the cleaned inspection results into a preset standard format to generate organized inspection results; and feeding back the organized inspection results to the inspection platform through a message queue or database sharing.

[0053] Specifically, the inspection engine performs validity checks on the target indicator information in the results. During the verification process, it checks whether each indicator conforms to normal logic and data specifications according to preset indicator data verification rules. For example, it checks whether indicators such as CPU utilization and memory utilization are within reasonable ranges, and whether data such as network inbound and outbound traffic have abnormal fluctuations that significantly exceed normal operating conditions. It also checks whether the data format is consistent with the agreed standards and whether there are invalid characters or garbled characters. After validity verification, outliers, such as indicator data that exceeds reasonable ranges or logically contradictory data, are directly removed to avoid abnormal data affecting the accuracy of subsequent analysis results. For missing data items, they are supplemented using preset reasonable completion rules, such as using the average data of the same type of inspection object during the same period, indicator data of similar historical periods, or estimated data that conforms to business logic to ensure the integrity of indicator data and finally generate cleaned inspection results.

[0054] Furthermore, the inspection engine will convert the cleaned inspection results according to a preset standard format. This preset standard format is a uniformly defined data format within the inspection system, ensuring consistency and compatibility of inspection data from different products and types, facilitating unified storage, analysis, and display by the inspection platform. During the conversion process, the field naming, data type, and numerical precision of the data are standardized, organizing the scattered indicator data by category and inspection object, making the data structure clear and easy to parse, thus generating the processed inspection results. Finally, the inspection engine will use the same message queue or database sharing method as when receiving inspection tasks to feed the processed inspection results back to the inspection platform. The message queue method enables asynchronous and efficient data transmission, ensuring the stability and timeliness of data feedback; the database sharing method allows the inspection platform to directly read the processed inspection results from a designated database through synchronous data storage.

[0055] S130. The inspection platform performs intelligent decision analysis based on the received inspection results.

[0056] Specifically, after receiving the cleaned and integrated inspection results from the inspection engine, the inspection platform activates its intelligent diagnosis and decision-making function. This function supports integration with large-scale artificial intelligence models or knowledge base case libraries to perform in-depth analysis of the inspection results. Through analysis, the inspection platform can identify whether the application system and related components are operating normally, promptly discover potential anomalies and hidden dangers, and clarify the root causes of problems. Then, the inspection platform generates an inspection report according to a pre-configured inspection report template, including inspection results, anomalies, and analysis conclusions. Based on the set notification methods and sending strategies, the report or alarm information is sent to designated contact groups so that maintenance personnel can promptly grasp the system's operating status and quickly take countermeasures to resolve problems. At the same time, the inspection platform also performs statistical analysis and archiving of the inspection reports, providing data support for subsequent system maintenance and optimization.

[0057] The technical solution of this invention configures and distributes inspection tasks through an inspection platform, achieving centralized and standardized task configuration and efficient distribution, ensuring accurate task delivery. The inspection engine locates the corresponding management service inspection address, calls interfaces to obtain results, cleans and organizes them for feedback, quickly adapting to multiple products, resolving network connectivity issues, and ensuring accurate and standardized inspection data. Based on the results, the inspection platform intelligently analyzes the data to quickly identify anomalies and potential hazards, reducing manual costs and improving operational response efficiency.

[0058] Example 2

[0059] Figure 2 This is a flowchart of a cloud platform inspection method provided in Embodiment 2 of the present invention. This embodiment adds a specific process for intelligent decision analysis based on the received inspection results through the inspection platform, building upon Embodiment 1. The specific content of steps S210-S220 is largely the same as steps S110-S120 in Embodiment 1, and therefore will not be repeated in this embodiment. Figure 2 As shown, the method includes:

[0060] S210: Configure and send inspection tasks to the inspection engine through the inspection platform.

[0061] Optionally, the inspection task can be configured and sent to the inspection engine through the inspection platform, including: obtaining the configuration information input by the user through the inspection platform, and creating the inspection task based on the configuration information, wherein the configuration information includes basic task information, inspection target, inspection indicators, execution method, execution time and inspection report notification settings; and sending the inspection task to the inspection engine in the form of a message queue or database sharing.

[0062] Optionally, the method also includes: acquiring indicator information of each inspection object through product management services by actively collecting or passively receiving information, wherein the inspection object is a specific instance under the inspection target; and temporarily storing each indicator information in its own database after cleaning and sorting, and encapsulating it into a pre-defined format.

[0063] S220: The inspection engine finds the inspection address of the corresponding product management service based on the received inspection task, calls the inspection interface based on the inspection task and inspection address to obtain the inspection results, and then cleans and organizes the inspection results before feeding them back to the inspection platform.

[0064] Optionally, the inspection engine can be used to find the inspection address of the corresponding product management service based on the received inspection task, including: obtaining the inspection target contained in the inspection task through the inspection engine, generating a query request based on the inspection target and sending it to the registration center; and receiving the inspection address of the product management service that matches the inspection target returned by the registration center.

[0065] Optionally, the inspection interface is invoked based on the inspection task and inspection address to obtain the inspection results, including: generating a call request based on the inspection target in the inspection task; invoking the inspection interface from the inspection address based on the call request to obtain the target indicator information corresponding to the call request in the product management service; and encapsulating the target indicator information in a specified format to generate the inspection results.

[0066] Optionally, the inspection results are cleaned and organized before being fed back to the inspection platform. This includes: validating the target indicator information in the inspection results, removing outliers from the target indicator information and filling in missing data to generate cleaned inspection results; converting the cleaned inspection results into a preset standard format to generate organized inspection results; and feeding back the organized inspection results to the inspection platform through a message queue or database sharing.

[0067] S230. Compare the inspection results with the inspection indicators to identify abnormal indicators.

[0068] Specifically, the inspection platform will compare the various indicator data acquired this time with the thresholds and normal ranges corresponding to the inspection indicators set by the user when configuring the inspection task. The inspection indicators cover key operational indicators such as CPU utilization, memory utilization, disk utilization, and network inbound and outbound traffic. During the comparison process, abnormal indicators that exceed the threshold range or do not conform to normal operating logic will be identified, and the specific type of abnormal indicator, the corresponding inspection object, and the degree of abnormality will be clearly identified.

[0069] S240. Connect to the knowledge base through the inspection platform and generate analysis results corresponding to abnormal indicators based on the knowledge base.

[0070] Specifically, the inspection platform leverages its integrated intelligent diagnostic and decision-making functions, connecting to a pre-set knowledge base and case library. In some scenarios, it can also integrate with large-scale artificial intelligence models to assist in analysis. The platform inputs information related to identified abnormal indicators into the knowledge base, including the anomaly type, the product and cluster to which it belongs, and the specific value of the indicator. It then retrieves historical fault cases, common problem solutions, and the logical relationships between abnormal indicators stored in the knowledge base. Based on matching cases and professional knowledge in the knowledge base, the system generates analysis results corresponding to the current abnormal indicator. The analysis results not only clarify the possible causes of the anomaly but also provide targeted troubleshooting directions and preliminary handling suggestions, helping operations and maintenance personnel quickly locate the root cause of the problem.

[0071] S250: Combine the analysis results with the configured report template to generate an inspection report, and send the inspection report to the designated user according to the sending strategy and notification method in the inspection report notification settings.

[0072] Specifically, the inspection platform combines the generated analysis results with the user-configured inspection report template to produce a complete and detailed inspection report. The report includes basic information about the inspection task, the inspection scope, the detection results of various indicators, details of abnormal indicators, analysis conclusions, and handling suggestions. After generating the report, the platform follows the inspection report notification settings configured by the user when configuring the inspection task, and sends the report to the configured contact group or designated users via preset notification methods such as email, SMS, and telephone, according to the specified sending strategy (e.g., immediate sending, scheduled summary sending). This allows relevant maintenance personnel to promptly obtain inspection results and anomaly warnings, enabling them to quickly take effective measures to address issues. Simultaneously, the platform statistically analyzes, archives, and stores the generated inspection reports, providing support for subsequent system maintenance optimization and historical data traceability.

[0073] Specific application scenarios: Figure 3 This is a schematic diagram of an inspection system architecture provided in Embodiment 2 of the present invention. Figure 3The mid-level inspection system architecture includes an inspection platform, an inspection engine, a PaaS product control plane, and inspection targets. The inspection platform comprises modules for inspection task management, inspection report management, real-time status monitoring, risk management, and intelligent diagnosis and decision-making. Inspection task management handles the configuration, creation, and distribution of inspection tasks. Inspection report management stores, queries, and archives reports generated from inspection results. Real-time status monitoring displays the real-time operational status of inspected objects. Risk management identifies, records, and tracks system risks discovered during inspections. Intelligent diagnosis and decision-making analyzes inspection results, locates problems, and provides recommendations. The inspection engine includes inspection task scheduling and execution, and inspection result cleaning and integration. Inspection task scheduling and execution receives tasks from the inspection platform, schedules and executes them, and invokes subsequent services. Inspection result cleaning and integration cleanses and organizes the acquired inspection data before feeding it back to the inspection platform. The PaaS product control plane acts as an intermediary layer connecting the inspection engine and inspection targets, using microservices to correspond to different PaaS products. PaaS management services are categorized into three types based on product type: application management, middleware management, and database management. Each type of management service corresponds to a specific product, such as the Kafka and Redis management services under middleware management; and the MySQL and PG management services under database management. These services are responsible for collecting metrics for the corresponding products and providing inspection interfaces. Inspection targets refer to the actual objects being inspected, corresponding to specific instances of the PaaS product's management interface. These include application clusters, middleware clusters (such as Kafka and Redis clusters), and database clusters (such as MySQL and PG clusters), and are the actual source of the inspection metric data.

[0074] Figure 4 This is a schematic diagram of a cloud platform inspection process provided in Embodiment 2 of the present invention. Figure 4The document showcases the four-layer collaborative process of the cloud platform inspection system. The inspection platform, the core of the entire system's management and decision-making, comprises four functional modules: the inspection task configuration module, responsible for creating and setting various information for inspection tasks; the inspection report management module, responsible for storing and managing the final generated inspection reports; the risk management module, responsible for identifying system risks discovered during inspections; and the intelligent diagnosis and decision-making module, responsible for analyzing inspection results, locating problems, and outputting recommendations. The inspection engine is the task execution and scheduling layer, supporting both periodically scheduled task execution and single-task execution. Periodically scheduled task execution refers to automatically executing inspections according to a preset cycle; single-task execution refers to performing a one-time inspection based on demand. The PaaS product management service is the intermediary layer connecting the inspection engine and the inspection target, including indicator collection and indicator data cleaning and organization functions. Indicator collection refers to obtaining the operational data of the inspection target through proactive collection of indicator information or passive reception of proactively reported indicator information; indicator data cleaning and organization refers to cleaning and standardizing the format of the collected raw data. The inspection target is the actual object being inspected and is the source of the indicator data. The entire inspection process consists of three core steps: S1, Issuing Inspection Tasks: After completing the task configuration, the inspection platform issues the inspection tasks to the inspection engine. S2, Obtaining Inspection Results: The inspection engine executes the task according to the task type, obtaining the cleaned and organized indicator data by accessing the HTTP interface provided by the PaaS product management service. S3, Reporting Inspection Results: The inspection engine sends the obtained inspection results back to the inspection platform, where the platform performs intelligent diagnosis and decision-making, ultimately generating an inspection report.

[0075] The technical solution of this invention compares inspection results with inspection indicators through an inspection platform, enabling rapid and accurate identification of abnormal indicators and timely detection of potential system vulnerabilities. By connecting to a knowledge base to generate corresponding analysis results, the root cause of anomalies and the direction of handling can be clearly identified, reducing the cost of manual judgment. By generating standardized inspection reports and pushing them to designated users, efficient transmission of anomaly information is achieved, assisting maintenance personnel in rapid response and handling, improving the efficiency of the inspection loop and the targeted nature of problem solving.

[0076] Example 3

[0077] Figure 5 This is a schematic diagram of a cloud platform inspection device provided in Embodiment 3 of the present invention. Figure 5 As shown, the device includes: an inspection task distribution module 310, which is used to configure and distribute inspection tasks to the inspection engine through the inspection platform;

[0078] The inspection result feedback module 320 is used to find the inspection address of the corresponding product management service through the inspection engine based on the received inspection task, call the inspection interface based on the inspection task and inspection address to obtain the inspection results, and then clean and organize the inspection results and feed them back to the inspection platform.

[0079] The intelligent decision analysis module 330 is used to perform intelligent decision analysis based on the received inspection results through the inspection platform.

[0080] Optionally, the inspection task distribution module 310 is specifically used to: obtain configuration information input by the user through the inspection platform, and create inspection tasks based on the configuration information, wherein the configuration information includes basic task information, inspection target, inspection indicators, execution method, execution time and inspection report notification settings; and send the inspection task to the inspection engine in the form of a message queue or database sharing.

[0081] Optionally, the device also includes: an indicator information acquisition module, used to: acquire indicator information of each inspection object through product management services by actively collecting or passively receiving information, wherein the inspection object is a specific instance under the inspection target; and temporarily store each indicator information in its own database after cleaning and sorting, and encapsulate it into a pre-defined format.

[0082] Optionally, the inspection result feedback module 320 specifically includes: an inspection address determination unit, used to: obtain the inspection targets contained in the inspection task through the inspection engine, generate a query request based on the inspection targets and send it to the registration center; and receive the inspection address of the product management service that matches the inspection targets returned by the registration center.

[0083] Optionally, the inspection result feedback module 320 specifically includes: an inspection result acquisition unit, used to: generate a call request based on the inspection target in the inspection task; call the inspection interface from the inspection address based on the call request to obtain the target indicator information corresponding to the call request in the product management service; and encapsulate the target indicator information in a specified format to generate the inspection result.

[0084] Optionally, the inspection result feedback module 320 specifically includes: an inspection result feedback unit, used to: verify the validity of the target indicator information in the inspection results, remove outliers from the target indicator information and fill in missing data, and generate cleaned inspection results; convert the cleaned inspection results according to a preset standard format to generate sorted inspection results, and feed back the sorted inspection results to the inspection platform through a message queue or database sharing.

[0085] Optionally, the intelligent decision analysis module 330 is specifically used to: compare inspection results with inspection indicators to identify abnormal indicators; connect to the knowledge base through the inspection platform and generate analysis results corresponding to the abnormal indicators based on the knowledge base; combine the analysis results with the configured report template to generate an inspection report, and send the inspection report to the designated user according to the sending strategy and notification method in the inspection report notification settings.

[0086] The technical solution of this invention configures and distributes inspection tasks through an inspection platform, achieving centralized and standardized task configuration and efficient distribution, ensuring accurate task delivery. The inspection engine locates the corresponding management service inspection address, calls interfaces to obtain results, cleans and organizes them for feedback, quickly adapting to multiple products, resolving network connectivity issues, and ensuring accurate and standardized inspection data. Based on the results, the inspection platform intelligently analyzes the data to quickly identify anomalies and potential hazards, reducing manual costs and improving operational response efficiency.

[0087] The cloud platform inspection device provided in this embodiment of the invention can execute a cloud platform inspection method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method.

[0088] Example 4

[0089] Figure 6 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0090] like Figure 6 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0091] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0092] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as a cloud platform inspection method.

[0093] In some embodiments, a cloud platform inspection method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the cloud platform inspection method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform a cloud platform inspection method by any other suitable means (e.g., by means of firmware).

[0094] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0095] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0096] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0097] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0098] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0099] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0100] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0101] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A cloud platform inspection method, characterized in that, The application is applied to a patrol system, and the patrol system comprises a patrol platform, a patrol engine and a product management service, and the method comprises the following steps: The patrol platform is configured and the patrol task is sent to the patrol engine; The patrol engine finds the patrol address of the product management service according to the received patrol task, calls the patrol interface based on the patrol task and the patrol address, obtains the patrol result, and feeds back the patrol result to the patrol platform after cleaning and arranging the patrol result; The patrol platform makes intelligent decision analysis according to the received patrol result.

2. The method of claim 1, wherein, The patrol platform is configured and the patrol task is sent to the patrol engine, which comprises the following steps: The patrol platform obtains the configuration information input by a user, and creates a patrol task based on the configuration information, wherein the configuration information comprises task basic information, a patrol target, a patrol index, an execution mode, an execution time and patrol report notification setting; The patrol task is sent to the patrol engine in the form of a message queue or database sharing.

3. The method of claim 2, wherein, The method further comprises the following steps: The product management service obtains index information of each patrol object in a manner of active collection or passive reception, wherein the patrol object is a specific instance under the patrol target; Each index information is temporarily stored in the database of the product management service after being cleaned and arranged, and is packaged in a predetermined format.

4. The method of claim 1, wherein, The patrol engine obtains the patrol target contained in the patrol task, generates a query request according to the patrol target and sends the query request to a registration center, and receives the patrol address of the product management service matched with the patrol target returned by the registration center. The calling request is generated according to the patrol target in the patrol task, the patrol interface is called from the patrol address based on the calling request, target index information corresponding to the calling request in the product management service is obtained, and the target index information is packaged in a specified format to generate a patrol result. The patrol result is cleaned and arranged and then fed back to the patrol platform, which comprises the following steps:

5. The method of claim 2, wherein, The target index information in the patrol result is subjected to validity verification, abnormal values in the target index information are eliminated and missing data is supplemented to generate a cleaned patrol result; The cleaned patrol result is converted into an arranged patrol result in a predetermined standard format, and the arranged patrol result is fed back to the patrol platform in the form of message queue or database sharing. The patrol platform makes intelligent decision analysis according to the received patrol result, which comprises the following steps: The patrol result and the patrol index are compared to identify abnormal indexes; 6. The method of claim 5, wherein, The patrol platform is connected to a knowledge base, and an analysis result corresponding to the abnormal index is generated based on the knowledge base; The analysis result is combined with a configured report template to generate a patrol report, and the patrol report is sent to a specified user according to a sending strategy and a notification mode in the patrol report notification setting. The application is applied to the method in any one of claims 1-7, and comprises:

7. The method of claim 2, wherein, A patrol task sending module is configured and the patrol task is sent to the patrol engine through the patrol platform; ​ ​ ​ 8. A cloud platform inspection device, characterized by, ​ ​ The inspection result feedback module is configured to: find, by the inspection engine, an inspection address of the product management and control service corresponding to the received inspection task, call an inspection interface based on the inspection task and the inspection address, obtain an inspection result, clean and arrange the inspection result, and feed back the inspection result to the inspection platform; The intelligent decision analysis module is configured to: perform intelligent decision analysis on the received inspection result by the inspection platform.

9. An electronic device, comprising: The electronic device comprises: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores a computer program capable of being executed by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the method of any one of claims 1-7.

10. A computer storage medium, characterized in that, The computer storage medium stores computer instructions, and the computer instructions are used to enable the processor to implement the method of any one of claims 1-7 when executed.

Images