Graph database monitoring method and apparatus, electronic device, and medium

Abstract

Embodiments of the present invention provide a graph database monitoring method, apparatus, electronic device, and medium, relating to the field of data processing technology. The method includes: receiving data processing requests for various graph databases based on a data access layer; determining whether the data processing request involves content to be monitored based on monitoring rules; and determining the target graph database for the request processing. If the data processing request involves content to be monitored, then during the processing of the target graph database based on the data processing request, the content to be monitored is monitored, thereby conveniently realizing the monitoring of multiple graph databases based on a graph data platform.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and more specifically, to a graph database monitoring method, apparatus, electronic device, and medium. Background Technology

[0002] Graph databases are data management systems based on nodes and edges as the basic storage units, designed for efficient storage and retrieval of graph data. Because graph database technology itself is still under development and improvement, most graph databases do not provide monitoring functionality, requiring application vendors to implement it themselves for specific scenarios. Furthermore, the lack of unified standards for query languages ​​and management specifications among existing graph databases means that monitoring different graph database types requires different implementations, making monitoring implementation inconvenient. Summary of the Invention

[0003] One of the objectives of this invention includes, for example, providing a graph database monitoring method, apparatus, electronic device, and medium to at least partially improve the convenience of graph database monitoring.

[0004] The embodiments of the present invention can be implemented as follows:

[0005] In a first aspect, the present invention provides a graph database monitoring method applied to a graph data platform, wherein the graph data platform is configured with monitoring rules and has a data access layer for connecting to two or more graph databases, the method comprising:

[0006] The data access layer receives data processing requests for each of the graph databases.

[0007] Based on the monitoring rules, determine whether the data processing request involves content to be monitored, and determine the target graph database for the request processing based on the data processing request.

[0008] If the data processing request involves content to be monitored, then during the processing of the target graph database based on the data processing request, the content to be monitored will be monitored.

[0009] In an optional implementation, the method further includes the step of configuring the listening rules, which includes:

[0010] In response to a rule creation operation, the rule creation interface is displayed;

[0011] The system retrieves the entity object to be monitored as input in the rule creation interface, checks whether the entity object exists in each of the graph databases, and if so, displays the relevant information of the entity object; otherwise, it displays a message indicating that the entity object does not exist.

[0012] In response to the warning type selected from the relevant information, a warning configuration interaction is performed to obtain configuration information;

[0013] In response to a save operation, the listening rules are derived based on the configuration information.

[0014] In an optional implementation, the step of performing early warning configuration interaction to obtain configuration information includes:

[0015] If the selected warning type is edge attribute, an interface for selecting edge attributes and configuring warning operators and warning thresholds will be displayed to obtain the configuration information corresponding to the edge attribute.

[0016] If the selected alert type is entity relationship, an interface will be displayed to select the alert operation type and whether to consider the direction, so as to obtain the configuration information corresponding to the entity relationship.

[0017] In an optional implementation, the alert operation types include creation, modification, and deletion; the data access layer includes a general graph query interface;

[0018] The data processing request includes a data input request. The step of determining whether the data processing request involves content to be monitored based on the monitoring rules includes:

[0019] The data to be input is determined based on the data processing request;

[0020] Based on the monitoring rules, it is determined whether there is any content to be monitored in the input data.

[0021] In an optional implementation, the step of obtaining the listening rules based on the configuration information includes:

[0022] Perform a completeness check on the configuration information;

[0023] If the completeness check passes, the configuration information will be stored as a listening rule;

[0024] If the completeness check fails, the configuration information adjustment interface will be displayed, prompting you to supplement or modify the configuration information until the completeness check of the supplemented or modified configuration information passes. Then, the supplemented or modified configuration information will be stored as a listening rule.

[0025] In an optional implementation, the content to be monitored includes entity relationship objects to be monitored;

[0026] The step of monitoring the content to be monitored includes:

[0027] If there is an entity relationship object to be monitored in the data processing request, and the warning operation type is creation or modification, then it is determined whether the entity relationship type corresponding to the entity relationship object has been monitored in the monitoring rule corresponding to the edge attribute. If so, the edge attribute configured in the monitoring rule corresponding to the edge attribute is read, the corresponding edge attribute value is obtained from the entity relationship object, and the entity relationship object is judged to meet the warning conditions by combining the warning operator and the warning threshold. If the warning conditions are met, a warning is issued.

[0028] If there is an entity relationship object to be monitored in the data processing request, and the warning operation type is creation or deletion, then it is determined whether the entity relationship type corresponding to the entity relationship object has been monitored in the monitoring rules corresponding to the entity relationship. If so, it is determined whether the entity relationship object meets the warning conditions according to the direction configured in the monitoring rules corresponding to the entity relationship, the entity objects at both ends of the relationship, and the warning operation type. If the warning conditions are met, then a warning is issued.

[0029] In an optional implementation, the graph data platform has pre-established connections with each of the graph databases and pre-stored the identification information of each of the graph databases;

[0030] The data processing request carries identification information of the target graph database. The step of determining the target graph database to be processed based on the data processing request includes:

[0031] Based on the identification information carried in the data processing request, relevant information about the target graph database is obtained, including the type and connection of the target graph database;

[0032] The data processing request is executed based on the type and connection of the target graph database.

[0033] Secondly, embodiments of the present invention provide a graph database monitoring device applied to a graph data platform, wherein the graph data platform is configured with monitoring rules and has a data access layer for connecting to two or more graph databases, and the graph database monitoring device includes:

[0034] The data receiving module is used to receive data processing requests for each of the graph databases based on the data access layer;

[0035] The data processing module is used to determine whether the data processing request involves content to be monitored based on the monitoring rules, and to determine the target graph database to be processed according to the data processing request; if the data processing request involves content to be monitored, then the content to be monitored is monitored during the processing of the target graph database based on the data processing request.

[0036] Thirdly, embodiments of the present invention provide an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the graph database monitoring method described in any of the foregoing embodiments.

[0037] Fourthly, embodiments of the present invention provide a computer-readable storage medium, the computer-readable storage medium including a computer program, wherein the computer program, when running, controls the electronic device where the computer-readable storage medium is located to execute the graph database monitoring method described in any of the foregoing embodiments.

[0038] The beneficial effects of this invention include, for example, connecting two or more graph databases through a graph data platform configured with monitoring rules and a data access layer, ensuring that all data enters each graph database via the graph data platform. This setup allows for convenient monitoring of different graph databases by simply monitoring the relationship data at the data access layer when monitoring changes in graph relationship data in different graph databases. Attached Figure Description

[0039] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 The diagram illustrates an application scenario provided by an embodiment of the present invention.

[0041] Figure 2 An exemplary structural block diagram of an electronic device provided by an embodiment of the present invention is shown.

[0042] Figure 3 The diagram shows a flowchart of a graph database monitoring method provided by an embodiment of the present invention.

[0043] Figure 4 The diagram illustrates a flowchart of configuring listening rules according to an embodiment of the present invention.

[0044] Figure 5 This diagram illustrates one of the interactive interfaces in a rule configuration process provided by an embodiment of the present invention.

[0045] Figure 6 The second diagram shows an interactive interface during a rule configuration process provided by an embodiment of the present invention.

[0046] Figure 7An exemplary structural block diagram of a graph database monitoring device provided by an embodiment of the present invention is shown.

[0047] Icons: 100 - Electronic device; 110 - Memory; 120 - Processor; 130 - Communication module; 140 - Graph database monitoring device; 141 - Data receiving module; 142 - Data processing module. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0049] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0050] It should be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0051] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0052] It should be noted that, where there is no conflict, the features in the embodiments of the present invention can be combined with each other.

[0053] Please see Figure 1This is a schematic diagram illustrating an application scenario provided in this embodiment. To monitor changes in relational data across various graph databases, this embodiment of the invention constructs a graph data platform. This platform includes a unified data access layer that interfaces with different graph databases, ensuring that all data enters the graph databases via the platform. Therefore, by configuring monitoring rules and monitoring relational data at the data access layer, monitoring changes in relational data across different graph databases can be achieved.

[0054] In this embodiment, the graph data platform and each graph database can be located on different electronic devices or integrated into the same electronic device.

[0055] Please refer to Figure 2 This is a block diagram of an electronic device 100 provided in this embodiment. The electronic device 100 in this embodiment can be a server, processing device, processing platform, etc., capable of data interaction and processing. The electronic device 100 integrates a graph data platform that interfaces with two or more graph databases. The electronic device 100 includes a memory 110, a processor 120, and a communication module 130. The memory 110, processor 120, and communication module 130 are electrically connected directly or indirectly to each other to realize data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses or signal lines.

[0056] The memory 110 is used to store programs or data. The memory 110 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.

[0057] The processor 120 is used to read / write data or programs stored in the memory 110 and to perform corresponding functions.

[0058] The communication module 130 is used to establish a communication connection between the electronic device 100 and other communication terminals through the network, and to send and receive data through the network.

[0059] It should be understood that, Figure 2 The structure shown is only a schematic diagram of the electronic device 100. The electronic device 100 may also include components that are larger than... Figure 2 The more or fewer components shown, or having the same Figure 2 The different configurations shown. Figure 2 The components shown can be implemented using hardware, software, or a combination thereof.

[0060] Please refer to the following: Figure 3 This is a flowchart illustrating a graph database monitoring method provided in an embodiment of the present invention. It can be derived from... Figure 2 The electronic device 100 executes the commands, for example, by the processor 120 within the electronic device 100. The electronic device 100 integrates a graph data platform, which is configured with monitoring rules and has a data access layer for interfacing with two or more graph databases. The graph database monitoring method includes steps S110, S120, and S130.

[0061] S110, receiving data processing requests for each of the graph databases based on the data access layer.

[0062] S120, based on the monitoring rules, determine whether the data processing request involves content to be monitored, and determine the target graph database for the request processing according to the data processing request.

[0063] S130, if the data processing request involves content to be monitored, then during the processing of the target graph database based on the data processing request, the content to be monitored is monitored.

[0064] This embodiment, through clever configuration of the graph data platform, enables convenient monitoring of changes in relational data in various graph databases.

[0065] The monitoring rules can be obtained in various ways. For example, historical monitoring and early warning records for various graph databases can be obtained through big data collection, and various monitoring rules can be derived by processing these historical records. Alternatively, a customization function can be provided, allowing users to define their own monitoring rules. Another example is that multiple monitoring rules derived from historical monitoring and early warning records can be provided for users to choose from, along with a customization function that allows users to define their own monitoring rules. This embodiment does not impose any limitations on this.

[0066] Please see Figure 4 This embodiment provides one implementation process for configuring listening rules, including S210 to S260.

[0067] S210, in response to the rule creation operation, displays the rule creation interface.

[0068] S220: Obtain the entity object to be monitored input in the rule creation interface, and check whether the entity object exists in each of the graph databases. If yes, execute S230 to S250; otherwise, execute S260.

[0069] S230 displays relevant information about the entity object.

[0070] S240, in response to the warning type selected from the relevant information, a warning configuration interaction is performed to obtain configuration information.

[0071] S250, in response to a save operation, obtains the listening rules based on the configuration information.

[0072] S260, a prompt message indicating that the entity object does not exist is displayed.

[0073] In one implementation, the display interface of the graph data platform may include an option to create rules. After the user selects the option, the corresponding rule creation operation is generated, and the graph data platform then executes S210 to S260 to obtain the listening rules.

[0074] In S240, there can be multiple types of warnings, such as edge attributes and entity relationships. There are multiple ways to perform warning configuration interaction to obtain configuration information for different warning types.

[0075] For example, please see Figure 5 If the selected warning type is edge attribute, an interface for selecting edge attributes and configuring warning operators and warning thresholds will be displayed to obtain the configuration information corresponding to the edge attribute.

[0076] For example, please see Figure 6 If the selected alert type is entity relationship, an interface will be displayed to select the alert operation type and whether to consider the direction, so as to obtain the configuration information corresponding to the entity relationship.

[0077] To ensure the reliability of the monitoring rule configuration, during the process of obtaining the monitoring rule based on the configuration information in S250, a completeness check can also be performed on the configuration information. If the completeness check passes, the configuration information is stored as a monitoring rule. If the completeness check fails, a configuration information adjustment interface is displayed, prompting for the supplementation or modification of the configuration information, until the completeness check of the supplemented or modified configuration information passes, at which point the supplemented or modified configuration information is stored as a monitoring rule.

[0078] For example, the configuration process for a monitoring rule (also known as an alert rule) may involve generating an alert rule, selecting the instance to monitor, selecting the alert type, selecting the alert operation type, selecting the entity relationship, selecting the target instance, and deciding whether to consider direction. The alert operation type can include creation, modification, and deletion.

[0079] In one implementation, an electronic device equipped with a graph data platform can monitor user operations. When it detects that the user selects to create an alert rule, it enters the alert rule creation interface, verifies the name of the entity object requiring alert input by the user, and returns the name to the user if the entity object exists in the graph database; otherwise, it prompts the user that the entity object does not exist. It also verifies the alert type selected by the user. When the alert type is selected as edge attribute, it enters the edge attribute monitoring configuration (e.g., ...). Figure 5 As shown in the image, the user is prompted to select the edge attribute of a specific entity relationship object to be monitored, and to configure the alert operator and alert threshold. When the alert type is selected as entity relationship, the user enters the instance-to-instance relationship monitoring configuration (e.g., ...). Figure 6 As shown in the image, the system prompts the user to select the target instance, alert operation type, entity relationship (type), and whether to consider a direction. When the user selects to save the alert rule, a rule completeness check is performed on the user-configured alert rule. If any data required from the previous steps is found to be empty or incorrect, the user is prompted to fill in or modify the information. Once the completeness check passes, the alert rule is saved to the database.

[0080] In this embodiment, the data access layer for connecting to two or more graph databases can be implemented in various ways. For example, it can be implemented using a general graph query interface. To achieve effective monitoring of each graph database, in one implementation, after the graph data platform starts, a connection can be established with each graph database based on the general graph query interface.

[0081] The data processing requests in S110 can be of various types, such as data input requests, data query requests, and data modification requests.

[0082] Accordingly, in S120, when the data processing request is a data input request, it can be determined whether the data processing request involves content to be monitored based on the monitoring rules in the following way: determine the data to be input based on the data processing request, and determine whether the content to be monitored exists in the data to be input based on the monitoring rules. The processing method for data processing requests such as data query requests and data modification requests is similar and will not be repeated here.

[0083] To facilitate the identification of target graph databases, the graph data platform can pre-store the identification information of each graph database. The platform can also establish connections with each graph database in advance; for example, connections can be established when the platform starts up. Correspondingly, the data processing request can carry the identification information of the target graph database.

[0084] Accordingly, in S120, determining the target graph database for processing based on the data processing request can be achieved in the following way: Based on the identification information carried in the data processing request, relevant information about the target graph database is obtained, including the type and connection of the target graph database. The data processing request is then executed based on the type and connection of the target graph database.

[0085] The identification information can be of various types, such as set characters or unique IDs. Taking ID as the identification information and a general graph query interface as the data access layer as an example, the electronic device listens for graph data processing requests from the general graph query interface. Upon receiving the request, it obtains the relevant information of the target graph database to be accessed based on the ID carried in the request. Based on the relevant information of the target graph database, it obtains the type and connection of the target graph database, and then executes the data processing request according to the obtained type and connection of the target graph database.

[0086] In this embodiment, the content to be monitored may include entity relationship objects to be monitored. In S130, different methods can be used to monitor different content.

[0087] For example, if there is an entity relationship object to be monitored in the data processing request, and the warning operation type is creation or modification, it can be determined whether the entity relationship type corresponding to the entity relationship object has been monitored in the monitoring rule corresponding to the edge attribute. If so, the edge attribute configured in the monitoring rule corresponding to the edge attribute is read, the corresponding edge attribute value is obtained from the entity relationship object, and the entity relationship object is judged to meet the warning conditions by combining the warning operator and the warning threshold. If the warning conditions are met, a warning is issued.

[0088] For example, if there is an entity relationship object to be monitored in the data processing request, and the warning operation type is creation or deletion, it can be determined whether the entity relationship type corresponding to the entity relationship object has been monitored in the monitoring rules corresponding to the entity relationship. If so, it can be determined whether the entity relationship object meets the warning conditions according to the direction configured in the monitoring rules corresponding to the entity relationship, the entity objects at both ends of the relationship, and the warning operation type. If the warning conditions are met, a warning is issued.

[0089] When a monitoring rule (also known as an alert rule) is executed, it compares and verifies external input data according to its configuration. For data that meets the alert conditions, an alert is issued. For example, when data input is detected, the configured listener can scan all alert rules sequentially and evaluate them one by one. If the alert conditions are met, an alert is issued; otherwise, the process stops. By executing each alert rule, reliable monitoring of the required content can be achieved.

[0090] For ease of understanding, the terminology in this embodiment is explained as follows:

[0091] Entity type: An abstract type definition for entity objects, such as people or companies.

[0092] An instance (entity, entity object, instance object) refers to a specific data object. For example, a specific person or a specific company.

[0093] Entity relationships (relationship definitions, edge definitions): are abstract definitions of the relationships between different entity types. For example, there is an entity relationship definition of friends between entity type people and entity type companies.

[0094] Entity relationship (relationship, edge) object: refers to a specific relationship between two concrete instances. Company A and Company B have a specific controlling relationship.

[0095] Relationship attributes (edge ​​attributes): Further description of entity relationships. For example, a description of a controlling relationship includes the start time of the controlling stake, the end time of the controlling stake, and the percentage of controlling stake.

[0096] Relationship attribute (edge ​​attribute) value: The value of the edge attribute defined on the relationship between two specific entities. For example, Company A has a controlling stake in Company B, the controlling stake begins on January 1, 2019 and ends on January 1, 2022, with a controlling stake of 52%.

[0097] Entity numerical attributes: Various attribute definitions used to describe entity objects, such as age, height, weight, etc., for a person entity.

[0098] Entity numerical attribute values: These refer to the specific numerical attributes of an entity / instance. The numerical attributes an entity / instance can possess are defined by the entity type to which it belongs. For example, if Xiaoming is a person, then Xiaoming's numerical attributes are defined by the entity type "person". For instance, Xiaoming's height is 1.5 meters, his weight is 40 kg, and his age is 15 years old.

[0099] Alert type: refers to the data type that needs to be monitored. Data types include numerical attribute definitions and entity relationship definitions.

[0100] Alert operation type: refers to the type of data operation that needs to be monitored. The data operation types here include creating data, deleting data, etc.

[0101] Warning operators: These refer to the operations performed on numerical attributes, including equal to, not equal to, greater than, less than, greater than or equal to, and less than or equal to operators.

[0102] Warning threshold: refers to the threshold that triggers a warning.

[0103] Direction: refers to the direction of relational data in a graph database.

[0104] To perform the corresponding steps in the above embodiments and various possible methods, an implementation of a graph database monitoring device is given below. Please refer to... Figure 7 , Figure 7 This is a functional block diagram of a graph database monitoring device 140 provided in an embodiment of the present invention. The graph database monitoring device 140 can be applied to... Figure 2 The electronic device 100 shown includes a graph data platform configured with monitoring rules and a data access layer for connecting to two or more graph databases. It should be noted that the graph database monitoring device 140 provided in this embodiment has the same basic principle and technical effects as the embodiments described above. For the sake of brevity, any parts not mentioned in this embodiment can be referred to the corresponding content in the above embodiments. The graph database monitoring device 140 includes a data receiving module 141 and a data processing module 142.

[0105] The data receiving module 141 is used to receive data processing requests for each of the graph databases based on the data access layer.

[0106] The data processing module 142 is used to determine whether the data processing request involves content to be monitored based on the monitoring rules, and to determine the target graph database to be processed according to the data processing request; if the data processing request involves content to be monitored, then the content to be monitored is monitored during the processing of the target graph database based on the data processing request.

[0107] Based on the above, embodiments of the present invention also provide a computer-readable storage medium, the computer-readable storage medium including a computer program, wherein the computer program, when running, controls the electronic device where the computer-readable storage medium is located to execute the above-described graph database monitoring method.

[0108] By adopting the above-described solution in this embodiment of the invention, different graph databases can be connected based on the graph data platform. This makes it convenient to monitor graph data without having to pay attention to the query syntax of different graph databases. Only the monitoring rules of the instance data to be monitored need to be configured.

[0109] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative; for example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of the invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0110] In addition, the functional modules in the various embodiments of the present invention can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0111] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0112] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A graph database monitoring method, characterized in that, Applied to a graph data platform, wherein the graph data platform is configured with listening rules and has a data access layer for connecting to two or more graph databases, the method includes: The data access layer receives data processing requests for each of the graph databases. Based on the monitoring rules, determine whether the data processing request involves content to be monitored, and determine the target graph database for the request processing based on the data processing request. If the data processing request involves content to be monitored, then during the processing of the target graph database based on the data processing request, the content to be monitored will be monitored. The method further includes: configuring the listening rules, which includes: In response to a rule creation operation, the rule creation interface is displayed; The system retrieves the entity object to be monitored as input in the rule creation interface, checks whether the entity object exists in each of the graph databases, and if so, displays the relevant information of the entity object; otherwise, it displays a message indicating that the entity object does not exist. In response to the warning type selected from the relevant information, if the selected warning type is an edge attribute, an interface for selecting the edge attribute and configuring the warning operator and warning threshold is displayed to obtain the configuration information corresponding to the edge attribute; if the selected warning type is an entity relationship, an interface for selecting the warning operation type and whether to consider the direction is displayed to obtain the configuration information corresponding to the entity relationship. In response to the save operation, the configuration information is checked for completeness. If the completeness check passes, the configuration information is stored as a listening rule. If the completeness check fails, the configuration information adjustment interface is displayed, prompting the user to supplement or modify the configuration information until the completeness check of the supplemented or modified configuration information passes. Then, the supplemented or modified configuration information is stored as a listening rule. The content to be monitored includes entity relationship objects to be monitored; the steps of monitoring the content to be monitored include: If there is an entity relationship object to be monitored in the data processing request, and the warning operation type is creation or modification, then it is determined whether the entity relationship type corresponding to the entity relationship object has been monitored in the monitoring rule corresponding to the edge attribute. If so, the edge attribute configured in the monitoring rule corresponding to the edge attribute is read, the corresponding edge attribute value is obtained from the entity relationship object, and the entity relationship object is judged to meet the warning conditions by combining the warning operator and the warning threshold. If the warning conditions are met, a warning is issued. If there is an entity relationship object to be monitored in the data processing request, and the warning operation type is creation or deletion, then it is determined whether the entity relationship type corresponding to the entity relationship object has been monitored in the monitoring rules corresponding to the entity relationship. If so, it is determined whether the entity relationship object meets the warning conditions according to the direction configured in the monitoring rules corresponding to the entity relationship, the entity objects at both ends of the relationship, and the warning operation type. If the warning conditions are met, then a warning is issued.

2. The graph database monitoring method of claim 1, wherein, The step of performing early warning configuration interaction to obtain configuration information includes: If the selected warning type is edge attribute, the interface for selecting edge attributes and configuring warning operators and warning thresholds will be displayed to obtain the configuration information corresponding to the edge attribute. If the selected alert type is entity relationship, an interface will be displayed to select the alert operation type and whether to consider the direction, so as to obtain the configuration information corresponding to the entity relationship.

3. The graph database monitoring method according to claim 2, characterized in that, The warning operation types include creation, modification, and deletion; the data access layer includes a general graph query interface; The data processing request includes a data input request. The step of determining whether the data processing request involves content to be monitored based on the monitoring rules includes: The data to be input is determined based on the data processing request; Based on the monitoring rules, it is determined whether there is any content to be monitored in the input data.

4. The graph database monitoring method of claim 1, wherein, The graph data platform has pre-established connections with each of the graph databases and pre-stored the identification information of each of the graph databases; The data processing request carries identification information of the target graph database. The step of determining the target graph database to be processed based on the data processing request includes: Based on the identification information carried in the data processing request, relevant information about the target graph database is obtained, including the type and connection of the target graph database; The data processing request is executed based on the type and connection of the target graph database.

5. A graph database monitoring device, characterized in that, Applied to a graph data platform, the graph data platform is configured with listening rules and has a data access layer for connecting to two or more graph databases. The graph database listening device includes: The data receiving module is used to receive data processing requests for each of the graph databases based on the data access layer; The data processing module is used to determine whether the data processing request involves content to be monitored based on the monitoring rules, and to determine the target graph database for the request processing based on the data processing request; if the data processing request involves content to be monitored, then during the processing of the target graph database based on the data processing request, the content to be monitored is monitored; and to execute the step of configuring the monitoring rules: in response to the rule creation operation, a rule creation interface is displayed; the entity object to be monitored input in the rule creation interface is obtained, and it is checked whether the entity object exists in each graph database. If it does, the relevant information of the entity object is displayed; if not, a prompt message indicating that the entity object does not exist is displayed; in response to the... If the selected alert type is an edge attribute, an interface for selecting the edge attribute and configuring the alert operator and alert threshold will be displayed to obtain the configuration information corresponding to the edge attribute. If the selected alert type is an entity relationship, an interface for selecting the alert operation type and whether to consider direction will be displayed to obtain the configuration information corresponding to the entity relationship. In response to the save operation, the configuration information is checked for completeness. If the completeness check passes, the configuration information is stored as a listening rule. If the completeness check fails, a configuration information adjustment interface will be displayed, prompting for the supplementation or modification of the configuration information, until the completeness check of the supplemented or modified configuration information passes, and then the supplemented or modified configuration information is stored as a listening rule. The content to be monitored includes entity relationship objects to be monitored. Monitoring the content to be monitored includes: if the data processing request contains entity relationship objects to be monitored, and the warning operation type is creation or modification, then determine whether the entity relationship type corresponding to the entity relationship object has been monitored in the monitoring rules corresponding to the edge attributes. If so, read the edge attributes configured in the monitoring rules corresponding to the edge attributes, obtain the corresponding edge attribute value from the entity relationship object, and combine the warning operator and warning threshold to determine whether the entity relationship object meets the warning conditions. If the warning conditions are met, then issue a warning. If the data processing request contains entity relationship objects to be monitored, and the warning operation type is creation or deletion, then determine whether the entity relationship type corresponding to the entity relationship object has been monitored in the monitoring rules corresponding to the entity relationship. If so, determine whether the entity relationship object meets the warning conditions based on the direction configured in the monitoring rules corresponding to the entity relationship, the entity objects at both ends of the relationship, and the warning operation type. If the warning conditions are met, then issue a warning.

6. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the graph database monitoring method according to any one of claims 1 to 4.

7. A computer readable storage medium characterized by The computer-readable storage medium includes a computer program, which, when executed, controls the electronic device containing the computer-readable storage medium to perform the graph database monitoring method according to any one of claims 1 to 4.

Images