WO2021000416A1

WO2021000416A1 - Micro-service early warning method and apparatus based on management platform, and computer device

Info

Publication number: WO2021000416A1
Application number: PCT/CN2019/103549
Authority: WO
Inventors: 王丽
Original assignee: 平安科技（深圳）有限公司
Priority date: 2019-07-03
Filing date: 2019-08-30
Publication date: 2021-01-07
Also published as: CN110445636B; CN110445636A

Abstract

A micro-service early warning method and apparatus based on a management platform, and a computer device and a storage medium. The method comprises: receiving a calling message sent by a first micro-service; if a specified communication protocol is the same as a pre-set communication protocol of a specified micro-service, obtaining a calling message header; calculating a similarity value between the calling message header and a standard calling message header; if the similarity value is greater than a similarity threshold value, replacing the calling message header with the standard calling message header; and if the number of times that the specified micro-service is called is greater than a first early warning threshold value for the number of times, generating early warning information, sending the early warning information and the replaced calling message to the specified micro-service, and adding the specified micro-service to a monitoring list by means of a monitoring plug-in. Therefore, a message is corrected while early warning is performed on a micro-service, so as to improve the availability and the use efficiency of a micro-service message.

Description

Microservice early warning method, device and computer equipment based on management platform

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on July 3, 2019, the application number is 201910596482.4, and the invention title is "microservice early warning methods, devices and computer equipment based on management platforms". The reference is incorporated in this application.

Technical field

This application relates to the computer field, in particular to a microservice early warning method, device, computer equipment and storage medium based on a management platform.

Background technique

The microservice framework is used to replace the original single large-scale enterprise application, and can solve the problems of high complexity, serious coupling, and so on. With the increase in business, the number of microservices is increasing day by day, which brings inconvenience to the management of microservices, such as the mutual invocation of multiple microservices, and the interaction between internal microservices and the outside world. And the call messages that are called between microservices sometimes have message errors. Traditional technologies cannot recognize the wrong messages and can only report errors, and cannot correct the errors in the request header. . In addition, the traditional technology modifies the early warning settings in aspects such as microservice invocation, etc., involving server container, load, network, etc., that is, the early warning settings are fixed on the server container, and it is difficult to adjust flexibly.

technical problem

The main purpose of this application is to provide an early warning method, device, computer equipment and storage medium for microservices based on a management platform, aiming to provide early warnings for microservices while realizing corrections to messages, so as to improve the usability of microservice messages And efficiency.

Technical solutions

In order to achieve the above-mentioned purpose of the invention, this application proposes a microservice early warning method based on a management platform, which includes the following steps:

Receive an invocation message for invoking a specified microservice with invocation information appended by the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes the service name of the specified microservice, At least one of the service URL address or service function;

Determine whether the specified communication protocol is the same as the preset communication protocol of the specified microservice;

If the specified communication protocol is the same as the preset communication protocol of the specified microservice, parse the call message according to the format of the specified communication protocol to obtain the call message header;

Using a preset similarity algorithm to calculate a similarity value between the call header and a preset standard call header, and determine whether the similarity value is greater than a preset similarity threshold;

If the similarity value is greater than the preset similarity threshold, replacing the invocation message header in the invocation message with the standard invocation message header, so as to obtain the replaced invocation message;

Acquiring, according to the invocation information, the number of times the designated microservice has been invoked within a predetermined time, and determining whether the number of invoked times is greater than a preset first warning number threshold;

If the number of calls is greater than the preset first warning number threshold, generate warning information, and send the warning information and the post-replacement call message to the designated microservice, and use the preset monitoring plug-in Add the specified microservice to the preset monitoring list.

This application provides a microservice early warning device based on a management platform, including:

The invocation message receiving unit is configured to receive an invocation message for invoking a specified microservice attached with invocation information from the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes all At least one of the service name, service URL address or service function of the specified microservice;

A communication protocol determining unit, configured to determine whether the designated communication protocol is the same as the preset communication protocol of the designated microservice;

A parsing unit, configured to parse the call message according to the format of the designated communication protocol if the designated communication protocol is the same as the preset communication protocol of the designated microservice, so as to obtain a header of the call message;

The similarity threshold judgment unit is used to calculate the similarity value between the calling message header and the preset standard calling message header by using a preset similarity algorithm, and to judge whether the similarity value is greater than the preset similarity Threshold

A replacement unit, configured to, if the similarity value is greater than a preset similarity threshold, replace the call message header in the call message with the standard call message header, so as to obtain a call message after replacement;

A called number determining unit, configured to obtain the called number of the designated microservice within a predetermined time according to the calling information, and determine whether the called number is greater than a preset first warning number threshold;

An early warning information generating unit, configured to generate early warning information if the number of calls is greater than a preset first warning number threshold, and send the early warning information and the post-replacement call message to the designated microservice, And use the preset monitoring plug-in to add the specified microservice to the preset monitoring list.

The present application provides a computer device including a memory and a processor, the memory stores a computer program, and the processor implements the steps of any one of the above methods when the computer program is executed.

The present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of any of the above methods are implemented.

Beneficial effect

The microservice early warning method, device, computer equipment, and storage medium based on the management platform of the present application receive a call message for calling a specified microservice with call information attached and sent by the first microservice; if the specified communication protocol is compatible with the If the preset communication protocol of the designated microservice is the same, the call header is obtained; the similarity value between the call header and the preset standard call header is calculated; if the similarity value is greater than the similarity threshold, then Replace the call message header with the standard call message header; if the number of calls is greater than the preset first warning times threshold, the warning information is generated, and the warning information and the replaced call message are sent to the Specify a microservice, and use a preset monitoring plug-in to add the specified microservice to the preset monitoring list. In this way, it can realize the correction of the message at the same time as the early warning of the microservice, so as to improve the availability and use efficiency of the microservice message.

Description of the drawings

FIG. 1 is a schematic flowchart of a microservice early warning method based on a management platform according to an embodiment of the application;

2 is a schematic block diagram of the structure of a microservice early warning device based on a management platform according to an embodiment of the application;

FIG. 3 is a schematic block diagram of the structure of a computer device according to an embodiment of the application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

The best mode of the invention

In order to make the purpose, technical solutions, and advantages of this application clearer, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the application, and not used to limit the application.

1, an embodiment of the present application provides a microservice early warning method based on a management platform, including the following steps:

S1. Receive an invocation message for invoking a specified microservice with invocation information appended by the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes the service of the specified microservice At least one of name, service URL address or service function;

S2. Determine whether the designated communication protocol is the same as the preset communication protocol of the designated microservice;

S3. If the designated communication protocol is the same as the preset communication protocol of the designated microservice, parse the call message according to the format of the designated communication protocol to obtain a call message header;

S4. Calculate the similarity value between the call header and the preset standard call header by using a preset similarity algorithm, and determine whether the similarity value is greater than a preset similarity threshold;

S5. If the similarity value is greater than the preset similarity threshold, replace the invocation message header in the invocation message with the standard invocation message header, so as to obtain the replaced invocation message;

S6. According to the invocation information, obtain the number of times the designated microservice is invoked within a predetermined time, and determine whether the number of times is greater than a preset first warning times threshold;

S7. If the number of calls is greater than the preset first warning number threshold, generate warning information, send the warning information and the post-replacement call message to the designated microservice, and use the preset The monitoring plug-in adds the specified microservice to the preset monitoring list.

As described in the above step S1, receiving an invocation message for invoking a specified microservice with invocation information appended by the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes the Specify at least one of the service name, service URL address, or service function of the microservice. Microservices are compared to monolithic applications (concentrating all functions in one application), decomposing an application into small, interconnected microservices. A microservice generally completes a specific function, and can also call or be called by other microservices to jointly complete all or part of the functions in an application. The management platform in this application refers to a platform that manages microservices, where management includes management in any feasible way, such as microservice registration, microservice discovery, gateway control, data monitoring, and so on. Among them, because this application manages the microservices through the management platform, the microservices do not need to expose too much information to the outside, and only need to expose one of the service name, service URL address, or service function. When the call message is With one of these pieces of information, the management platform can determine the accurate microservices from the stored correspondence table, which is not only more convenient, but also improves information security.

As described in step S2 above, it is determined whether the designated communication protocol is the same as the preset communication protocol of the designated microservice. If the designated communication protocol is different from the preset communication protocol of the designated microservice, it cannot be directly sent to the designated microservice according to the invocation request. Therefore, first determine whether the specified communication protocol is the same as the preset communication protocol of the specified microservice. Wherein determining whether the specified communication protocol is the same as the preset communication protocol of the specified microservice may be any manner, for example, including: determining whether the first microservice and the specified microservice belong to a preset microservice cluster; If the first microservice does not belong to the preset microservice cluster, and the specified microservice belongs to the preset microservice cluster, check whether the call request is legal according to the preset legality check rule; if said If the call request is legal, it is determined whether the communication protocol of the call request is the same as the preset communication protocol of the designated microservice. In order to determine whether it is necessary to switch between communication protocols.

As described in step S3 above, if the designated communication protocol is the same as the preset communication protocol of the designated microservice, the invocation message is parsed according to the format of the designated communication protocol to obtain the invocation message header. Generally speaking, a message consists of a message header and a message body. Different communication protocols have different message headers. For example, the format of the HTTP request message is: request line, request header (HTTP request message header, also known as HEADER) and request body. According to this, the call message is parsed according to the format of the designated communication protocol to obtain the call message header.

As described in step S4, the preset similarity algorithm is used to calculate the similarity value between the call header and the preset standard call header, and it is determined whether the similarity value is greater than the preset similarity threshold . In some situations, a small amount of errors may occur in the header of the message, such as partial character errors. For example, write Content-Type: application/json; charset=utf-8 error writes application/json; charset=utf-8 and so on. The traditional technology cannot identify the above-mentioned erroneous message headers, and thus performs a rejection operation. In this application, the correct message header is replaced with the wrong message header, thereby reducing network overhead and improving information transmission efficiency. Wherein, the standard calling message header can be retrieved from a preset message header library. The method of calculating the similarity value between the call message header and the preset standard call message header by using a preset similarity algorithm may adopt any algorithm, such as an overlapping word algorithm. According to this, no matter whether the calling message header is wrong or not, only the correct message header needs to be replaced.

As described in step S5 above, if the similarity value is greater than the preset similarity threshold, the call message header in the call message is replaced with the standard call message header, so as to obtain the replaced call message. Text. If the similarity value is greater than the preset similarity threshold, it indicates that the preset standard calling message header is the same as the calling message header, and the calling message header needs to be replaced with the preset standard Call message header, no matter whether the call message header is wrong, it will not affect the identification of the call message.

As described in step S6, the number of times the designated microservice is called within a predetermined time is obtained according to the invocation information, and it is determined whether the number of times is greater than the preset first warning times threshold. The invocation information includes at least one of the service name, service URL address, or service function of the designated microservice. The management platform of the present application can determine the designated microservice according to the invocation information, and can obtain the predetermined time The number of invocations of the designated microservice within, and determine whether the number of invocations is greater than a preset first warning number threshold to determine whether the designated microservice is in an abnormal state.

As described in step S7 above, if the number of times of being called is greater than the preset first warning number threshold, generating warning information, and sending the warning information and the post-replacement call message to the designated microservice, And use the preset monitoring plug-in to add the specified microservice to the preset monitoring list. If the number of calls is greater than the preset first warning threshold, it indicates that the designated microservice may be in an abnormal state, and the warning information is generated accordingly, and the designated microservice is added to the preset monitoring using the preset monitoring plug-in. List. The management platform of the present application adopts a monitoring stripping method, and realizes functions such as monitoring data embedding points through monitoring plug-ins, thereby avoiding affecting server containers, load, network and other aspects when the monitoring settings need to be adjusted. Wherein, adding the specified microservice to the preset monitoring list can be implemented by modifying the bytecode through java agent. Further, the method further includes: if the number of times of being called is greater than a preset second warning times threshold, rejecting the call message, wherein the second warning times threshold is greater than the first warning times threshold, and the abnormal situation The call application is processed in a hierarchical manner. When the number of calls is high but is still in a tolerable state (that is, the first warning threshold), the warning information will be generated, and the warning information and the post-replacement call message will be sent To the designated microservice, and use a preset monitoring plug-in to add the designated microservice to the preset monitoring list; when the number of calls is high but in an intolerable state (ie, the second warning threshold), Then the call message is rejected.

In one embodiment, before the step S2 of determining whether the designated communication protocol is the same as the preset communication protocol of the designated microservice, the method includes:

S11. Determine whether the first microservice and the designated microservice belong to the same microservice cluster;

S12. If the first microservice and the designated microservice do not belong to the same microservice cluster, determine whether the invocation message carries an identity token, wherein the identity token is the target of the management platform The identity authentication information generated by the first microservice;

S13. If the invocation message carries an identity token, determine whether the identity token carried in the invocation message has the authority to invoke the designated microservice according to the preset correspondence between the identity token and the authority;

S14. If the identity token carried in the invocation message has the authority to invoke the designated microservice, determine whether the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice;

S15. If the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice, a communication protocol determination instruction is generated, wherein the communication protocol determination instruction is used to instruct to determine whether the designated communication protocol and the designated Whether the preset communication protocols of the microservices are the same.

As described above, the generation of communication protocol judgment instructions is realized. In order to ensure the correct identification of the message, this application also adopts the method of determining whether the first microservice and the designated microservice belong to the same before determining whether the designated communication protocol is the same as the preset communication protocol of the designated microservice. Microservice cluster; determine whether the call message carries an identity token; determine whether the identity token carried in the call message has the authority to call the specified microservice; determine whether the call parameters of the call message are the same A multi-step judgment process that matches the predetermined parameters of the designated microservice to ensure that the call message has a basis for identification, and a communication protocol judgment instruction is generated on this basis. The process of pre-generating the identity token includes: the first microservice sends an identity authentication application to the management platform; the management platform sends and generates identity authentication information and sends it to the first microservice; the first microservice receives and saves the identity Token. The invocation parameter of the invocation request matches the predetermined parameter of the designated microservice, which means that the invocation parameter does not exceed the range specified by the predetermined parameter of the designated microservice, for example, the length of the storage field is within a predetermined range.

In one embodiment, if the designated communication protocol is the same as the preset communication protocol of the designated microservice, the call message is parsed according to the format of the designated communication protocol, so as to obtain the information of the call header Step S3 includes:

S301: If the designated communication protocol is the same as the preset communication protocol of the designated microservice, determine the position of the header in the call message according to the format of the preset designated communication protocol;

S302: Determine whether the content in the position of the message header conforms to a preset message header format;

S303. If the content in the position of the message header conforms to the preset format of the message header, extract the content in the position of the message header and record it as a call message header.

As mentioned above, the call header is obtained. The call message generally includes a message header and a message body. If the format of the message header does not match the format that the preset message does not have, the call message must not be recognized, and because the format does not match, Nor can it be corrected to determine the correct header. Therefore, this application adopts a scheme of first determining whether the content in the position of the message header conforms to the preset message header format. Among them, take the format of a communication protocol as an example: the format of the preset communication protocol is the request line, request header, and request body (for example, the format of the HTTP communication protocol), where the first line break exists between the request line and the request header, and the request There is a blank line between the header and the request body, for example. Only by finding the first newline character in the call message and the first blank line, the position of the message header in the call message can be determined. It is then judged whether the content in the position of the message header conforms to the preset message header format, for example, whether it has the format of Content-Type: [type]/[subtype]; parameter.

In one embodiment, the preset similarity algorithm is used to calculate the similarity value between the call message header and the preset standard call message header, and to determine whether the similarity value is greater than the preset similarity Step S4 of the threshold includes:

S401, adopt the formula:

Calculate the similarity value between the calling message header and the preset standard calling message header; where A is the character frequency vector of the calling message header, and B is the character frequency vector of the preset standard calling message header , Ai and Bi are the i-th component vector of the vectors A and B, and n is the value of the component vector with the largest number of component vectors in the vectors A and B, and it is determined whether the similarity value is greater than a preset Similarity threshold.

As described above, it is achieved that the preset similarity algorithm is used to calculate the similarity value between the call header and the preset standard call header, and to determine whether the similarity value is greater than the preset similarity threshold. Wherein, the cosine similarity calculation method is used to calculate the similarity value between the call message header and the preset standard call message header. Wherein, the character frequency vector of the call message header refers to the number of times the characters in the call message header appear. For example, the character frequency vector of Content is (1,1,2,2,1), that is, except for n and t appearing twice, other characters only appear once, where (1,1,2,2,1) The 2 is the sub-vector of characters n and t. Therefore, the cosine similarity calculation method is used to calculate the similarity value between the call message header and the preset standard call message header. Further, the calculating the similarity value between the calling message header and the preset standard calling message header by using the preset similarity algorithm, and determining whether the similarity value is greater than the preset similarity threshold further includes : Use a preset similarity algorithm to calculate the similarity value between the call message header and multiple preset standard call message headers, so as to obtain multiple similarity values, and determine which of the multiple similarity values Whether the maximum value is greater than the preset similarity threshold; if the maximum value of the multiple similarity values is greater than the preset similarity threshold, then the maximum value of the multiple similarity values corresponds to the standard call header As the correct call header.

In one embodiment, before the step S6 of acquiring the number of times the designated microservice has been invoked within a predetermined time according to the invocation information, and determining whether the number of invocations is greater than a preset first warning number threshold, include:

S51. Execute an identification command for the call message after the replacement;

S52: Determine whether an error is reported in the process of executing the recognition command;

S53. If no error is reported during the execution of the recognition command, an early warning judgment instruction is generated, where the early warning judgment instruction is used to instruct to obtain the number of times the designated microservice has been called within a predetermined time according to the calling information, and judge Whether the number of times of being called is greater than a preset first warning number threshold.

As mentioned above, the recognition command is executed to determine whether the replaced call message is correct. Although the call message has been replaced, in order to further ensure the recognizability of the call message, this application also executes the identification command of the call message after the replacement; it is judged whether the process of executing the identification command reports an error Way to ensure that the call message can be correctly identified. Accordingly, if the process of executing the recognition command does not report an error, an early warning judgment instruction is generated, where the early warning judgment instruction is used to instruct to obtain the number of times the designated microservice has been called within a predetermined time according to the calling information, and It is determined whether the number of times of being called is greater than a preset first warning number threshold.

In one embodiment, after the step S6 of obtaining the number of times of the designated microservice within a predetermined time according to the invocation information, and determining whether the number of times is greater than a preset first warning number threshold, include:

S61. If the number of times of being called is not greater than the preset first warning number threshold, collect the traffic data of the designated microservice within a predetermined time, and determine whether the distribution of the traffic data over time is within the preset traffic data Distribution range

S62. If the distribution of the flow data over time is within a preset flow data distribution range, send the call message after replacement to the designated microservice.

As described above, it is achieved that the post-replacement invocation message is sent to the designated microservice. The abnormal state of a designated microservice may be related to factors such as time. Therefore, only judging the number of calls within a predetermined period of time may lead to inaccurate judgment. Based on this, statistics on the traffic data of the designated microservice within the predetermined period of time are used to determine the traffic data Whether the time-varying distribution is within the preset flow data distribution range is used to determine whether the flow data of the specified microservice is normal. If the distribution of the flow data over time is within the preset flow data distribution range, it indicates that there is no abnormality in the flow data, so the call message after replacement is sent to the designated microservice. Wherein, the flow data distribution range can be set in any manner, for example, set to the actual value of the flow data of the previous period multiplied by (-M%, +M%), where M is greater than zero.

In one embodiment, if the number of calls is greater than a preset first warning number threshold, generating warning information, and sending the warning information and the call message after replacement to the designated microservice , And use the preset monitoring plug-in to add the specified microservice to the preset monitoring list. Step S7 includes:

S701: If the number of times of being called is greater than a preset first warning number threshold, generate warning information, and send the warning information and the post-replacement call message to the designated microservice;

S702. Use a preset monitoring plug-in based on java agent technology to modify the bytecode to add a data embedding point at the communication port of the specified microservice, so as to add the specified microservice to the preset monitoring list.

As described above, it is achieved that the early warning information and the post-replacement call message are sent to the designated microservice, and the designated microservice is added to the preset monitoring list using a preset monitoring plug-in. The java agent technology is a computer system packaged in a certain environment based on the java language. In order to achieve the design purpose, it can be flexible and autonomous in this environment. When the code is changed in the ordinary way, a manual restart is required to take effect, but because the java agent technology frees some functions of Java from the local code, only a partial restart is required, which is equivalent to only reloading the modified code, thus avoiding the traditional The defect in the technology that all the specified microservices have to be restarted when they are added to the preset monitoring list. The monitoring plug-in based on java agent technology refers to the monitoring plug-in implemented by java agent, which realizes the monitoring stripping. When the monitoring list needs to be adjusted, only the bytecode of the java agent is modified, and only a partial restart is required.

The microservice early warning method based on the management platform of the present application receives an invocation message for invoking a specified microservice with invoking information appended by the first microservice; if the specified communication protocol is the preset communication protocol of the specified microservice Are the same, get the call message header; calculate the similarity value between the call message header and the preset standard call message header; if the similarity value is greater than the similarity threshold, replace the call message header with the standard Call message header; if the number of calls is greater than the preset first warning times threshold, generate warning information, and send the warning information and the call message after replacement to the designated microservice, and use the preset The monitoring plug-in for adding the specified microservice to the preset monitoring list. In this way, it can realize the correction of the message at the same time as the early warning of the microservice, so as to improve the availability and use efficiency of the microservice message.

Referring to Figure 2, an embodiment of the present application provides a microservice early warning device based on a management platform, including:

The invocation message receiving unit 10 is configured to receive an invocation message for invoking a specified microservice attached with invocation information sent by the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes At least one of the service name, service URL address, or service function of the designated microservice;

The communication protocol determining unit 20 is configured to determine whether the designated communication protocol is the same as the preset communication protocol of the designated microservice;

The parsing unit 30 is configured to parse the call message according to the format of the designated communication protocol if the designated communication protocol is the same as the preset communication protocol of the designated microservice, so as to obtain the header of the call message;

The similarity threshold judging unit 40 is configured to calculate the similarity value between the call message header and the preset standard call message header by using a preset similarity algorithm, and determine whether the similarity value is greater than the preset similarity Degree threshold

The replacement unit 50 is configured to, if the similarity value is greater than a preset similarity threshold, replace the call message header in the call message with the standard call message header, so as to obtain the call message after replacement ；

The called number determining unit 60 is configured to obtain the called number of the designated microservice within a predetermined time according to the calling information, and determine whether the called number is greater than a preset first warning number threshold;

The early warning information generating unit 70 is configured to generate early warning information if the number of calls is greater than a preset first warning number threshold, and send the early warning information and the post-replacement call message to the designated microservice , And use the preset monitoring plug-in to add the specified microservice to the preset monitoring list.

The operations performed by the above-mentioned units respectively correspond to the steps of the microservice early warning method based on the management platform of the foregoing embodiment, and will not be repeated here.

In one embodiment, the device includes:

A microservice cluster judging unit, configured to judge whether the first microservice and the specified microservice belong to the same microservice cluster;

The identity token judging unit is configured to, if the first microservice and the designated microservice do not belong to the same microservice cluster, judge whether the invocation message carries an identity token, wherein the identity token is Identity authentication information generated by the management platform for the first microservice;

The authority judgment unit is configured to determine whether the identity token carried in the call message has the ability to call the designated microservice according to the preset correspondence between the identity token and the authority if the call message carries an identity token permission;

A parameter matching judgment unit, configured to determine whether the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice if the identity token carried in the invocation message has the authority to invoke the designated microservice ；

The judgment instruction generating unit is configured to generate a communication protocol judgment instruction if the invocation parameter of the invocation message matches the predetermined parameter of the specified microservice, wherein the communication protocol judgment instruction is used to instruct to judge the specified communication Whether the protocol is the same as the preset communication protocol of the designated microservice.

In one embodiment, the parsing unit 30 includes:

The message header position determining subunit is configured to determine the message in the call message according to the format of the preset designated communication protocol if the designated communication protocol is the same as the preset communication protocol of the designated microservice Head position

A format judging subunit for judging whether the content in the position of the message header conforms to the preset message header format;

The calling message header marking subunit is used to extract the content in the position of the message header if the content in the position of the message header conforms to the format of the preset message header, and record it as a calling message head.

The operations performed by the above-mentioned sub-units respectively correspond to the steps of the microservice early warning method based on the management platform of the foregoing embodiment, and will not be repeated here.

In one embodiment, the similarity threshold judgment unit 40 includes:

The similarity threshold judgment subunit is used to adopt the formula:

In one embodiment, the device includes:

An identification command execution unit, configured to execute an identification command for the call message after the replacement;

An error judgment unit, configured to judge whether an error is reported during the execution of the identification command;

An early warning judgment instruction generating unit, configured to generate an early warning judgment instruction if no error is reported in the process of executing the recognition command, wherein the early warning judgment instruction is used to instruct to obtain the specified microservice information within a predetermined time according to the call information And determine whether the number of calls is greater than the preset first warning number threshold.

In one embodiment, the device includes:

The flow data judging unit is configured to, if the number of times of being called is not greater than the preset first warning number threshold, collect the flow data of the designated microservice within a predetermined time, and judge whether the distribution of the flow data over time is in Within the preset flow data distribution range;

The call message sending unit is configured to send the replaced call message to the designated microservice if the distribution of the flow data over time is within a preset flow data distribution range.

In one embodiment, the warning information generating unit 70 includes:

An early warning information generating subunit, configured to generate early warning information if the number of calls is greater than a preset first warning number threshold, and send the early warning information and the call message after replacement to the designated microservice ；

The monitoring list add subunit is used to modify the bytecode by using a preset monitoring plug-in based on java agent technology to add a data embedding point at the communication port of the specified microservice, thereby adding the specified microservice to the preset Set the monitoring list.

The microservice early warning device based on the management platform of the present application receives the invocation message for invoking a specified microservice with invoking information appended by the first microservice; if the specified communication protocol is the preset communication protocol of the specified microservice Are the same, get the call message header; calculate the similarity value between the call message header and the preset standard call message header; if the similarity value is greater than the similarity threshold, replace the call message header with the standard Call message header; if the number of calls is greater than the preset first warning times threshold, generate warning information, and send the warning information and the call message after replacement to the designated microservice, and use the preset The monitoring plug-in for adding the specified microservice to the preset monitoring list. In this way, it can realize the correction of the message at the same time as the early warning of the microservice, so as to improve the availability and use efficiency of the microservice message.

Referring to FIG. 3, an embodiment of the present invention also provides a computer device. The computer device may be a server, and its internal structure may be as shown in the figure. The computer equipment includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the computer designed processor is used to provide calculation 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 memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer equipment is used to store the data used in the microservice early warning method based on the management platform. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer program is executed by the processor to realize a microservice early warning method based on the management platform.

The above-mentioned processor executes the above-mentioned microservice early warning method based on the management platform, wherein the steps included in the method respectively correspond to the steps of executing the microservice early warning method based on the management platform of the foregoing embodiment, and will not be repeated here.

Those skilled in the art can understand that the structure shown in the figure is only a block diagram of a part of the 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.

An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, a microservice warning method based on a management platform is implemented, wherein the steps included in the method are respectively the same as those in the foregoing The steps of the microservice early warning method based on the management platform of the implementation manner correspond to each other, and will not be repeated here.

Claims

A microservice early warning method based on a management platform is characterized in that it includes:

Receive an invocation message for invoking a specified microservice with invocation information appended by the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes the service name of the specified microservice, At least one of the service URL address or service function;

Determine whether the specified communication protocol is the same as the preset communication protocol of the specified microservice;

If the specified communication protocol is the same as the preset communication protocol of the specified microservice, parse the call message according to the format of the specified communication protocol to obtain the call message header;

Using a preset similarity algorithm to calculate a similarity value between the call header and a preset standard call header, and determine whether the similarity value is greater than a preset similarity threshold;

If the similarity value is greater than the preset similarity threshold, replacing the invocation message header in the invocation message with the standard invocation message header, so as to obtain the replaced invocation message;

Acquiring, according to the invocation information, the number of times the designated microservice has been invoked within a predetermined time, and determining whether the number of invoked times is greater than a preset first warning number threshold;

If the number of calls is greater than the preset first warning number threshold, generate warning information, and send the warning information and the post-replacement call message to the designated microservice, and use the preset monitoring plug-in Add the specified microservice to the preset monitoring list.
The microservice early warning method based on a management platform according to claim 1, wherein before the step of determining whether the designated communication protocol is the same as the preset communication protocol of the designated microservice, the method comprises:

Determining whether the first microservice and the designated microservice belong to the same microservice cluster;

If the first microservice and the designated microservice do not belong to the same microservice cluster, then it is determined whether the invocation message carries an identity token, where the identity token is the management platform’s response to the first microservice cluster. Identity authentication information generated by a microservice;

If the invocation message carries an identity token, determining whether the identity token carried in the invocation message has the authority to invoke the designated microservice according to the preset correspondence between the identity token and the authority;

If the identity token carried in the invocation message has the authority to invoke the designated microservice, determining whether the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice;

If the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice, a communication protocol determination instruction is generated, wherein the communication protocol determination instruction is used to instruct to determine whether the designated communication protocol and the designated microservice Whether the preset communication protocol is the same.
The micro-service early warning method based on the management platform of claim 1, wherein if the designated communication protocol is the same as the preset communication protocol of the designated micro-service, according to the format of the designated communication protocol The step of parsing the call message to obtain the call message header includes:

If the designated communication protocol is the same as the preset communication protocol of the designated microservice, determine the position of the message header in the call message according to the format of the preset designated communication protocol;

Judging whether the content in the position of the message header conforms to the preset message header format;

If the content in the position of the message header conforms to the format of the preset message header, the content in the position of the message header is extracted and recorded as the calling message header.
The microservice early warning method based on the management platform according to claim 1, wherein the preset similarity algorithm is used to calculate the similarity value between the call header and the preset standard call header, and And the step of determining whether the similarity value is greater than a preset similarity threshold includes:

Use the formula:

Calculate the similarity value between the calling message header and the preset standard calling message header; where A is the character frequency vector of the calling message header, and B is the character frequency vector of the preset standard calling message header , Ai and Bi are the i-th component vector of the vectors A and B, and n is the value of the component vector with the largest number of component vectors in the vectors A and B, and it is determined whether the similarity value is greater than a preset Similarity threshold.
The microservice early warning method based on the management platform of claim 1, wherein the number of calls of the designated microservice within a predetermined time is obtained according to the call information, and it is determined whether the number of calls is Before the step that is greater than the preset first warning times threshold, it includes:

Execute an identification command for the call message after the replacement;

Determine whether an error is reported in the process of executing the recognition command;

If no error is reported in the process of executing the recognition command, an early warning judgment instruction is generated, where the early warning judgment instruction is used to instruct to obtain the number of times the designated microservice has been called within a predetermined time according to the call information, and determine the Whether the number of calls is greater than the preset first warning number threshold.
The microservice early warning method based on the management platform of claim 1, wherein the number of calls of the designated microservice within a predetermined time is obtained according to the call information, and it is determined whether the number of calls is After the step greater than the preset threshold of the first warning times, it includes:

If the number of calls is not greater than the preset first warning threshold, then the traffic data of the designated microservice within the predetermined time is counted, and it is determined whether the distribution of the traffic data over time is within the preset traffic data distribution range Inside;

If the distribution of the flow data over time is within a preset flow data distribution range, the call message after replacement is sent to the designated microservice.
The microservice early warning method based on the management platform according to claim 1, wherein if the number of calls is greater than a preset first warning threshold, the early warning information is generated, and the early warning information is combined with The step of sending the call message after the replacement to the designated microservice and adding the designated microservice to the preset monitoring list using a preset monitoring plug-in includes:

If the number of calls is greater than the preset first warning number threshold, generating warning information, and sending the warning information and the post-replacement call message to the designated microservice;

A preset monitoring plug-in based on java agent technology is used to modify the bytecode to add a data embedding point at the communication port of the specified microservice, thereby adding the specified microservice to the preset monitoring list.
A microservice early warning device based on a management platform is characterized in that it comprises:

The invocation message receiving unit is configured to receive an invocation message for invoking a specified microservice attached with invocation information from the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes all At least one of the service name, service URL address or service function of the specified microservice;

A communication protocol determining unit, configured to determine whether the designated communication protocol is the same as the preset communication protocol of the designated microservice;

A parsing unit, configured to parse the call message according to the format of the designated communication protocol if the designated communication protocol is the same as the preset communication protocol of the designated microservice, so as to obtain a header of the call message;

The similarity threshold judgment unit is used to calculate the similarity value between the calling message header and the preset standard calling message header by using a preset similarity algorithm, and to judge whether the similarity value is greater than the preset similarity Threshold

A replacement unit, configured to, if the similarity value is greater than a preset similarity threshold, replace the call message header in the call message with the standard call message header, so as to obtain a call message after replacement;

A called number determining unit, configured to obtain the called number of the designated microservice within a predetermined time according to the calling information, and determine whether the called number is greater than a preset first warning number threshold;

An early warning information generating unit, configured to generate early warning information if the number of calls is greater than a preset first warning number threshold, and send the early warning information and the post-replacement call message to the designated microservice, And use the preset monitoring plug-in to add the specified microservice to the preset monitoring list.
The microservice early warning device based on a management platform according to claim 8, wherein the device comprises:

A microservice cluster judging unit, configured to judge whether the first microservice and the specified microservice belong to the same microservice cluster;

The identity token judging unit is configured to, if the first microservice and the designated microservice do not belong to the same microservice cluster, judge whether the invocation message carries an identity token, wherein the identity token is Identity authentication information generated by the management platform for the first microservice;

The authority judgment unit is configured to determine whether the identity token carried in the call message has the ability to call the designated microservice according to the preset correspondence between the identity token and the authority if the call message carries an identity token permission;

A parameter matching judgment unit, configured to determine whether the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice if the identity token carried in the invocation message has the authority to invoke the designated microservice ；

The judgment instruction generating unit is configured to generate a communication protocol judgment instruction if the invocation parameter of the invocation message matches the predetermined parameter of the specified microservice, wherein the communication protocol judgment instruction is used to instruct to judge the specified communication Whether the protocol is the same as the preset communication protocol of the designated microservice.
The microservice early warning device based on the management platform of claim 8, wherein the analysis unit comprises:

The message header position determining subunit is configured to determine the message in the call message according to the format of the preset designated communication protocol if the designated communication protocol is the same as the preset communication protocol of the designated microservice Head position

A format judging subunit for judging whether the content in the position of the message header conforms to the preset message header format;

The calling message header marking subunit is used to extract the content in the position of the message header if the content in the position of the message header conforms to the format of the preset message header, and record it as a calling message head.
The microservice early warning device based on the management platform according to claim 8, wherein the similarity threshold judgment unit comprises:

The similarity threshold judgment subunit is used to adopt the formula:

Calculate the similarity value between the calling message header and the preset standard calling message header; where A is the character frequency vector of the calling message header, and B is the character frequency vector of the preset standard calling message header , Ai and Bi are the i-th component vector of the vectors A and B, and n is the value of the component vector with the largest number of component vectors in the vectors A and B, and it is determined whether the similarity value is greater than a preset Similarity threshold.
The microservice early warning device based on a management platform according to claim 8, wherein the device comprises:

An identification command execution unit, configured to execute an identification command for the call message after the replacement;

An error judgment unit, configured to judge whether an error is reported during the execution of the identification command;

An early warning judgment instruction generating unit, configured to generate an early warning judgment instruction if no error is reported in the process of executing the recognition command, wherein the early warning judgment instruction is used to instruct to obtain the specified microservice information within a predetermined time according to the call information And determine whether the number of calls is greater than the preset first warning number threshold.
The microservice early warning device based on a management platform according to claim 8, wherein the device comprises:

The flow data judging unit is configured to, if the number of times of being called is not greater than the preset first warning number threshold, collect the flow data of the designated microservice within a predetermined time, and judge whether the distribution of the flow data over time is in Within the preset flow data distribution range;

The call message sending unit is configured to send the replaced call message to the designated microservice if the distribution of the flow data over time is within a preset flow data distribution range.
The microservice early warning device based on the management platform of claim 8, wherein the early warning information generating unit comprises:

An early warning information generating subunit, configured to generate early warning information if the number of calls is greater than a preset first warning number threshold, and send the early warning information and the call message after replacement to the designated microservice ；

The monitoring list add subunit is used to modify the bytecode by using a preset monitoring plug-in based on java agent technology to add data embedding points at the communication port of the specified microservice, thereby adding the specified microservice to the preset Set the monitoring list.
A computer device includes a memory and a processor, the memory stores a computer program, and is characterized in that, when the processor executes the computer program, a management platform-based microservice early warning method is implemented, and the management platform-based microservice Service warning methods, including:

Receive an invocation message for invoking a specified microservice with invocation information appended by the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes the service name of the specified microservice, At least one of the service URL address or service function;

Determine whether the specified communication protocol is the same as the preset communication protocol of the specified microservice;

If the specified communication protocol is the same as the preset communication protocol of the specified microservice, parse the call message according to the format of the specified communication protocol to obtain the call message header;

Using a preset similarity algorithm to calculate a similarity value between the call header and a preset standard call header, and determine whether the similarity value is greater than a preset similarity threshold;

If the similarity value is greater than the preset similarity threshold, replacing the invocation message header in the invocation message with the standard invocation message header, so as to obtain the replaced invocation message;

Acquiring, according to the invocation information, the number of times the designated microservice has been invoked within a predetermined time, and determining whether the number of invoked times is greater than a preset first warning number threshold;

If the number of calls is greater than the preset first warning number threshold, generate warning information, and send the warning information and the post-replacement call message to the designated microservice, and use the preset monitoring plug-in Add the specified microservice to the preset monitoring list.
The computer device according to claim 15, wherein before the step of determining whether the designated communication protocol is the same as the preset communication protocol of the designated microservice, the method comprises:

Determining whether the first microservice and the designated microservice belong to the same microservice cluster;

If the first microservice and the designated microservice do not belong to the same microservice cluster, then it is determined whether the invocation message carries an identity token, where the identity token is the management platform’s response to the first microservice cluster. Identity authentication information generated by a microservice;

If the invocation message carries an identity token, determining whether the identity token carried in the invocation message has the authority to invoke the designated microservice according to the preset correspondence between the identity token and the authority;

If the identity token carried in the invocation message has the authority to invoke the designated microservice, determining whether the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice;

If the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice, a communication protocol determination instruction is generated, wherein the communication protocol determination instruction is used to instruct to determine whether the designated communication protocol and the designated microservice Whether the preset communication protocol is the same.
The computer device according to claim 15, wherein if the specified communication protocol is the same as the preset communication protocol of the specified microservice, the call message is parsed according to the format of the specified communication protocol , So as to obtain the steps of calling the message header, including:

If the designated communication protocol is the same as the preset communication protocol of the designated microservice, determine the position of the message header in the call message according to the format of the preset designated communication protocol;

Judging whether the content in the position of the message header conforms to the preset message header format;

If the content in the position of the message header conforms to the format of the preset message header, the content in the position of the message header is extracted and recorded as the calling message header.
A computer-readable storage medium with a computer program stored thereon, wherein the computer program implements a management platform-based microservice early warning method when the computer program is executed by a processor, and the management platform-based microservice early warning method includes :

Receive an invocation message for invoking a specified microservice with invocation information appended by the first microservice, wherein the invocation message is encapsulated based on a specified communication protocol, and the invocation information includes the service name of the specified microservice, At least one of the service URL address or service function;

Determine whether the specified communication protocol is the same as the preset communication protocol of the specified microservice;

If the specified communication protocol is the same as the preset communication protocol of the specified microservice, parse the call message according to the format of the specified communication protocol to obtain the call message header;

Using a preset similarity algorithm to calculate a similarity value between the call header and a preset standard call header, and determine whether the similarity value is greater than a preset similarity threshold;

If the similarity value is greater than the preset similarity threshold, replacing the invocation message header in the invocation message with the standard invocation message header, so as to obtain the replaced invocation message;

Acquiring, according to the invocation information, the number of times the designated microservice has been invoked within a predetermined time, and determining whether the number of invoked times is greater than a preset first warning number threshold;

If the number of calls is greater than the preset first warning number threshold, generate warning information, and send the warning information and the post-replacement call message to the designated microservice, and use the preset monitoring plug-in Add the specified microservice to the preset monitoring list.
The computer-readable storage medium according to claim 18, wherein before the step of judging whether the designated communication protocol is the same as the preset communication protocol of the designated microservice, it comprises:

Determining whether the first microservice and the designated microservice belong to the same microservice cluster;

If the first microservice and the designated microservice do not belong to the same microservice cluster, then it is determined whether the invocation message carries an identity token, where the identity token is the management platform’s response to the first microservice cluster. Identity authentication information generated by a microservice;

If the invocation message carries an identity token, determining whether the identity token carried in the invocation message has the authority to invoke the designated microservice according to the preset correspondence between the identity token and the authority;

If the identity token carried in the invocation message has the authority to invoke the designated microservice, determining whether the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice;

If the invocation parameter of the invocation message matches the predetermined parameter of the designated microservice, a communication protocol determination instruction is generated, wherein the communication protocol determination instruction is used to instruct to determine whether the designated communication protocol and the designated microservice Whether the preset communication protocol is the same.
The computer-readable storage medium according to claim 18, wherein if the specified communication protocol is the same as the preset communication protocol of the specified microservice, then the specified communication protocol is parsed according to the format of the specified communication protocol. The steps of calling the message to obtain the header of the calling message include:

If the designated communication protocol is the same as the preset communication protocol of the designated microservice, determine the position of the message header in the call message according to the format of the preset designated communication protocol;

Judging whether the content in the position of the message header conforms to the preset message header format;

If the content in the position of the message header conforms to the format of the preset message header, the content in the position of the message header is extracted and recorded as the calling message header.