CN114615169B - Path monitoring method, path monitoring device and computer readable storage medium - Google Patents
Path monitoring method, path monitoring device and computer readable storage medium Download PDFInfo
- Publication number
- CN114615169B CN114615169B CN202011409453.1A CN202011409453A CN114615169B CN 114615169 B CN114615169 B CN 114615169B CN 202011409453 A CN202011409453 A CN 202011409453A CN 114615169 B CN114615169 B CN 114615169B
- Authority
- CN
- China
- Prior art keywords
- service data
- monitoring
- path
- node
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
Abstract
The application provides a path monitoring method, a path monitoring device and a computer readable storage medium, wherein the path monitoring method comprises the following steps: acquiring service data information reported by at least two nodes on a monitoring path and path configuration information of the monitoring path, wherein the service data information comprises service data identifiers and service data contents corresponding to the service data identifiers, and the path configuration information is used for defining calling relations of all nodes in the monitoring path and the service data identifiers of all nodes; according to the service data identifiers reported by the at least two nodes and the service data identifiers of all the nodes in the path configuration information of the monitoring path, the service data contents reported by the at least two nodes are associated to the corresponding nodes in the monitoring path, so that the service data contents of all the nodes in the monitoring path are obtained; and monitoring the monitoring path according to the service data content of each node in the monitoring path.
Description
Technical Field
The present application relates to the field of computer technology, and more particularly, to a path monitoring method, apparatus, and computer readable storage medium.
Background
With the rapid development and wide application of communication and network technologies, computer systems have penetrated into various fields of human activities, and more enterprises, institutions and organizations build computer systems related to their own business, thereby improving working efficiency and reducing cost.
The computer system may be split into multiple functionally independent nodes, each of which may be used to implement a business function. Meanwhile, there are many dependency relationships between the nodes, for example, one node may be called by one or more other nodes, and once a certain node fails and loses response, the other node calling the node can continuously try to resend the request and wait.
In the related art, indexes such as call success rate, failure rate, call time consumption and the like among nodes can be monitored to determine the node with the fault, but the method is only suitable for calling paths with simple relations, and effective monitoring cannot be realized on paths with complex calling relations (such as tree or graph). Therefore, how to realize the monitoring of any path is an urgent problem to be solved.
Disclosure of Invention
The application provides a path monitoring method, a path monitoring device and a computer readable storage medium, which can realize the monitoring of any path.
In a first aspect, a path monitoring method is provided, including: acquiring service data information reported by at least two nodes on a monitoring path and path configuration information of the monitoring path, wherein the service data information comprises service data identifiers and service data contents corresponding to the service data identifiers, and the path configuration information is used for defining calling relations of all nodes in the monitoring path and the service data identifiers of all nodes;
according to the service data identifiers reported by the at least two nodes and the service data identifiers of all nodes in the path configuration information of the monitoring path, the service data contents reported by the at least two nodes are associated to the corresponding nodes in the monitoring path, so that the service data contents of all nodes in the monitoring path are obtained;
and monitoring the monitoring path according to the service data content of each node in the monitoring path.
In a second aspect, a path monitoring method is provided, including:
and reporting service data information to a monitoring platform, wherein the service data information comprises a service data identifier and service data content corresponding to the service data identifier, and the service data identifier is used for identifying service data of a node.
In some embodiments, the method further comprises:
and receiving configuration information of a monitoring platform, wherein the configuration information is used for configuring a data structure used by a node to report the service data information.
In a third aspect, a path monitoring apparatus is provided for performing the method of the first aspect or each implementation thereof.
Specifically, the path monitoring device includes: the system comprises an acquisition unit, a monitoring unit and a processing unit, wherein the acquisition unit is used for acquiring service data information reported by at least two nodes on a monitoring path and path configuration information of the monitoring path, wherein the service data information comprises a service data identifier and service data content corresponding to the service data identifier, and the path configuration information is used for defining calling relations of all nodes in the monitoring path and the service data identifiers of all nodes;
the association unit is used for associating the service data content reported by the at least two nodes to the corresponding node in the monitoring path according to the service data identifier reported by the at least two nodes and the service data identifier of each node in the path configuration information of the monitoring path to obtain the service data content of each node in the monitoring path;
And the monitoring unit is used for monitoring the monitoring path according to the service data content of each node in the monitoring path.
In a fourth aspect, a path monitoring device is provided for performing the method of the second aspect or each implementation manner thereof.
Specifically, the path monitoring device includes: and the sending unit is used for reporting the service data information to the monitoring platform, wherein the service data information comprises a service data identifier and service data content corresponding to the service data identifier, and the service data identifier is used for identifying the service data of the node.
In a fifth aspect, a path monitoring apparatus is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.
In a sixth aspect, a path monitoring apparatus is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.
In a seventh aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.
In an eighth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.
A ninth aspect provides a computer program which, when run on a computer, causes the computer to perform the method of any one of the above-described first to second aspects or implementations thereof.
According to the technical scheme, the reporting data structure adopted by the node reporting service data information is configured to comprise the service data identifier, the service data content and the path configuration information describing the calling relation of each node in the path and the node service data identifier of each node, so that the node can report the service data information based on the reporting data structure, and further, the service data information reported by the node can be associated to each node in the path according to the service data identifier to obtain the service data content of each node, so that path monitoring can be performed based on the service data content of each node.
Drawings
Fig. 1 is a schematic topology of a tree link.
Fig. 2 is a schematic topology of the graph-like links.
Fig. 3 is a schematic diagram of a system architecture suitable for use with embodiments of the present application.
Fig. 4 is a schematic flow chart of a path monitoring method according to an embodiment of the present application.
Fig. 5 is a schematic topology of a path.
Fig. 6 is a schematic flow chart of a path monitoring method provided according to another embodiment of the present application.
Fig. 7 is a schematic block diagram of a path monitoring apparatus according to an embodiment of the present application.
Fig. 8 is a schematic block diagram of another path monitoring apparatus provided in accordance with an embodiment of the present application.
Fig. 9 is a schematic block diagram of yet another path monitoring apparatus provided in accordance with an embodiment of the present application.
Detailed Description
The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art to which the application pertains without inventive faculty, are intended to fall within the scope of the application.
In the related art, monitoring of a path with a simple calling relationship, for example, monitoring between two nodes, and for a path with a complex calling relationship, for example, a tree path shown in fig. 1, or a tree link, or a graph path shown in fig. 2, or a graph link, a custom development monitoring program is often required, which is time-consuming and labor-consuming.
It should be understood that in the path topology diagrams shown in fig. 1 and 2, Δ represents a node, or a service node, etc., a connection line between two adjacent nodes is called an edge, which represents a call relationship between the two nodes, a direction indicated by an arrow of the connection line is a called node (i.e., a stop node of the edge), and a tail of the arrow of the connection line is a calling node, or a main adjustment node (i.e., a start node of the edge).
Because the node and the service provided by the node have correspondence, delta can also represent the service provided by the node, the direction indicated by the arrow of the connection is the service provided by the called node, the tail of the arrow of the connection is the service provided by the calling node, and the path topological graph can also be regarded as a call relation topological graph of the service.
Referring to fig. 3, fig. 3 is a system architecture diagram of a path monitoring method according to an embodiment of the present application. The system may comprise at least two nodes 101 and a monitoring server 103, or monitoring platform, between which monitoring server 103 and nodes 101 may communicate via a network 102. The network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
Alternatively, the at least two nodes 101 may be service nodes providing specific service functions, or may be monitoring nodes preconfigured in the system for monitoring service nodes, i.e. the nodes 101 may not perform services and are only responsible for monitoring the performance of service nodes.
In some embodiments, the at least two nodes 101 may be at least two sub-programs divided for an application program, where the at least two sub-programs coordinate with each other and are mutually configured to provide specific service functions. Alternatively, the at least two-piece subroutine may be disposed in one or more computing devices, to which embodiments of the present application are not limited.
In this case, the nodes communicate with each other using a lightweight communication mechanism, for example, based on an application programming interface (Application Programming Interface, API) conforming to the design criteria of the presentation layer state transfer (REpresentational State Transfer, REST), or referred to as RESTful API, which may be implemented based on the hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP)) protocol.
In other embodiments, the at least two nodes 101 may be separate devices, such as a personal computer, a notebook computer, a smart phone, a tablet computer, or other mobile internet devices.
The at least two nodes 101 may report service data information to the monitoring server 103, where the service data information may be, for example, the number of times that one node initiates a call request to another node, the number of times that the other node initiates the call request, time information of initiating the call request, time information of responding to the call request initiated by the other node, and so on.
The monitoring server 103 may be a server configured in the system for providing a path monitoring service. For example, a background server providing a path monitoring service, where the background server may calculate, according to service data information reported by the node 101, a monitoring index of a path where the node 101 is located, so that a developer may perform fixed positioning, or perform capacity assessment of a system, system optimization, and so on.
It should be understood that the system architecture shown in fig. 3 is only an example, and in other embodiments, the system may further include a storage system, for example, mysql or other storage engine, for storing data such as traffic data information reported by the at least two nodes 101 and monitoring indicators of paths.
Hereinafter, a path monitoring method according to an embodiment of the present application will be described in detail with reference to fig. 4 to 6.
Referring to fig. 4, the method may be applied to the system architecture described in fig. 3, and the path monitoring method is described from the perspective of a monitoring server, and may specifically include at least part of the following steps:
s401, service data information reported by at least two nodes on a monitoring path and path configuration information of the monitoring path are obtained, wherein the service data information comprises service data identifiers and service data contents corresponding to the service data identifiers, and the path configuration information is used for defining calling relations of all nodes in the monitoring path and service data identifiers of all nodes.
It should be understood that this node in the embodiment of the present application may correspond to the node 101 in fig. 3, and the specific implementation refers to the related description in fig. 3, which is not repeated herein for brevity.
In the embodiment of the application, the service data information reported by the node can adopt a specific data structure, which is called a reporting data structure, and the reporting data structure can comprise a service data identifier and service data content.
In some embodiments, the monitoring server may configure the reporting data structure for the node, further the node may record the content to be reported in the reporting data structure, and then report the service data information based on the reporting data structure.
In some embodiments, the service data identifier may be a string type, which is used to identify service data that needs to be reported by the node.
As some examples, the business data may include at least one of:
the number of calls one node calls another node;
the calling time of one node for calling the other node;
the calling frequency of one node for calling the other node;
the number of successful calls that one node calls another node;
the number of call failures that one node calls another node;
the success rate of calling another node by one node;
the number of calls that one node is called by other nodes;
the calling time of one node by other nodes;
the calling frequency of one node by other nodes;
the number of successful calls of one node by other nodes;
the number of call failures that one node calls by other nodes;
the success rate of the call of one node by other nodes.
Since there is a correspondence between nodes and traffic, the traffic data may include at least one of:
the number of calls that one service calls another service;
calling time of one service for calling another service;
The calling frequency of one service to another service;
the number of successful invocations of one service to another service;
call failure times for one service to call another service;
the success rate of calling one service to another service;
the number of times one service is called by other services;
the calling time of one service by other service;
the calling frequency of one service by other service;
the number of successful calls of one service by other services;
call failure times of one service being called by other services;
the call success rate of one service being called by other services.
It should be understood that the foregoing exemplary description describes specific examples of traffic data between nodes, and those skilled in the art will recognize that such description is merely exemplary and is not intended to limit the scope of embodiments of the present application.
In some embodiments, the service data content field may be a group type, which is used to record specific data corresponding to the reported service data identifier. The type of each element in the array can be determined according to the type of data actually required to be reported. For example, if the call number is to be reported, each element may be of integer type, and for example, if the call success rate is to be reported, each element may be of floating point type, etc.
In the embodiment of the application, the service data content is specific content corresponding to the service data identifier, and the specific content changes according to actual service use conditions.
For example, the service data identifier is used for identifying the calling times of the node A for calling the node B, if the node A records that the calling times of the node B is 200 times in a period of time, the service data content corresponding to the service data identifier is 200; if the node a records that the number of times of calling the node B is 300 in another time period, the service data content corresponding to the service data identifier is 300.
Optionally, in some embodiments, the service data information reported by the node may further include time information, which is used to identify a time point or a time period corresponding to the reported service data content.
Optionally, in some embodiments, the node may also report the identification information of the node, such as an IP address, a port number, etc., to the monitoring server, so as to be used by the monitoring server to distinguish which node reports the service data information.
Taking the path shown in fig. 5 as an example, an implementation of service data identification and service data content is illustrated.
It should be understood that in the path topology diagram of table 5, a1 to a4 each identify a piece of service data, for example, the service data may refer to the number of times a node calls other nodes, or may represent the node itself. I.e. the call relations of the nodes can also be regarded as call relations of the service.
For convenience of distinguishing and description, the node and the service data are represented by different identifiers, for example, the node corresponding to the service data a1 is denoted as n1, the node corresponding to the service data a2 is denoted as n2, the node corresponding to the service data a3 is denoted as n3, the node corresponding to the service data a4 is denoted as n4, then the service data a1 may represent the number of times the node n1 schedules the node n2, the service data a2 may represent the number of times the node n2 is scheduled by the node n1, the service data a3 may represent the number of times the node n3 is scheduled by other nodes, and the service data a4 may represent the number of times the node n4 schedules the node n 3.
TABLE 1
| Service data identification | Content of business data |
| a1 | [300] |
| a2 | [300] |
| a3 | [200] |
| a4 | [100] |
In table 1, a service data content corresponding to a1 being 300 may indicate that the number of times node n1 calls node n2 is 300; the service data content corresponding to a2 being 300 may indicate that the number of times that the node n2 is called by the node n1 is 300; the service data content corresponding to a3 is 200, which can indicate that the calling number of the node n3 called by other nodes is 200; a service data content corresponding to a4 is 100, which may indicate that the number of times node n4 calls node n3 is 100.
Optionally, in some embodiments, the path configuration information of the monitoring path includes:
A path identifier of the monitoring path;
the edge identifier is used for identifying an edge included in the monitoring path, wherein the edge is a connecting line between two nodes;
the service data identification;
a starting point identifier, configured to identify whether a node corresponding to the service data identifier is used as a starting point of an edge;
the terminal mark is used for marking whether the node corresponding to the service data mark is used as the terminal of the edge;
and the connection point identifier is used for identifying whether the node corresponding to the service data identifier is used as a connection point between different edges.
In the embodiment of the application, the path configuration information can be used for describing any complex path, so that in the embodiment of the application, the description of the calling relationship and the service data identification of each node in any path can be realized by introducing the path configuration information or the configuration data structure.
In some embodiments, the path identification may be of the string type, which uniquely identifies a monitoring path.
Alternatively, the edge identifiers may be of the string type, each edge identifier being used to uniquely identify an edge under a monitoring path.
Taking the path shown in fig. 5 as an example, the edge corresponding to the connection line between a1 and a2 is identified as the edge a, the edge corresponding to the connection line between a2 and a4 is identified as the edge B, the edge corresponding to the connection line between a4 and a3 is identified as the edge C, and the edge corresponding to the connection line between a2 and a3 is identified as the edge D.
Alternatively, in some embodiments, the start identifier may be a boolean (bool) type, which is used to identify whether a service data is a start of an edge, or whether a node corresponding to a service data is a start node of an edge, for example, a value of 1 indicates yes and a value of 0 indicates no.
Optionally, in some embodiments, the endpoint identifier may be a pool type, which is used to identify whether a service data is an endpoint of an edge, or whether a node corresponding to a service data is a termination node of an edge, for example, a value of 1 indicates yes and a value of 0 indicates no.
Alternatively, in some embodiments, the connection point identifier may be a pool type, which is used to identify whether one service data is a connection point of two adjacent edges, or whether a node corresponding to one service data is a connection node of two adjacent edges, for example, a value of 1 indicates yes and a value of 0 indicates no.
Table 2 is an example of path configuration information of the path shown in fig. 5.
TABLE 2
| Path | Edge(s) | Service data identification | Origin mark | Endpoint identification | Connection point identification |
| XX | Edge A | a1 | 1 | 0 | 0 |
| XX | Edge A | a2 | 0 | 1 | 1 |
| XX | Edge B | a2 | 1 | 0 | 1 |
| XX | Edge B | a4 | 0 | 1 | 1 |
| XX | Edge C | a4 | 1 | 0 | 1 |
| XX | Edge C | a3 | 0 | 1 | 0 |
| XX | Edge D | a2 | 1 | 0 | 1 |
| XX | Edge D | a3 | 0 | 1 | 0 |
In table 2, XX is a path identifier, which is used to identify paths in fig. 5, and the meanings of a1 to a4 refer to the related descriptions of the foregoing embodiments, which are not repeated herein.
In some embodiments, the monitoring server may monitor which monitoring path may be based on a user's selection. For example, the monitoring server may receive path configuration information entered by the user, and further determine which path the user chooses to monitor in conjunction with the path configuration information. Optionally, the user may also update or adjust the monitoring path, and correspondingly, the path configuration information may also be updated or adjusted.
It should be understood that, the embodiment of the present application does not specifically limit the order in which the monitoring server acquires the information of the service data reported by the node and acquires the path configuration information of the monitoring path.
After the service data information reported by the nodes and the path configuration information of the monitoring path are obtained, further, in S402, according to the service data identifier reported by at least two nodes and the service data identifier of each node in the path configuration information of the monitoring path, the service data content reported by at least two nodes is associated to the corresponding node in the monitoring path, so as to obtain the service data content of each node in the monitoring path.
Because the service data information reported by the node comprises the service data identifier, and the path configuration information of the monitoring path also comprises the service data identifier, in the embodiment of the application, the monitoring server can associate the service data content with the node based on the service data identifier, thereby obtaining the service data content of each node.
Taking the path shown in fig. 5 as an example, the monitoring server may associate the service data content reported in table 1 with the path configuration information in table 2 according to the service data identifier. Table 3 shows the results after the two are associated.
TABLE 3 Table 3
| Service data identification | Content of business data | Path | Edge(s) | Origin mark | Endpoint identification | Connection point identification |
| a1 | [300] | XX | Edge A | 1 | 0 | 0 |
| a2 | [300] | XX | Edge A | 0 | 1 | 1 |
| a2 | [300] | XX | Edge B | 1 | 0 | 1 |
| a4 | [100] | XX | Edge B | 0 | 1 | 1 |
| a4 | [100] | XX | Edge C | 1 | 0 | 1 |
| a3 | [200] | XX | Edge C | 0 | 1 | 0 |
| a2 | [300] | XX | Edge D | 1 | 0 | 1 |
| a3 | [200] | XX | Edge D | 0 | 1 | 0 |
Optionally, in some embodiments of the present application, the method further comprises:
generating each edge in the monitoring path according to the service data identifier, the edge identifier, the starting point identifier and the end point identifier;
and determining the connection relation among the edges according to the service data identification and the connection point identification to obtain a topological graph of the monitoring path. Wherein the topology graph may represent call relationships between various nodes in the monitoring path.
For example, each edge in the monitoring path, e.g., edge a, edge B, edge C, and edge D, may be generated from the traffic data identification, edge identification, start identification, and end identification in table 2 or table 3. And further determining the connection relation between the edges according to the service data identifier and the connection point identifier, thereby obtaining a complete monitoring path. For example, according to the connection point identifier corresponding to the service data identifier a2 being 1, the service data identifier a2 being the end point of the edge a, the service data identifier a2 being the start point of the edge B, it may be determined that the edge a and the edge B are connected by the service data identifier a 2.
It should be understood that, in the embodiment of the present application, the embodiment of the present application does not limit the order of generating the topology map of the monitoring path and the associated service data information and the path configuration information.
In some embodiments, a topology map may be generated first, further associating traffic data content to each monitoring node in the monitoring path according to the traffic data identification.
In other embodiments, the traffic data content may be first associated with each monitoring node in the monitoring path according to the traffic data identification, and then the topology map may be generated according to the path configuration information.
Further, in some embodiments, the topology of the monitoring path may be presented through a visual interface. By displaying the topological graph of the calling relationship between the nodes on the visual interface, the calling relationship among the starting node, the called ending node and the intermediate node between the starting node and the ending node for initiating the service can be intuitively and conveniently presented.
Further, in S403, the monitoring server may further monitor the monitoring path according to the service data content of each node in the monitoring path.
As an embodiment, the monitoring server may perform an aggregation operation according to the service data content of each node to obtain the monitoring index of each node. The aggregation operation herein may be combining, averaging, maximum, minimum, etc. The monitoring index here may be the number of calls, the number of called times, the frequency of calls, the time consuming call, etc.
As a further embodiment, the monitoring index of each edge is obtained according to the monitoring indexes of the start node and the end node of each edge in the monitoring path. The aggregation operation herein may be combining, averaging, maximum, minimum, etc. The monitoring index here may be the number of calls, the number of called times, the frequency of calls, the time consuming call, etc.
For example, the service data is the number of calls, and the service data content corresponding to a1 may be the number of calls of a1 in a period of time, and then the monitoring server may combine the service data content corresponding to a1 in a plurality of periods of time, for example, accumulate to 300, and similarly may combine the service data content corresponding to a2 in a plurality of periods of time, for example, accumulate to 300. Thus, the number of calls index of a1 is 300, and the number of called index of a2 is 300. Further, the call success rate of the edge a may be determined according to the call number index of the a1 and the call number index of the a2, for example, the call number index of the a1 may be divided by the call number index of the a2, that is, 300/300, to obtain the call success rate of the edge a as 100%.
In some embodiments of the application, the method further comprises:
And displaying the monitoring index of each edge through a visual interface. By displaying the monitoring indexes of each side on the visual interface and further combining the topological graph of the monitoring path, a developer can intuitively and conveniently determine the node with the fault, so that the fault can be accurately positioned.
In summary, in the embodiment of the present application, by introducing a report data structure of reporting service data information by a node and a configuration data structure describing a calling relationship and a service data identifier of each node in a path, the node may report service data information based on the report data structure, and further, may associate the service data information reported by the node to each node in the path according to the service data identifier, so as to obtain service data content of each node, thereby performing path monitoring based on the service data content of each node.
Fig. 6 is a path monitoring method according to another embodiment of the present application, which may be applied to the system architecture described in fig. 3, and the path monitoring method is described from the node point of view, and may specifically include at least part of the following steps:
s501, reporting service data information to a monitoring platform, wherein the service data information comprises service data identifiers and service data contents corresponding to the service data identifiers, and the service data identifiers are used for identifying service data of nodes.
Optionally, in some embodiments, the method further comprises:
and receiving configuration information of a monitoring platform, wherein the configuration information is used for configuring a data structure used by a node to report the service data information.
Based on the same inventive concept, the specific implementation of the node side refers to the description of the monitoring server side, and for brevity, the description is omitted here.
Fig. 7 is a schematic structural diagram of a path monitoring apparatus according to an embodiment of the present application. As shown in fig. 7, the path monitoring apparatus 600 may include:
an obtaining unit 601, configured to obtain service data information reported by at least two nodes on a monitoring path and path configuration information of the monitoring path, where the service data information includes a service data identifier and service data content corresponding to the service data identifier, and the path configuration information is used to define a calling relationship of each node in the monitoring path and the service data identifier of each node;
the association unit 602 is configured to associate the service data content reported by the at least two nodes to a corresponding node in the monitoring path according to the service data identifier reported by the at least two nodes and the service data identifier of each node in the path configuration information of the monitoring path, so as to obtain the service data content of each node in the monitoring path;
And the monitoring unit 603 is configured to monitor the monitoring path according to the service data content of each node in the monitoring path.
Optionally, in some embodiments, the path configuration information of the monitoring path includes:
a path identifier of the monitoring path;
an edge identifier, configured to identify an edge included in the monitoring path, where the edge is a connection line between two nodes;
the service data identification;
the starting point identifier is used for identifying whether the node corresponding to the service data identifier is used as the starting node of the edge;
the terminal point identifier is used for identifying whether the node corresponding to the service data identifier is used as a termination node of the edge;
and the connection point identifier is used for identifying whether the node corresponding to the service data identifier is used as a connection node between different edges.
Optionally, in some embodiments, the apparatus 600 further comprises:
the generating unit is used for generating each edge in the monitoring path according to the service data identifier, the edge identifier, the starting point identifier and the end point identifier;
and the determining unit is used for determining the connection relation among the edges according to the service data identifier and the connection point identifier to obtain a topological graph of the monitoring path.
Optionally, in some embodiments, the association module 602 is specifically configured to:
and associating the service data content corresponding to the first service data identifier to the node corresponding to the first service data identifier in the monitoring path.
Optionally, in some embodiments, the apparatus 600 further comprises:
the computing unit is used for carrying out aggregation operation on the business data content of each node in the monitoring path to obtain the monitoring index of each node; and
obtaining monitoring indexes of the edges in the monitoring path according to the monitoring indexes of the starting node and the ending node of each edge in the monitoring path;
the monitoring unit 603 is configured to: and monitoring the monitoring path according to the monitoring index of each side and the monitoring index of each node.
Optionally, in some embodiments, the apparatus 600 further comprises:
the display unit is used for displaying the monitoring index of each side through the visual interface and displaying the topological graph of the monitoring path through the visual interface.
The principle and the beneficial effects of solving the problems provided by the path monitoring device in the embodiment of the application are similar to those of the path monitoring method in the embodiment of the application, and can be referred to the principle and the beneficial effects of implementation of the method, and are not repeated here for brevity of description.
Fig. 8 is a schematic structural view of a path monitoring apparatus according to another embodiment of the present application. As shown in fig. 8, the path monitoring apparatus 700 may include:
and the reporting unit 701 is configured to report service data information to the monitoring platform, where the service data information includes a service data identifier and service data content corresponding to the service data identifier, and the service data identifier is used to identify service data of the node.
Optionally, in some embodiments, the apparatus 700 further comprises:
and the receiving unit is used for receiving the configuration information of the monitoring platform, wherein the configuration information is used for configuring a data structure used by the node for reporting the service data information.
The principle and the beneficial effects of solving the problems provided by the path monitoring device in the embodiment of the application are similar to those of the path monitoring method in the embodiment of the application, and can be referred to the principle and the beneficial effects of implementation of the method, and are not repeated here for brevity of description.
The embodiment of the present application further provides a path monitoring device, as shown in fig. 9, where the path monitoring device 800 includes: a memory 801 for storing a computer program; a processor 802 for invoking the computer program to perform the path monitoring method in the previous embodiment.
Optionally, the memory 801 may also be used to store traffic data information reported by the node and calculated path monitoring data.
Optionally, the path monitoring device 800 may further include a communication interface 803 and a communication bus 804, where the memory 801, the processor 802, and the communication interface 803 may communicate with each other via the communication bus 804. The communication interface 803 may enable communication between the path monitoring apparatus 800 and other devices. For example, the path monitoring device 800 is a monitoring server, and the communication interface 803 may enable communication between the monitoring server and the node.
In one exemplary embodiment, the processor 802 (and in particular the devices contained by the processor) performs the steps of the path monitoring method shown in FIG. 4 by invoking one or more instructions in a memory. In particular, the memory stores one or more first instructions adapted to be loaded by the processor and to perform the steps of:
acquiring service data information reported by at least two nodes on a monitoring path and path configuration information of the monitoring path, wherein the service data information comprises service data identifiers and service data contents corresponding to the service data identifiers, and the path configuration information is used for defining calling relations of all nodes in the monitoring path and the service data identifiers of all nodes;
According to the service data identifiers reported by the at least two nodes and the service data identifiers of all nodes in the path configuration information of the monitoring path, the service data contents reported by the at least two nodes are associated to the corresponding nodes in the monitoring path, so that the service data contents of all nodes in the monitoring path are obtained;
and monitoring the monitoring path according to the service data content of each node in the monitoring path.
In another exemplary embodiment, a processor (and in particular the devices contained by the processor) performs the steps of the path monitoring method shown in fig. 6 by invoking one or more instructions in a memory. In particular, the memory stores one or more second instructions adapted to be loaded by the processor and to perform the steps of:
and reporting service data information to a monitoring platform, wherein the service data information comprises a service data identifier and service data content corresponding to the service data identifier, and the service data identifier is used for identifying service data of a node.
The embodiment of the application also provides a computer readable storage medium for storing a computer program. The computer readable storage medium may be applied to a computer device, and the computer program causes the computer device to execute the corresponding flow in the path monitoring method in the embodiment of the present application, which is not described herein for brevity.
Embodiments of the present application also provide a computer program product comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium and executes the computer instructions to cause the computer device to perform the corresponding content of the method embodiments of fig. 4 to 6 described above.
Embodiments of the present application also provide a computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium and executes the computer instructions to cause the computer device to perform the corresponding content of the method embodiments of fig. 4 to 6 described above.
It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (13)
1. A method of path monitoring, comprising:
acquiring service data information reported by at least two nodes on a monitoring path and path configuration information of the monitoring path, wherein the service data information comprises service data identifiers and service data contents corresponding to the service data identifiers, the path configuration information is used for defining calling relations of all nodes in the monitoring path and the service data identifiers of all nodes, the service data contents are specific contents corresponding to the service data identifiers, and the service data contents change according to actual service use conditions;
according to the service data identifiers reported by the at least two nodes and the service data identifiers of all nodes in the path configuration information of the monitoring path, the service data contents reported by the at least two nodes are associated to the corresponding nodes in the monitoring path, so that the service data contents of all nodes in the monitoring path are obtained;
monitoring the monitoring path according to the service data content of each node in the monitoring path;
the path configuration information of the monitoring path comprises:
A path identifier of the monitoring path;
an edge identifier, configured to identify an edge included in the monitoring path, where the edge is a connection line between two nodes;
the service data identification;
the starting point identifier is used for identifying whether the node corresponding to the service data identifier is used as a starting node of the edge;
the terminal point identifier is used for identifying whether the node corresponding to the service data identifier is used as a termination node of the edge;
and the connection point identifier is used for identifying whether the node corresponding to the service data identifier is used as a connection node between different edges.
2. The method according to claim 1, wherein the method further comprises:
generating each edge in the monitoring path according to the service data identifier, the edge identifier, the starting point identifier and the end point identifier;
and determining the connection relation among the edges according to the service data identifier and the connection point identifier to obtain a topological graph of the monitoring path.
3. The method according to claim 2, wherein the associating the service data content reported by the at least two nodes to the corresponding node in the monitoring path according to the service data identifier of the at least two nodes and the service data identifier of each node in the path configuration information of the monitoring path includes:
And associating the service data content corresponding to the first service data identifier to the node corresponding to the first service data identifier in the monitoring path.
4. A method according to claim 3, wherein monitoring the monitoring path based on the traffic data content of each node in the monitoring path comprises:
performing aggregation operation on the service data content of each node in the monitoring path to obtain a monitoring index of each node;
obtaining monitoring indexes of each side in the monitoring path according to the monitoring indexes of the starting node and the ending node of each side in the monitoring path;
and monitoring the monitoring path according to the monitoring indexes of the sides and the monitoring indexes of each node.
5. The method according to claim 4, wherein the method further comprises:
and displaying the monitoring index of each side through a visual interface.
6. The method according to claim 2, wherein the method further comprises:
and displaying the topological graph of the monitoring path through a visual interface.
7. A path monitoring apparatus, comprising:
The system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring service data information reported by at least two nodes on a monitoring path and path configuration information of the monitoring path, wherein the service data information comprises service data identifiers and service data contents corresponding to the service data identifiers, the path configuration information is used for defining calling relations of all nodes in the monitoring path and the service data identifiers of all nodes, the service data contents are specific contents corresponding to the service data identifiers, and the service data contents are changed according to actual service use conditions;
the association unit is used for associating the service data content reported by the at least two nodes to the corresponding node in the monitoring path according to the service data identifier reported by the at least two nodes and the service data identifier of each node in the path configuration information of the monitoring path to obtain the service data content of each node in the monitoring path;
the monitoring unit is used for monitoring the monitoring path according to the service data content of each node in the monitoring path;
the path configuration information of the monitoring path comprises:
A path identifier of the monitoring path;
an edge identifier, configured to identify an edge included in the monitoring path, where the edge is a connection line between two nodes;
the service data identification;
the starting point identifier is used for identifying whether the node corresponding to the service data identifier is used as a starting node of the edge;
the terminal point identifier is used for identifying whether the node corresponding to the service data identifier is used as a termination node of the edge;
and the connection point identifier is used for identifying whether the node corresponding to the service data identifier is used as a connection node between different edges.
8. The apparatus of claim 7, wherein the apparatus further comprises:
the generating unit is used for generating each edge in the monitoring path according to the service data identifier, the edge identifier, the starting point identifier and the end point identifier;
and the determining unit is used for determining the connection relation among the edges according to the service data identifier and the connection point identifier to obtain a topological graph of the monitoring path.
9. The apparatus according to claim 8, wherein the association unit is specifically configured to:
and associating the service data content corresponding to the first service data identifier to the node corresponding to the first service data identifier in the monitoring path.
10. The apparatus of claim 9, wherein the apparatus further comprises:
the computing unit is used for carrying out aggregation operation on the business data content of each node in the monitoring path to obtain the monitoring index of each node; and
obtaining monitoring indexes of the edges in the monitoring path according to the monitoring indexes of the starting node and the ending node of each edge in the monitoring path;
the monitoring unit is used for: and monitoring the monitoring path according to the monitoring indexes of the sides and the monitoring indexes of each node.
11. The apparatus of claim 10, wherein the apparatus further comprises:
the display unit is used for displaying the monitoring indexes of each side through a visual interface and displaying the topological graph of the monitoring path through the visual interface.
12. A path monitoring apparatus, comprising:
a memory for storing a computer program;
a processor for invoking and running a computer program stored in said memory, performing the method of any of claims 1 to 6.
13. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011409453.1A CN114615169B (en) | 2020-12-03 | 2020-12-03 | Path monitoring method, path monitoring device and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011409453.1A CN114615169B (en) | 2020-12-03 | 2020-12-03 | Path monitoring method, path monitoring device and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114615169A CN114615169A (en) | 2022-06-10 |
| CN114615169B true CN114615169B (en) | 2023-10-20 |
Family
ID=81856944
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011409453.1A Active CN114615169B (en) | 2020-12-03 | 2020-12-03 | Path monitoring method, path monitoring device and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114615169B (en) |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012177213A2 (en) * | 2011-06-20 | 2012-12-27 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and devices for monitoring a data path |
| CN103782552A (en) * | 2013-09-03 | 2014-05-07 | 华为技术有限公司 | Method for protecting service path, controller, device and system |
| WO2015124073A1 (en) * | 2014-02-18 | 2015-08-27 | Tencent Technology (Shenzhen) Company Limited | Process monitoring method, apparatus, and system |
| CN105610594A (en) * | 2014-11-19 | 2016-05-25 | 华为技术有限公司 | Service chain fault diagnosis method and service chain fault diagnosis device |
| WO2017132947A1 (en) * | 2016-02-04 | 2017-08-10 | 华为技术有限公司 | Method for acquiring security parameters of to-be-transmitted service, signalling management network element, security function node and transmitting terminal |
| CN107086940A (en) * | 2017-03-31 | 2017-08-22 | 北京奇艺世纪科技有限公司 | A kind of single service operation method and device |
| CN107992398A (en) * | 2017-12-22 | 2018-05-04 | 宜人恒业科技发展（北京）有限公司 | The monitoring method and monitoring system of a kind of operation system |
| CN109039738A (en) * | 2018-08-01 | 2018-12-18 | 北京广利核系统工程有限公司 | The configuration of the DCS network equipment and monitoring method, device, maintenance node and terminal |
| CN109495302A (en) * | 2018-11-16 | 2019-03-19 | 北京车和家信息技术有限公司 | Link monitoring method, cloud server and computer readable storage medium |
| CN109495335A (en) * | 2017-09-12 | 2019-03-19 | 阿里巴巴集团控股有限公司 | Business monitoring method, device, system and electronic equipment |
| CN109873717A (en) * | 2019-01-18 | 2019-06-11 | 深圳壹账通智能科技有限公司 | Monitoring method, device, computer equipment and storage medium |
| CN110120878A (en) * | 2018-02-05 | 2019-08-13 | 华为技术有限公司 | The method and apparatus for obtaining link-quality |
| CN110120887A (en) * | 2019-04-25 | 2019-08-13 | 新华三技术有限公司合肥分公司 | A kind of network quality information monitoring method, electronic equipment and storage medium |
| CN110442641A (en) * | 2019-08-06 | 2019-11-12 | 中国工商银行股份有限公司 | A kind of link topology figure methods of exhibiting, device, storage medium and equipment |
| CN110752952A (en) * | 2019-10-25 | 2020-02-04 | 腾讯科技（深圳）有限公司 | Network fault positioning method and device, network equipment and computer storage medium |
| CN110855473A (en) * | 2019-10-16 | 2020-02-28 | 平安科技（深圳）有限公司 | Monitoring method, device, server and storage medium |
| CN111224843A (en) * | 2019-12-31 | 2020-06-02 | 北京百度网讯科技有限公司 | Resource link monitoring method, device, equipment and storage medium |
| CN111598382A (en) * | 2020-04-01 | 2020-08-28 | 深圳壹账通智能科技有限公司 | Service chain data checking method and device based on block chain, storage medium and electronic equipment |
| CN111682982A (en) * | 2020-06-03 | 2020-09-18 | 北京东土军悦科技有限公司 | Path fault detection method, device, equipment, system and storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090161658A1 (en) * | 2007-12-19 | 2009-06-25 | Solar Winds.Net | Method for selecting VOIP call path to monitor |
| US8838781B2 (en) * | 2010-07-15 | 2014-09-16 | Cisco Technology, Inc. | Continuous autonomous monitoring of systems along a path |
| US9294944B2 (en) * | 2012-12-21 | 2016-03-22 | International Business Machines Corporation | Method and apparatus to monitor and analyze end to end flow control in an Ethernet/enhanced Ethernet environment |
| US20150117244A1 (en) * | 2013-10-30 | 2015-04-30 | Fluke Corporation | Methods to visualize time-aligned data flow between nodes in a communication network |
-
2020
- 2020-12-03 CN CN202011409453.1A patent/CN114615169B/en active Active
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012177213A2 (en) * | 2011-06-20 | 2012-12-27 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and devices for monitoring a data path |
| CN103782552A (en) * | 2013-09-03 | 2014-05-07 | 华为技术有限公司 | Method for protecting service path, controller, device and system |
| WO2015124073A1 (en) * | 2014-02-18 | 2015-08-27 | Tencent Technology (Shenzhen) Company Limited | Process monitoring method, apparatus, and system |
| CN105610594A (en) * | 2014-11-19 | 2016-05-25 | 华为技术有限公司 | Service chain fault diagnosis method and service chain fault diagnosis device |
| WO2017132947A1 (en) * | 2016-02-04 | 2017-08-10 | 华为技术有限公司 | Method for acquiring security parameters of to-be-transmitted service, signalling management network element, security function node and transmitting terminal |
| CN107086940A (en) * | 2017-03-31 | 2017-08-22 | 北京奇艺世纪科技有限公司 | A kind of single service operation method and device |
| CN109495335A (en) * | 2017-09-12 | 2019-03-19 | 阿里巴巴集团控股有限公司 | Business monitoring method, device, system and electronic equipment |
| CN107992398A (en) * | 2017-12-22 | 2018-05-04 | 宜人恒业科技发展（北京）有限公司 | The monitoring method and monitoring system of a kind of operation system |
| CN110120878A (en) * | 2018-02-05 | 2019-08-13 | 华为技术有限公司 | The method and apparatus for obtaining link-quality |
| CN109039738A (en) * | 2018-08-01 | 2018-12-18 | 北京广利核系统工程有限公司 | The configuration of the DCS network equipment and monitoring method, device, maintenance node and terminal |
| CN109495302A (en) * | 2018-11-16 | 2019-03-19 | 北京车和家信息技术有限公司 | Link monitoring method, cloud server and computer readable storage medium |
| CN109873717A (en) * | 2019-01-18 | 2019-06-11 | 深圳壹账通智能科技有限公司 | Monitoring method, device, computer equipment and storage medium |
| WO2020147419A1 (en) * | 2019-01-18 | 2020-07-23 | 深圳壹账通智能科技有限公司 | Monitoring method and apparatus, computer device and storage medium |
| CN110120887A (en) * | 2019-04-25 | 2019-08-13 | 新华三技术有限公司合肥分公司 | A kind of network quality information monitoring method, electronic equipment and storage medium |
| CN110442641A (en) * | 2019-08-06 | 2019-11-12 | 中国工商银行股份有限公司 | A kind of link topology figure methods of exhibiting, device, storage medium and equipment |
| CN110855473A (en) * | 2019-10-16 | 2020-02-28 | 平安科技（深圳）有限公司 | Monitoring method, device, server and storage medium |
| CN110752952A (en) * | 2019-10-25 | 2020-02-04 | 腾讯科技（深圳）有限公司 | Network fault positioning method and device, network equipment and computer storage medium |
| CN111224843A (en) * | 2019-12-31 | 2020-06-02 | 北京百度网讯科技有限公司 | Resource link monitoring method, device, equipment and storage medium |
| CN111598382A (en) * | 2020-04-01 | 2020-08-28 | 深圳壹账通智能科技有限公司 | Service chain data checking method and device based on block chain, storage medium and electronic equipment |
| CN111682982A (en) * | 2020-06-03 | 2020-09-18 | 北京东土军悦科技有限公司 | Path fault detection method, device, equipment, system and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114615169A (en) | 2022-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8819241B1 (en) | System and method for a self service portal and automation for internally hosted virtual server resources | |
| CN111104635B (en) | Method and device for generating form webpage | |
| CN104395884A (en) | Tiers of data storage for web applications and browser extensions | |
| CN112867988A (en) | Implementing compliance settings by a mobile device to follow a configuration scenario | |
| WO2019134340A1 (en) | Salary calculation method, application server, and computer readable storage medium | |
| CN109885786B (en) | Data caching processing method and device, electronic equipment and readable storage medium | |
| CN108289034B (en) | A kind of fault discovery method and apparatus | |
| US9875137B2 (en) | Intelligent application back stack management | |
| CN111309593A (en) | JSON interface verification method, device and equipment and computer readable storage medium | |
| CN112202617B (en) | Resource management system monitoring method, device, computer equipment and storage medium | |
| CN110555014B (en) | Data migration method and system, electronic device and storage medium | |
| CN114615169B (en) | Path monitoring method, path monitoring device and computer readable storage medium | |
| CN106790380A (en) | Data reporting method and device | |
| CN109032693A (en) | Method and device for loading display information, electronic equipment and readable storage medium | |
| CN108664343A (en) | A kind of stateful call method and device of micro services | |
| CN112540808B (en) | Recording method of program behavior hierarchy call relationship and related equipment | |
| CN110362294A (en) | Development task executes method, apparatus, electronic equipment and storage medium | |
| US20170316035A1 (en) | Rule-governed entitlement data structure change notifications | |
| CN106649370B (en) | The acquisition methods and device of website access information | |
| JP7422699B2 (en) | Data distribution intermediary system and data distribution intermediary method | |
| CN116431275B (en) | Tolerance configuration method, device, computer equipment and storage medium | |
| CN112235451B (en) | Method and device for providing alarm about deleted contact | |
| CN110347748B (en) | Data verification method, system, device and equipment based on inverted index | |
| CN114386838A (en) | Index configuration method and device, computer equipment and computer readable storage medium | |
| CN116633774A (en) | Platform address configuration method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |