Connection status monitoring method, device, equipment and storage medium

Abstract

The present invention provides a connection status monitoring method, apparatus, equipment and storage medium, which, based on interface metadata, sends an interface detection request to the corresponding interface of a subsystem at intervals of a first predetermined time; receives interface call status information fed back by the subsystem in response to the interface detection request, and obtains an interface detection result between a local interface and the corresponding interface of the subsystem based on the interface call status information; the interface detection result represents the connection status between the local interface and the corresponding interface of the subsystem; based on the interface detection result, displays the connection status between the local interface and the corresponding interface of the subsystem in an expected connection diagram; since the interface metadata includes the connection data between the local interface and the corresponding interface, the main system can send a connection detection request to the corresponding interface of the subsystem, thereby realizing connection detection between different microservice systems and being able to efficiently obtain the connection status between different microservice systems.

Description

Technical Field

[0001] Embodiments of the present invention relate to the fields of communications and Internet technology, and in particular to a connection status monitoring method, apparatus, device, and storage medium. Background Art

[0002] In the existing technology, monitoring solutions for microservice systems include: dubbo (open source distributed service framework monitoring) or service health monitoring. However, open source distributed service framework monitoring and service health monitoring both monitor the internal connection status of the microservice system.

[0003] Since different microservice systems may have different structures, existing monitoring solutions for microservice systems cannot monitor the connection status between different microservice systems. As a result, it is difficult to monitor the connection status between different microservice systems in real time. Summary of the Invention

[0004] The embodiments of the present invention provide a connection status monitoring method, device, and storage medium that can efficiently obtain the connection status between different microservice systems.

[0005] The embodiment of the present invention is implemented as follows:

[0006] An embodiment of the present invention provides a connection status monitoring method, which is applied to a main system device, including:

[0007] Loading interface metadata, and constructing an expected connection graph between the local interface and the corresponding interface of the subsystem based on the interface metadata; the interface metadata represents the connection data between the local interface and the corresponding interface of the subsystem;

[0008] Based on the interface metadata, sending an interface detection request to the interface corresponding to the subsystem at a first predetermined interval; the interface detection request is used to retrieve interface call status information of the interface corresponding to the subsystem;

[0009] receiving the interface call status information fed back by the subsystem in response to the interface detection request, and obtaining an interface detection result between the local interface and the corresponding interface of the subsystem based on the interface call status information; wherein the interface detection result represents a connection status between the local interface and the corresponding interface of the subsystem;

[0010] Based on the interface detection result, the connection status between the local interface and the corresponding interface of the subsystem is displayed in the expected connection diagram for monitoring.

[0011] An embodiment of the present invention further provides a connection status monitoring method, which is applied to a subsystem device and includes:

[0012] Receiving an interface detection request sent by a host system based on interface metadata; the interface metadata represents connection data between a local interface of the host system and a corresponding interface;

[0013] In response to the interface detection request, interface detection data is fed back to the main system.

[0014] An embodiment of the present invention further provides a connection status monitoring method, which is applied to a central system device, comprising:

[0015] Receive connection status information corresponding to a key interface sent by at least one main system, and information on a call status of a local microservice external interface corresponding to the at least one main system; the key interface represents an interface for a preset key business;

[0016] Based on the connection status information corresponding to the key interface and the local microservice external interface call status information, a connection status diagram of each main system is constructed for display.

[0017] An embodiment of the present invention further provides a connection status monitoring device, comprising:

[0018] A loading unit, configured to load interface metadata and construct an expected connection graph between the local interface and the corresponding interface of the subsystem based on the interface metadata; the interface metadata represents connection data between the local interface and the corresponding interface of the subsystem;

[0019] A first sending unit is configured to send an interface detection request to the interface corresponding to the subsystem at a first predetermined interval based on the interface metadata; the interface detection request is used to retrieve interface call status information of the interface corresponding to the subsystem;

[0020] a first receiving unit, configured to receive interface call status information fed back by the subsystem in response to the interface detection request, and obtain an interface detection result between the local interface and the interface corresponding to the subsystem based on the interface call status information; the interface detection result represents a connection status between the local interface and the interface corresponding to the subsystem;

[0021] A processing unit is configured to update, in the expected connection diagram, a connection status between the local interface and a corresponding interface of the secondary system based on the interface detection result, for monitoring.

[0022] An embodiment of the present invention further provides a connection status monitoring device, comprising:

[0023] A second receiving unit is configured to receive an interface detection request sent by the main system based on interface metadata; the interface metadata represents connection data between the local interface of the main system and the corresponding interface;

[0024] The second sending unit is configured to respond to the interface detection request and feed back interface detection data to the main system.

[0025] An embodiment of the present invention further provides a connection status monitoring device, comprising:

[0026] The third receiving unit is configured to receive connection status information corresponding to a key interface and corresponding local microservice external interface call status information sent by at least one main system;

[0027] A graph construction unit is used to construct a connection status graph of each of the main systems for display based on the connection status information corresponding to the multiple key interfaces and the call status information of the microservice external interface.

[0028] An embodiment of the present invention further provides a system monitoring device, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and the processor implements the steps in the above method when executing the program.

[0029] An embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which implements the steps in the above method when executed by a processor.

[0030] In an embodiment of the present invention, interface metadata is loaded, and an expected connection diagram between a local interface and a corresponding interface of a subsystem is constructed based on the interface metadata; an interface detection request is sent to the corresponding interface of the subsystem at a first predetermined interval based on the interface metadata; interface detection data fed back by the subsystem in response to the interface detection request is received, and the interface detection data is analyzed to obtain an interface detection result between the local interface and the corresponding interface of the subsystem; the interface detection result represents the connection status between the local interface and the corresponding interface of the subsystem; based on the interface detection result, the connection status between the local interface and the corresponding interface of the subsystem is displayed in the expected connection diagram for monitoring. Since the interface metadata includes the connection data between the local interface and the corresponding interface, the main system can send a connection detection request to the corresponding interface of the subsystem, thereby realizing connection detection between different microservice systems and efficiently obtaining the connection status between different microservice systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A system structure diagram of a connection status monitoring method provided by an embodiment of the present invention;

[0032] Figure 2 An optional flow chart of a connection status monitoring method provided in an embodiment of the present invention;

[0033] Figure 3 A schematic diagram of an optional effect of the connection status monitoring method provided by an embodiment of the present invention;

[0034] Figure 4 A schematic diagram of an optional effect of the connection status monitoring method provided by an embodiment of the present invention;

[0035] Figure 5 An optional flow chart of a connection status monitoring method provided in an embodiment of the present invention;

[0036] Figure 6 An optional flow chart of a connection status monitoring method provided in an embodiment of the present invention;

[0037] Figure 7 An interaction diagram of the connection status monitoring method provided by an embodiment of the present invention;

[0038] Figure 8 A schematic diagram of the structure of the connection status monitoring device provided by the embodiment of the present invention Figure 1 ;

[0039] Figure 9 A schematic diagram of the structure of the connection status monitoring device provided by the embodiment of the present invention Figure 2 ;

[0040] Figure 10 A schematic diagram of the structure of the connection status monitoring device provided by the embodiment of the present invention Figure 3 ;

[0041] Figure 11 A schematic diagram of a hardware entity of a connection status monitoring device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0042] See also Figure 1 , which is a system structure diagram of the connection status monitoring method provided by an embodiment of the present invention.

[0043] In this embodiment of the present invention, the overall system cluster includes a central system, as well as System A 2, System B 3, and System C 4, all connected to Central System 1. Central System 1, System A 2, System B 3, and System C 4 can each be connected to their own local systems. The local systems connected to Central System 1 include the support system and the complaint system; the local systems connected to System A 2 include System 1 and System 2; the local systems connected to System B 3 include the performance system and the operation and maintenance system; and the local systems connected to System C 4 include the resource system and the alarm system.

[0044] It should be noted that system A 2, system B 3, and system C 4 all include their own corresponding system microservices. The system microservices corresponding to system A may include: a governance microservice cluster 5, a business microservice cluster 6, a public microservice cluster 7, a docking microservice cluster 9, and a monitoring microservice cluster 8. In an embodiment of the present invention, the governance microservice cluster 5 is used to process registration services, configuration services, and entry gateway services. The business microservice cluster 6 is used to process business services 1, 2, 3 to n. The public microservice cluster 7 is used to process authentication services, user services, and message services. The docking microservice cluster 9 is used to process interface registration services, interface call services, interface provision services, and egress gateway services.

[0045] The monitoring microservice cluster 8 can include an internal microservice monitoring service and an external interface monitoring microservice. The internal microservice monitoring service, as an independent monitoring service within System A, is primarily responsible for monitoring the status of each microservice within System A. Commonly used monitoring tools include distributed system performance monitoring tools, link tracing tools, and distributed tracing and monitoring tools. The external interface monitoring microservice, as a microservice within System A, is responsible for monitoring the interaction between System A and other systems, as well as other local systems. This monitoring aspect of the external interface monitoring microservice relies on the docking microservice cluster. Furthermore, the docking microservice cluster 9 is also monitored by the internal microservice monitoring service as a microservice within the system.

[0046] In the embodiment of the present invention, since the system structures of the central system 1, system A 2, system B 3, and system C 4 may be different from each other, in order to realize the connection status monitoring among the central system, system A, system B, and system C, the connection status monitoring method provided in the embodiment of the present invention is to load interface metadata through any one of system A 2, system B 3, and system C 4. Since the interface metadata includes relevant information such as the identifier, path information, and message between the local interface and the corresponding interface, the main system can send a connection detection request to the corresponding interface of the secondary system, thereby realizing the connection detection between different microservice systems and efficiently obtaining the connection status between different microservice systems.

[0047] Figure 2 An optional flow chart of the connection status monitoring method provided by the embodiment of the present invention is applied to the main system device, which is combined with Figure 2 The steps shown are explained.

[0048] S101: Load interface metadata, and construct an expected connection graph between a local interface and a corresponding interface of a subsystem based on the interface metadata.

[0049] In an embodiment of the present invention, any one of system A, system B, and system C is the primary system. Other systems connected to the primary system are secondary systems. In an embodiment of the present invention, the primary system loads interface metadata from a third-party database into the cache of the primary system. The monitoring microservice cluster and the export gateway service in the primary system both load interface metadata. The interface metadata represents the connection data between the local interface of the primary system and the corresponding interface of the secondary system. After the primary system loads the interface metadata, the primary system constructs an expected connection graph between the local interface and the corresponding interface based on the connection data in the interface metadata.

[0050] Interface metadata may include: interface identifiers of the local interface and the corresponding interface, initiator information, receiver information, interface path information, call method information, input parameter simulation message, output parameter message, connection type between the local interface and the corresponding interface, interface status information, etc. It should be noted that the input parameter simulation message is used by operators to manually detect the connection information between certain specified interfaces in the main system. The output parameter message is used to detect the interface connection information between multiple microservice clusters within the main system.

[0051] In embodiments of the present invention, the secondary system may be a monitoring system connected to the primary system for monitoring other services. The communication connection between the primary system and the secondary system may be achieved by establishing a communication connection between a local interface of the primary system and a corresponding interface of the secondary system. Interface metadata represents the connection data between the local interface and the corresponding interface of the secondary system.

[0052] In the embodiment of the present invention, the expected connection diagram represents the connection status diagram between the local interface of the corresponding main system and the corresponding interface of the secondary system. The staff of the main system can monitor the connection status between the local interface and the secondary system through the connection status between the local interface and the corresponding interface shown in the expected connection diagram. The expected connection diagram can be a star diagram or a tree diagram. Figure 3 , which is an optional flow diagram of the connection status monitoring method provided by an embodiment of the present invention. Here, the primary system is System A, and the secondary systems are the local system and the central system. System A establishes connections between the local interface and the local system's user details query interface and conference creation interface based on interface metadata. System A also establishes connections between the local interface and the central system's work order status synchronization interface and performance information query interface. Furthermore, System A can construct a desired connection diagram with the local system and the central system.

[0053] In an embodiment of the present invention, before loading interface metadata into the primary system, an operator can construct interface metadata corresponding to the primary system based on the relevant data between the primary system's local interface and the corresponding interface of the secondary system, and store the interface metadata in a third-party database.

[0054] S102: Based on the interface metadata, send an interface detection request to the corresponding interface of the secondary system at a first predetermined time interval.

[0055] In this embodiment of the present invention, the primary system sends interface detection requests to multiple secondary systems based on relevant data in the interface metadata. The interface detection requests retrieve information about the interface call status of the corresponding interfaces of the secondary systems. The interface detection requests can also be used to detect the port connectivity and network status between the primary and secondary systems.

[0056] In an embodiment of the present invention, a primary system can send an interface detection request to the corresponding interfaces of multiple secondary systems based on interface metadata. The interface detection request is used to detect the connection between a local interface and the corresponding interface of a secondary system. If the primary system detects that the connection between the local interface and the corresponding interface of the secondary system is abnormal, the primary system will send a port detection request to the multiple secondary systems. The secondary systems will feedback port detection data in response to their own port detection requests. The primary system analyzes the port detection data and determines that the port connection between the primary system and the secondary system is abnormal. The primary system will then continue to detect the network connection between the primary system and the secondary system.

[0057] In an embodiment of the present invention, when the main system sends an interface detection request to multiple sub-systems, the main system configures the interface identifier of the corresponding interface, the receiver information of the corresponding interface, and the interface path information of the corresponding interface to the corresponding sub-systems sent in the interface detection request.

[0058] In the embodiment of the present invention, combined with Figure 1 The external interface monitoring microservice of the primary system sends the interface detection request to the external interface monitoring microservice of the corresponding secondary system through the docking microservice cluster 9. The secondary system responds to the interface detection request and sends the interface detection data to the primary system through its own egress gateway service.

[0059] S103: Receive the interface call status information fed back by the subsystem in response to the interface detection request, and obtain the interface detection result between the local interface and the corresponding interface of the subsystem according to the interface call status information.

[0060] In an embodiment of the present invention, after a primary system sends an interface detection request to multiple secondary systems, the multiple secondary systems respond to their respective interface detection requests and feed back interface call status information to the primary system. The primary system receives the interface call status information sent by the secondary systems. The primary system analyzes the interface detection results between the primary system and the secondary systems based on the multiple connection statuses between the primary system and the secondary systems in the interface call status information.

[0061] In an embodiment of the present invention, a primary system may send an interface detection request to multiple secondary systems. The multiple secondary systems respond to their respective interface detection requests and feed back corresponding interface call status information to the primary system. After receiving the interface call status information from the secondary systems, the primary system analyzes the ratio of the number of successful connections between the local interface and the corresponding interface of the secondary system to the total number of successful connections in the interface call status information to obtain an interface detection result between the local interface and the corresponding interface of the secondary system.

[0062] The interface call status information may include information such as the number of communications between the local interface and the corresponding interface, the number of successful communications, and the number of failed communications.

[0063] S104 : Based on the interface detection result, the connection status between the local interface and the corresponding interface of the secondary system is displayed in the expected connection diagram for monitoring.

[0064] In the embodiment of the present invention, the main system displays the detection result on the connection line between the local interface of the main system and the corresponding interface of the corresponding secondary system in the expected connection diagram to facilitate monitoring by staff.

[0065] In an embodiment of the present invention, the primary system may also pre-assign preset colors to different interface detection results. Based on the preset colors corresponding to the different interface detection results, the primary system constructs connection lines between the primary system's local interfaces and the corresponding interfaces of the secondary systems in the expected connection diagram. For example, red indicates an abnormal detection result, while green indicates a normal detection result.

[0066] In this embodiment of the present invention, the primary system analyzes and obtains the interface test results between the local interface and the corresponding interface of the secondary system. Based on the preset color corresponding to the interface test results, the primary system constructs a connection line between the local interface and the corresponding interface of the secondary system in the expected connection diagram. The primary system also displays the interface test results as text information on the side of the corresponding connection line.

[0067] For example, combined Figure 3 , System A 2 analyzed and obtained that the interface detection result of the interface for querying household details with the local system 10 is that the policy is not valid, then System A 2 constructs the corresponding connection line through the red line in the expected connection diagram. System A 2 analyzed and obtained that the interface detection result of the interface for creating a conference with the local system 10 is that the service is exited, then System A 2 constructs the corresponding connection line through the black line in the expected connection diagram. System A 2 analyzed and obtained that the interface detection result of the interface for synchronizing the work order status with the central system 1 is that the interface is abnormal, then System A 2 constructs the corresponding connection line through the yellow line in the expected connection diagram. System A 2 analyzed and obtained that the interface detection result of the interface for querying the performance information with the central system 1 is that the interface is normal, then System A 2 constructs the corresponding connection line through the green line in the expected connection diagram.

[0068] In an embodiment of the present invention, interface metadata is loaded, and an expected connection diagram between a local interface and a corresponding interface of a subsystem is constructed based on the interface metadata; an interface detection request is sent to the corresponding interface of the subsystem at a first predetermined interval based on the interface metadata; interface detection data fed back by the subsystem in response to the interface detection request is received, and the interface detection data is analyzed to obtain an interface detection result between the local interface and the corresponding interface of the subsystem; the interface detection result represents the connection status between the local interface and the corresponding interface of the subsystem; based on the interface detection result, the connection status between the local interface and the corresponding interface of the subsystem is displayed in the expected connection diagram for monitoring. Since the interface metadata includes the connection data between the local interface and the corresponding interface, the main system can send a connection detection request to the corresponding interface of the subsystem, thereby realizing connection detection between different microservice systems and efficiently obtaining the connection status between different microservice systems.

[0069] In some embodiments, Figure 2 The illustrated S103 can be implemented through S105 , which will be described in conjunction with each step.

[0070] S105. Obtain an interface detection result between the local interface and the interface corresponding to the subsystem based on the proportion information in the interface call status information. The proportion information represents the ratio of the number of successful calls of the local interface and the interface corresponding to the subsystem within a preset time period to the total number of calls.

[0071] In an embodiment of the present invention, the main system obtains the interface detection result between the local interface and the corresponding interface of the secondary system based on the ratio of the number of successful calls of the local interface and the corresponding interface of the secondary system within a preset time period to the total number of calls in the interface call status information.

[0072] In an embodiment of the present invention, the main system obtains the interface detection result between the local interface and the corresponding interface of the secondary system based on the ratio of the number of successful calls of the local interface and the corresponding interface of the secondary system within the preset connection times to the total number of calls in the interface call status information.

[0073] For example, the local interface connects to the corresponding interface of the secondary system 100 times within a preset time period, with 95 successful connections. The primary system divides 95 by 100 to obtain 0.95. Assuming the preset connection threshold in the primary system is 0.9, since 0.95 is greater than 0.9, the primary system will determine that the local interface and the corresponding interface of the secondary system are connected normally.

[0074] In the embodiment of the present invention, the main system can accurately analyze and obtain the interface detection result between the local interface and the corresponding interface based on the ratio of the successful call times of the local interface and the corresponding interface to the total call times.

[0075] In some embodiments, Figure 2 S103 shown in FIG. 1 also includes S106 , which will be described in conjunction with each step.

[0076] S106. If the interface detection result indicates that the connection status between the local interface and the corresponding interface of the subsystem is abnormal, detect the port connection result and network connection status information between the local interface and the corresponding interface of the subsystem to adjust the connection status between the local interface and the corresponding interface of the subsystem.

[0077] In an embodiment of the present invention, if the primary system analyzes and determines that the connection status between the local interface and the corresponding interface of the secondary system is abnormal, the primary system needs to detect the cause of the abnormal connection status between the local interface and the corresponding interface of the secondary system. The primary system can send a port detection request to the secondary system to detect the port connection result between the primary system and the secondary system, and can also obtain network connection information between the primary system and the secondary system by detecting the network status. The primary system staff can use the port connection result and network connection information to adjust the connection status between the local interface and the corresponding interface of the secondary system.

[0078] In an embodiment of the present invention, if the primary system detects that the port connection between the primary system and the secondary system is abnormal, the primary system needs to detect the cause of the abnormal port connection between the primary system and the secondary system. The primary system can obtain the cause of the abnormal port connection by detecting the network connection between the primary system and the secondary system.

[0079] In some embodiments, S106 can also be implemented through S107-S109, which will be explained in conjunction with each step.

[0080] S107: If the interface detection result indicates that the connection status between the local interface and the corresponding interface of the subsystem is abnormal, send a port detection request to the corresponding interface of the subsystem.

[0081] In this embodiment of the present invention, the primary system analyzes interface detection data and obtains an interface detection result indicating an abnormal connection between the primary system's local interface and the corresponding interface of the secondary system. The primary system needs to detect the cause of the abnormal connection between the local interface and the corresponding interface. This cause could be a protocol port issue or a network issue. Since the likelihood of a network issue is very low, the primary system first detects whether there is a port issue. The primary system then sends a port detection request to the corresponding interface of the secondary system.

[0082] The port detection request is used to detect the connection status between the primary system port and the secondary system port.

[0083] In the embodiment of the present invention, the primary system may send port detection requests corresponding to different interfaces to different corresponding interfaces of the secondary system respectively.

[0084] S108: Receive port detection data fed back by the subsystem in response to the port detection request, and obtain a port connection result between the local interface and the corresponding port of the subsystem according to the port detection data.

[0085] In this embodiment of the present invention, after the secondary system receives a port detection request, it retrieves the port-related information stored in the database. The secondary system sends the port-related information along with port detection data to the primary system. The primary system receives the port detection data sent by the secondary system and obtains a port detection result based on the port-related information in the port detection data.

[0086] In the embodiment of the present invention, the port related information may be the connection status of the port within a period of time. The main system may analyze the number of successful connections of the port within a period of time to obtain the port detection result.

[0087] In the embodiment of the present invention, the port may be a port for connecting the primary system to the secondary system, including a TCP (Transmission Control Protocol, TCP) transmission control protocol port or a UDP (User Datagram Protocol, UDP) user datagram protocol port.

[0088] S109: If the port connection result indicates that the connection status between the port corresponding to the subsystem is abnormal, then detect and obtain network connection status information between the subsystem.

[0089] In the embodiment of the present invention, the primary system analyzes the port detection data to obtain a port connection result indicating that the connection status between the primary system and the secondary system is abnormal. The primary system can detect the network connection between the primary system and the secondary system by testing the network signal.

[0090] In the embodiment of the present invention, when the interface detection result indicates that the connection is abnormal, the main system can promptly obtain the cause of the connection abnormality by detecting the port connection and the network connection.

[0091] In some embodiments, S108 can also be implemented through S110 - S111 , which will be described in conjunction with each step.

[0092] S110: Receive port detection data fed back by the secondary system in response to the port detection request.

[0093] In an embodiment of the present invention, the primary system receives port detection data sent by the secondary system in response to a port detection request. The port detection data may be port connection information for the corresponding port within a predetermined time period stored in a database of the secondary system. The port connection information may include the number of connections to the corresponding port, the connection duration, and the number of successful connections.

[0094] S111. Obtain a port connection result between the local interface and the corresponding port of the secondary system according to the proportion information in the port detection data, where the proportion information represents the number of successful connections between the local port and the corresponding port of the secondary system within a preset time period relative to the total number of connections.

[0095] In the embodiment of the present invention, the primary system obtains the port connection result between the local port and the secondary system corresponding port according to the number of successful connections between the local port and the secondary system corresponding port in the preset time period and the total number of connections in the port detection data.

[0096] In the embodiment of the present invention, the main system obtains the port connection result between the local port and the corresponding port of the secondary system according to the number of successful connections between the local port and the corresponding port of the secondary system within the preset connection times in the port detection data.

[0097] In some embodiments, Figure 2 The illustrated S104 can also be implemented through S112 , which will be described in conjunction with each step.

[0098] S112. In the expected connection diagram, based on the preset identifier corresponding to the interface detection result, a connection line is formed between the local interface and the corresponding interface of the secondary system, and the corresponding interface detection result is displayed at the connection line for monitoring.

[0099] In this embodiment of the present invention, the primary system uses the interface detection results analyzed in the expected connection diagram and the preset identifier corresponding to the interface detection results to form a connection line between the local interface corresponding to the interface detection result and the corresponding interface of the secondary system. Simultaneously, the primary system displays the interface detection results in the form of text information on one side of the connection line. Using the interface detection results displayed in the expected connection diagram, staff of the primary system can monitor the connection status between the local interface and the corresponding interface.

[0100] The preset mark may be a preset color corresponding to the interface detection result, or the preset mark may be a preset connection line type corresponding to the interface detection result.

[0101] In the embodiment of the present invention, the primary system may form a connection line between the local interface corresponding to the interface detection result and the corresponding interface of the secondary system according to the interface detection result obtained by analysis and the corresponding preset color in the expected connection diagram.

[0102] In an embodiment of the present invention, the primary system may form a connection line between a local interface corresponding to the interface detection result and a corresponding interface of the secondary system based on the interface detection result and the corresponding connection line type obtained by analysis in the expected connection diagram. The connection line type may be one of a solid line, a dashed line, a double solid line, and a double dashed line.

[0103] In the embodiment of the present invention, the main system constructs corresponding connection lines in the expected connection diagram through preset identifiers corresponding to different interface detection results, thereby intuitively reflecting the interface detection results.

[0104] In some embodiments, S112 can also be implemented through S113, which will be explained in conjunction with each step.

[0105] S113. In the expected connection diagram, based on a first preset identifier corresponding to the policy failure, a first connection line is formed between the local interface and the corresponding interface of the secondary system, and policy failure information is displayed at the first connection line for monitoring.

[0106] In an embodiment of the present invention, interface detection results may include: policy failure, interface abnormality, normal interface, and service exit. If the interface detection result indicates a policy difference, the primary system establishes a first connection line between the local interface and the corresponding interface of the secondary system based on a first preset identifier corresponding to the policy failure in the expected connection diagram. The primary system then displays the policy failure in text on one side of the first connection line. Primary system staff can monitor the connection status between the local interface and the corresponding interface using the interface detection results displayed in the expected connection diagram.

[0107] For example, combined Figure 3 System A 2 analyzes and obtains the interface detection result of the household details query interface with the local system 10, which is that the policy is not available. System A 2 then constructs a corresponding connection line in the expected connection diagram using a red line. The red line is the first preset indicator of the policy not available.

[0108] In this embodiment of the present invention, if the primary system analyzes and determines that the connection status between the local interface and the corresponding interface of the secondary system is policy-unreachable, the primary system constructs a connection line between the local interface of the primary system and the corresponding interface of the secondary system using a solid line. The solid line represents a third preset indicator corresponding to policy-unreachable.

[0109] In the embodiment of the present invention, the main system constructs a corresponding connection line in the expected connection diagram through the first preset identifier corresponding to the policy failure, which intuitively reflects the interface detection result between the local interface of the policy failure and the corresponding interface.

[0110] In some embodiments, S112 can also be implemented through S114, which will be explained in conjunction with each step.

[0111] S114. In the expected connection diagram, based on a second preset identifier corresponding to the interface anomaly, a second connection line is formed between the local interface and the corresponding interface of the secondary system, and interface anomaly information is displayed at the second connection line for monitoring.

[0112] In this embodiment of the present invention, if the interface detection result indicates an interface anomaly, the primary system establishes a second connection line between the local interface and the corresponding interface of the secondary system based on a second preset identifier corresponding to the interface anomaly in the expected connection diagram. The primary system also displays the interface anomaly in text on one side of the second connection line. Primary system personnel can monitor the connection status between the local interface and the corresponding interface using the interface detection result displayed in the expected connection diagram.

[0113] For example, combined Figure 3 System A 2 analyzes the interface detection result of the synchronization work order status interface with the central system 1 and finds that the interface is abnormal. System A then constructs a corresponding connection line in the expected connection diagram using a yellow line. Yellow is the second preset indicator corresponding to the interface abnormality.

[0114] In this embodiment of the present invention, if the primary system analyzes and determines that the connection status between the local interface and the corresponding interface of the secondary system is abnormal, the primary system constructs a connection line between the local interface of the primary system and the corresponding interface of the secondary system using a dotted line. The dotted line represents a third preset indicator corresponding to the abnormal interface.

[0115] In the embodiment of the present invention, the main system constructs a corresponding connection line in the expected connection diagram through the second preset identifier corresponding to the interface abnormality, which intuitively reflects the interface detection result between the local interface with the interface abnormality and the corresponding interface.

[0116] In some embodiments, S112 can also be implemented through S115, which will be explained in conjunction with each step.

[0117] S115. In the expected connection diagram, based on a third preset identifier corresponding to a normal interface, a third connection line is formed between the local interface and the corresponding interface of the secondary system, and normal interface information is displayed at the third connection line for monitoring.

[0118] In this embodiment of the present invention, if the interface detection result indicates that the interface is normal, the primary system forms a third connection line between the local interface and the corresponding interface of the secondary system based on the third preset identifier corresponding to the normal interface in the expected connection diagram. The primary system also displays "Normal Interface" in text on one side of the third connection line.

[0119] For example, combined Figure 3 System A 2 analyzes and obtains the interface test result of the query performance information interface with the central system 1, and the interface is normal. Then, system A 2 constructs the corresponding connection line in the expected connection diagram using a green line. Among them, green is the third preset indicator corresponding to the normal interface.

[0120] In this embodiment of the present invention, if the primary system analyzes and determines that the connection status between the local interface and the corresponding interface of the secondary system is normal, the primary system will construct a connection line between the local interface of the primary system and the corresponding interface of the secondary system using a double solid line. The double solid line represents a third preset indicator corresponding to a normal interface.

[0121] In the embodiment of the present invention, the main system constructs a corresponding connection line in the expected connection diagram through the third preset identifier of the normal interface, which intuitively reflects the interface detection result between the local interface with a normal interface and the corresponding interface.

[0122] In some embodiments, S112 can also be implemented through S116, which will be explained in conjunction with each step.

[0123] S116. In the expected connection diagram, based on a fourth preset identifier corresponding to the exit service, a fourth connection line is formed between the local interface and the corresponding interface of the secondary system, and exit service information is displayed at the fourth connection line for monitoring.

[0124] In this embodiment of the present invention, if the interface detection result indicates that the service has been withdrawn, the primary system forms a fourth connection line between the local interface and the corresponding interface of the secondary system based on the fourth preset identifier corresponding to the withdrawn service in the expected connection diagram. The primary system also displays the withdrawal service in text on one side of the fourth connection line.

[0125] For example, combined Figure 3 System A 2 analyzes and obtains the result of the interface detection of the creation conference interface with the local system 10 as exiting the service, and then System A 2 constructs a corresponding connection line in the expected connection diagram using a black line. Among them, the black line is the fourth preset mark corresponding to the exit service.

[0126] In this embodiment of the present invention, if the primary system analyzes and determines that the connection status between the local interface and the corresponding interface of the secondary system is out of service, the primary system will construct a connection line between the local interface of the primary system and the corresponding interface of the secondary system using a double-dashed line. The double-dashed line represents the fourth preset indicator corresponding to the out of service status.

[0127] In the embodiment of the present invention, the main system constructs a corresponding connection line in the expected connection diagram through the fourth preset identifier corresponding to the exit service, which intuitively reflects the interface detection result between the local interface of the exit service and the corresponding interface.

[0128] In some embodiments, Figure 2 S104 shown in FIG. 1 also includes S117 , which will be described in conjunction with each step.

[0129] S117. Obtain local interface call status information of the local microservice.

[0130] In the embodiment of the present invention, in order to improve the comprehensiveness of connection monitoring, the main system can obtain the interface call status information of the local microservice after obtaining the connection status information of the interface corresponding to the secondary system.

[0131] In an embodiment of the present invention, the main system may use any one of a distributed system performance monitoring tool, a link tracking tool, and a distributed tracking system tool to detect and obtain information about the interface call status of the local microservice.

[0132] The interface call status information may include: interface call status information of each microservice in multiple microservice clusters of the local microservice.

[0133] In an embodiment of the present invention, the main system can proactively send a detection request to the local microservice. The main system can also directly receive interface call status information sent by the local microservice. Before the main system receives the interface call status information from the local microservice, the operator can configure the relevant sending process on the local microservice.

[0134] In some embodiments, S117 can also be implemented through S118-S120, which will be explained in conjunction with each step.

[0135] S118. Send a local detection request to the local microservice at a second predetermined time interval.

[0136] In an embodiment of the present invention, the main system may actively detect and obtain information about the interface call status of the local microservice. The main system may send a local detection request to the local microservice at a second predetermined time interval.

[0137] The second predetermined time may be the same as or different from the first predetermined time, and may be 1 minute or 1 hour, which is not limited here.

[0138] In an embodiment of the present invention, the internal microservice monitoring service of the main system may send a local detection request to the local microservice at a second predetermined time interval.

[0139] S119. Obtain local interface call status data fed back by the local microservice in response to the local detection request.

[0140] In the embodiment of the present invention, the main system can receive its own call status data fed back by each local microservice in response to its own local detection request through the communication line within the system.

[0141] In the embodiment of the present invention, the internal microservice monitoring service of the main system receives the local detection request corresponding to each local microservice and feeds back its own call status data.

[0142] The call status data may include the interface call status information of the corresponding local microservice within a period of time.

[0143] In an embodiment of the present invention, the call status data may include call status information of the internal interface and call status information of the external interface of the local microservice.

[0144] S120: Analyze local interface call status data to obtain internal interface call status information and external interface call status information of local microservices.

[0145] In the embodiment of the present invention, the interfaces of local microservices are further divided into internal interfaces and external interfaces. The internal interfaces are used for communication between local microservices, while the external interfaces are used for communication between local microservices and secondary systems. The main system analyzes the number of successful calls to the internal interfaces within a certain period of time in the call status data to obtain the corresponding internal interface call status information of the local microservice. The main system analyzes the number of successful calls to the external interfaces within a certain period of time in the call status data to obtain the corresponding external interface call status information of the local microservice.

[0146] In an embodiment of the present invention, the main system can more comprehensively monitor the connection status of the main system by obtaining the internal interface call status information and external interface call status information of the local microservice, combined with the interface detection result information between the local interface and the corresponding interface of the secondary system.

[0147] In some embodiments, Figure 2 S104 shown in the figure also includes S121 to S124 implementation, which will be explained in conjunction with each step.

[0148] S121 : Acquire a touch signal of a target object, respond to the touch signal, and send a designated detection request to a designated interface of the subsystem.

[0149] In this embodiment of the present invention, an operator of the primary system, or the target subject, needs to obtain connection information between the primary system and a designated interface of the secondary system. The target subject pre-configures a relevant program in the primary system. When the target subject sends a touch signal on the primary system's console, the primary system responds to the touch signal and begins executing the relevant program. The primary system then sends a designated detection request to the designated interface of the secondary system.

[0150] The touch signal may be clicking or double-clicking the corresponding button.

[0151] In the embodiment of the present invention, the designated interface of the secondary system may be one or more. If the designated interface of the secondary system is multiple, the primary system may send corresponding designated detection requests to the multiple designated interfaces respectively according to a preset program.

[0152] S122: Receive designated detection data fed back by the secondary system in response to the designated detection request, analyze the designated detection data, and obtain a designated detection result between the local interface and the designated interface.

[0153] In this embodiment of the present invention, after receiving a designated test request, the secondary system retrieves the call log information corresponding to the designated interface from its database. The secondary system transmits the designated test data along with the call log information for the designated interface to the primary system. The primary system analyzes the number of successful calls to the designated interface, as reflected in the call log information, to obtain the designated test results for the local interface and the designated interface.

[0154] S123. Based on the specified detection result, update the connection status between the local interface and the specified interface in the expected connection graph.

[0155] In the embodiment of the present invention, the main system constructs a connection line between the local interface and the corresponding designated interface according to the preset identifier corresponding to the designated detection result in the expected connection diagram.

[0156] In the embodiment of the present invention, the main system may further display the designated detection result in the form of text on one side of the corresponding connection line.

[0157] Combine Figure 4 This is a schematic diagram of an optional effect of the connection status monitoring method provided by an embodiment of the present invention. The front end of System A 2 receives the target object's behavior information, triggering interface debugging of System A 2. The ingress gateway of System A 2 receives the behavior information and transmits it to the external interface monitoring microservice. The external interface monitoring microservice sends the specified detection request to the corresponding secondary system via the egress gateway.

[0158] In the embodiment of the present invention, the main system detects and obtains the specified detection result of the specified interface through the touch signal of the target object, and can promptly detect the cause of the failure after a connection failure has occurred in some interfaces.

[0159] S124. Send the connection status information corresponding to the key interface and the external interface call status information of the corresponding local microservice to the central system.

[0160] In this embodiment of the present invention, the central system pre-defines at least one key service interface among multiple local interfaces in the primary system as a key interface. The primary system transmits connection information between the key interface and the corresponding interface of the secondary system, as well as information about the external interface call status of the local microservice, to the central system.

[0161] It should be noted that the central system can be connected to multiple main systems. Multiple main systems respectively send the connection information of the corresponding key interfaces and the external interface call status information of the local microservices to the central system.

[0162] In some embodiments, Figure 2 The illustrated S104 is followed by S125 , which will be described in conjunction with each step.

[0163] S125. Sending connection status information corresponding to the key interface and corresponding local microservice external interface call status information to the central system; the key interface represents the interface of the preset key business.

[0164] In an embodiment of the present invention, the main system sends connection status information corresponding to the key interface and corresponding local microservice external interface call status information to the central system; the key interface represents the interface of the preset key business.

[0165] The central system may be communicatively connected to at least one main system to receive business information of the at least one main system.

[0166] See Figure 5 , is an optional flow chart of a connection status monitoring method provided by an embodiment of the present invention. It is applied to a subsystem device and will be described in conjunction with the steps.

[0167] S126: Receive an interface detection request sent by the main system based on the interface metadata.

[0168] In an embodiment of the present invention, the secondary system is connected to the primary system. The primary system sends a connection detection request to the secondary system based on relevant data in the interface metadata at a first preset interval. Simultaneously, the secondary system receives the interface detection request sent by the primary system.

[0169] The interface metadata represents the connection data between the local interface of the host system and the corresponding interface.

[0170] S127. Respond to the interface detection request and feed back interface detection data to the main system.

[0171] In this embodiment of the present invention, the secondary system responds to the interface detection request and retrieves the interface call status information of the local interface of the primary system and the corresponding interface of the secondary system from its own database within a certain period of time. The interface call status information is then sent to the primary system along with the interface detection data.

[0172] In an embodiment of the present invention, the secondary system receives and responds to the interface detection request sent to itself by the main system based on the interface metadata, and feeds back its own interface detection data to the main system. Since the interface metadata includes the relevant data between the local interface and the corresponding interface, regardless of whether the structures of the main system and the secondary system are the same, the interface status monitoring between the main system and the secondary system can be realized in a timely and comprehensive manner.

[0173] In some embodiments, Figure 5 The illustrated S127 is followed by S128, which will be described in conjunction with each step.

[0174] S128. Receive a port detection request sent by the main system. The port detection request is sent by the main system when analyzing the interface detection data and determining that the connection status between the local interface and the corresponding interface is abnormal.

[0175] In an embodiment of the present invention, if the primary system detects an abnormal connection between a local interface and a corresponding interface of a secondary system through interface detection data, the primary system will detect whether the port connection between the primary system and the secondary system is normal. The primary system sends a port detection request to the secondary system.

[0176] In some embodiments, Figure 5 The illustrated S127 also includes S129-S130 implementation, which will be described in conjunction with each step.

[0177] S129: Receive a designated detection request corresponding to a designated interface sent by the main system.

[0178] In the embodiment of the present invention, the primary system receives a touch signal from a target object, and the primary system sends a designated detection request to a designated interface of the secondary system.

[0179] S130 , responding to the designated detection request and feeding back designated detection data corresponding to the designated interface to the main system.

[0180] In this embodiment of the present invention, the secondary system responds to a specified detection request by retrieving interface call status information for the primary system's local interface and the secondary system's specified interface from its own database over a period of time. The secondary system then sends this interface call status information along with the specified detection data to the primary system.

[0181] See Figure 6 , is an optional flow chart of a connection status monitoring method provided by an embodiment of the present invention. It is applied to central system equipment and will be described in conjunction with the steps.

[0182] S131. Receive connection status information corresponding to a key interface and corresponding local microservice external interface call status information sent by at least one main system.

[0183] In the embodiment of the present invention, the central system receives connection status information between key interfaces and corresponding local microservice external interface call status information sent by each main system connected to the central system.

[0184] S132. Based on the connection status information corresponding to the key interfaces and the local microservice external interface call status information, a connection status diagram of each main system is constructed for display.

[0185] In this embodiment of the present invention, the central system constructs a connection state diagram of the key interfaces between each main system and the corresponding secondary system. The central system then displays the local microservice interface status information of each main system in the corresponding main system state diagram.

[0186] The secondary systems corresponding to each primary system may include other primary systems or a central system.

[0187] In an embodiment of the present invention, the central system constructs a connection status diagram of multiple main systems by obtaining the connection status information between the key interfaces of other main systems and the corresponding local microservice external interface call status information, and can then comprehensively display the connection status between each system in the global system.

[0188] See Figure 7 , which is an interaction diagram of the connection status monitoring method provided by an embodiment of the present invention. It will be described in conjunction with the steps.

[0189] S134, the primary system loads the interface metadata, and constructs an expected connection graph between the local interface and the corresponding interface of the secondary system based on the interface metadata.

[0190] The detailed implementation of step S134 is consistent with that of S101 and will not be repeated here.

[0191] S135 , the primary system sends an interface detection request to the corresponding interface of the secondary system at a first predetermined interval based on the interface metadata.

[0192] The detailed implementation of step S135 is consistent with that of step S102 and will not be repeated here.

[0193] S136 , the primary system receives the interface call status information fed back by the secondary system in response to the interface detection request, and obtains the interface detection result between the local interface and the corresponding interface of the secondary system according to the interface call status information.

[0194] The detailed implementation of step S136 is consistent with that of step S103 and will not be repeated here.

[0195] S137 , based on the interface detection result, the primary system displays the connection status of the local interface and the corresponding interface of the secondary system in the expected connection diagram for monitoring.

[0196] The detailed implementation of step S137 is consistent with that of step S104 and will not be repeated here.

[0197] S138, the central system receives connection status information corresponding to the key interface and corresponding local microservice external interface call status information sent by at least one main system.

[0198] The detailed implementation of step S138 is consistent with that of step S131 and will not be repeated here.

[0199] S139, the main system builds a connection status diagram of each main system for display based on the connection status information corresponding to the key interfaces and the local microservice external interface call status information.

[0200] The detailed implementation of step S139 is consistent with that of step S132 and will not be repeated here.

[0201] See Figure 8 , which is a schematic diagram of the structure of the connection status monitoring device provided by an embodiment of the present invention Figure 1 .

[0202] An embodiment of the present invention provides a connection status monitoring device 800 , which is applied to a main system and includes: a loading unit 803 , a first sending unit 804 , a first receiving unit 805 and a processing unit 806 .

[0203] The loading unit 803 is configured to load interface metadata and construct an expected connection diagram between the local interface and the corresponding interface of the subsystem based on the interface metadata; the interface metadata represents relevant data between the local interface and the corresponding interface of the subsystem;

[0204] The first sending unit 804 is configured to send an interface detection request to the corresponding interface of the subsystem at a first predetermined interval based on the interface metadata; the interface detection request is used to retrieve interface call status information of the corresponding interface of the subsystem;

[0205] The first receiving unit 805 is configured to receive interface call status information fed back by the subsystem in response to the interface detection request, and obtain an interface detection result between the local interface and the interface corresponding to the subsystem based on the interface call status information; the interface detection result indicates the connection status between the local interface and the interface corresponding to the subsystem;

[0206] The processing unit 806 is configured to display the connection status between the local interface and the corresponding interface of the subsystem in the expected connection diagram based on the interface detection result for monitoring.

[0207] In an embodiment of the present invention, the first receiving unit 805 in the connection status monitoring device 800 is used to obtain the interface detection result between the local interface and the corresponding interface of the sub-system based on the proportion information in the interface call status information. The proportion information represents the ratio of the number of successful calls between the local interface and the corresponding interface of the sub-system within a preset time period to the total number of calls.

[0208] In an embodiment of the present invention, the first sending unit 804 in the connection status monitoring device 800 is used to detect the port connection result and network connection status information between the local interface and the corresponding interface of the subsystem if the interface detection result indicates that the connection status between the local interface and the corresponding interface of the subsystem is abnormal, so as to adjust the connection status between the local interface and the corresponding interface of the subsystem.

[0209] In an embodiment of the present invention, the first sending unit 804 in the connection status monitoring device 800 is used to send a port detection request to the corresponding interface of the subsystem if the interface detection result indicates that the connection status between the local interface and the corresponding interface of the subsystem is abnormal; receive port detection data fed back by the subsystem in response to the port detection request, and obtain the port connection result between the local interface and the corresponding port of the subsystem based on the port detection data; if the port connection result indicates that the connection status with the corresponding port of the subsystem is abnormal, then detect and obtain network connection status information between the subsystem.

[0210] In an embodiment of the present invention, the first receiving unit 805 in the connection status monitoring device 800 is used to receive port detection data fed back by the subsystem in response to a port detection request; based on the proportion information in the port detection data, the port connection result between the local interface and the corresponding port of the subsystem is obtained, and the proportion information represents the number of successful connections between the local port and the corresponding port of the subsystem within a preset time period as a percentage of the total number of connections.

[0211] In an embodiment of the present invention, the processing unit 806 in the connection status monitoring device 800 is used to form a connection line between the local interface and the corresponding interface of the subsystem based on the preset identifier corresponding to the interface detection result in the expected connection diagram, and display the corresponding interface detection result at the connection line for monitoring.

[0212] In an embodiment of the present invention, the interface detection result includes any one of: policy failure, interface abnormality, interface normality and service exit. The processing unit 806 in the connection status monitoring device 800 is used to form a first connection line between the local interface and the corresponding interface of the subsystem based on the first preset identifier corresponding to the policy failure in the expected connection diagram, and display the policy failure information at the first connection line for monitoring; or, in the expected connection diagram, based on the second preset identifier corresponding to the interface abnormality, form a second connection line between the local interface and the corresponding interface of the subsystem, and display the interface abnormality information at the second connection line for monitoring; or, in the expected connection diagram, based on the third preset identifier corresponding to the interface normality, form a third connection line between the local interface and the corresponding interface of the subsystem, and display the interface normal information at the third connection line for monitoring; or, in the expected connection diagram, based on the fourth preset identifier corresponding to the service exit, form a fourth connection line between the local interface and the corresponding interface of the subsystem, and display the service exit information at the fourth connection line for monitoring.

[0213] In the embodiment of the present invention, the first sending unit 804 in the connection status monitoring device 800 is used to obtain local interface call status information of the local microservice.

[0214] In an embodiment of the present invention, the first sending unit 804 in the connection status monitoring device 800 is used to send a local detection request to the local microservice at an interval of a second predetermined time; the first receiving unit 805 in the connection status monitoring device 800 is used to obtain the local interface call status data fed back by the local microservice in response to the local detection request; analyze the local interface call status data to obtain the internal interface call status information and external interface call status information of the local microservice; the internal interface of the local microservice is used for the connection between local microservices, and the external interface of the local microservice is used for the connection between the local microservice and the subsystem service.

[0215] In an embodiment of the present invention, the first sending unit 804 in the connection status monitoring device 800 is used to obtain the touch signal of the target object, respond to the touch signal, and send a specified detection request to the specified interface of the subsystem; the first receiving unit 805 in the connection status monitoring device 800 is used to receive the specified detection data fed back by the subsystem in response to the specified detection request, and analyze the specified detection data to obtain the specified detection result between the subsystem and the specified interface; the processing unit 806 updates the connection status between the subsystem and the specified interface in the expected connection diagram based on the specified detection result.

[0216] The first sending unit 804 in the connection status monitoring device 800 is used to send connection status information corresponding to the key interface and external interface call status information of the local microservice to the central system; the key interface is at least one local interface preset by the central system.

[0217] In an embodiment of the present invention, the loading unit 803 in the connection status monitoring device 800 loads the interface metadata, and constructs an expected connection diagram between the local interface and the corresponding interface of the subsystem based on the interface metadata; the first sending unit 804 sends an interface detection request to the corresponding interface of the subsystem at an interval of a first predetermined time based on the interface metadata; the first receiving unit 805 receives the interface call status information feedback by the subsystem in response to the interface detection request, and obtains the interface detection result between the local interface and the corresponding interface of the subsystem based on the interface call status information; the interface detection result represents the connection status between the local interface and the corresponding interface of the subsystem; and the processing unit 806 displays the connection status of the local interface and the corresponding interface of the subsystem in the expected connection diagram based on the interface detection result. Since the interface metadata includes the connection data between the local interface and the corresponding interface, the main system can send a connection detection request to the corresponding interface of the subsystem, thereby realizing connection detection between different microservice systems and efficiently obtaining the connection status between different microservice systems.

[0218] The first sending unit 804 in the connection status monitoring device 800 is used to send connection status information corresponding to the key interface and corresponding local microservice external interface call status information to the central system; the key interface represents the interface of the preset key business.

[0219] See Figure 9 , which is a schematic diagram of the structure of the connection status monitoring device provided by an embodiment of the present invention Figure 2 .

[0220] The connection status monitoring device 900 provided in an embodiment of the present invention is applied to a secondary system and includes: a second receiving unit 903 and a second sending unit 904 .

[0221] The second receiving unit 903 is configured to receive an interface detection request sent by the main system based on the interface metadata; the interface metadata represents connection data between the local interface of the main system and the corresponding interface.

[0222] The second sending unit 904 is configured to respond to the interface detection request and feed back interface detection data to the main system.

[0223] In an embodiment of the present invention, the second receiving unit 903 in the connection status monitoring device 900 is used to receive a port detection request sent by the main system. The port detection request is obtained when the main system analyzes the interface detection data and finds that the connection status between the local interface and the corresponding interface is abnormal.

[0224] In the embodiment of the present invention, the second receiving unit 903 in the connection status monitoring device 900 is further configured to receive a designated detection request corresponding to a designated interface sent by the main system.

[0225] In the embodiment of the present invention, the second sending unit 904 in the connection status monitoring device 900 is further configured to respond to the designated detection request and feed back designated detection data corresponding to the designated interface to the main system.

[0226] In an embodiment of the present invention, the secondary system receives and responds to the interface detection request sent to itself by the main system based on the interface metadata through the second receiving unit 903, and feeds back its own interface detection data to the main system through the second sending unit 904. Since the interface metadata includes relevant data between the local interface and the corresponding interface, regardless of whether the structures of the main system and the secondary system are the same, the interface status monitoring between the main system and the secondary system can be realized in a timely and comprehensive manner.

[0227] See Figure 10 , which is a schematic diagram of the structure of the connection status monitoring device provided by an embodiment of the present invention Figure 3 .

[0228] The embodiment of the present invention provides a connection status monitoring device 700, applied to a central system, comprising: a third receiving unit 703 and a composition unit 704.

[0229] The third receiving unit 703 is used to receive connection status information corresponding to the key interface and corresponding local microservice external interface call status information sent by at least one main system;

[0230] The graph construction unit 704 is used to construct a connection status graph of each main system for display based on the connection status information corresponding to the key interfaces and the local microservice external interface call status information.

[0231] In an embodiment of the present invention, the central system obtains the connection status information between the key interfaces of other main systems and the corresponding local microservice external interface call status information through the third receiving unit 703, and then constructs the connection status diagram of multiple main systems through the composition unit 704, thereby comprehensively displaying the connection status between each system in the global system.

[0232] Correspondingly, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, which implements the steps in the above method when executed by a processor.

[0233] Correspondingly, an embodiment of the present invention provides a system monitoring device 600, including a memory 602 and a processor 601. The memory 602 stores a computer program that can be run on the processor 601. When the processor 601 executes the program, the steps in the above method are implemented.

[0234] In the embodiment of the present invention, the system monitoring device 600 includes any one of a main system device, a secondary system device, and a central system device.

[0235] It should be noted that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of the present invention, please refer to the description of the method embodiments of the present invention for understanding.

[0236] It should be noted that Figure 11 A schematic diagram of a hardware entity of a connection status monitoring device provided by an embodiment of the present invention, such as Figure 11 As shown, the hardware entity of the system monitoring device 600 includes: a processor 601 and a memory 602, wherein;

[0237] The processor 601 generally controls the overall operation of the connection status monitoring device 700 or the connection status monitoring device 800 or the connection status monitoring device 900 .

[0238] The memory 602 is configured to store instructions and applications executable by the processor 601, and can also cache data to be processed or processed by the processor 601 and various modules in the system monitoring device 600 (for example, image data, audio data, voice communication data and video communication data), which can be implemented through flash memory (FLASH) or random access memory (RAM).

Claims

1. A connection status monitoring method, characterized in that: Applicable to main system equipment, including: Loading interface metadata, and constructing an expected connection graph between the local interface and the corresponding interface of the subsystem based on the interface metadata; the interface metadata represents the connection data between the local interface and the corresponding interface of the subsystem; Based on the interface metadata, sending an interface detection request to the interface corresponding to the subsystem at a first predetermined interval; the interface detection request is used to retrieve interface call status information of the interface corresponding to the subsystem; receiving the interface call status information fed back by the subsystem in response to the interface detection request, and obtaining an interface detection result between the local interface and the corresponding interface of the subsystem based on ratio information in the interface call status information, wherein the ratio information represents the ratio of the number of successful calls between the local interface and the corresponding interface of the subsystem within a preset time period to the total number of calls; and the interface detection result represents the connection status between the local interface and the corresponding interface of the subsystem; In the expected connection diagram, based on the preset identifier corresponding to the interface detection result, a connection line is formed between the local interface and the corresponding interface of the subsystem, and the corresponding interface detection result is displayed at the connection line for monitoring.

2. The connection status monitoring method according to claim 1, wherein: After loading the interface metadata and constructing an expected connection graph between the local interface and the corresponding interface of the subsystem based on the interface metadata, the method further includes: Get the local interface call status information of the local microservice.

3. The connection status monitoring method according to claim 1, wherein: After forming a connection line between the local interface and the corresponding interface of the subsystem based on a preset identifier corresponding to the interface detection result in the expected connection diagram, and displaying the corresponding interface detection result on the connection line for monitoring, the method further includes: Acquire a touch signal of a target object, and send a specified detection request to a specified interface of the subsystem in response to the touch signal; receiving designated detection data fed back by the subsystem in response to the designated detection request, and analyzing the designated detection data to obtain a designated detection result between the local interface and the designated interface; Based on the designated detection result, the connection status between the local interface and the designated interface is updated in the expected connection map.

4. The connection status monitoring method according to claim 1, wherein: After forming a connection line between the local interface and the corresponding interface of the subsystem based on a preset identifier corresponding to the interface detection result in the expected connection diagram, and displaying the corresponding interface detection result on the connection line for monitoring, the method further includes: Send the connection status information corresponding to the key interface and the corresponding local microservice external interface call status information to the central system; the key interface represents the interface of the preset key business.

5. A connection status monitoring device, characterized in that: include: a loading unit, configured to load interface metadata and construct an expected connection graph between the local interface and the corresponding interface of the subsystem based on the interface metadata; The interface metadata represents the connection data between the local interface and the corresponding interface of the subsystem; A first sending unit, configured to send an interface detection request to the corresponding interface of the secondary system at a first predetermined time interval based on the interface metadata; The interface detection request is used to retrieve the interface call status information of the corresponding interface of the secondary system; a first receiving unit, configured to receive interface call status information fed back by the subsystem in response to the interface detection request, and obtain an interface detection result between the local interface and the corresponding interface of the subsystem based on ratio information in the interface call status information, wherein the ratio information represents a ratio of the number of successful calls between the local interface and the corresponding interface of the subsystem within a preset time period to the total number of calls; The interface detection result represents the connection status between the local interface and the corresponding interface of the secondary system; A processing unit is used to form a connection line between the local interface and the corresponding interface of the subsystem based on the preset identifier corresponding to the interface detection result in the expected connection diagram, and display the corresponding interface detection result at the connection line for monitoring.

6. A connection status monitoring device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, the steps in the method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images