Entity relationship determination method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses an entity relationship determination method and device, electronic equipment and a storage medium. The method comprises the following steps: in response to a determination instruction of an entity relationship between target entities in a target service, obtaining at least one reference data of the target service; generating a target entity field based on a first entity field under the condition of determining that the target reference data contains the first entity field defined in the preset entity configuration rule; generating target entity data according to the target reference data and the target entity field; and determining an entity relationship between target entities in the target entity data, and generating an entity relationship graph corresponding to the target service according to the entity relationship. According to the scheme provided by the embodiment of the invention, the entity relationship of different data in the system can be quickly determined, and a basis is provided for operation and maintenance of the system.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for determining entity relationships. Background Art

[0002] With the rapid development of computer and Internet technologies, business operations are increasingly concentrated on information systems or information platforms. To ensure the normal operation of the system and improve the reliability and security of the system, technicians need to continuously accumulate operation and maintenance knowledge and quickly complete system troubleshooting. The application of operation and maintenance-related knowledge is divided into explicit configuration management data, processing plans, and implicit operation status, maintenance process, etc.

[0003] How to quickly determine the entity relationships between different data in the system and provide a basis for system operation and maintenance is a key research issue in the industry. Summary of the invention

[0004] The present invention provides a method, device, electronic device and storage medium for determining entity relationships, so as to quickly determine the entity relationships of different data in a system and provide a basis for the operation and maintenance of the system.

[0005] According to one aspect of the present invention, a method for determining an entity relationship is provided, the method comprising:

[0006] In response to an instruction to determine an entity relationship between target entities in a target business, acquiring at least one reference data of the target business;

[0007] In a case where it is determined that the target reference data includes a first entity field defined in a preset entity configuration rule, generating a target entity field based on the first entity field;

[0008] Generate target entity data according to the target reference data and the target entity field;

[0009] An entity relationship between target entities in the target entity data is determined, and an entity relationship graph corresponding to the target business is generated according to the entity relationship.

[0010] According to another aspect of the present invention, there is provided a device for determining an entity relationship, the device comprising:

[0011] A reference data acquisition module, configured to acquire at least one reference data of the target business in response to an instruction to determine an entity relationship between target entities in the target business;

[0012] A target entity field generating module, configured to generate a target entity field based on a first entity field defined in a preset entity configuration rule when it is determined that the target reference data contains the first entity field;

[0013] A target entity data generating module, used to generate target entity data according to the target reference data and the target entity field;

[0014] The entity relationship diagram determination module is used to determine the entity relationship between each target entity in the target entity data, and generate an entity relationship diagram corresponding to the target business according to the entity relationship.

[0015] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0016] at least one processor; and

[0017] a memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for determining entity relationships described in any embodiment of the present invention.

[0019] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for determining entity relationships described in any embodiment of the present invention when executed.

[0020] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the method for determining an entity relationship according to any embodiment of the present invention is implemented.

[0021] The technical solution of the embodiment of the present invention obtains at least one reference data of the target business by responding to an instruction to determine the entity relationship between each target entity in the target business; generates a target entity field based on the first entity field when it is determined that the target reference data contains a first entity field defined in a preset entity configuration rule; generates target entity data according to the target reference data and the target entity field; determines the entity relationship between each target entity in the target entity data, and generates an entity relationship graph corresponding to the target business according to the entity relationship, so as to quickly determine the entity relationship between different data in the system and provide a basis for the operation and maintenance of the system.

[0022] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 is a flow chart of a method for determining an entity relationship provided according to Embodiment 1 of the present invention;

[0025] Figure 2 is a flow chart of a method for determining an entity relationship provided according to a second embodiment of the present invention;

[0026] Figure 3 is a schematic diagram of the structure of an entity relationship determination device provided according to Embodiment 3 of the present invention;

[0027] Figure 4 It is a schematic diagram of the structure of an electronic device for implementing the method for determining entity relationships according to an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] Embodiment 1

[0031] Figure 1This is a flowchart of a method for determining entity relationships according to the first embodiment of the present invention. This embodiment is applicable to the case of quickly generating an entity relationship diagram between entities in various data in a target business. The method can be executed by an entity relationship determination device, which can be implemented in the form of hardware and / or software. The entity relationship determination device can be configured in an electronic device with data processing functions such as a computer, a server or a tablet computer. Figure 1 As shown, the method includes:

[0032] Step 110: In response to an instruction for determining an entity relationship between target entities in a target business, obtain at least one reference data of the target business.

[0033] The target business may be any business generated in the system, such as an online transaction business, a data upload business, or an invoicing business, which is not limited in this embodiment.

[0034] In this embodiment, the reference data includes at least one of the following: log data, indicator data, link data, and alarm data. The log data and link data (i.e., call chain data) in the system are the main sources of the business layer and the application layer. The log data and indicator data in the system are the main sources of the application layer and the device layer. Exemplarily, the log data in the system may include web page access logs, content click logs, and search logs. The indicator data (e.g., monitoring indicators) in the system may include the host name, the central processing unit (CPU) usage rate of the host, and the memory usage rate. The link data in the system is the relevant data of the link process for each request call in the system, which may include parent-child identity identification numbers, access portals, and backend addresses. The alarm data may be the alarm information recorded when an abnormal situation occurs in the system; the alarm data may also be an alarm event that requires root cause analysis of the fault. Exemplarily, it may be an alarm event generated by the system in real time, or it may be a historical alarm event selected according to current needs.

[0035] In an optional implementation of this embodiment, after receiving an instruction to determine the entity relationship between target entities in the target business, at least one reference data in the target business may be further acquired.

[0036] Optionally, in this embodiment, after receiving the instruction to determine the entity relationship between each target entity in the target business, log data, indicator data, link data and alarm data related to the target business can be further obtained in the database of the target business. It should be noted that in this embodiment, each reference data can be obtained from the same database or from different databases, which is not limited in this embodiment.

[0037] Step 120: When it is determined that the target reference data includes a first entity field defined in a preset entity configuration rule, generate a target entity field based on the first entity field.

[0038] Among them, the target reference data can be any data obtained in the above steps, such as log data, indicator data, link data or alarm data, etc., which is not limited in this embodiment.

[0039] Optionally, in this embodiment, after obtaining each reference data, it can be further determined whether each reference data contains the first entity field defined in the preset entity configuration rule. If it is determined that the target reference data contains the first entity field defined in the preset entity configuration rule, the target entity field can be further generated based on the first entity field.

[0040] It should be noted that in this embodiment, different rules are defined in the preset entity configuration rules. For example, multiple entity fields and the generation method of each entity field are defined; the generation method of the entity identifier can also be defined, which is not limited in this embodiment.

[0041] In an optional implementation of the present embodiment, the preset entity configuration rule can be determined by the following steps: defining at least one first entity field, and determining each of the first entity fields as an entity type; randomly generating a target string, and determining the target string and the first entity field as the first component of the target entity field; determining the data content matching the first entity field as the second component of the target entity field; connecting the first component and the second component through a preset connector to obtain the target entity field; or, determining the combined content of each of the target entity fields as a unique key; the unique key randomly generates a target entity identifier based on the data content of each of the target entity fields; wherein the first entity field includes hostname and / or process; and the target string is yotta.entity.

[0042] Optionally, in the present embodiment, the fields hostname and / or process are determined as the first entity fields in the preset entity configuration rules, and the defined first entity field is determined as the entity type; further, a target string can be randomly generated, such as generating yotta.entity, and the target string is combined with the first entity field to be determined as the first component of the target entity field; further, the data content matching the first entity field is determined as the second component of the target entity field; further, the first component and the second component are connected by a preset connector to obtain the target entity field.

[0043] The preset connector may be “=”, “-” or “+”, etc., which is not limited in this embodiment.

[0044] Optionally, in this embodiment, the preset entity configuration rule may also determine the combined content of the target entity fields as a unique key. Further, the unique key may randomly generate a target entity identifier according to the data content of the target entity fields defined by the above rule.

[0045] Exemplarily, in this embodiment, the entity configuration rule may define the following two rules:

[0046] Rule 1: hostname and process fields are used as entity types, and a new field yotta.entity.entity type is created; generating: yotta.entity.hostname = 10.23.42.1 and yotta.entity.process = cmd123;

[0047] Rule 2: define hostname+process as a unique key, and each unique key randomly generates a target entity identifier based on the field value; illustratively, the target entity identifier can be generated based on the string yotta.entity.hostname=10.23.42.1 and yotta.entity.process=cmd123, specifically, the target entity identifier is 10.23.42.1-cmd123.

[0048] In an optional implementation of this embodiment, generating the target entity field based on the first entity field may include generating the target entity field according to rule 1 in the entity configuration rules, and generating the target entity identifier according to rule 1 in the entity configuration rules.

[0049] Step 130: Generate target entity data according to the target reference data and the target entity field.

[0050] Optionally, in this embodiment, after generating the target entity field, the target entity data can be further generated based on the target reference data and the generated target entity field; exemplarily, after generating the target entity field, the target entity field can be further added to the target reference data to obtain the target entity data.

[0051] Step 140: Determine the entity relationship between target entities in the target entity data, and generate an entity relationship graph corresponding to the target business according to the entity relationship.

[0052] In an optional implementation of this embodiment, after obtaining the target entity data, the entity relationship between the target entities in the target entity data may be further determined, and an entity relationship graph corresponding to the target business may be generated according to the entity relationship between the target entities.

[0053] Optionally, in this embodiment, determining the entity relationship between each target entity in the target entity data, and generating an entity relationship diagram corresponding to the target business based on the entity relationship, may include: comparing each target entity field in the target entity data with a pre-established entity relationship, and determining the entity relationship between each target entity in the target entity data based on the comparison result; determining the upstream and downstream entities of each target entity based on the entity relationship between each target entity, and generating the entity relationship diagram based on each upstream and downstream entity; the pre-established entity relationship includes: containment or connection.

[0054] In an optional implementation of the present embodiment, after obtaining the target entity data, each target entity field in the target entity data can be further compared with a pre-established entity relationship, and the entity relationship between each target entity in the target entity data can be determined based on the comparison result; illustratively, if the target entity data contains two target entity fields, and the entity relationship between the two target entity fields is determined to be inclusive based on the pre-established entity relationship, then the relationship between each target entity in the target entity data is inclusive; after determining the entity relationship between each target entity in the target entity data, an entity relationship graph can be generated based on the upstream and downstream entities of each entity.

[0055] Exemplarily, in this embodiment, the entity relationship can be pre-established by the following rules: relationshipname: belong{source: -trace; -metric; from: yotta.entity.process; to: yotta.entity.hostname}; relationshipname: connect{source: -trace; -metric; from: yotta.entity.kafka; to: yotta.entity.hostname}.

[0056] Optionally, in this embodiment, after determining the entity relationship between each target entity in the target entity data, the upstream entity and the downstream entity of the target entity can be further determined according to the entity identifier of each target entity, so as to generate an entity relationship graph.

[0057] The technical solution of this embodiment obtains at least one reference data of the target business by responding to an instruction to determine the entity relationship between target entities in the target business; generates a target entity field based on the first entity field when it is determined that the target reference data contains a first entity field defined in a preset entity configuration rule; generates target entity data according to the target reference data and the target entity field; determines the entity relationship between target entities in the target entity data, and generates an entity relationship graph corresponding to the target business according to the entity relationship, so as to quickly determine the entity relationship between different data in the system and provide a basis for the operation and maintenance of the system.

[0058] Embodiment 2

[0059] Figure 2 1 is a flow chart of a method for determining entity relationships according to Embodiment 2 of the present invention. This embodiment is a further refinement of the above technical solution. The technical solution in this embodiment can be combined with each optional solution in one or more of the above embodiments. Figure 2 As shown, the method includes:

[0060] Step 210: In response to an instruction to determine an entity relationship between target entities in a target business, obtain at least one reference data of the target business.

[0061] Step 220: split the target reference data into intermediate data including fields and data content matching each field; match each field with the first entity field defined in the preset entity configuration rule; if the matches are consistent, determine that the target reference data contains the first entity field defined in the preset entity configuration rule.

[0062] In an optional implementation of the present embodiment, after obtaining each reference data, the target reference data can be further split into intermediate data containing each field and data content matching each field; further, each field can be matched with the first entity field defined in the preset entity configuration rule respectively; if the matches are consistent, for example, the first field in the target reference data is consistent with the first entity field defined in the preset entity configuration rule, then it can be determined that the target reference data contains the first entity field defined in the preset entity configuration rule.

[0063] Step 230: Generate a target entity field based on the first entity field.

[0064] In an optional implementation of this embodiment, after determining that the target reference data includes the first entity field defined in the preset entity configuration rule, the target entity field may be further generated based on the first entity field.

[0065] Optionally, in this embodiment, generating a target entity field based on the first entity field may include: generating a target entity field based on the entity configuration rule, according to the first entity field, data content of the first entity field, and a target character string.

[0066] In an optional implementation of the present embodiment, based on the entity configuration rule, generating the target entity field according to the first entity field, the data content of the first entity field and the target string can include combining the first entity field with a preset string to obtain a first component of the target entity field; using the data content of the first entity field as the second component of the target entity field; connecting the first component and the second component by a preset connector to obtain the target entity field; and generating the target entity identifier according to the data content of the first entity field.

[0067] In this embodiment, the preset string can be combined with the first entity field to obtain the first component of the target entity field; exemplarily, if the preset string is "yotta.entity" and the first entity field is "hostname", then the first component of the target entity field can be "yotta.entity.hostname".

[0068] Furthermore, the data content of the first entity field can be used as the second component of the target entity field, and the first component and the second component can be connected by a preset connector to obtain the target entity field. It can be understood that in this embodiment, the target entity field can be expressed as "first component (preset string + first entity field) = second component".

[0069] For example, if the specific numeric content of the first entity field is "10.23.42.1", it can be used as the second component of the target entity field, and the obtained target entity field can be "yotta.entity.hostname=10.23.42.1".

[0070] Step 240: Generate a target entity identifier according to the data content of the target entity field.

[0071] Optionally, in this embodiment, after obtaining the target entity field, a target entity identifier may be further generated according to the data content of the target entity field.

[0072] Exemplarily, if the target entity fields of the target reference data are yotta.entity.hostname=10.23.42.1 and yotta.entity.process=cmd123, then the target entity identifier generated according to these two target entity fields may be yotta.entity.id=10.23.42.1-cmd123.

[0073] Step 250: Add the target entity field and the target entity identifier to the target reference data to obtain the target entity data.

[0074] In an optional implementation of this embodiment, after obtaining the target entity field and the target entity identifier of the target reference data, the target entity field and the target entity identifier may be further added to the target reference data to obtain the target entity data.

[0075] Exemplarily, the data content of the target entity data may be as follows: source=indicator; hostname=10.23.42.1; process=cmd1234; process.cpu.usage=80%; time=2024.8.10 16:34:34; process.type=java; yotta.entity.hostname=10.23.42.1; yotta.entity.process=cmd1234; yotta.entity.id=10.23.42.1-cmd123.

[0076] In an optional implementation of the present embodiment, after obtaining the target entity data, the target entity data can be stored in a target memory. By way of example, in the present embodiment, entity data of the same indicator can be stored in the same memory, so that the data of the same indicator can be processed quickly, preventing different data from being stored together, which would increase the difficulty of data processing.

[0077] Step 260: Determine the entity relationship between the target entities in the target entity data, and generate an entity relationship graph corresponding to the target business according to the entity relationship.

[0078] In an optional implementation of this embodiment, after the target entity data is obtained, the entity relationship between the target entities in the target entity data may be further determined, and an entity relationship graph corresponding to the target business may be generated according to the entity relationship.

[0079] Optionally, in this embodiment, after obtaining the entity relationship between the target entities, the entity relationship can be added to the target entity data in a simplified version. For example, in the above example, the entity relationship is added to the target entity data, and the following can be obtained: source = metric; hostname = 10.23.42.1; process = cmd1234; process.cpu.usage = 80%; time = 2024.8.10 16:34:34; process.type = java; yotta.entity.hostname = 10.23.42.1; yotta.entity.process = cmd1234; yotta.entity.id = 10.23.42.1-cmd123; relationshipname: belong{from: yotta.entity.process = cmd1234; to: yotta.entity.id = 10.23.42.1-cmd123}.

[0080] In an optional implementation of the present embodiment, after an entity relationship diagram corresponding to the target business is generated based on the entity relationship, the root cause of the alarm data can also be determined based on the entity relationship diagram. For example, the first target entity that generates the alarm data can be determined through the entity relationship diagram. This entity is the root cause of the alarm data. By maintaining this entity, the anomaly generated by the alarm data can be processed.

[0081] The solution of this embodiment, after acquiring each reference data, can further split the target reference data, and split the target reference data into intermediate data containing each field and data content matching each field; further, each field can be matched with the first entity field defined in the preset entity configuration rule respectively; if the matches are consistent, for example, the first field in the target reference data is consistent with the first entity field defined in the preset entity configuration rule, then it can be determined that the target reference data contains the first entity field defined in the preset entity configuration rule, and it can be quickly determined whether the target reference data contains the first entity field, providing a basis for the subsequent generation of a relationship diagram between the entities.

[0082] Embodiment 3

[0083] Figure 3 FIG. 1 is a schematic diagram of a structure of an entity relationship determination device provided according to Embodiment 3 of the present invention. Figure 3 As shown, the device includes: a reference data acquisition module 310, a target entity field generation module 320, a target entity data generation module 330 and an entity relationship diagram determination module 340.

[0084] A reference data acquisition module 310, configured to acquire at least one reference data of the target business in response to an instruction to determine an entity relationship between target entities in the target business;

[0085] A target entity field generating module 320 is configured to generate a target entity field based on a first entity field defined in a preset entity configuration rule when it is determined that the target reference data includes the first entity field;

[0086] A target entity data generating module 330, configured to generate target entity data according to the target reference data and the target entity field;

[0087] The entity relationship diagram determination module 340 is used to determine the entity relationship between target entities in the target entity data, and generate an entity relationship diagram corresponding to the target business according to the entity relationship.

[0088] The solution of this embodiment is to obtain at least one reference data of the target business by a reference data acquisition module in response to an instruction to determine the entity relationship between target entities in the target business; to generate a target entity field based on the first entity field defined in a preset entity configuration rule when determining that the target reference data contains the first entity field; to generate target entity data according to the target reference data and the target entity field by a target entity data generation module; to determine the entity relationship between target entities in the target entity data by an entity relationship graph determination module, and to generate an entity relationship graph corresponding to the target business according to the entity relationship, so as to quickly determine the entity relationship between different data in the system and provide a basis for the operation and maintenance of the system.

[0089] In an optional implementation of this embodiment, the preset entity configuration rule is determined by the following steps:

[0090] defining at least one first entity field, and determining each of the first entity fields as an entity type;

[0091] randomly generating a target character string, and determining the target character string and the first entity field as a first component of a target entity field;

[0092] Determine the data content matching the first entity field as the second component of the target entity field;

[0093] Connecting the first component and the second component by a preset connector to obtain the target entity field;

[0094] Alternatively, the combined content of each of the target entity fields is determined as a unique key;

[0095] The unique key randomly generates a target entity identifier according to the data content of each target entity field;

[0096] The first entity field includes hostname and / or process; and the target string is yotta.entity.

[0097] In an optional implementation of this embodiment, the reference data includes at least one of the following:

[0098] Log data, indicator data, link data, and alarm data.

[0099] In an optional implementation of this embodiment, the target entity field generation module 320 is specifically used to split the target reference data into intermediate data including each field and data content matching each field;

[0100] Matching each of the fields with the first entity field defined in the preset entity configuration rule respectively;

[0101] If the match is consistent, it is determined that the target reference data contains the first entity field defined in the preset entity configuration rule.

[0102] In an optional implementation of this embodiment, the target entity field generation module 320 is further used to generate a target entity field based on the entity configuration rule according to the first entity field, the data content of the first entity field and the target string;

[0103] Correspondingly, the entity relationship determination device further includes: a target entity identifier generation module, which is used to generate a target entity identifier according to the data content of the target entity field.

[0104] In an optional implementation of this embodiment, the target entity data generating module 330 is specifically configured to add the target entity field and the target entity identifier to the target reference data to obtain the target entity data.

[0105] In an optional implementation of this embodiment, the entity relationship diagram determining module 340 is specifically used to compare each target entity field in the target entity data with the pre-established entity relationship, and determine the entity relationship between each target entity in the target entity data according to the comparison result;

[0106] Determine the upstream and downstream entities of each target entity according to the entity relationship between each target entity, and generate the entity relationship graph according to each upstream and downstream entity;

[0107] The pre-established entity relationship includes: inclusion or connection.

[0108] The device for determining entity relationships provided in the embodiment of the present invention can execute the method for determining entity relationships provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0109] Embodiment 4

[0110] Figure 4A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0111] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0112] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0113] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 11 executes the various methods and processes described above, such as a method for determining an entity relationship, which may include: in response to an instruction for determining an entity relationship between target entities in a target business, obtaining at least one reference data of the target business; in the case of determining that the target reference data contains a first entity field defined in a preset entity configuration rule, generating a target entity field based on the first entity field; generating target entity data according to the target reference data and the target entity field; determining the entity relationship between target entities in the target entity data, and generating an entity relationship graph corresponding to the target business according to the entity relationship.

[0114] In some embodiments, the method for determining entity relationships may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the method for determining entity relationships described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the method for determining entity relationships in any other appropriate manner (e.g., by means of firmware).

[0115] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0116] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0117] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0118] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0119] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0120] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0121] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0122] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for determining entity relationships, characterized in that: include: In response to an instruction to determine an entity relationship between target entities in a target business, acquiring at least one reference data of the target business; In a case where it is determined that the target reference data includes a first entity field defined in a preset entity configuration rule, generating a target entity field based on the first entity field; Generate target entity data according to the target reference data and the target entity field; An entity relationship between target entities in the target entity data is determined, and an entity relationship graph corresponding to the target business is generated according to the entity relationship.

2. The method for determining entity relationships according to claim 1, characterized in that: The preset entity configuration rule is determined by the following steps: defining at least one first entity field, and determining each of the first entity fields as an entity type; randomly generating a target character string, and determining the target character string and the first entity field as a first component of a target entity field; Determine the data content matching the first entity field as the second component of the target entity field; Connecting the first component and the second component by a preset connector to obtain the target entity field; Alternatively, the combined content of each of the target entity fields is determined as a unique key; The unique key randomly generates a target entity identifier according to the data content of each target entity field; Wherein, the first entity field includes hostname and / or process; The target string is yotta.entity.

3. The method for determining entity relationships according to claim 1, characterized in that: The reference data includes at least one of the following: Log data, indicator data, link data, and alarm data.

4. The method for determining entity relationships according to claim 2, characterized in that: The determining target reference data includes a first entity field defined in a preset entity configuration rule, including: Splitting the target reference data into intermediate data including each field and data content matching each field; Matching each of the fields with the first entity field defined in the preset entity configuration rule respectively; If the match is consistent, it is determined that the target reference data contains the first entity field defined in the preset entity configuration rule.

5. The method for determining entity relationships according to claim 4, characterized in that: The generating a target entity field based on the first entity field includes: Based on the entity configuration rule, generating a target entity field according to the first entity field, data content of the first entity field, and a target character string; Correspondingly, after generating the target entity field according to the first entity field, the data content of the first entity field and the target character string, the method further includes: A target entity identifier is generated according to the data content of the target entity field.

6. The method for determining entity relationships according to claim 5, characterized in that: The generating target entity data according to the target reference data and the target entity field includes: The target entity field and the target entity identifier are added to the target reference data to obtain the target entity data.

7. The method for determining entity relationships according to claim 1, characterized in that: The determining the entity relationship between the target entities in the target entity data, and generating an entity relationship graph corresponding to the target business according to the entity relationship, includes: Comparing each target entity field in the target entity data with a pre-established entity relationship, and determining the entity relationship between each target entity in the target entity data according to the comparison result; Determine the upstream and downstream entities of each target entity according to the entity relationship between each target entity, and generate the entity relationship graph according to each upstream and downstream entity; The pre-established entity relationship includes: inclusion or connection.

8. A device for determining entity relationships, characterized in that: include: A reference data acquisition module, configured to acquire at least one reference data of the target business in response to an instruction to determine an entity relationship between target entities in the target business; A target entity field generating module, configured to generate a target entity field based on a first entity field defined in a preset entity configuration rule when it is determined that the target reference data contains the first entity field; A target entity data generating module, used to generate target entity data according to the target reference data and the target entity field; The entity relationship diagram determination module is used to determine the entity relationship between each target entity in the target entity data, and generate an entity relationship diagram corresponding to the target business according to the entity relationship.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the method for determining entity relationships according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for determining an entity relationship according to any one of claims 1 to 7 when executed.

Images