Monitoring method and device of calling link, electronic equipment and storage medium
By obtaining the target object attribute information and call links of heterogeneous systems, using multiple monitoring tools to obtain log data and generate graph databases, the problem of complexity of call link monitoring in heterogeneous systems is solved, and the heterogeneous systems are realized Unified monitoring and reduce monitoring complexity.
Patent Information
- Application Number
- CN202410954753.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-16
- Publication Date
- 2024-11-22
AI Technical Summary
The monitoring complexity of calling links in heterogeneous systems is high, and a single calling link tool cannot uniformly monitor all applications, components, loads, databases, etc.
By obtaining the attribute information and call links of each target object in the business system, using the JAVA type and network bypass type monitoring tool to obtain the monitoring log, determine the call data between the target objects, and convert it into a graph database, and perform the following steps: monitor.
It realizes unified monitoring of call links in heterogeneous systems, reduces monitoring complexity, accurately extracts call data and generates graph databases, and meets user monitoring needs.
Smart Images

Figure CN119003270A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a monitoring method, device, electronic device and storage medium for a call link. Background Art
[0002] With the microservices and complexity of modern application system architectures, application systems often have both traditional architectures and modern distributed architectures (i.e., heterogeneous systems). However, different call chain tools are often designed for different architectures and monitoring scenarios. A single call chain tool cannot monitor all applications, components, loads, databases, and other call chains in a heterogeneous system. Monitoring call chains in heterogeneous systems is relatively complex.
[0003] Therefore, there is an urgent need for a method for monitoring call links in heterogeneous systems to reduce the complexity of call link monitoring in heterogeneous systems. Summary of the invention
[0004] The present application aims to solve one of the technical problems in the related art at least to some extent.
[0005] To this end, the first purpose of the present application is to propose a call link monitoring method to achieve unified monitoring of call links in heterogeneous systems and reduce the complexity of call link monitoring in heterogeneous systems.
[0006] The second objective of the present application is to provide a monitoring device for a call link.
[0007] The third objective of the present application is to provide an electronic device.
[0008] A fourth objective of the present application is to provide a computer-readable storage medium.
[0009] A fifth object of the present application is to provide a computer program product.
[0010] To achieve the above-mentioned purpose, the first embodiment of the present application proposes a monitoring method for a call link, including:
[0011] Obtaining attribute information of each target object in the business system and presetting call links between target objects, where the target objects include applications, load balancers, intermediate components, and databases;
[0012] Determine the call data between the target objects based on the monitoring logs and call links obtained from the monitoring tools corresponding to the target objects, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools;
[0013] Each target object is respectively regarded as a node, and the attribute information of the edges between the nodes is determined based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge;
[0014] Based on the graph database and preset monitoring conditions, the call links in the business system are monitored.
[0015] To achieve the above-mentioned purpose, the second embodiment of the present application proposes a monitoring device for a call link, including:
[0016] An acquisition module is used to obtain attribute information of each target object in the business system and preset call links between target objects, wherein the target objects include applications, load balancers, intermediate components, and databases;
[0017] A determination module, used to determine the call data between each target object based on the monitoring log and call link obtained from the monitoring tool corresponding to each target object, wherein the monitoring tool includes a JAVA type monitoring tool and a network bypass type monitoring tool;
[0018] A generation module, used to treat each target object as a node, and determine the attribute information of the edges between the nodes based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge;
[0019] The monitoring module is used to monitor the call links in the business system based on the graph database and preset monitoring conditions.
[0020] To achieve the above-mentioned purpose, the third aspect of the present application provides an electronic device, including:
[0021] at least one processor; and
[0022] a memory communicatively connected to at least one processor; wherein,
[0023] The memory stores instructions that can be executed by at least one processor. The instructions are executed by the at least one processor so that the at least one processor can execute the method of the above embodiment.
[0024] To achieve the above objectives, the fourth aspect of the present application proposes a computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the method according to the above embodiment.
[0025] To achieve the above objectives, the fifth aspect of the present application proposes a computer program product, including a computer program, which implements the method of the above embodiment when executed by a processor.
[0026] The monitoring method, device, electronic device and storage medium of the call link provided by the present application obtain the attribute information of each target object in the business system and the call link between each target object, wherein the target object includes an application, a load balancer, an intermediate component, and a database, and then, based on the monitoring log and the call link obtained from the monitoring tool corresponding to each target object, the call data between each target object is determined, wherein the monitoring tool includes a JAVA type monitoring tool and a network bypass type monitoring tool, and then, each target object is respectively regarded as a node, and the attribute information of the edge between each node is determined based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge, so as to monitor each call link of the business system based on the graph database and the preset monitoring conditions. Thus, in combination with the call link, the call data between each target object is accurately extracted from the monitoring log obtained from different types of monitoring tools, and a graph database is generated based on the call data, thereby realizing the unified monitoring of the call link in the heterogeneous system and reducing the complexity of the call link monitoring in the heterogeneous system.
[0027] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:
[0029] Figure 1 A flowchart of a monitoring method for a call link provided in an embodiment of the present application;
[0030] Figure 2 A flowchart of another method for monitoring a call link provided in an embodiment of the present application;
[0031] Figure 3 A flowchart of another method for monitoring a call link provided in an embodiment of the present application;
[0032] Figure 4 A schematic diagram of the structure of a monitoring device for a call link provided in an embodiment of the present application. DETAILED DESCRIPTION
[0033] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.
[0034] The following describes the call link monitoring method and device of the embodiment of the present application with reference to the accompanying drawings.
[0035] The call link monitoring method of the embodiment of the present application is executed by the call link monitoring device provided by the embodiment of the present application. The device can be configured in a computer device or a terminal device to achieve unified monitoring of the call links in a heterogeneous system.
[0036] Figure 1 A flowchart of a method for monitoring a call link provided in an embodiment of the present application.
[0037] like Figure 1 As shown, the monitoring method of the call link includes the following steps:
[0038] Step 101, obtaining attribute information of each target object in the business system and call links between each target object, wherein the target objects include applications, load balancers, intermediate components, and databases.
[0039] The attribute information of the application includes the application system name, IP, port, etc. The attribute information of the load balancer includes the load balancer name, load (Virtual IP Address, VIP), etc. The attribute information of the intermediate component includes the component name, IP, port, version, queue name, etc. The attribute information of the database includes the database IP, port, and instance name.
[0040] At present, business systems often have both traditional architecture and modern distributed architecture (that is, the business system is a heterogeneous system). Therefore, the applications that need to be monitored include traditional architecture applications, distributed architecture microservices, etc., load balancers include F5, LVS (Linux Virtual Server), etc., intermediate components include agents (Agent, AG), gateways (Gateway, GW), registration centers (Registration Center, RC), configuration centers (Configuration Center, CC), message middleware (Message Queue, MQ), etc., and databases include relational databases (Redis DataBase, RDB), cache databases (Container Database, CDB), etc.
[0041] In this application, the attribute information of each target object and the call links between each target object are configured in the Configuration Management Database (CMDB) in advance. For example, the call links between each target object are as follows: APP1 sends a request to APP2; APP1 sends a request to load LB1, and LB1 distributes it to APP2; APP1 sends a request to the proxy component AG1, and AG1 forwards it to the application APP2; APP1 and APP2 register with RC1; APP1 and APP2 obtain configuration from CC1; APP1 sends a request to GW1 and finds APP2 through RC1; APP1 produces a message to MQ1, and APP2 consumes the MQ1 message; APP1 calls RDB1, CDB1, etc. In this way, the attribute information of each target object in the business system and the call links between each target object can be obtained from the CMDB.
[0042] It can be understood that the above-mentioned call link set in the CMDB is static configuration information.
[0043] Step 102, based on the monitoring logs and call links obtained from the monitoring tools corresponding to the target objects, determine the call data between the target objects, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools.
[0044] The monitoring log contains the actual call request information between target objects, as well as the call time, call frequency, response time, error rate, data transmission rate, delay time, packet loss rate, bandwidth usage and other information between target objects.
[0045] In this application, different monitoring tools are used for different architectures or different monitoring scenarios. For example, the JAVA type monitoring tool based on JAVA bytecode technology can obtain multi-layer call relationships by collecting TraceID and SpanID information through Java Agent, which is mainly suitable for system monitoring running on JVM. The network bypass type monitoring tool that implements call link monitoring by obtaining mirror switch traffic has no dependence on the server architecture, but cannot implement multi-layer call relationship monitoring.
[0046] In the present application, the monitoring log can be extracted from the monitoring tool corresponding to each target object, and the monitoring log can be parsed in combination with the call link to obtain the call data between each target object. For example, by parsing the monitoring log, it is determined that the target object APP1 has sent a call request to the target object LB1, and based on the call link obtained in step 101, it is determined that the call request is sent from the target object LB1 to the target object APP2. Therefore, it is determined that the actual call link corresponding to the call request is from the target object APP1 to the target object LB1 and then to the target object APP2, and the call time, call frequency, response time, error rate, data transmission rate, delay time, packet loss rate, bandwidth usage and other information between the target object APP1 and the target object LB1 in the monitoring log are determined as the call data between the target object APP1 to the target object LB1 and then to the target object APP2. In addition, the call data also includes data flow information between nodes.
[0047] Step 103, taking each target object as a node, and determining the attribute information of the edges between the nodes based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge.
[0048] In this application, based on the call data, edges between nodes are created. For example, assuming that target object 1 in the call data calls the service or API of target object 2, an edge can be created between the node corresponding to target object 1 and the node corresponding to target object 2. The direction of the edge points to the node corresponding to the called target object, and the attribute information of the edge includes the call time, call frequency, response time, error rate, data transmission rate, delay time, packet loss rate, bandwidth usage, etc. between the nodes corresponding to the edge.
[0049] After that, you can use any graph database technology, such as Neo4j, JanusGraph, or Amazon Neptune, to create nodes and edges based on the defined nodes and edges using the query language (such as Cypher, Gremlin) or API of the graph database. Then, import the node and edge information into the graph database to obtain the graph database.
[0050] In addition, during the operation of the business system, the above-mentioned process of step 102-step 103 can be cyclically executed at preset time intervals to update the graph database in real time, thereby ensuring that the graph database can reflect the real-time status of the application system.
[0051] Step 104, based on the graph database and preset monitoring conditions, monitor each call link in the business system.
[0052] The monitoring conditions include indicator values corresponding to monitoring indicators, wherein the monitoring indicators are one or more types of attribute information.
[0053] In this application, each attribute value of each node in the graph database can be compared with its corresponding indicator value in the monitoring condition to determine whether each node meets the monitoring condition. If the monitoring condition is met, no warning is issued, and if the monitoring condition is not met, a warning can be issued.
[0054] Similarly, the attribute values of each edge in the graph database can be compared with the corresponding indicator values in the monitoring conditions to determine whether each edge meets the monitoring conditions. This allows unified call link monitoring for the business system.
[0055] In this application, the graph database can be visualized to achieve visual monitoring of each call link between various types of target objects.
[0056] In this application, the attribute information of each target object in the business system and the call links between each target object are obtained, wherein the target objects include applications, load balancers, intermediate components, and databases. Then, based on the monitoring logs and call links obtained from the monitoring tools corresponding to each target object, the call data between each target object is determined, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools. Then, each target object is taken as a node, and the attribute information of the edges between each node is determined based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge, so as to monitor each call link of the business system based on the graph database and preset monitoring conditions. Thus, in combination with the call link, the call data between each target object is accurately extracted from the monitoring logs obtained from different types of monitoring tools, and a graph database is generated based on the call data, thereby realizing unified monitoring of the call links in heterogeneous systems and reducing the complexity of call link monitoring in heterogeneous systems.
[0057] Figure 2 A flowchart of a method for monitoring a call link provided in an embodiment of the present application.
[0058] like Figure 2 As shown, the monitoring method of the call link includes the following steps:
[0059] Step 201, obtain the attribute information of each target object in the business system and preset the call link between each target object, wherein the target objects include application programs, load balancers, intermediate components, and databases.
[0060] Step 202, based on the monitoring logs and call links obtained from the monitoring tools corresponding to the target objects, the call data between the target objects is determined, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools.
[0061] In the present application, the specific implementation process of step 201-step 202 can be found in the detailed description of any embodiment of the present application and will not be repeated here.
[0062] Step 203: Obtain preset monitoring requirements and determine monitoring data dimensions associated with the monitoring requirements.
[0063] The monitoring data dimension may be the attribute information corresponding to the target object and the attribute information of the edge corresponding to the call link.
[0064] In this application, due to different scenario requirements, users may have different monitoring requirements for business systems. For example, operation and maintenance personnel are concerned about system performance, and business personnel are concerned about business access data. Therefore, the monitoring requirements of operation and maintenance personnel are data related to monitoring business system performance, and the monitoring requirements of business personnel are data related to monitoring business access. Based on this, the monitoring data dimensions associated with each monitoring requirement can be pre-set in the system. For example, monitoring requirement 1 is data related to monitoring business performance, and the monitoring data dimensions associated with monitoring requirement 1 can be the data transmission rate, delay time, packet loss rate, etc. corresponding to the edge. Monitoring requirement 2 is data related to monitoring business access, and the monitoring data dimensions associated with monitoring requirement 2 can be the call frequency corresponding to the edge, etc. It can also support users to pre-set monitoring requirements in the system. Afterwards, after obtaining the preset monitoring requirements, query to determine the monitoring data dimensions associated with the monitoring requirements, so as to obtain monitoring data in a targeted manner based on the monitoring data dimensions.
[0065] Step 204: filter the call data based on the monitoring data dimension.
[0066] In this application, only the data under the monitoring data dimension in the call data can be retained, so as to perform the subsequent generation of the graph database and the monitoring process based on the retained call data, thereby realizing selective data acquisition, thereby reducing the amount of data while meeting the user's monitoring needs.
[0067] Step 205, taking each target object as a node, and determining the attribute information of the edges between the nodes based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge.
[0068] Step 206, based on the graph database and preset monitoring conditions, monitor each call link in the business system.
[0069] In the present application, the specific implementation process of step 205-step 206 can be found in the detailed description of any embodiment of the present application and will not be repeated here.
[0070] In this application, the attribute information of each target object in the business system is obtained, and the call links between each target object are preset, wherein the target objects include applications, load balancers, intermediate components, and databases. Afterwards, based on the monitoring logs and call links obtained from the monitoring tools corresponding to each target object, the call data between each target object is determined, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools, and the preset monitoring requirements are obtained, and the monitoring data dimensions associated with the monitoring requirements are determined, so as to filter the call data based on the monitoring data dimensions, and then, each target object is respectively regarded as a node, and the attribute information of the edges between each node is determined based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge, and monitor each call link in the business system based on the graph database and the preset monitoring conditions. Thus, based on the preset monitoring requirements, the call data is filtered, and the call data is obtained in a targeted manner. Thus, while meeting the user's monitoring needs, the amount of data is reduced.
[0071] Figure 3 A flowchart of a method for monitoring a call link provided in an embodiment of the present application.
[0072] like Figure 3 As shown, the monitoring method of the call link includes the following steps:
[0073] Step 301, obtain the attribute information of each target object in the business system and preset the call links between the target objects, wherein the target objects include applications, load balancers, intermediate components, and databases, and the attribute information includes custom attributes, and the custom attributes are used to indicate the classification of the target objects or the classification of the call links.
[0074] Among them, the process of obtaining the attribute information of each target object in the business system and presetting the call link between each target object can be referred to the detailed description of any embodiment of the present application, and will not be repeated here.
[0075] In this application, the target objects can be classified according to the type of the target objects, and the type of the target objects can be an application, a load balancer, an intermediate component, and a database. A level can be set for each target object, and the target objects can be classified according to the level of the target object, and the level of the target object can be level one, level two, etc. Therefore, the custom attributes of the target object can be level, type, etc. The call link can be classified according to the request method, strong or weak call, whether to block the process, etc. Therefore, the custom attributes of the call link can be request method, strong or weak call, whether to block the process.
[0076] Step 302, based on the monitoring logs and call links obtained from the monitoring tools corresponding to the target objects, determine the call data between the target objects, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools.
[0077] Step 303, taking each target object as a node, and determining the attribute information of the edges between the nodes based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge.
[0078] Step 304: monitor each call link in the business system based on the graph database and preset monitoring conditions.
[0079] In the present application, the specific implementation process of steps 302 to 304 can be found in the detailed description of any embodiment of the present application and will not be repeated here.
[0080] Step 305: Determine the visualization parameters corresponding to each node based on the attribute information of each node, and determine the visualization parameters of each edge based on the attribute information of each edge, wherein the visualization parameters include color, size, shape, and line thickness.
[0081] In this application, visualization parameters associated with different attribute information can be pre-set in the system. For example, the color and shape associated with the type of each target object, the size associated with the level of each target object, etc. can be pre-set in the system to distinguish target objects of different types or levels by color, size, shape, etc. The line type, line thickness, color, etc. associated with the request mode, strong or weak call, and whether to block the process of each call link can be pre-set in the system to distinguish the call links of different request modes, strong or weak calls, and whether to block the process by line type, line thickness, color, etc.
[0082] After that, you can query based on the attribute information of each node to determine the visualization parameters corresponding to each node. You can query based on the attribute information of each edge to determine the visualization parameters of each edge.
[0083] Step 306: Visually display the graph database based on the visualization parameters.
[0084] In this application, a preset graph visualization tool can be used to display the graph database based on visualization parameters. Thus, the nodes in the graph database and the edges between the nodes can be displayed in a graphical manner according to different visualization parameters, thereby realizing visual monitoring of unified call links.
[0085] In addition, users are also supported to set the target attribute value corresponding to the custom attribute, where the target attribute value can be the attribute value of the custom attribute of the call link or target object that the user wants to display or focus on. This allows the user to selectively display the nodes corresponding to the target object or the edges corresponding to the call link based on the target attribute value in the future, so as to meet personalized monitoring needs.
[0086] Optionally, obtain the target attribute value corresponding to the custom attribute. Afterwards, match the target attribute value with the attribute value of the custom attribute corresponding to each node or each edge to determine the target visualization object from the node or edge. For example, when the custom attribute corresponds to the target object, the target attribute value corresponding to the custom attribute can be matched with the attribute value of the custom attribute corresponding to each node. When the attribute value of the custom attribute corresponding to a certain node is the same as the target attribute value, the target object corresponding to the node is determined as the target visualization object. When the custom attribute corresponds to the call link, the target attribute value corresponding to the custom attribute can be matched with the attribute value of the custom attribute corresponding to each call link. When the attribute value of the custom attribute corresponding to a certain call link is the same as the target attribute value, the target object corresponding to the call link is determined as the target visualization object. Then, the graph database is visualized based on the visualization parameters corresponding to the target visualization object.
[0087] In this application, the visualization parameters corresponding to each node are determined based on the attribute information of each node, and the visualization parameters of each edge are determined based on the attribute information of each edge, wherein the visualization parameters include color, size, shape, and line thickness, and the graph database is visualized based on the visualization parameters, thereby realizing the visualization monitoring of the unified call link.
[0088] In order to implement the above embodiment, the present application also proposes a monitoring device for a call link.
[0089] Figure 4 A schematic diagram of the structure of a monitoring device for a call link provided in an embodiment of the present application.
[0090] like Figure 4 As shown, the monitoring device of the call link includes an acquisition module 410 , a determination module 420 , a generation module 430 , and a monitoring module 440 .
[0091] The acquisition module 410 is used to acquire the attribute information of each target object in the business system and preset the call link between each target object, wherein the target objects include applications, load balancers, intermediate components, and databases;
[0092] A determination module 420, configured to determine the call data between the target objects based on the monitoring logs and call links obtained from the monitoring tools corresponding to the target objects, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools;
[0093] A generation module 430 is used to treat each target object as a node, and determine the attribute information of the edges between the nodes based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge;
[0094] The monitoring module 440 is used to monitor each call link in the business system based on the graph database and preset monitoring conditions.
[0095] Furthermore, in a possible implementation of the embodiment of the present application, a screening module is also included, which is used to:
[0096] Obtain the preset monitoring requirements and determine the monitoring data dimensions associated with the monitoring requirements;
[0097] Filter call data based on monitoring data dimensions.
[0098] Furthermore, in a possible implementation of the embodiment of the present application, the attribute information includes a custom attribute, and the custom attribute is used to indicate the classification of the target object or the classification of the call link.
[0099] Furthermore, in a possible implementation of the embodiment of the present application, the device further includes a visualization module, which is used to:
[0100] Determine a visualization parameter corresponding to each node based on the attribute information of each node, and determine a visualization parameter of each edge based on the attribute information of each edge, wherein the visualization parameter includes color, size, shape, and line thickness;
[0101] Visualize the graph database based on visualization parameters.
[0102] Furthermore, in a possible implementation of the embodiment of the present application, the visualization module is used to:
[0103] Get the target attribute value corresponding to the custom attribute;
[0104] Matching the target attribute value with the attribute value of the custom attribute corresponding to each node or each edge to determine the target visualization object from the node or edge;
[0105] The graph database is visualized based on the visualization parameters corresponding to the target visualization object.
[0106] It should be noted that the aforementioned explanation of the embodiment of the monitoring method for the call link is also applicable to the monitoring device for the call link of this embodiment, and will not be repeated here.
[0107] In this application, the attribute information of each target object in the business system and the call links between each target object are obtained, wherein the target objects include applications, load balancers, intermediate components, and databases. Then, based on the monitoring logs and call links obtained from the monitoring tools corresponding to each target object, the call data between each target object is determined, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools. Then, each target object is taken as a node, and the attribute information of the edges between each node is determined based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target object corresponding to the node and the attribute information of the edge, so as to monitor each call link of the business system based on the graph database and preset monitoring conditions. Thus, in combination with the call link, the call data between each target object is accurately extracted from the monitoring logs obtained from different types of monitoring tools, and a graph database is generated based on the call data, thereby realizing unified monitoring of the call links in heterogeneous systems and reducing the complexity of call link monitoring in heterogeneous systems.
[0108] In order to implement the above embodiments, the present application also proposes an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method provided by the above embodiments.
[0109] In order to implement the above embodiments, the present application also proposes a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the methods provided by the above embodiments.
[0110] In order to implement the above embodiments, the present application also proposes a computer program product, including a computer program, which implements the methods provided by the above embodiments when executed by a processor.
[0111] The collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in this application are in compliance with relevant laws and regulations and do not violate public order and good morals.
[0112] It should be noted that personal information from users should be collected for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. In addition, such collection / sharing should be carried out after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign the agreement / authorization including authorization of relevant user information before the user uses the function. In addition, any necessary steps should be taken to protect and safeguard access to such personal information data and ensure that others who have access to personal information data comply with its privacy policy and procedures.
[0113] This application is expected to provide an implementation scheme for users to selectively block the use or access of personal information data. That is, this application is expected to provide hardware and / or software to prevent or block access to such personal information data. Once the personal information data is no longer needed, risks can be minimized by limiting data collection and deleting data. In addition, when applicable, personal identifiers are removed from such personal information to protect the privacy of users.
[0114] In the description of the aforementioned embodiments, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.
[0115] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.
[0116] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.
[0117] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute the instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.
[0118] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.
[0119] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.
[0120] In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.
[0121] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present application.
Claims
1. A method for monitoring a call link, characterized in that: The method comprises: Acquire attribute information of each target object in the business system and preset call links between the target objects, wherein the target objects include applications, load balancers, intermediate components, and databases; Determine the call data between the target objects based on the monitoring log and the call link obtained from the monitoring tool corresponding to each target object, wherein the monitoring tool includes a JAVA type monitoring tool and a network bypass type monitoring tool; Each of the target objects is respectively regarded as a node, and attribute information of the edges between the nodes is determined based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target objects corresponding to the nodes and the attribute information of the edges; Based on the graph database and preset monitoring conditions, the call links in the business system are monitored.
2. The method according to claim 1, characterized in that Before taking each of the target objects as a node and determining the attribute information of the edges between the nodes based on the call data, the method further includes: Obtaining preset monitoring requirements and determining monitoring data dimensions associated with the monitoring requirements; The call data is filtered based on the monitoring data dimension.
3. The method according to claim 1, characterized in that The attribute information includes a custom attribute, and the custom attribute is used to indicate the classification of the target object or the classification of the call link.
4. The method according to claim 3, characterized in that The method further comprises: Determine a visualization parameter corresponding to each of the nodes based on the attribute information of each of the nodes, and determine a visualization parameter of each of the edges based on the attribute information of each of the edges, wherein the visualization parameters include color, size, shape, and line thickness; The graph database is visualized based on the visualization parameters.
5. The method according to claim 4, characterized in that The visual display of the graph database based on the visualization parameter includes: Obtain the target attribute value corresponding to the custom attribute; Matching the target attribute value with the attribute value of the custom attribute corresponding to each of the nodes or each of the edges to determine a target visualization object from the nodes or the edges; The graph database is visualized based on the visualization parameters corresponding to the target visualization object.
6. A monitoring device for a call link, characterized in that: The device comprises: An acquisition module is used to acquire attribute information of each target object in the business system and preset call links between the target objects, wherein the target objects include applications, load balancers, intermediate components, and databases; A determination module, configured to determine the call data between the target objects based on the monitoring logs and the call links obtained from the monitoring tools corresponding to the target objects, wherein the monitoring tools include JAVA type monitoring tools and network bypass type monitoring tools; A generation module, used to take each of the target objects as a node, and determine the attribute information of the edges between the nodes based on the call data, so as to generate a graph database corresponding to the application system based on the attribute information of the target objects corresponding to the nodes and the attribute information of the edges; A monitoring module is used to monitor the call links in the business system based on the graph database and preset monitoring conditions.
7. The device according to claim 6, characterized in that Also includes screening modules for: Obtaining preset monitoring requirements and determining monitoring data dimensions associated with the monitoring requirements; The call data is filtered based on the monitoring data dimension.
8. The device according to claim 6, characterized in that The attribute information includes a custom attribute, and the custom attribute is used to indicate the classification of the target object or the classification of the call link.
9. The device according to claim 8, characterized in that The device also includes a visualization module, which is used to: Determine a visualization parameter corresponding to each of the nodes based on the attribute information of each of the nodes, and determine a visualization parameter of each of the edges based on the attribute information of each of the edges, wherein the visualization parameters include color, size, shape, and line thickness; The graph database is visualized based on the visualization parameters.
10. The device according to claim 9, characterized in that The visualization module is used to: Obtain the target attribute value corresponding to the custom attribute; Matching the target attribute value with the attribute value of the custom attribute corresponding to each of the nodes or each of the edges to determine a target visualization object from the nodes or the edges; The graph database is visualized based on the visualization parameters corresponding to the target visualization object.
11. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 5.
12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 5 when executed by a processor.
13. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 5 when being executed by a processor.
