Communication management method, terminal equipment and storage medium

Abstract

The invention relates to the technical field of communication, and particularly provides a communication management method, which is used for improving the efficiency of positioning performance bottlenecks and faults in a micro-service architecture, and is applied to terminal equipment, the terminal equipment is provided with a first micro-service, and the terminal equipment executes the communication management method based on the first micro-service. The first micro-service is in communication connection with a plurality of second micro-services through a distributed mechanism, the distributed mechanism comprises a plurality of information themes, the second micro-services are used for uploading information data to the distributed mechanism, and the distributed mechanism distributes the information data to the information themes; the communication management method comprises the steps that information data on a target information theme is acquired, the target information theme is any one or more of multiple information themes, and the information data comprises a tracking label and a sender label; acquiring a subscription relationship between the target information theme and the second micro-service; and generating communication link data corresponding to the plurality of second micro-services according to the tracking tag, the sender tag and the subscription relationship.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication management method, terminal equipment and storage medium. Background Art

[0002] With the development of communication technology, microservice architecture for software development has emerged. The software consists of small independent microservices that communicate with well-defined APIs. When using the microservice architecture, each independent application is run as a microservice. These microservices are built around business functions, and each service performs a function. This can improve the speed and scalability of software development. In the microservice architecture, a business request may need to go through multiple different microservices to complete. Since each microservice is responsible for different business functions, the call relationship and call time of each microservice are different. As the complexity of business functions increases, the number of microservices required is also increasing, which can easily lead to performance bottlenecks in some microservices, or make it difficult to quickly locate faulty microservices, resulting in a decrease in the overall operating efficiency of the software. Summary of the invention

[0003] The main purpose of this application is to provide a communication management method, a terminal device and a storage medium for managing the communication process between multiple microservices to improve the performance bottleneck and fault location efficiency of the microservice architecture.

[0004] In a first aspect, an embodiment of the present application provides a communication management method, which is applied to a terminal device, wherein the terminal device is installed with a first microservice, and the terminal device executes the communication management method based on the first microservice, wherein the first microservice is communicatively connected with multiple second microservices through a distributed mechanism, wherein the distributed mechanism includes multiple information topics, and the second microservice is used to upload information data to the distributed mechanism, and the distributed mechanism assigns the information data to the information topic; the communication management method includes:

[0005] Acquire information data on a target information subject, the target information subject being any one or more of the plurality of information subjects, the information data including a tracking tag and a sender tag;

[0006] Obtaining a subscription relationship between the target information topic and the second microservice;

[0007] Generate a plurality of communication link data corresponding to the second microservices according to the tracking tag, the sender tag, and the subscription relationship.

[0008] In a second aspect, an embodiment of the present application provides a terminal device, comprising a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for implementing a connection and communication between the processor and the memory, wherein the program, when executed by the processor, implements the steps of a communication management method as described in any one of the embodiments of the present application.

[0009] In a third aspect, an embodiment of the present application provides a storage medium for computer-readable storage, wherein the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of a communication management method as described in any one of the embodiments of the present application.

[0010] The embodiment of the present application provides a communication management method, which is applied to a terminal device, the terminal device is installed with a first microservice, the terminal device executes the communication management method based on the first microservice, the first microservice communicates with multiple second microservices through a distributed mechanism, the distributed mechanism includes multiple information topics, the second microservice is used to upload information data to the distributed mechanism, and the distributed mechanism assigns the information data to the information topic; the communication management method includes: obtaining information data on a target information topic, the target information topic is any one or more of multiple information topics, and the information data includes a tracking tag and a sender tag; obtaining a subscription relationship between the target information topic and the second microservice; according to the tracking tag, the sender tag and the subscription relationship, generating communication link data corresponding to multiple second microservices. In the above process, the second microservices participating in the business function are determined, and the communication link data between the second microservices are obtained. The communication link data is used to display the communication link between the second microservices, which enables managers to quickly determine the communication failure between the microservices to improve the performance bottleneck of the microservice structure and the efficiency of locating the failure. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 It is a schematic diagram of a microservice architecture provided in an embodiment of the present application;

[0012] Figure 2 is a schematic flow chart of a communication management method provided in an embodiment of the present application;

[0013] Figure 3 is a schematic diagram of a communication process provided by an embodiment of the present application;

[0014] Figure 4 is a schematic diagram of a message list provided in an embodiment of the present application;

[0015] Figure 5 is a schematic diagram of communication link data provided by an embodiment of the present application;

[0016] Figure 6 is a schematic diagram of a message list provided in an embodiment of the present application;

[0017] Figure 7 is a schematic diagram of communication time data provided by an embodiment of the present application;

[0018] Figure 8 is a schematic diagram of communication link data provided by an embodiment of the present application;

[0019] Fig. 9 is a schematic diagram of communication time data provided by an embodiment of the present application;

[0020] Fig.10 It is a structural block diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the heat dissipation device and base station equipment provided by the present disclosure are described in detail below in conjunction with the accompanying drawings.

[0022] Example embodiments will be described more fully below with reference to the accompanying drawings, but the example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. On the contrary, the purpose of providing these embodiments is to make the present disclosure thorough and complete and to enable those skilled in the art to fully understand the scope of the present disclosure.

[0023] In the absence of conflict, the various embodiments of the present disclosure and the various features therein may be combined with each other.

[0024] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0025] The terms used herein are only used to describe specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a", "an" and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, the presence of the features, wholes, steps, operations, elements and / or components is specified, but the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof is not excluded.

[0026] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless explicitly defined as such herein.

[0027] In an embodiment of the present application, the distributed mechanism includes a message bus (Message Bus) and database communication. Message buses include: Kafka, RabbitMQ and ActiveMQ. Some databases also implement Pub / Sub functions similar to message buses, that is, the sender (Pub) sends messages and the subscriber (sub) receives messages. These databases include: Redis, Cassandra and Etcd, among which Redis provides some message queue functions, such as publish / subscribe, list blocking, etc. Cassandra supports asynchronous information transmission and has reliability and persistence. Etcd is a distributed key-value storage system that can implement Pub / Sub-like functions through Watch operations.

[0028] In the embodiment of the present application, the subject managed by the communication management method is a microservice. In actual applications, it is not limited to microservices. The subject can also be any process, program (app), software module, etc. As long as they use the distributed mechanism in the embodiment of the present application to transmit information, the technical solution of the present application is applicable.

[0029] Based on the distributed mechanism in the embodiment of the present application, for example, the distributed mechanism is a message bus. When a process or microservice needs to send information, it first publishes the information to the message bus. The message bus routes the information to one or more processes or microservices that have subscribed to the information. This method can realize multiple communication modes such as broadcast, point-to-point, publish / subscribe, etc., and is suitable for complex asynchronous communication scenarios in distributed mechanisms.

[0030] In a microservice architecture, multiple microservices communicate through a distributed mechanism, and each microservice is responsible for different business functions to realize business requests as a whole. As the complexity of business functions increases, it is easy to cause performance bottlenecks in some microservices. If the faulty microservice cannot be quickly located, the overall operating efficiency of the microservice architecture will decrease.

[0031] The embodiment of the present application provides a communication management method, which is applied to a terminal device. The terminal device is installed with a first microservice, and the terminal device executes the communication management method based on the first microservice.

[0032] See also Figure 1 , Figure 1 A schematic diagram of a microservice architecture provided by an embodiment of the present application is shown. Figure 1As shown, the first microservice M communicates with multiple second microservices (A, B, C, D and E) through a distributed mechanism, the distributed mechanism is a message bus, the message bus includes multiple information topics, the second microservice is used to upload information data to the distributed mechanism, the distributed mechanism assigns the information data to the information topic, and the second microservice receives the corresponding information data from the subscribed information topic. The first microservice M subscribes to all information topics in the microservice architecture.

[0033] It should be noted that when the first microservice M subscribes to an information topic, the second microservice (sender and / or receiver) corresponding to the information topic needs to grant relevant information acquisition permissions to ensure that the information data obtained by the first microservice from the information topic is reasonable and legal.

[0034] See also Figure 2 , Figure 2 A schematic flow chart of a communication management method provided by an embodiment of the present application is shown. Figure 2 As shown, the specific steps of the communication management method include: S101-S103.

[0035] S101. Acquire information data on a target information topic, where the target information topic is any one or more of a plurality of information topics, and the information data includes a tracking tag and a sender tag.

[0036] For example, Figure 1 As shown, the first microservice M and multiple second microservices (A, B, C, D and E) form a microservice architecture through a message bus, and the microservice architecture serves the same functional theme. Based on the functional theme, each second microservice subscribes to one or more target information topics (Topic) on the message bus. For example, the second microservice A subscribes to Topic 1, the second microservice B subscribes to information topic 2, the second microservice C subscribes to Topic 3 and Topic 4, and the first microservice M subscribes to all target information topics (Topic 1-5). That is, the first microservice M can receive information data on all target information topics.

[0037] The second microservice uploads the information data to the message bus. Before uploading, the second microservice also adds a tracking tag, a sender tag, and an information subject tag to the information data, wherein the tracking tag is used to identify the functional subject to which the information data belongs, the sender tag is used to identify the identity of the sender of the information data, and the information subject tag is used to indicate the information subject receiving the information data. After receiving the information data, the message bus assigns the corresponding information data to the corresponding target information subject according to the information subject tag.

[0038] S102: Obtain a subscription relationship between the target information topic and the second microservice.

[0039] Exemplarily, the same target information topic can be subscribed to by one or more second microservices. When the target information topic is subscribed to by the second microservice, a subscription relationship exists between the target information topic and the second microservice. The subscription relationship can be recorded in a Json file and stored in a database for easy calling by a terminal device.

[0040] S103: Generate communication link data corresponding to multiple second microservices according to the tracking tag, the sender tag, and the subscription relationship.

[0041] Exemplarily, based on the first microservice, the terminal device reads the sender tag in the information data, and determines the second microservice that sends the information data according to the sender tag. After the information data is sent, the message bus distributes the information data to the target information topic, and determines the second microservice that receives the information data according to the subscription relationship between the target information topic and the second microservice. The second microservice that receives the information data and the second microservice that sends the information serve as communication nodes. The communication relationship between multiple second microservices can also be determined based on the sender tag and the subscription relationship. In the communication relationship, if any two microservices communicate with each other, there is a communication link between the two microservices. Thus, the communication link data corresponding to multiple microservices can be determined based on the communication nodes and the communication links. Since the above-mentioned multiple second microservices belong to the same microservice architecture and serve the same functional theme, the communication link data is named by tracking tags so that users can quickly find them.

[0042] The communication link data is used to locate performance bottlenecks or faults in the microservice architecture. For example, after a preset time, if a communication link is still not detected between two second microservices that have a communication relationship, it means that a communication anomaly is detected between the two microservices and intervention and improvement are required.

[0043] After collecting the communication link data, the first microservice can output it to information data collectors such as Zipkin, Jaeger and SkyWalking, so that the information data can be further processed in the information data collector. The first microservice can also directly output the communication link data as graphical data for users to monitor whether there are any abnormalities in the information flow.

[0044] In the above process, the second microservices involved in the business function are determined, and the communication link data between the second microservices are obtained. The communication link data is used to display the communication link between the second microservices, which enables managers to quickly determine the communication failure between the microservices, so as to improve the performance bottleneck of the microservice architecture and the efficiency of locating faults.

[0045] Through the communication management method provided in the embodiment of the present application, when implementing the management of information data, there is no need to make too many changes to the second microservice. It is only necessary to add tracking tags and publisher tags to the information data. The changes are small, easy to apply, and convenient for the first microservice to read and manage. At the same time, the first microservice can be turned on and off without affecting the communication between the second microservice, and the scope of information management can be modified by modifying the subscribed information topic.

[0046] In order to more clearly introduce the technical solution of the present application, the technical solution of the present application will be introduced through a specific embodiment below. It should be noted that the specific embodiment is used to expand the technical solution of the present application, but is not intended to limit the present application.

[0047] In some embodiments, communication link data corresponding to multiple second microservices are generated according to the tracking tag, the sender tag, and the subscription relationship, including: determining the communication relationship between multiple target second microservices and multiple target second microservices according to the sender tag and the subscription relationship, the target second microservice is the second microservice for communication; generating communication link data according to the target second microservice and the communication relationship, and naming the communication link data using the tracking tag.

[0048] For example, see Figure 3 , Figure 3 A schematic diagram of a communication process provided by an embodiment of the present application is shown. A communication event is initiated from the second microservice A. To complete the communication event, follow the steps below: Figure 3 The second microservices B, C, D and E are notified in the order shown, and the tracking tag of the information data generated during the process is 123abc. The second microservices A, B, C, D and E all send information data to the corresponding Topics, and the information data sent to the Topic is sent to the subscribers of the Topic. For example, Topic-3 is subscribed by the second microservice C and the second microservice D. When the second microservice B sends Msg-2 to Topic-3, the second microservice C and the second microservice D both receive Msg-2. The first microservice subscribes to all Topics in the above communication process and fully records the communication events that occurred in the above communication process, forming the following: Figure 4 A list of messages is shown.

[0049] See also Figure 4 , Figure 4 A schematic diagram of a message list provided in an embodiment of the present application is shown. Figure 4As shown, the sender of the information data is determined according to the sender tag, and the sender is the second microservice A, B, C, D, E, D and B. The receiver of the information data can be determined according to the subscription relationship, and the receiver is the second microservice B, C, D, B, E, D, B and A. The second microservice included in the sender and the receiver is the target second microservice, and the target second microservice includes the second microservice A, B, C, D and E. On this basis, it can also be determined that the target second microservice A and B, the target second microservice B and C, the target second microservice B and D, and the target second microservice D and E have communicated with each other, that is, there is a communication relationship between each of the above two target second microservices, that is, there is a communication link. Therefore, the communication link data can be determined according to the target second microservice A, B, C, D and E, and according to the communication relationship between the target second microservice A, B, C, D and E.

[0050] See also Figure 5 , Figure 5 A schematic diagram of a communication link data provided by an embodiment of the present application is shown. Figure 5 As shown, the communication link data is a tree diagram, and the nodes of the tree diagram are the target second microservices A, B, C, D and E. The communication link is represented by a line segment with an arrow, and the arrow indicates the direction of the information flow. If, in the process of monitoring the tree diagram, it is detected that no communication link is generated between two target second microservices that have a communication relationship, it can be quickly determined that a performance bottleneck or communication failure has occurred between the two target second microservices. As a result, the performance bottleneck or communication failure between multiple target second microservices can be intuitively displayed to the user, so that the user can follow up and eliminate it, thereby improving the efficiency of locating communication failures in the microservice architecture.

[0051] In some embodiments, the communication management method further includes: obtaining the publishing time of the information data; and generating communication time data corresponding to multiple second terminals according to the publishing time, the tracking tag, the sender tag and the subscription relationship.

[0052] It should be noted that the publishing time may be the sending time of the information data sent by the second microservice, and the sending time is based on the local time of the second microservice. Before sending the information data, the second microservice adds a time tag to the information data, and the time tag is used to record the publishing time of the information data. The publishing time may also be the receiving time when the first microservice receives the information data. If the first microservice does not detect that the information data includes a time tag after receiving the information data, the receiving time is used as the publishing time of the information data.

[0053] By monitoring the release time, it is possible to monitor the time required for communication between every two second microservices that have a communication relationship. This time can more intuitively show the performance bottleneck in the communication process to the user.

[0054] In some embodiments, communication time data corresponding to multiple second microservices are generated according to the publishing time, tracking tags, sender tags and subscription relationships, including: determining multiple target second microservices according to the sender tags and subscription relationships, and determining every two target second microservices for communication, where the target second microservices are multiple second microservices for communication; determining the communication time between every two target second microservices for communication according to the publishing time; determining the communication time data according to the target second microservices and the communication time, and naming the communication time data using the tracking tags.

[0055] In such Figure 3 Based on the communication process shown, the first microservice also obtains the release time of the information data and obtains the following Figure 6 A list of messages is shown.

[0056] See also Figure 6 , Figure 6 A schematic diagram of a message list provided in an embodiment of the present application is shown. Figure 6 As shown, the first microservice can determine that the target second microservices are second microservices A, B, C, D and E, and determine that there are communication relationships (Msg-1-AB, Msg-1-BC, Msg-1-BD and Msg-1-DE) between the target second microservices A and B, the target second microservices B and C, the target second microservices B and D, and the target second microservices D and E. The first microservice can determine the communication time between each two target second microservices that communicate based on the communication relationship and the release time. For example, the time difference between the release time of Msg-1-ack and the release time of Msg-1 is used as the communication time between the target second microservices A and B, and the communication time data is determined based on the target second microservices and the communication time.

[0057] See also Figure 7 , Figure 7 A schematic diagram of communication time data provided by an embodiment of the present application is shown. Figure 7 As shown, the communication time data is displayed through a bar graph, with the release time as the time node of the time axis, and the communication duration of each two target second microservices communicating is represented by the length of the column, and the two ends of the column correspond to the time node. If, in the process of monitoring the bar graph, it is detected that the length of the column exceeds the corresponding preset threshold, it can be considered that a performance bottleneck has occurred between the target second microservices corresponding to the column. In this way, the performance bottleneck or communication failure between multiple target second microservices can be intuitively displayed to the user, so that the user can follow up and eliminate it, thereby improving the efficiency of locating communication failures in the microservice architecture.

[0058] In addition, the bar chart can also reflect to the user the overall time required to complete communication between each two target second microservices. The longer time is the performance bottleneck in the microservice architecture. Therefore, the user can be reminded to perform performance tuning between the two target second microservices with longer time.

[0059] In some embodiments, the information data also includes multiple span tags, and the span tags are used to distinguish multiple groups of information data sent by the second microservice to another second microservice; based on the tracking tag, the sender tag and the subscription relationship, communication link data corresponding to the multiple second microservices are generated, including: based on the tracking tag, the sender tag, the subscription relationship and the span tag, communication link data corresponding to the multiple second terminals are generated, and the communication link data includes multiple groups of communication links, and each group of communication links corresponds to a span tag.

[0060] Exemplarily, when the second microservice sends information data, it also adds multiple span tags to the information data. The span tags are used to distinguish multiple groups of information data of different spans under the same functional theme. For example, the target second microservice sends Msg-1 and Msg-10 to the target second microservice B respectively. The target second microservice A adds span tag 001 to Msg-1 and adds span tag 002 to Msg-10. When the target second microservice B replies to Msg-1 and Msg-10, it also adds span tag 001 to Msg-1-ack and adds span tag 002 to Msg-10-ack. In this way, it is beneficial for the first microservice to determine the corresponding relationship between Msg-1, Msg-10, Msg-1-ack and Msg-10-ack according to the span tags when receiving them. Based on the span tags, the first microservice can distinguish multiple groups of information data and generate a corresponding set of communication links according to each group of information data. In this way, the direction of information flow in the microservice architecture can be better monitored.

[0061] In some embodiments, communication link data corresponding to multiple second microservices are generated according to the tracking tag, the sender tag, the subscription relationship, and the span tag, including: determining the communication relationship between the target second microservice and multiple target second microservices according to the sender tag and the subscription relationship, where the target second microservice is multiple second microservices for communication; determining multiple groups of communication links according to the span tag, the target second microservice, and the communication relationship; determining the communication link data according to the communication link, and naming the communication link using the tracking tag.

[0062] Exemplarily, according to the tracking tag, the sender tag and the subscription relationship, multiple communication links corresponding to the target second microservices are generated. The process has been described in detail above and will not be repeated here. If there are multiple groups of information data, a group of communication links is generated according to each group of information data. If multiple groups of information data are transmitted during the communication process of multiple second microservices, multiple groups of communication links can be generated based on the multiple groups of information data. Since each group of information data corresponds to a span tag, the communication links are displayed in different forms according to different span tags.

[0063] See also Figure 8 , Figure 8 A schematic diagram of a communication link data provided by an embodiment of the present application is shown. Figure 8 As shown, the communication link data is a tree diagram, and the nodes of the tree diagram are the target second microservices A, B, C, D and E. The communication links of the first group are represented by solid lines with arrows, and the communication links of the second group are represented by dashed lines with arrows. In this way, two different groups of communication links can be simply and directly distinguished. When multiple groups of information data exist in the same functional theme at the same time, it can help users locate the second microservice with performance bottlenecks and the faulty information flow more quickly.

[0064] In some embodiments, the information data also includes multiple span tags, and the span tags are used to distinguish multiple groups of information data sent by the second microservice to another second microservice. The communication management method also includes: generating communication time data corresponding to multiple second microservices according to the publishing time, tracking tag, sender tag, subscription relationship and span tag, and the communication time data includes multiple groups of communication time, and each group of communication time corresponds to a span tag.

[0065] Based on the span tag, the first microservice can distinguish multiple groups of information data and generate a corresponding set of communication time according to each group of information data. In this way, the communication time required for different information flows in the microservice architecture can be better monitored.

[0066] In some embodiments, communication time data corresponding to multiple second microservices are generated according to the publishing time, tracking tags, sender tags, subscription relationships, and span tags, including: determining multiple target second microservices according to the sender tags and subscription relationships, and determining every two target second microservices for communication, where the target second microservices are multiple second microservices for communication; determining multiple groups of communication times between every two target second microservices for communication according to the span tags and the publishing time; determining the communication time data according to the target second microservices and the communication time, and naming the communication time data using the tracking tags.

[0067] Exemplarily, communication time data corresponding to multiple second terminals are generated according to the publishing time, tracking tag, sender tag and subscription relationship. The process has been described in detail above and will not be repeated here. If there are multiple groups of information data, a group of communication time is generated according to each group of information data. If multiple groups of information data are transmitted during the communication process of multiple second microservices, multiple groups of communication time can be generated based on the multiple groups of information data. Since each group of information data corresponds to a span tag, the communication time is displayed in different forms according to different span tags.

[0068] See also Fig. 9 , Fig. 9 A schematic diagram of communication time data provided by an embodiment of the present application is shown. Fig. 9 As shown, the communication link data is a bar graph, the nodes of the bar graph are the target second microservices A, B, C, D and E, the release time is the time node of the time axis, the communication time of the first group is represented by a solid bar, and the communication time of the second group is represented by a shaded bar, and the two ends of the bar correspond to the time node. In this way, two different groups of communication time can be distinguished simply and directly. When there are multiple groups of information data in the same functional theme at the same time, it can help users locate the second microservice with performance bottleneck and the faulty information flow more quickly.

[0069] See also Fig.10 , Fig.10 The following figure shows a structural block diagram of a terminal device. Fig.10 As shown, an embodiment of the present application proposes a terminal device 20, which includes a memory 21, a processor 22, a program stored in the memory and executable on the processor, and a data bus 23 for realizing connection communication between the processor 21 and the memory 22. When the program is executed by the processor, the steps of the communication management method as described in any one of the embodiments of the present application are realized.

[0070] Specifically, for example, the following Figure 2 The specific steps shown are: obtaining information data on a target information topic, where the target information topic is any one or more of a plurality of information topics, and the information data includes a tracking tag and a sender tag; obtaining a subscription relationship between the target information topic and a second microservice; and generating communication link data corresponding to a plurality of second microservices according to the tracking tag, the sender tag and the subscription relationship.

[0071] In some embodiments, when the processor 22 is used to generate communication link data corresponding to multiple second microservices according to the tracking tag, the sender tag and the subscription relationship, it is specifically used to implement: determining the communication relationship between multiple target second microservices and multiple target second microservices according to the sender tag and the subscription relationship, the target second microservice is the second microservice for communication; generating communication link data according to the target second microservice and the communication relationship, and naming the communication link data using the tracking tag.

[0072] In some embodiments, the processor 22 is further configured to: obtain the publishing time of the information data; and generate communication time data corresponding to the plurality of second terminals according to the publishing time, the tracking tag, the sender tag and the subscription relationship.

[0073] In some embodiments, when the processor 22 is used to generate communication time data corresponding to multiple second microservices according to the publishing time, tracking tags, sender tags and subscription relationships, it is specifically used to implement: determining multiple target second microservices according to the sender tags and subscription relationships, and determining every two target second microservices for communication, where the target second microservices are multiple second microservices for communication; determining the communication time between every two target second microservices for communication according to the publishing time; determining the communication time data according to the target second microservice and the communication time, and naming the communication time data using the tracking tag.

[0074] In some embodiments, when the processor 22 is used to generate communication link data corresponding to multiple second microservices according to the tracking tag, the sender tag, and the subscription relationship, it is specifically used to implement: generating communication link data corresponding to multiple second terminals according to the tracking tag, the sender tag, the subscription relationship, and the span tag, the communication link data including multiple groups of communication links, each group of communication links corresponding to a span tag.

[0075] In some embodiments, when the processor 22 is used to generate communication link data corresponding to multiple second microservices according to the tracking tag, the sender tag, the subscription relationship and the span tag, it is specifically used to implement: determining the communication relationship between the target second microservice and multiple target second microservices according to the sender tag and the subscription relationship, where the target second microservice is multiple second microservices for communication; determining multiple groups of communication links according to the span tag, the target second microservice and the communication relationship; determining the communication link data according to the communication link, and naming the communication link using the tracking tag.

[0076] In some embodiments, the processor 22 is also used to generate communication time data corresponding to multiple second microservices according to the publishing time, tracking tag, sender tag, subscription relationship and span tag, and the communication time data includes multiple groups of communication time, and each group of communication time corresponds to a span tag.

[0077] In some embodiments, when the processor 22 is used to generate communication time data corresponding to multiple second microservices according to the release time, tracking tag, sender tag, subscription relationship and span tag, it is also specifically used to implement: determining multiple target second microservices according to the sender tag and the subscription relationship, and determining every two target second microservices for communication, the target second microservice is a plurality of second microservices for communication; determining multiple groups of communication time between every two target second microservices for communication according to the span tag and the release time; determining the communication time data according to the target second microservice and the communication time, and naming the communication time data using the tracking tag.

[0078] An embodiment of the present application provides a storage medium for computer-readable storage, wherein the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of any communication management method provided in the embodiment of the present application.

[0079] The preferred embodiments of the present application are described above with reference to the accompanying drawings, but the scope of the present application is not limited thereby. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present application shall be within the scope of the present application.

Claims

1. A communication management method, characterized in that: Applied to a terminal device, the terminal device is installed with a first microservice, the terminal device executes the communication management method based on the first microservice, the first microservice is connected to communicate with multiple second microservices through a distributed mechanism, the distributed mechanism includes multiple information topics, the second microservice is used to upload information data to the distributed mechanism, and the distributed mechanism distributes the information data to the information topics; The communication management method comprises: Acquire information data on a target information subject, the target information subject being any one or more of the plurality of information subjects, the information data including a tracking tag and a sender tag; Obtaining a subscription relationship between the target information topic and the second microservice; Generate a plurality of communication link data corresponding to the second microservices according to the tracking tag, the sender tag, and the subscription relationship.

2. The communication management method according to claim 1, characterized in that: The generating a plurality of communication link data corresponding to the second microservice according to the tracking tag, the sender tag and the subscription relationship includes: Determine, according to the sender tag and the subscription relationship, a communication relationship between a plurality of target second microservices and a plurality of the target second microservices, the target second microservice being the second microservice for communication; The communication link data is generated according to the target second microservice and the communication relationship, and the communication link data is named using the tracking tag.

3. The communication management method according to claim 1, characterized in that: The communication management method further includes: Obtaining the release time of the information data; Communication time data corresponding to a plurality of second terminals are generated according to the publishing time, the tracking tag, the sender tag and the subscription relationship.

4. The communication management method according to claim 3, characterized in that: The generating, according to the publishing time, the tracking tag, the sender tag and the subscription relationship, a plurality of communication time data corresponding to the second microservices includes: Determine a plurality of target second microservices according to the sender tag and the subscription relationship, and determine every two of the target second microservices for communication, wherein the target second microservices are the plurality of the second microservices for communication; Determine the communication time between each two of the target second microservices that are communicating according to the publishing time; The communication time data is determined according to the target second microservice and the communication time, and the communication time data is named using the tracking tag.

5. The communication management method according to claim 1, characterized in that: The information data further includes a plurality of span tags, where the span tags are used to distinguish a plurality of groups of the information data sent by the second microservice to another second microservice; The generating a plurality of communication link data corresponding to the second microservice according to the tracking tag, the sender tag and the subscription relationship includes: Communication link data corresponding to a plurality of the second terminals are generated according to the tracking tag, the sender tag, the subscription relationship and the span tag, wherein the communication link data includes a plurality of groups of communication links, and each group of the communication links corresponds to one span tag.

6. The communication management method according to claim 5, characterized in that: The generating a plurality of communication link data corresponding to the second microservice according to the tracking tag, the sender tag, the subscription relationship and the span tag includes: Determine, according to the sender tag and the subscription relationship, a communication relationship between a target second microservice and a plurality of the target second microservices, wherein the target second microservice is a plurality of the second microservices that are communicating; Determine a plurality of groups of the communication links according to the span label, the target second microservice and the communication relationship; The communication link data is determined based on the communication link, and the communication link is named using the tracking tag.

7. The communication management method according to claim 3, characterized in that: The information data further includes a plurality of span tags, and the span tags are used to distinguish a plurality of groups of information data sent by the second microservice to another second microservice. The communication management method further includes: According to the publishing time, the tracking tag, the sender tag, the subscription relationship and the span tag, a plurality of communication time data corresponding to the second microservices are generated, wherein the communication time data includes a plurality of groups of communication times, and each group of the communication time corresponds to one span tag.

8. The communication management method according to claim 7, characterized in that: The generating, according to the publishing time, the tracking tag, the sender tag, the subscription relationship and the span tag, a plurality of communication time data corresponding to the second microservices includes: Determine a plurality of target second microservices according to the sender tag and the subscription relationship, and determine every two of the target second microservices for communication, wherein the target second microservices are the plurality of the second microservices for communication; Determine, according to the span tag and the release time, a plurality of groups of communication times between each two of the target second microservices that are communicating; The communication time data is determined according to the target second microservice and the communication time, and the communication time data is named using the tracking tag.

9. A terminal device, characterized in that: It includes a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection communication between the processor and the memory, wherein the program, when executed by the processor, realizes the steps of the communication management method as described in any one of claims 1 to 8.

10. A storage medium for computer-readable storage, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the communication management method according to any one of claims 1-8.

Images