CN118860771A - Method, device, computer equipment, readable storage medium and program product based on microservice instance number and call chain inspection - Google Patents

Abstract

The present application relates to a method, device, computer equipment, readable storage medium and computer program product for microservice instance number and call chain inspection, and relates to the field of computer technology. The present application can improve the monitoring efficiency of the microservice architecture, and also help to improve the stability, scalability and maintainability of the system. The method includes: responding to an inspection request for a microservice, obtaining the microservice instances existing in the microservice architecture and the call chain information corresponding to each microservice instance, counting the microservice instances, and obtaining the number of microservice instances; creating an inspection task based on the number of microservice instances and the call chain information; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain; executing the inspection task regularly according to a preset frequency, and synchronously generating an inspection report according to the data collection results corresponding to the inspection task; analyzing the inspection report, obtaining the inspection result, and pushing the inspection result by message.

Description

Method, device, computer equipment, readable storage medium and program product based on the number of microservice instances and call chain inspection

Technical Field

The present application relates to the field of computer technology, and in particular to a method, apparatus, computer device, computer-readable storage medium, and computer program product for inspecting the number of microservice instances and call chains.

Background Art

With the development of computer technology, a software architecture style called microservice architecture has emerged. Microservice architecture splits applications into a series of small independent services, each of which can be independently deployed, expanded, and maintained. However, due to the large number of microservice instances in the microservice architecture, monitoring and managing these microservice instances becomes very complicated, and there are complex call relationships between microservice instances, and the call links are numerous, making it difficult to track and analyze.

In traditional technology, the operation of microservice architecture is mainly monitored by using some monitoring and inspection tools. However, most of these tools monitor and analyze a single microservice instance or call chain, lacking a comprehensive assessment of the entire microservice architecture, resulting in low monitoring efficiency in the current microservice architecture monitoring methods.

Summary of the invention

Based on this, it is necessary to provide a method, device, computer equipment, computer-readable storage medium and computer program product for inspecting the number of instances and call chains based on microservices in order to solve the above technical problems.

In a first aspect, the present application provides a method for inspecting the number of microservice instances and call chains, including:

In response to an inspection request for a microservice, obtain microservice instances existing in the microservice architecture and call chain information corresponding to each of the microservice instances, count the microservice instances, and obtain the number of microservice instances;

Based on the number of microservice instances and the call chain information, an inspection task is created; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain;

The inspection task is executed regularly according to a preset frequency, and an inspection report is generated synchronously according to the data collection results corresponding to the inspection task;

The inspection report is analyzed to obtain inspection results, and the inspection results are pushed as messages.

In one embodiment, the periodically performing the inspection task according to a preset frequency includes:

The microservice instance status and the call chain status in the microservice architecture are monitored regularly according to a preset frequency to obtain monitoring results; the monitoring results are identified to obtain target microservice instances in an online state and target call chains in an abnormal state; the target microservice instances and the target call chains are summarized to obtain the number of online instances and the number of abnormal states of the call chains.

In one embodiment, the synchronously generating an inspection report according to the data collection results in the inspection task includes:

According to the number of online instances and the number of microservice instances, the online proportion of microservices in the microservice architecture is obtained; according to the number of call chain abnormal states and the call chain information, the abnormal proportion of call chains in the microservice architecture is obtained; and the inspection report including the online proportion of microservices and the abnormal proportion of call chains is synchronously generated.

In one embodiment, analyzing the inspection report to obtain the inspection result, and pushing the inspection result as a message includes:

Respectively determine whether the online proportion of the microservices and the abnormal proportion of the call chain meet corresponding threshold conditions; if at least one of the values of the online proportion of the microservices and the abnormal proportion of the call chain does not meet the threshold condition, generate the inspection result including the value that does not meet the threshold condition, and push the inspection result as a message according to a preset push method.

In one embodiment, after creating the inspection task based on the number of microservice instances and the call chain information, the method further includes:

Generate unique identification information corresponding to the inspection task; match the target information entry in the inspection task list according to the unique identification information; enter the inspection task into the target information entry in the inspection task list for storage.

In one embodiment, the method further comprises:

When an export instruction for a target inspection task is received, the unique identification information corresponding to the target inspection task is extracted according to the export instruction; based on the unique identification information corresponding to the target inspection task, the target inspection task is identified and extracted from the inspection task list to obtain the inspection task information corresponding to the target inspection task.

In a second aspect, the present application also provides a device for inspecting the number of microservice instances and call chains, including:

An instance acquisition module is used to respond to inspection requests for microservices, obtain microservice instances existing in the microservice architecture and call chain information corresponding to each of the microservice instances, and count the microservice instances to obtain the number of microservice instances;

A task creation module, used to create an inspection task based on the number of microservice instances and the call chain information; the inspection items in the inspection task include monitoring of the number of online instances and the number of abnormal states of the call chain;

A report generation module, used to execute the inspection task regularly according to a preset frequency, and synchronously generate an inspection report based on the data collection results corresponding to the inspection task;

The message push module is used to analyze the inspection report, obtain the inspection result, and push the inspection result as a message.

In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

In response to an inspection request for a microservice, the microservice instances existing in the microservice architecture and the call chain information corresponding to each of the microservice instances are obtained, the microservice instances are counted to obtain the number of microservice instances; based on the number of microservice instances and the call chain information, an inspection task is created; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain; the inspection task is executed regularly at a preset frequency, and an inspection report is synchronously generated according to the data collection result corresponding to the inspection task; the inspection report is analyzed to obtain the inspection result, and the inspection result is pushed as a message.

In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

In response to an inspection request for a microservice, the microservice instances existing in the microservice architecture and the call chain information corresponding to each of the microservice instances are obtained, the microservice instances are counted to obtain the number of microservice instances; based on the number of microservice instances and the call chain information, an inspection task is created; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain; the inspection task is executed regularly at a preset frequency, and an inspection report is synchronously generated according to the data collection result corresponding to the inspection task; the inspection report is analyzed to obtain the inspection result, and the inspection result is pushed as a message.

In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

In response to an inspection request for a microservice, the microservice instances existing in the microservice architecture and the call chain information corresponding to each of the microservice instances are obtained, the microservice instances are counted to obtain the number of microservice instances; based on the number of microservice instances and the call chain information, an inspection task is created; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain; the inspection task is executed regularly at a preset frequency, and an inspection report is synchronously generated according to the data collection result corresponding to the inspection task; the inspection report is analyzed to obtain the inspection result, and the inspection result is pushed as a message.

The above-mentioned inspection method, device, computer equipment, computer-readable storage medium and computer program product based on the number of microservice instances and call chain can comprehensively evaluate the entire microservice architecture, including monitoring and evaluating the number of each microservice instance in the microservice architecture and the operation of the call chain, and collecting the operation data of the microservice instance and the tracking information of the call chain by creating inspection tasks, so as to provide a reference basis for analyzing the performance indicators of the number of microservice instances and the call chain, so as to more accurately and efficiently identify potential performance bottlenecks and causes of failures, and provide users with corresponding inspection results in a timely manner to help users optimize the microservice architecture, thereby improving the monitoring efficiency of the microservice architecture, and also helping to improve the stability, scalability and maintainability of the system.

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIG1 is an application environment diagram of a method for inspecting the number of microservice instances and call chains in one embodiment;

FIG2 is a flow chart of a method for inspecting the number of microservice instances and call chains in one embodiment;

FIG3 is a schematic diagram of a flow chart of steps for executing an inspection task in one embodiment;

FIG4 is a flow chart of a method for inspecting the number of microservice instances and call chains in a specific embodiment;

FIG5 is a structural block diagram of a device for inspecting the number of microservice instances and call chains in one embodiment;

FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

The microservice-based instance number and call chain inspection method provided in the embodiment of the present application can be applied to the application environment shown in Figure 1. Among them, the terminal communicates with the server through the network. The data storage system can store the data that the server needs to process. The data storage system can be integrated on the server, or it can be placed on the cloud or other network servers.

Specifically, the microservice-based instance number and call chain inspection method provided in the embodiments of the present application can be executed by the server.

Exemplarily, the server responds to an inspection request for a microservice, obtains the microservice instances existing in the microservice architecture and the call chain information corresponding to each microservice instance, counts the microservice instances, and obtains the number of microservice instances; the server creates an inspection task based on the number of microservice instances and the call chain information; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal call chain states; the server executes the inspection task at a preset frequency, and synchronously generates an inspection report based on the data collection results corresponding to the inspection task; the server analyzes the inspection report, obtains the inspection results, and pushes the inspection results as a message.

In the application environment shown in FIG1 , the terminal may be, but is not limited to, various personal computers, notebook computers, smart phones, and tablet computers. The server may be implemented as an independent server or a server cluster consisting of multiple servers.

In one embodiment, as shown in FIG2 , a method for inspecting the number of microservice instances and call chains is provided. The method is described by taking the application of the method to the server in FIG1 as an example, and includes the following steps:

Step S201, in response to an inspection request for a microservice, obtain microservice instances existing in the microservice architecture and call chain information corresponding to each microservice instance, count the microservice instances, and obtain the number of microservice instances.

Among them, the microservice architecture is a software architecture design pattern in which the application is divided into a series of small, autonomous service units. Each service unit is built around a specific business function and can be independently deployed, expanded, and updated.

Among them, a microservice instance can be one or more running instances in the microservice architecture, responsible for providing specific business functions or services, and can be deployed and run independently.

Among them, the call chain can be a call relationship chain formed by mutual calls between multiple microservices in a distributed system or microservice architecture, which can be used to complete complex business logic or business processes.

Specifically, the server responds to the user's inspection request for the microservice, queries and obtains the microservice instances existing in the microservice architecture and the call chain information corresponding to each microservice instance, counts the microservice instances, and summarizes the number of microservice instances.

Step S202: Create an inspection task based on the number of microservice instances and call chain information; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain.

Among them, the inspection task can be an operation task for regular monitoring and maintenance of the microservice architecture configured by the server according to the number of microservice instances and call chain information.

Specifically, the server determines the inspection configuration based on the number of microservice instances and the call chain information, and creates an inspection task according to the inspection configuration; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain.

Step S203, regularly executing the inspection task according to the preset frequency, and synchronously generating an inspection report according to the data collection result corresponding to the inspection task.

Among them, the inspection report can be a report generated based on relevant data collected during the inspection process, which is used to record key information such as the number of online instances in the microservice architecture and the number of abnormal states of the call chain, and can provide data support for the generation of inspection results.

The data collection results may include various data collected during system operation, including but not limited to the operation data of microservice instances and tracking information of call chains, which can be used for subsequent analysis and evaluation.

Specifically, the server regularly performs inspection tasks according to a preset frequency, collects various data during system operation, obtains data collection results, and synchronously generates inspection reports based on the data collection results corresponding to the inspection tasks.

Step S204, analyzing the inspection report, obtaining the inspection result, and pushing the inspection result as a message.

The inspection result may be an analysis result corresponding to the inspection report, which is used to summarize the system's performance status, problems found, analysis results and suggestions, and provide a reference for system optimization and improvement.

Specifically, the server judges and analyzes the data collection results contained in the inspection report to obtain the inspection results, and pushes the inspection results in a message according to the push method preset by the user.

The above-mentioned inspection method based on the number of microservice instances and call chains can comprehensively evaluate the entire microservice architecture, including monitoring and evaluating the number of each microservice instance in the microservice architecture and the operation of the call chain, and collecting the operation data of the microservice instance and the tracking information of the call chain by creating inspection tasks, so as to provide a reference for analyzing the performance indicators of the number of microservice instances and the call chain, so as to more accurately and efficiently identify potential performance bottlenecks and causes of failures, and provide users with corresponding inspection results in a timely manner to help users optimize the microservice architecture, thereby improving the monitoring efficiency of the microservice architecture, and also helping to improve the stability, scalability and maintainability of the system.

In one embodiment, as shown in FIG. 3 , in the above step S203, the inspection task is performed regularly according to a preset frequency, specifically including the following steps:

Step S301, monitor the microservice instance status and call chain status in the microservice architecture at a preset frequency to obtain monitoring results.

Step S302: Identify the monitoring results to obtain the target microservice instance in the online state and the target call chain in the abnormal state.

Step S303: Summarize the target microservice instances and target call chains to obtain the number of online instances and the number of abnormal call chain states.

Among them, the abnormal state of the call chain refers to the error or abnormal situation in which the entire request processing chain has problems due to errors or exceptions in some services during the request processing process composed of multiple microservices in a distributed system, including but not limited to timeout exceptions, network exceptions, and service failures.

Specifically, the server obtains the inspection configuration from the database, and monitors the status of the microservice instances and the call chain in the microservice architecture according to the preset frequency and the inspection configuration, and obtains the detailed information of the microservices; analyzes and identifies the detailed information of the microservices, obtains the target microservice instances in the online state and the target call chain in the abnormal state; summarizes the target microservice instances and the target call chain, and counts the number of online instances and the number of abnormal states of the call chain.

In this embodiment, by regularly monitoring the status of microservice instances and call chain status in the microservice architecture, and identifying and summarizing the monitoring results, the number of online instances and the number of abnormal call chain states are accurately counted, providing an effective basis for analyzing the number of microservice instances and the performance indicators of the call chain.

In one embodiment, in the above step S203, the inspection report is synchronously generated according to the data collection result in the inspection task, which specifically includes the following steps:

According to the number of online instances and the number of microservice instances, the online proportion of microservices in the microservice architecture is obtained; according to the number of call chain abnormal states and call chain information, the call chain abnormal proportion in the microservice architecture is obtained; and an inspection report including the online proportion of microservices and the call chain abnormal proportion is generated synchronously.

Specifically, the server calculates the online proportion of microservices in the microservice architecture through the first computing model based on the number of online instances and the number of microservice instances; then calculates the call chain abnormality proportion in the microservice architecture through the second computing model based on the number of call chain abnormal states and call chain information; and simultaneously generates an inspection report including the microservice online proportion and the call chain abnormality proportion.

In this embodiment, by calculating the online proportion of microservices and the abnormal proportion of call chains in the microservice architecture, and synchronously generating an inspection report including the online proportion of microservices and the abnormal proportion of call chains, scientific and accurate data support is provided for the generation of inspection results.

In one embodiment, in the above step S204, the inspection report is analyzed to obtain the inspection result, and the inspection result is pushed as a message, which specifically includes the following steps:

Determine whether the online proportion of microservices and the abnormal proportion of call chains meet the corresponding threshold conditions respectively; if at least one of the values of the online proportion of microservices and the abnormal proportion of call chains does not meet the threshold conditions, generate an inspection result including the value that does not meet the threshold conditions, and push the inspection result by message according to the preset push method.

The threshold condition may be a limit value or threshold value set by the user according to the actual situation, which is used to determine whether the online proportion of microservices and the abnormal proportion of call chains meet the corresponding conditions.

The preset push method may be to push via email or text message.

Specifically, the server determines whether the online proportion of microservices and the call chain abnormality proportion meet the corresponding threshold conditions respectively; when it is identified that at least one of the values of the online proportion of microservices and the call chain abnormality proportion does not meet the threshold condition, the target value that does not meet the threshold condition is determined, and an inspection result including the target value is generated, and then the inspection result is pushed as a message according to a preset push method.

In this embodiment, by identifying the target values that do not meet the threshold conditions and generating inspection results containing the target values, accurate analysis of the inspection report is achieved, and the inspection results containing the analysis content can be provided to users in a timely manner to help users optimize the microservice architecture.

In one embodiment, after creating the inspection task based on the number of microservice instances and the call chain information, the method of the present application further includes the following steps:

Generate unique identification information corresponding to the inspection task; match the target information item in the inspection task list according to the unique identification information; enter the inspection task into the target information item in the inspection task list for storage.

The unique identification information may be a task name or a task number of the inspection task, and the information items in the inspection task list correspond one-to-one with each inspection task through the identification information.

The information entry may be a short information unit arranged according to certain rules in the inspection task list, similar to a title or a section.

Specifically, after creating the inspection task, the server generates unique identification information corresponding to the inspection task, matches the target information item in the inspection task list according to the unique identification information; and enters the inspection task into the target information item in the inspection task list for storage.

In this embodiment, the target information items in the inspection task list are matched according to the unique identification information, and the inspection tasks are entered into the target information items in the inspection task list for storage. Thus, the inspection tasks are entered into the inspection task list in a regular and orderly manner based on the unique identification information corresponding to the inspection tasks, which is conducive to the efficient and accurate execution of the inspection tasks.

In one embodiment, the method of the present application further includes the following steps:

When an export instruction for a target inspection task is received, the unique identification information corresponding to the target inspection task is extracted according to the export instruction; based on the unique identification information corresponding to the target inspection task, the target inspection task is identified and extracted from the inspection task list to obtain the inspection task information corresponding to the target inspection task.

The export instruction may be an instruction issued by a relevant operation and maintenance personnel who has the authority to view the inspection task list.

Specifically, when the server receives an export instruction for a target inspection task, it extracts the unique identification information corresponding to the target inspection task according to the export instruction; based on the unique identification information corresponding to the target inspection task, it identifies and extracts the target inspection task from the inspection task list, and sends the inspection task information corresponding to the target inspection task to the terminal for display by the terminal.

In this embodiment, the target inspection task is identified and extracted from the inspection task list based on the unique identification information corresponding to the target inspection task, and the inspection task information corresponding to the target inspection task is sent to the terminal for display by the terminal, so as to quickly and accurately identify and obtain the inspection task information corresponding to the target inspection task, thereby facilitating the operation and maintenance personnel to perform subsequent analysis and processing of the inspection task information.

In one embodiment, as shown in FIG4 , a method for inspecting the number of microservice instances and call chains is provided, which specifically includes the following steps:

Step S401, in response to an inspection request for a microservice, obtain microservice instances existing in the microservice architecture and call chain information corresponding to each microservice instance, count the microservice instances, and obtain the number of microservice instances.

Step S402: Create an inspection task based on the number of microservice instances and call chain information.

Step S403, generating unique identification information corresponding to the inspection task; matching the target information item in the inspection task list according to the unique identification information; entering the inspection task into the target information item in the inspection task list for storage.

Step S404, monitor the status of microservice instances and call chain status in the microservice architecture at a preset frequency to obtain monitoring results; identify the monitoring results to obtain target microservice instances in online status and target call chains in abnormal status; summarize the target microservice instances and target call chains to obtain the number of online instances and the number of abnormal call chain statuses.

Step S405, according to the number of online instances and the number of microservice instances, obtain the online proportion of microservices in the microservice architecture; according to the number of call chain abnormal states and the call chain information, obtain the call chain abnormal proportion in the microservice architecture; and synchronously generate an inspection report including the online proportion of microservices and the call chain abnormal proportion.

Step S406, respectively determine whether the online proportion of microservices and the abnormal proportion of call chains meet the corresponding threshold conditions; if at least one of the values of the online proportion of microservices and the abnormal proportion of call chains does not meet the threshold condition, generate an inspection result including the value that does not meet the threshold condition, and push the inspection result in a message according to a preset push method.

Step S407, when receiving the export instruction for the target inspection task, extract the unique identification information corresponding to the target inspection task according to the export instruction; identify and extract the target inspection task in the inspection task list according to the unique identification information corresponding to the target inspection task, and obtain the inspection task information corresponding to the target inspection task.

The beneficial effects brought by the above embodiments are as follows:

1) Comprehensiveness: This application can comprehensively evaluate the entire microservice architecture, including the number of microservice instances and performance indicators of the call chain, so as to more accurately discover potential performance bottlenecks and causes of failures.

2) Simplicity: This application uses simple and easy-to-use methods and tools, allowing operators to easily perform microservice inspections without the need for professional technical knowledge and experience.

3) Scientificity: This application not only provides monitoring and analysis functions, but also conducts in-depth analysis of performance bottlenecks and failure causes, and provides corresponding optimization suggestions to help users optimize the microservice architecture and improve the stability, scalability and maintainability of the system.

It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

Based on the same inventive concept, the embodiment of the present application also provides a device for inspecting the number of microservice-based instances and call chains for implementing the above-mentioned method for inspecting the number of microservice-based instances and call chains. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above-mentioned method, so the specific limitations in the embodiments of one or more microservice-based instance number and call chain inspection devices provided below can refer to the limitations of the microservice-based instance number and call chain inspection method above, and will not be repeated here.

In an exemplary embodiment, as shown in FIG5 , a device for inspecting the number of microservice instances and call chains is provided, including:

The instance acquisition module 501 is used to respond to the inspection request for the microservice, obtain the microservice instances existing in the microservice architecture and the call chain information corresponding to each microservice instance, count the microservice instances, and obtain the number of microservice instances;

The task creation module 502 is used to create an inspection task based on the number of microservice instances and call chain information; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain;

The report generation module 503 is used to perform the inspection task regularly according to the preset frequency, and synchronously generate the inspection report according to the data collection results corresponding to the inspection task;

The message push module 504 is used to analyze the inspection report, obtain the inspection result, and push the inspection result as a message.

In one embodiment, the report generation module 503 is also used to monitor the microservice instance status and call chain status in the microservice architecture at a preset frequency to obtain monitoring results; identify the monitoring results to obtain the target microservice instance in the online state and the target call chain in the abnormal state; summarize the target microservice instance and the target call chain to obtain the number of online instances and the number of abnormal call chains.

In one embodiment, the report generation module 503 is also used to obtain the online proportion of microservices in the microservice architecture based on the number of online instances and the number of microservice instances; obtain the call chain abnormality proportion in the microservice architecture based on the number of call chain abnormal states and call chain information; and synchronously generate an inspection report including the microservice online proportion and the call chain abnormality proportion.

In one embodiment, the message push module 504 is also used to determine whether the online proportion of microservices and the abnormal proportion of call chains meet the corresponding threshold conditions; when at least one of the values of the online proportion of microservices and the abnormal proportion of call chains does not meet the threshold conditions, an inspection result containing the value that does not meet the threshold conditions is generated, and the inspection result is pushed as a message according to a preset push method.

In one embodiment, the microservice instance number and call chain inspection device also includes a task entry module for generating unique identification information corresponding to the inspection task; matching the target information entry in the inspection task list according to the unique identification information; and entering the inspection task into the target information entry in the inspection task list for storage.

In one embodiment, the microservice instance number and call chain inspection device also includes a task export module, which is used to extract the unique identification information corresponding to the target inspection task according to the export instruction when receiving the export instruction for the target inspection task; according to the unique identification information corresponding to the target inspection task, identify and extract the target inspection task in the inspection task list to obtain the inspection task information corresponding to the target inspection task.

Each module in the above-mentioned microservice-based instance number and call chain inspection device can be implemented in whole or in part by software, hardware, and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG6. The computer device includes a processor, a memory, an input/output interface (Input/Output, referred to as I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store inspection task data. The input/output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for inspecting the number of instances and call chains based on microservices is implemented.

Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims (10)

1. A method for inspecting the number of microservice instances and call chains, characterized in that the method comprises: In response to an inspection request for a microservice, obtain microservice instances existing in the microservice architecture and call chain information corresponding to each of the microservice instances, count the microservice instances, and obtain the number of microservice instances; Based on the number of microservice instances and the call chain information, an inspection task is created; the inspection items in the inspection task include monitoring the number of online instances and the number of abnormal states of the call chain; The inspection task is executed regularly according to a preset frequency, and an inspection report is generated synchronously according to the data collection results corresponding to the inspection task; The inspection report is analyzed to obtain inspection results, and the inspection results are pushed as messages. 2. The method according to claim 1, characterized in that the step of regularly performing the inspection task at a preset frequency comprises: Monitor the microservice instance status and call chain status in the microservice architecture regularly according to a preset frequency to obtain monitoring results; Identify the monitoring results to obtain the target microservice instance in the online state and the target call chain in the abnormal state; The target microservice instances and the target call chains are summarized to obtain the number of online instances and the number of abnormal states of the call chains. 3. The method according to claim 2, characterized in that the step of synchronously generating an inspection report according to the data collection results in the inspection task comprises: According to the number of online instances and the number of microservice instances, an online proportion of microservices in the microservice architecture is obtained; According to the number of abnormal states of the call chain and the call chain information, a call chain abnormality ratio in the microservice architecture is obtained; The inspection report including the online proportion of the microservices and the abnormal proportion of the call chain is synchronously generated. 4. The method according to claim 3, characterized in that the analyzing the inspection report to obtain the inspection result and pushing the inspection result as a message comprises: Determine whether the online proportion of the microservices and the abnormal proportion of the call chain meet corresponding threshold conditions respectively; When at least one of the values of the online proportion of the microservices and the abnormal proportion of the call chain does not meet the threshold condition, the inspection result including the value that does not meet the threshold condition is generated, and the inspection result is pushed as a message according to a preset push method. 5. The method according to claim 1, characterized in that after creating the inspection task based on the number of microservice instances and the call chain information, it also includes: Generate unique identification information corresponding to the inspection task; According to the unique identification information, matching the target information entry in the inspection task list; The inspection task is entered into the target information item in the inspection task list for storage. 6. The method according to claim 5, characterized in that the method further comprises: When receiving an export instruction for a target inspection task, extracting unique identification information corresponding to the target inspection task according to the export instruction; According to the unique identification information corresponding to the target inspection task, the target inspection task is identified and extracted in the inspection task list to obtain the inspection task information corresponding to the target inspection task. 7. A device for inspecting the number of microservice instances and call chains, characterized in that the device comprises: An instance acquisition module is used to respond to inspection requests for microservices, obtain microservice instances existing in the microservice architecture and call chain information corresponding to each of the microservice instances, and count the microservice instances to obtain the number of microservice instances; A task creation module, used to create an inspection task based on the number of microservice instances and the call chain information; the inspection items in the inspection task include monitoring of the number of online instances and the number of abnormal states of the call chain; A report generation module, used to execute the inspection task regularly according to a preset frequency, and synchronously generate an inspection report based on the data collection results corresponding to the inspection task; The message push module is used to analyze the inspection report, obtain the inspection result, and push the inspection result as a message. 8. A computer device, comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor implements the steps of the method according to any one of claims 1 to 6 when executing the computer program. 9. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented. 10. A computer program product, comprising a computer program, characterized in that when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.