CN113792008A - Method and device for acquiring network topology structure, electronic equipment and storage medium - Google Patents
Method and device for acquiring network topology structure, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113792008A CN113792008A CN202111016589.0A CN202111016589A CN113792008A CN 113792008 A CN113792008 A CN 113792008A CN 202111016589 A CN202111016589 A CN 202111016589A CN 113792008 A CN113792008 A CN 113792008A
- Authority
- CN
- China
- Prior art keywords
- program
- connection
- module
- instance
- network topology
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/163—Interprocessor communication
- G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
Abstract
The present disclosure provides a method and an apparatus for obtaining a network topology, an electronic device and a storage medium, which relate to the field of computer technologies and further relate to the field of network topologies, and at least solve the technical problem that the existing solution cannot accurately construct and timely update a network topology composed of large-scale program modules in a computer complex system. The specific implementation scheme is as follows: collecting connection type data of a computer system; generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service; identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship; and determining node information in the first program service network topology structure based on the identification information of each program module in the plurality of program modules, and determining side information in the first program service network topology structure based on the connection relationship to obtain the first program service network topology structure.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and further relates to the field of network topologies, and in particular, to a method and an apparatus for acquiring a network topology, an electronic device, and a storage medium.
Background
In a computer complex system, program modules can access each other through a network, the network topology structure among the program modules is efficiently and accurately identified, and the method has important significance for network problem investigation, system rapid copying and migration and system global information grasping.
In the existing scheme, a network topology structure in a complex system is acquired and maintained by adopting manual experience, but with the micro-service of an internet architecture, the number of program modules in the complex system is further expanded, and the perception difficulty of the overall architecture of the complex system is further increased.
Disclosure of Invention
The disclosure provides a method and a device for acquiring a network topology structure, electronic equipment and a storage medium, which are used for at least solving the technical problem that the existing scheme cannot accurately construct and timely update the network topology structure formed by large-scale program modules in a computer complex system.
According to an aspect of the present disclosure, a method for acquiring a network topology is provided, including: collecting connection type data of a computer system, wherein the computer system comprises: a plurality of program modules, each program module of the plurality of program modules for initiating a plurality of instances, the connection type data comprising: the remote call connection relation acquired by each program module and the module connection relation acquired from the service network system; generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service; identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship; and determining node information in the first program service network topology structure based on the identification information of each program module in the plurality of program modules, and determining side information in the first program service network topology structure based on the connection relationship to obtain the first program service network topology structure.
According to another aspect of the present disclosure, there is provided an apparatus for acquiring a network topology, including: the acquisition module is used for acquiring connection type data of a computer system, wherein the computer system comprises: a plurality of program modules, each program module of the plurality of program modules for initiating a plurality of instances, the connection type data comprising: the remote call connection relation acquired by each program module and the module connection relation acquired from the service network system; a generation module for generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service; an identification module for identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship; the acquisition module is used for determining node information in the first program service network topological structure based on the identification information of each program module in the plurality of program modules, and determining side information in the first program service network topological structure based on the connection relation to obtain the first program service network topological structure.
According to still another aspect of the present disclosure, there is provided an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform any of the above described methods of network topology acquisition.
According to yet another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the method of acquiring a network topology of any one of the above.
According to yet another aspect of the present disclosure, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the method of acquiring a network topology of any of the above.
In the present disclosure, by collecting connection type data of a computer system; generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service; identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship; the node information in the first program service network topological structure is determined based on the identification information of each program module in the plurality of program modules, the side information in the first program service network topological structure is determined based on the connection relation, the first program service network topological structure is obtained, the purpose of efficiently sensing the whole framework of the computer complex system is achieved, the technical effect of accurately constructing and timely updating the network topological structure formed by large-scale program modules in the computer complex system is achieved, and the technical problem that the network topological structure formed by large-scale program modules in the computer complex system cannot be accurately constructed and timely updated in the existing scheme is solved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
fig. 1 is a hardware configuration block diagram of a computer terminal (or mobile device) for implementing an acquisition method of a network topology according to an embodiment of the present disclosure;
fig. 2 is a flowchart of a method for acquiring a network topology according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a module connection relationship based on a service grid according to an embodiment of the present disclosure;
FIG. 4 is a schematic representation of identification information for a downstream instance in accordance with embodiments of the present disclosure;
fig. 5 is a schematic diagram of a network topology acquisition method according to an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of a network topology based on dispatch log retrieval in accordance with an embodiment of the present disclosure;
fig. 7 is a schematic diagram of a method for acquiring a network topology according to another embodiment of the present disclosure;
FIG. 8 is a schematic diagram of a network topology acquisition system according to an embodiment of the present disclosure;
fig. 9 is a block diagram of an apparatus for acquiring a network topology according to an embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Some of the nouns or terms appearing in the description of the embodiments of the present application are applicable to the following explanations:
a computer system: the computer system is usually composed of a plurality of computer program modules, for example, program module a calls program module B, and program module B calls program module C, so that program module a, program module B, and program module C together form a computer system capable of providing complete functions, and common computer systems include information systems, website programs, search engines, and the like.
A program module: a computer program, which may also be referred to as a program Service (Service), is a computer program that can implement certain local functions, such as providing a user registration function, a user query function, etc., and may be implemented using a computer program to constitute a program module.
Example (c): in an actual production environment, a program module is started by a plurality of same computer programs, each started computer program becomes an instance Server, and the use of multiple instances by the program module is generally used for dispersing the processing pressure of the computer programs and can also achieve certain redundancy mutual backup.
Name Service (NS): for the same set of functionally identical instances, the names used in grouping and identifying represent the location of the instances in the system. The name service is generally used for addressing between program modules, that is, when a program module a calls a program module B, the name service is queried by the name of the program module B, and a network address where each instance in the program module B is located is obtained, where the network address includes an Internet Protocol (IP) address and PORT (PORT) information.
In the existing scheme, the network topology structure in the computer complex system is generally obtained by adopting the following two ways:
the first scheme is as follows: the method comprises the steps of dividing a computer complex system to form a plurality of subsystems, combing and drawing network topological structures of dozens of program modules in the subsystems manually, maintaining the changing conditions of the topological structures in the subsystems periodically, and finally summarizing and combining topological information of the subsystems to form a complex system network topological structure maintained by means of manual experience.
Firstly, when a network topology structure formed by a large number of program modules is constructed, a complex system is refined and disassembled, and local topology structure information is given by means of manual experience after a subsystem is disassembled. The method has higher requirements on manual experience, and needs to spend more human resources for topology maintenance; secondly, the perception of the topology change of some specific program services by adopting manual experience is slow, and the legacy and error information is easy to exist, so that the topology information of the program services is incorrect and is not updated timely.
Scheme II: in a computer complex system, the same network acquisition component is integrated for each computer program, remote calling of each downstream network is carried out for embedded point acquisition and acquisition through the network acquisition component embedded into the computer program, and the network acquisition component reports connection information to an acquisition center node to acquire a network topology structure of the complex system.
In the scheme II, each computer program is modified and designed through the unified assembly, different network acquisition assemblies are required to be provided for the computer programs under different programming languages, and the added network acquisition assemblies bring potential risks to the original functions of the computer programs. For example, compatibility issues with the original computer program cause program service to function abnormally. In addition, after the computer program integrates the network acquisition component, explicit calling needs to be performed for the upstream and downstream of each topology structure to ensure that the topology structure data is collected, and if the network acquisition component is not explicitly called for the downstream program service in the computer program, the topology data is omitted. Moreover, the second scheme strongly depends on the development of computer program logic, and brings more work and cost to program maintenance when being implemented for a long time.
The prior art can not accurately construct and timely update a network topology structure consisting of a plurality of program modules in a computer complex system.
In accordance with an embodiment of the present disclosure, a method for acquiring a network topology is provided, it should be noted that the steps illustrated in the flowchart of the figure may be executed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowchart, in some cases, the steps illustrated or described may be executed in an order different from that here.
The method embodiments provided by the embodiments of the present disclosure may be executed in a mobile terminal, a computer terminal or similar electronic devices. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein. Fig. 1 shows a hardware configuration block diagram of a computer terminal (or mobile device) for implementing the network topology acquisition method.
As shown in fig. 1, the computer terminal 100 includes a computing unit 101 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)102 or a computer program loaded from a storage unit 108 into a Random Access Memory (RAM) 103. In the RAM 103, various programs and data necessary for the operation of the computer terminal 100 can also be stored. The computing unit 101, the ROM 102, and the RAM 103 are connected to each other via a bus 104. An input/output (I/O) interface 105 is also connected to bus 104.
A number of components in the computer terminal 100 are connected to the I/O interface 105, including: an input unit 106 such as a keyboard, a mouse, and the like; an output unit 107 such as various types of displays, speakers, and the like; a storage unit 108, such as a magnetic disk, optical disk, or the like; and a communication unit 109 such as a network card, modem, wireless communication transceiver, etc. The communication unit 109 allows the computer terminal 100 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.
Various implementations of the systems and techniques described here can be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
It should be noted that in some alternative embodiments, the computer terminal shown in fig. 1 may include hardware elements (including circuitry), software elements (including computer code stored on a computer-readable medium), or a combination of both hardware and software elements. It should be noted that fig. 1 is only one example of a particular specific example and is intended to illustrate the types of components that may be present in the electronic device described above.
In the above operating environment, the present disclosure provides a method for acquiring a network topology as shown in fig. 2, which may be executed by a computer terminal or similar electronic device as shown in fig. 1. Fig. 2 is a flowchart of a method for acquiring a network topology according to an embodiment of the present disclosure. As shown in fig. 2, the method may include the steps of:
step S21, collecting the connection type data of the computer system;
wherein, the computer system includes: a plurality of program modules, each program module of the plurality of program modules for initiating a plurality of instances, the connection type data comprising: the remote call connection relation acquired by each program module and the module connection relation acquired from the service network system.
Optionally, the connection type data of the computer system is collected by index reporting and data polling. Specifically, the index reporting mainly obtains the remote call connection relation of each program module through a network acquisition component in each computer program; the data polling is to obtain the module connection relation in the service grid according to the pre-configured query task. Wherein a service grid is a sub-network of a portion of the network having program modules of the service grid components.
For example, in network communication of cloud computer programs, an instance of each program application uses a Remote Procedure Call (RPC) to perform network communication, data required for constructing a topology based on the network communication includes two dimensions of an instance and a name service, and a connection relationship of the Remote Call that can be obtained is shown in table 1. In table 1, the remote invocation connection relation includes the IP and IP where the instance is located, the IP and NS, and the connection relation between the NS and NS, and the remote invocation relation can be described by the starting point and the ending point.
Table 1 remote invocation relationship based on network communication acquisition
| Type (B) | Type description | Starting point upstream | Destination downstream |
| Type-1 | IP-2-IP | IP-A:PORT | IP-B:PORT |
| Type-2 | IP-2-NS | IP-A:PORT | NS-B |
| Type-3 | NS-2-NS | NS-A | NS-B |
For another example, fig. 3 is a schematic diagram of a module connection relationship based on a service grid according to an embodiment of the present disclosure. As shown in fig. 3, the service grid is used in a cloud-native architecture to solve service module call relation management in a complex system, and provides services for three program modules X, Y, Z in a constituent computer system. The module X accesses the calling module Y, the module Y accesses the calling module Z, service grid services are deployed in service instances of the module X and the module Y, and the service grid services are responsible for managing calling access relations between the module X and the module Y. Collecting and reporting network connection data of program service X- > Y and program service Y- > Z from service grids of the module X and the module Y, using the network connection data as topological connection between service topologies NS, and further determining that the connection relation of the modules is the module X- > module Y- > module Z through module mapping information.
Step S22, generating a reverse mapping relation between each instance of the plurality of program modules and the corresponding program module based on the name service;
the program modules and the NS are in one-to-one mapping relationship, the program modules and the instances are in one-to-many mapping relationship, and the reverse mapping relationship is the mapping relationship from each instance to the corresponding program module.
For example, the inverse mapping relationship of each instance of the plurality of program modules to the corresponding program module generated based on the name service may be as shown in Table 2.
TABLE 2 program Module mapping Table
In particular, the implementation process of generating the reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service may refer to the further description of the embodiments of the present disclosure.
Step S23, identifying the connection relation among the program modules by using the connection type data and the reverse mapping relation;
in particular, an implementation process for identifying connection relationships between multiple program modules using connection type data and inverse mapping relationships may be referred to in further detail in connection with the embodiments of the disclosure.
Step S24, determining node information in the first program service network topology based on the identification information of each of the plurality of program modules, and determining side information in the first program service network topology based on the connection relationship, to obtain the first program service network topology.
Optionally, the side information of the first program service network topology is evaluated to obtain a side confidence, and the first program service network topology is obtained according to the side confidence and the point information of the first program service network topology.
In particular, the implementation process of determining the side information in the first program service network topology based on the connection relationship may refer to further descriptions of the embodiments of the present disclosure.
According to the present disclosure, the connection type data of the computer system is collected from the steps S21 to S24; generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service; identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship; the node information in the first program service network topological structure is determined based on the identification information of each program module in the plurality of program modules, the side information in the first program service network topological structure is determined based on the connection relation, the first program service network topological structure is obtained, the purpose of efficiently sensing the whole framework of the computer complex system is achieved, the technical effect of accurately constructing and timely updating the network topological structure formed by large-scale program modules in the computer complex system is achieved, and the technical problem that the network topological structure formed by large-scale program modules in the computer complex system cannot be accurately constructed and timely updated in the existing scheme is solved.
The above-described method of this embodiment is further described below.
As an optional implementation manner, the method for acquiring a network topology further includes:
step S25, outputting the first program service network topology.
Alternatively, the output first program service network topology can be directly provided to the external demand application party, for example, the external demand party may include building architecture topology awareness, service grid display, system stability construction, and the like.
Optionally, the system core index is added to the output first program service network topology structure, and a system architecture topology map is obtained. The system core index may include one or more of a system memory, a response time, a node name, a data transmission speed between interconnected nodes, the number of nodes in each subsystem, a starting node of a service topology, and a topology depth.
For example, a system core index is added in the output first program service network topology structure, different states of network nodes are displayed according to different system core indexes, and different colors can be adopted for dynamic data conditions of the nodes and the connecting edges in the network topology structure, so that the dynamic data conditions are provided for scenes such as external pressure testing, machine room construction, connection testing and the like.
As an optional implementation manner, the method for acquiring a network topology further includes:
step S26, adding auxiliary configuration information for the first program service network topological structure to obtain a second program service network topological structure;
the auxiliary configuration information may be label information associated with the first program service network topology structure, and the auxiliary configuration information may be used to supplement the first program service network topology structure. For example, the auxiliary configuration information may include manually labeled blacklist auxiliary information and whitelist auxiliary information.
For example, as shown in table 3, the auxiliary configuration information may include manually labeled blacklist auxiliary information and whitelist auxiliary information. The manually labeled topological edge types comprise connection white lists, connection black lists and other types, actual weighted confidence evaluation of the program modules is carried out by combining connection type data when the network topological structure is obtained, the priority weights of module connection are determined according to evaluation results, and finally a second program service network topological structure is obtained, wherein the priority of the manually labeled auxiliary configuration information is higher than the evaluation results of the confidence.
In table 3, the confidence between the module a and the module B is 100, and the topology edge types of the module a and the module B are white lists, that is, the connection relationship between the module a and the module B can be set manually; the confidence between the module A and the module E is 100, but the topological side types of the module A and the module E are blacklists, namely the module A and the module E can not be connected by manual setting; the confidence between the module B and the module C is 99, but the topology edge types of the module B and the module C are automatic, namely whether the module B is connected with the module C or not can be automatically judged according to a preset confidence threshold value, and the confidence threshold value can be flexibly adjusted in real time. For example, confidence > 80 is set as trustworthy, and confidence below <50 is set as untrustworthy.
TABLE 3 manually labeled blacklist and whitelist assistance information
| Type (B) | Starting point upstream | Destination downstream | Confidence reliability |
| White list | module-A | module- |
100 |
| Black list | module-A | module- |
100 |
| Automatic | module-B | module-C | 99 |
Step S27, outputting the second program service network topology.
As an alternative embodiment, the identifying the connection relationship between the plurality of program modules using the connection type data and the inverse mapping relationship at step S23 includes:
step S231, obtaining original instance data information by using the connection type data;
where the original instance data includes the IP and PORT information of the instance.
Step S232, acquiring a connection relation based on the reverse mapping relation and the original instance data information.
As an alternative implementation, in step S231, the obtaining of the original instance data information by using the connection type data includes:
step S2311, selecting a target program module from the plurality of program modules using the connection type data;
step S2312, a plurality of instances corresponding to the target program module are obtained through the name service of the target program module;
step S2313, identification information of an upstream instance and a downstream instance connected to each of the multiple instances is obtained.
The identification information of the upstream instance and the downstream instance includes IP and PORT information of the upstream instance and the downstream instance. For example, the identification information of FIG. 4 for the downstream instance includes a network communication data indicator of the computer program service instance, which may be used to calculate connection relationships and connection counts between program modules. In fig. 4, the network communication data indicators for the computer program service instance include creation time, remote end, Secure Sockets Layer (SSL), protocol, byte transfer speed, etc.
As an alternative implementation manner, in step S232, acquiring the connection relationship based on the inverse mapping relationship and the original instance data information includes:
step S2321, determining an upstream connection relationship, an upstream connection count, a downstream connection relationship and a downstream connection count of each instance in the multiple instances according to the identification information of the upstream instance and the downstream instance connected to each instance in the multiple instances;
the upstream connection relation is a connection relation between each instance in the multiple instances and an adjacent upstream instance, the downstream connection relation is a connection relation between each instance in the multiple instances and an adjacent downstream instance, the upstream connection count is used for determining a confidence degree that a topologic relationship exists between the target program module and an upstream program module corresponding to the upstream instance, and the downstream connection count is used for determining a confidence degree that a topologic relationship exists between the target program module and a downstream program module corresponding to the downstream instance.
Step S2322, a connection relationship is obtained based on the reverse mapping relationship, the upstream connection relationship of each instance of the multiple instances, the upstream connection count, the downstream connection relationship, and the downstream connection count.
For example, the obtained connection relationship may be as shown in table 4. In the connection relation construction, some newly added program modules at the downstream can be found, the newly found modules are marked as unknown (unknown) and recorded as new node discovery, the new node discovery is fed back and recorded into the configuration platform system, and the modules are promoted to be identified and added perfectly according to the unknown connection quantity of each module. For example, module-B → unknown in table 3 represents that a potential unknown module needs to be mined from module B, and updated and added to the connection relationship of the network topology after being confirmed by platform audit.
TABLE 4 connection relationships of program modules
An implementation of identifying connection relationships between multiple program modules using connection type data and inverse mapping relationships is described below in conjunction with FIG. 5. Fig. 5 is a schematic diagram of a network topology acquisition method according to an embodiment of the present disclosure. As shown in fig. 5, connection type data is obtained first, and is used to identify the connection relationship between modules by constructing a reverse mapping relationship table (such as table 2) of instance- > module and NS- > module. In the method for acquiring a network topology of the present disclosure, the upstream start point of the connection relationship is represented by upstream, and the downstream end point is represented by downstream, and the connection relationship of the program modules as shown in table 4 can be obtained by solving the pair-wise combination relationship of F (upstream).
As an alternative embodiment, in step S22, the generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service includes: and generating a reverse mapping relation between each instance and the corresponding program module based on the name service every preset time interval, wherein the preset time interval is used for determining the effective time interval of the reverse mapping relation. The effective duration of the reverse mapping relation is set, namely the reverse mapping relation can be timely reconstructed after being invalid, so that useless data which are invalid can be eliminated regularly, and the updated network topology structure can be timely obtained.
For example, the preset duration may be 10 minutes, a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module is generated based on the name service, and after the first round of reverse mapping relationship is generated, reconstruction is performed every 10 minutes, so as to update the network topology in time.
As an alternative embodiment, the determining the side information in the first program service network topology based on the connection relationship at step S24 includes:
step S241, selecting any one program module from the plurality of program modules as an upstream node based on the connection relationship;
step S242, sequentially searching for adjacent downstream nodes from the upstream node, and constructing a topology edge of the program service network topology structure between the upstream node and the adjacent downstream node to obtain edge information in the program service network topology structure.
As an alternative embodiment, in step S21, the collecting the connection type data of the computer system includes: connection type data is obtained using a dispatch log between a plurality of program modules.
The dispatch log among the program modules includes log name, time, NS of the downstream program module, downstream instance, access unique ID tag, and access time.
For example, the connection type data of the IP-2-NS can be obtained according to the IP of the module A and the NS of the downstream module in the dispatch log of the module A. Fig. 6 is a schematic diagram of a network topology obtained based on a scheduling log according to an embodiment of the present disclosure, and as shown in fig. 6, a connection relationship with a step length of 1 may be generated by using the scheduling log of a module a, an upstream module a- > a downstream module B is started, and scheduling log analysis is performed on the downstream module in sequence recursively, so as to obtain further connection relationships, for example, the upstream module B- > the downstream module F, the upstream module F- > the downstream module G, and the upstream module G- > the downstream module H. And acquiring connection type data according to the multi-step long connection relation obtained by each analysis, and further acquiring the network topology structure of the computer system.
The method for acquiring the network topology structure can support more customization capabilities on the upper layer of the service topology. For example, processing capabilities such as start point selection, topology depth, module consolidation exposure, and the like may be supported. The method for acquiring the network topology structure can realize the mutual access of thousands of program modules in a complex system, and correctly and efficiently identify the network topology structure among the program modules, thereby having important roles in network problem investigation, system rapid copy and migration and system global information grasping.
Fig. 7 is a schematic diagram of a network topology acquisition method according to an embodiment of the present disclosure. As shown in fig. 7, in the process of constructing a computer service topology, data is first introduced through topology acquisition, node discovery and connection relation discrimination are realized through analyzing and identifying policies, and the connection relation identified through calculation is actively updated into a network topology structure. Meanwhile, the artificial experience is used as auxiliary supplement, the auxiliary intervention of the connection relation is carried out through the platform, the artificial experience configuration is generated, finally, the artificial experience configuration and the analyzed and identified topology form the overall topology data of the system, the network topology structure can be obtained by combining with the system indexes, and finally, the network topology structure is provided for multi-party application. For example, currently, the number of nodes covering a service topology exceeds 10000 when the method is applied to a search engine, an information flow recommendation system and a cloud service system, and each node supports more than 1500 topology index data.
The various implementations shown in fig. 7 are further described below in conjunction with fig. 8.
Fig. 8 is a schematic diagram of a network topology acquisition system according to an embodiment of the present disclosure. As shown in fig. 8, the system mainly includes five execution components, namely, data acquisition, module analysis, analysis and identification, topology construction, and topology data output.
The data acquisition component can be used for acquiring connection type data of the computer system; the module parsing component is operable to generate a reverse mapping relationship of each instance of the plurality of program modules to a corresponding program module based on the name service; the analysis recognition component is operable to recognize a connection relationship between the plurality of program modules using the connection type data and the inverse mapping relationship; the topology construction component may be configured to determine node information in the first program service network topology based on the identification information of each of the plurality of program modules, and determine side information in the first program service network topology based on the connection relationship, to obtain a first program service network topology; the topology data output component can be configured to output either the first programmatic service network topology or the second programmatic service network topology. By using the system shown in fig. 8 to obtain the network topology structure, dynamic update of the topology information of the service program can be realized, meanwhile, the influence of intrusion modification on the existing service program can be avoided, and the technical defect of artificial experience-assisted topology construction is overcome.
In the present disclosure, by collecting connection type data of a computer system; generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service; identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship; the node information in the first program service network topological structure is determined based on the identification information of each program module in the plurality of program modules, the side information in the first program service network topological structure is determined based on the connection relation, the first program service network topological structure is obtained, the purpose of efficiently sensing the whole framework of the computer complex system is achieved, the technical effect of accurately constructing and timely updating the network topological structure formed by large-scale program modules in the computer complex system is achieved, and the technical problem that the network topological structure formed by large-scale program modules in the computer complex system cannot be accurately constructed and timely updated in the existing scheme is solved.
In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations and do not violate the good customs of the public order.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device) to execute the methods according to the embodiments of the present disclosure.
The present disclosure further provides a device for acquiring a network topology, where the device is used to implement the foregoing embodiments and preferred embodiments, and the description of the device that has been already made is omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 9 is a block diagram of an apparatus for acquiring a network topology according to an embodiment of the present disclosure, and as shown in fig. 9, the apparatus 900 for acquiring a network topology includes: the device comprises an acquisition module 901, a generation module 902, an identification module 903 and an acquisition module 904.
An acquisition module 901, configured to acquire connection type data of a computer system, where the computer system includes: a plurality of program modules, each program module of the plurality of program modules for initiating a plurality of instances, the connection type data comprising: the remote call connection relation acquired by each program module and the module connection relation acquired from the service network system;
a generating module 902, configured to generate a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service;
an identifying module 903 for identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship;
an obtaining module 904, configured to determine node information in the first program service network topology structure based on the identification information of each program module in the plurality of program modules, and determine side information in the first program service network topology structure based on the connection relationship, so as to obtain the first program service network topology structure.
Optionally, the obtaining apparatus 900 of the network topology further includes: a first output module 905, configured to output the first program service network topology.
Optionally, the obtaining apparatus 900 of the network topology further includes: an auxiliary module 906, configured to add auxiliary configuration information to the first program service network topology structure to obtain a second program service network topology structure, where the auxiliary configuration information is label information associated with the first program service network topology structure; a second output module 907 for outputting the second program service network topology.
Optionally, the identifying module 903, configured to identify a connection relationship between a plurality of program modules by using the connection type data and the inverse mapping relationship, includes: acquiring original example data information by using the connection type data; and acquiring the connection relation based on the reverse mapping relation and the original instance data information.
Optionally, the obtaining of the original instance data information by using the connection type data includes: selecting a target program module from the plurality of program modules using the connection type data; acquiring a plurality of instances corresponding to the target program module through the name service of the target program module; identification information of an upstream instance and a downstream instance connected to each instance in the plurality of instances is obtained.
Optionally, obtaining the connection relationship based on the reverse mapping relationship and the original instance data information includes: determining an upstream connection relationship, an upstream connection count, a downstream connection relationship and a downstream connection count of each instance in the multiple instances according to identification information of an upstream instance and a downstream instance connected with each instance in the multiple instances, wherein the upstream connection relationship is the connection relationship between each instance in the multiple instances and an adjacent upstream instance, the downstream connection relationship is the connection relationship between each instance in the multiple instances and an adjacent downstream instance, the upstream connection count is used for determining a confidence that a topologic relationship exists between the target program module and an upstream program module corresponding to the upstream instance, and the downstream connection count is used for determining a confidence that a topologic relationship exists between the target program module and a downstream program module corresponding to the downstream instance; and acquiring the connection relation based on the reverse mapping relation, the upstream connection relation of each instance in the multiple instances, the upstream connection count, the downstream connection relation and the downstream connection count.
Optionally, the generating module 902, configured to generate a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service, includes: and generating a reverse mapping relation between each instance and the corresponding program module based on the name service every preset time interval, wherein the preset time interval is used for determining the effective time interval of the reverse mapping relation.
Optionally, the obtaining module 904, configured to determine, based on the connection relationship, side information in the first program service network topology, includes: selecting any program module from the plurality of program modules as an upstream node based on the connection relationship; and sequentially searching adjacent downstream nodes from the upstream node, and constructing a topology edge of the program service network topology structure between the upstream node and the adjacent downstream nodes to obtain edge information in the program service network topology structure.
Optionally, the acquiring module 901, configured to acquire connection type data of the computer system, includes: connection type data is obtained using a dispatch log between a plurality of program modules.
It should be noted that, the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.
According to an embodiment of the present disclosure, there is also provided an electronic device including a memory having stored therein computer instructions and at least one processor configured to execute the computer instructions to perform the steps in any of the above method embodiments.
Optionally, the electronic device may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:
s1, collecting the connection type data of the computer system;
s2, generating a reverse mapping relation between each instance in the program modules and the corresponding program module based on the name service;
s3, identifying the connection relation among the program modules by using the connection type data and the reverse mapping relation;
s4, determining node information in the first program service network topology based on the identification information of each of the plurality of program modules, and determining side information in the first program service network topology based on the connection relationship, to obtain a first program service network topology.
Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.
According to an embodiment of the present disclosure, there is also provided a non-transitory computer readable storage medium having stored therein computer instructions, wherein the computer instructions are arranged to perform the steps in any of the above method embodiments when executed.
Alternatively, in the present embodiment, the above-mentioned nonvolatile storage medium may be configured to store a computer program for executing the steps of:
s1, collecting the connection type data of the computer system;
s2, generating a reverse mapping relation between each instance in the program modules and the corresponding program module based on the name service;
s3, identifying the connection relation among the program modules by using the connection type data and the reverse mapping relation;
s4, determining node information in the first program service network topology based on the identification information of each of the plurality of program modules, and determining side information in the first program service network topology based on the connection relationship, to obtain a first program service network topology.
Optionally, in this embodiment, the non-transitory computer readable storage medium may include, but is not limited to: various media capable of storing computer programs, such as a U disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and the like.
The present disclosure also provides a computer program product according to an embodiment of the present disclosure. Program code for implementing the audio processing methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
The above-mentioned serial numbers of the embodiments of the present disclosure are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present disclosure, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present disclosure, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present disclosure. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
The foregoing is merely a preferred embodiment of the present disclosure, and it should be noted that modifications and embellishments could be made by those skilled in the art without departing from the principle of the present disclosure, and these should also be considered as the protection scope of the present disclosure.
Claims (13)
1. A method for acquiring a network topology structure comprises the following steps:
collecting connection type data of a computer system, wherein the computer system comprises: a plurality of program modules, each of the plurality of program modules for launching a plurality of instances, the connection type data comprising: the remote call connection relation acquired by each program module and the module connection relation acquired from the service network system;
generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on the name service;
identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship;
and determining node information in a first program service network topological structure based on the identification information of each program module in the plurality of program modules, and determining side information in the first program service network topological structure based on the connection relation to obtain the first program service network topological structure.
2. The method of claim 1, further comprising:
and outputting the first program service network topology.
3. The method of claim 1, further comprising:
adding auxiliary configuration information to the first program service network topological structure to obtain a second program service network topological structure, wherein the auxiliary configuration information is label information associated with the first program service network topological structure;
and outputting the second program service network topology.
4. The method of claim 1, wherein identifying connection relationships between the plurality of program modules using the connection type data and the reverse mapping relationships comprises:
acquiring original example data information by using the connection type data;
and acquiring the connection relation based on the reverse mapping relation and the original instance data information.
5. The method of claim 4, wherein obtaining the raw instance data information using the connection type data comprises:
selecting a target program module from the plurality of program modules using the connection type data;
acquiring a plurality of instances corresponding to the target program module through the name service of the target program module;
and acquiring identification information of an upstream instance and a downstream instance connected with each instance in the plurality of instances.
6. The method of claim 5, wherein obtaining the connection relationship based on the reverse mapping relationship and the original instance data information comprises:
determining an upstream connection relationship, an upstream connection count, a downstream connection relationship and a downstream connection count of each instance in the multiple instances according to identification information of an upstream instance and a downstream instance connected to each instance in the multiple instances, wherein the upstream connection relationship is a connection relationship between each instance in the multiple instances and an adjacent upstream instance, the downstream connection relationship is a connection relationship between each instance in the multiple instances and an adjacent downstream instance, the upstream connection count is used for determining a confidence that a topologic relationship exists between the target program module and an upstream program module corresponding to the upstream instance, and the downstream connection count is used for determining a confidence that a topologic relationship exists between the target program module and a downstream program module corresponding to the downstream instance;
and acquiring the connection relation based on the reverse mapping relation, the upstream connection count, the downstream connection relation and the downstream connection count of each of the multiple instances.
7. The method of claim 1, wherein generating the reverse mapping of each instance of the plurality of program modules to a corresponding program module based on the name service comprises:
and generating the reverse mapping relation between each instance and the corresponding program module based on the name service every preset time interval, wherein the preset time interval is used for determining the effective time interval of the reverse mapping relation.
8. The method of claim 1, wherein determining side information in the first program service network topology based on the connection relationship comprises:
selecting any program module from the plurality of program modules as an upstream node based on the connection relationship;
and sequentially searching adjacent downstream nodes from the upstream node, and constructing a topological edge of the program service network topological structure between the upstream node and the adjacent downstream nodes to obtain edge information in the program service network topological structure.
9. The method of claim 1, wherein collecting the connection type data of the computer system comprises:
and acquiring the connection type data by using the dispatch logs among the plurality of program modules.
10. An apparatus for acquiring a network topology, comprising:
an acquisition module for acquiring connection type data of a computer system, wherein the computer system comprises: a plurality of program modules, each of the plurality of program modules for launching a plurality of instances, the connection type data comprising: the remote call connection relation acquired by each program module and the module connection relation acquired from the service network system;
a generation module for generating a reverse mapping relationship between each instance of the plurality of program modules and the corresponding program module based on a name service;
an identifying module for identifying a connection relationship between the plurality of program modules using the connection type data and the reverse mapping relationship;
an obtaining module, configured to determine node information in a first program service network topology structure based on the identification information of each of the plurality of program modules, and determine side information in the first program service network topology structure based on the connection relationship, so as to obtain the first program service network topology structure.
11. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-9.
12. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-9.
13. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111016589.0A CN113792008A (en) | 2021-08-31 | 2021-08-31 | Method and device for acquiring network topology structure, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111016589.0A CN113792008A (en) | 2021-08-31 | 2021-08-31 | Method and device for acquiring network topology structure, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113792008A true CN113792008A (en) | 2021-12-14 |
Family
ID=79182476
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111016589.0A Pending CN113792008A (en) | 2021-08-31 | 2021-08-31 | Method and device for acquiring network topology structure, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113792008A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115801589A (en) * | 2022-11-15 | 2023-03-14 | 北京优特捷信息技术有限公司 | Event topological relation determining method, device, equipment and storage medium |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040171074A1 (en) * | 2002-10-17 | 2004-09-02 | Mount Sinai Hospital | Structures of substrate binding pockets of SCF complexes |
| CN1650287A (en) * | 2002-05-07 | 2005-08-03 | 因卡网络工程公司 | Methods and systems for changing a topology of a network |
| US20080040455A1 (en) * | 2006-08-08 | 2008-02-14 | Microsoft Corporation | Model-based deployment and configuration of software in a distributed environment |
| US20130268638A1 (en) * | 2012-04-05 | 2013-10-10 | International Business Machines Corporation | Mapping requirements to a system topology in a networked computing environment |
| CN105227342A (en) * | 2014-06-27 | 2016-01-06 | 瞻博网络公司 | For the graphic data base that the service in network service zone is planned and configured |
| US20160234095A1 (en) * | 2015-02-06 | 2016-08-11 | Dell Products, L.P. | Systems and methods for bare-metal network topology discovery |
| US9419842B1 (en) * | 2011-10-04 | 2016-08-16 | Amazon Technologies, Inc. | Dynamic network device configuration |
| CN107209814A (en) * | 2015-01-13 | 2017-09-26 | 10X基因组学有限公司 | For making structure variation and the visual system and method for phase information |
| US20180091374A1 (en) * | 2016-09-28 | 2018-03-29 | Mcafee, Inc. | Dynamically identifying criticality of services and data sources |
| US20180124008A1 (en) * | 2016-10-31 | 2018-05-03 | International Business Machines Corporation | Network Topology-Preserving Internet Protocol Address Anonymization |
| US20180337824A1 (en) * | 2017-05-18 | 2018-11-22 | Datera, Inc. | System and method for an improved placement of storage nodes in network |
| US20190190812A1 (en) * | 2017-12-19 | 2019-06-20 | Juniper Networks, Inc. | Systems and methods for facilitating transparent service mapping across multiple network transport options |
| US20190190773A1 (en) * | 2017-12-15 | 2019-06-20 | International Business Machines Corporation | Building and fixing a dynamic application topology in a cloud based environment leveraging log file data |
| CN110249588A (en) * | 2017-02-03 | 2019-09-17 | 维萨国际服务协会 | System and method for detecting network topology |
| US20200389477A1 (en) * | 2019-06-07 | 2020-12-10 | Hewlett Packard Enterprise Development Lp | Automatic identification of roles and connection anomalies |
| US20200403876A1 (en) * | 2019-06-21 | 2020-12-24 | At&T Intellectual Property I, L.P. | Mapping Network Topology for Latency Sensitive Applications in a Mobile network |
-
2021
- 2021-08-31 CN CN202111016589.0A patent/CN113792008A/en active Pending
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1650287A (en) * | 2002-05-07 | 2005-08-03 | 因卡网络工程公司 | Methods and systems for changing a topology of a network |
| US20040171074A1 (en) * | 2002-10-17 | 2004-09-02 | Mount Sinai Hospital | Structures of substrate binding pockets of SCF complexes |
| US20080040455A1 (en) * | 2006-08-08 | 2008-02-14 | Microsoft Corporation | Model-based deployment and configuration of software in a distributed environment |
| US9419842B1 (en) * | 2011-10-04 | 2016-08-16 | Amazon Technologies, Inc. | Dynamic network device configuration |
| US20130268638A1 (en) * | 2012-04-05 | 2013-10-10 | International Business Machines Corporation | Mapping requirements to a system topology in a networked computing environment |
| CN105227342A (en) * | 2014-06-27 | 2016-01-06 | 瞻博网络公司 | For the graphic data base that the service in network service zone is planned and configured |
| CN107209814A (en) * | 2015-01-13 | 2017-09-26 | 10X基因组学有限公司 | For making structure variation and the visual system and method for phase information |
| US20160234095A1 (en) * | 2015-02-06 | 2016-08-11 | Dell Products, L.P. | Systems and methods for bare-metal network topology discovery |
| US20180091374A1 (en) * | 2016-09-28 | 2018-03-29 | Mcafee, Inc. | Dynamically identifying criticality of services and data sources |
| US20180124008A1 (en) * | 2016-10-31 | 2018-05-03 | International Business Machines Corporation | Network Topology-Preserving Internet Protocol Address Anonymization |
| CN110249588A (en) * | 2017-02-03 | 2019-09-17 | 维萨国际服务协会 | System and method for detecting network topology |
| US20180337824A1 (en) * | 2017-05-18 | 2018-11-22 | Datera, Inc. | System and method for an improved placement of storage nodes in network |
| US20190190773A1 (en) * | 2017-12-15 | 2019-06-20 | International Business Machines Corporation | Building and fixing a dynamic application topology in a cloud based environment leveraging log file data |
| US20190190812A1 (en) * | 2017-12-19 | 2019-06-20 | Juniper Networks, Inc. | Systems and methods for facilitating transparent service mapping across multiple network transport options |
| US20200389477A1 (en) * | 2019-06-07 | 2020-12-10 | Hewlett Packard Enterprise Development Lp | Automatic identification of roles and connection anomalies |
| US20200403876A1 (en) * | 2019-06-21 | 2020-12-24 | At&T Intellectual Property I, L.P. | Mapping Network Topology for Latency Sensitive Applications in a Mobile network |
Non-Patent Citations (1)
| Title |
|---|
| 牟鹏至;李飞;罗传军;: "基于Web和SNMP的拓扑更新策略", 计算机工程, no. 10 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115801589A (en) * | 2022-11-15 | 2023-03-14 | 北京优特捷信息技术有限公司 | Event topological relation determining method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110855473B (en) | Monitoring method, device, server and storage medium | |
| CN108804618B (en) | Database configuration method, device, computer equipment and storage medium | |
| CN109086182B (en) | Automatic database alarming method and terminal equipment | |
| CN107800565B (en) | Inspection method, inspection device, inspection system, computer equipment and storage medium | |
| CN111752799A (en) | Service link tracking method, device, equipment and storage medium | |
| CN112905323B (en) | Data processing method, device, electronic equipment and storage medium | |
| CN113377626B (en) | Visual unified alarm method, device, equipment and medium based on service tree | |
| CN111556158A (en) | Access method, access device, access equipment and storage medium of Internet of things platform | |
| CN107783880A (en) | A kind of log analysis method of server system, device and server system | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| CN111309734A (en) | Method and system for automatically generating table data | |
| CN114090388A (en) | Information acquisition method, server cluster, server and equipment | |
| CN116204438A (en) | Test case generation method, automatic test method and related device | |
| CN113792008A (en) | Method and device for acquiring network topology structure, electronic equipment and storage medium | |
| CN113962597A (en) | Data analysis method and device, electronic equipment and storage medium | |
| CN113434506A (en) | Data management and retrieval method and device, computer equipment and readable storage medium | |
| CN112883088B (en) | Data processing method, device, equipment and storage medium | |
| US20180336171A1 (en) | System and method for constructing extensible event log with javascript object notation (json) encoded payload data | |
| WO2023151397A1 (en) | Application program deployment method and apparatus, device, and medium | |
| CN114756301A (en) | Log processing method, device and system | |
| CN112527453B (en) | Virtualization information simulation system, method and computer-readable storage medium | |
| CN111679899A (en) | Task scheduling method, device, platform equipment and storage medium | |
| CN109814911A (en) | Method, apparatus, computer equipment and storage medium for Manage Scripts program | |
| TWI765447B (en) | Decoupling method and system for decomposing services | |
| CN115510112A (en) | Data reporting method and device, storage medium and electronic equipment |
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 |