Data consistency monitoring method, device, equipment, medium and program

Abstract

The embodiment of the invention provides a data consistency monitoring method, device, equipment, medium and program, which can be applied to the fields of database management, big data processing and the like, and the method comprises the following steps: obtaining a target monitoring item from a monitoring pool according to monitoring information of a monitoring event submitted by a user, and when the target monitoring item does not exist in the monitoring pool, sending the target monitoring item to the user; generating a target monitoring item according to the monitoring information; and determining target alarm configuration information of the target monitoring item, generating a monitoring task according to the target monitoring item and at least one to-be-merged monitoring item, generating an alarm task according to the target monitoring item and the alarm configuration information of each to-be-merged monitoring item, and performing consistency monitoring and alarm according to the monitoring task and the alarm task. The monitoring items are managed in a unified mode through the monitoring pool, redundant monitoring items are prevented from being generated, multiple monitoring tasks and alarm tasks are prevented from being generated by conducting monitoring merging processing and alarm merging processing on the multiple monitoring items, and storage resources and computing resources of monitoring equipment are saved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data processing, and in particular to a data consistency monitoring method, apparatus, device, medium, and program. Background Art

[0002] A large amount of data is stored in the data cluster, and the quality of this large amount of data needs to be monitored. Data quality monitoring includes data accuracy monitoring, consistency monitoring, integrity monitoring, etc.

[0003] In existing data consistency monitoring solutions, users configure monitoring objects, consistency monitoring indicators, monitoring alarm indicators, monitoring alarm thresholds, etc. on the data quality monitoring platform. The consistency monitoring objects are two objects (two tables or two fields). The monitoring platform generates monitoring alarm tasks based on the user-configured configuration information of the monitoring objects, consistency monitoring indicators, and monitoring alarms. Existing technologies use stovepipe-style monitoring and alarming, which prevents integration of different monitoring indicators for the same pair of monitoring objects. Each user needs to configure monitoring and alarms separately, resulting in multiple separate monitoring and alarm tasks, causing redundancy. Summary of the Invention

[0004] The embodiments of the present application provide a data consistency monitoring method, apparatus, device, medium, and program, which save storage resources and computing resources of the monitoring device and improve the performance of the monitoring system.

[0005] In a first aspect, an embodiment of the present application provides a data consistency monitoring method, the method comprising: obtaining a target monitoring item corresponding to a monitoring event submitted by a user from a monitoring pool, the monitoring pool including multiple generated monitoring items, the target monitoring item being used to perform consistency monitoring on a group of monitoring objects, the group of monitoring objects including two monitoring objects; when the target monitoring item does not exist in the monitoring pool, generating the target monitoring item according to the monitoring information; determining the target alarm configuration information of the target monitoring item according to the target monitoring item; generating a monitoring task according to the target monitoring item and at least one monitoring item to be merged, executing the monitoring task to obtain a consistency monitoring result of the monitoring event, generating an alarm task according to the target alarm configuration information and the alarm configuration information corresponding to the at least one monitoring item to be merged, executing the alarm task to obtain an alarm result of the monitoring event, wherein the monitoring table of the target monitoring item and each of the monitoring items to be merged is the same; determining a monitoring display result according to the consistency monitoring result, and performing alarm processing according to the alarm result.

[0006] In a second aspect, an embodiment of the present application provides a data consistency monitoring device, which includes: an acquisition module for acquiring a target monitoring item corresponding to a monitoring event submitted by a user from a monitoring pool, wherein the monitoring pool includes multiple generated monitoring items, and the target monitoring item is used to perform consistency monitoring on a group of monitoring objects, wherein the group of monitoring objects includes two monitoring objects; a generation module for generating the target monitoring item according to the monitoring information when the target monitoring item does not exist in the monitoring pool; a determination module for determining the target alarm configuration information of the target monitoring item according to the target monitoring item; a monitoring alarm module for generating a monitoring task according to the target monitoring item and at least one monitoring item to be merged, executing the monitoring task to obtain a consistency monitoring result of the monitoring event, generating an alarm task according to the target alarm configuration information and the alarm configuration information corresponding to the at least one monitoring item to be merged, executing the alarm task to obtain an alarm result of the monitoring event, wherein the monitoring table of the target monitoring item and each of the monitoring items to be merged is the same; a display module for determining a monitoring display result according to the consistency monitoring result, and performing alarm processing according to the alarm result.

[0007] In a third aspect, an embodiment of the present application provides a monitoring device, which includes: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to execute the method described in the first aspect above.

[0008] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program, and the computer program enables a computer to execute the method described in the first aspect above.

[0009] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which implements the method described in the first aspect above when executed by a processor.

[0010] Through the technical solution provided by the embodiment of the present application, according to the monitoring information of the monitoring event submitted by the user, the target monitoring item corresponding to the monitoring event is obtained from the monitoring pool, and the monitoring pool includes multiple generated monitoring items. The target monitoring item is used to perform consistency monitoring on a group of monitoring objects; when the target monitoring item does not exist in the monitoring pool, the target monitoring item is generated according to the monitoring information; the target alarm configuration information of the target monitoring item is determined according to the target monitoring item; a monitoring task is generated according to the target monitoring item and at least one monitoring item to be merged, and an alarm task is generated according to the target alarm configuration information and the alarm configuration information corresponding to at least one monitoring item to be merged, and consistency monitoring and alarming are performed according to the monitoring task and the alarm task. The monitoring pool is used to uniformly manage the monitoring items to avoid generating redundant monitoring items. By performing monitoring merging processing and alarm merging processing on multiple monitoring items, the generation of multiple monitoring tasks and alarm tasks is avoided, the storage resources and computing resources of the monitoring equipment are saved, and the performance of the monitoring system is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] 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.

[0012] Figure 1 A schematic diagram of an application scenario applicable to the embodiments of the present application;

[0013] Figure 2 This is a flow chart of the data consistency monitoring method provided in Example 1 of the present application;

[0014] Figure 3 A schematic diagram of the alarm page;

[0015] Figure 4 This is an architectural diagram of the consistency monitoring method provided in an embodiment of the present application;

[0016] Figure 5 Flowchart of the data consistency monitoring method provided in Example 2 of the present application;

[0017] Figure 6 Flowchart of the data consistency monitoring method provided in Example 3 of the present application;

[0018] Figure 7 A schematic diagram of the structure of a data consistency monitoring device provided in Example 4 of the present application;

[0019] Figure 8 A schematic diagram of the structure of the monitoring device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. 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 making any creative efforts shall fall within the scope of protection of the present invention.

[0021] It should be noted that the terms "first", "second", etc. in the description 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 numbers used in this way are interchangeable 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 server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0022] In order to facilitate understanding of the embodiments of the present application, before describing the various embodiments of the present application, some concepts involved in all the embodiments of the present application are first appropriately explained.

[0023] A data cluster (also called a database cluster) consists of multiple database servers. Data can be stored in a distributed manner in multiple database servers. These multiple database servers form a virtual single database logical image and can provide data services to users like a single database system.

[0024] A database, in short, can be thought of as a digital filing cabinet—a place where electronic files are stored, allowing users to add, query, update, and delete data. A database is a collection of data stored in a specific way, shared by multiple users, with minimal redundancy, and independent of applications.

[0025] Tables and fields are the fundamental elements of a database; together they constitute its structure and content. A table, also known as a data table, is a grid-like virtual table that temporarily stores data and is used to store and organize it. A table consists of three parts: the table name, the fields within the table, and the records within the table. Each row in the table represents a record or entity, while each column represents a field or attribute.

[0026] In a table, a field usually represents some type of information, such as account number, transaction time, transaction amount, etc. Each field has its specific data type and length to ensure the consistency and accuracy of the data stored in it.

[0027] The following is a brief introduction to the application scenarios to which the technical solutions of the embodiments of the present application can be applied. It should be noted that the application scenarios described below are only used to illustrate the embodiments of the present application and are not limiting. In specific implementation, the technical solutions provided by the embodiments of the present application can be flexibly applied according to actual needs.

[0028] For example, Figure 1 This is a schematic diagram of an application scenario applicable to the embodiment of the present application, such as Figure 1 As shown, the application scenario includes: a data quality monitoring platform (hereinafter referred to as monitoring platform) 10 and a database system 20. The monitoring platform 10 and the database system 20 are connected via a communication network.

[0029] The monitoring platform 10 is used to monitor the quality of the data in the database system 20. Quality monitoring includes data accuracy monitoring, data consistency monitoring, and data integrity monitoring. Data consistency monitoring and accuracy monitoring are two core aspects of data quality and are crucial to ensuring the reliability and validity of data.

[0030] Accuracy monitoring primarily monitors the accuracy of the information and data recorded in the data, and whether there are any anomalies or errors. Accuracy monitoring typically includes monitoring data range, format, outliers, missing values, and other aspects. Using pre-set rules and algorithms, the monitoring platform 10 can automatically monitor data accuracy and generate detailed monitoring reports. These monitoring reports allow users to quickly identify and resolve issues, thereby improving data accuracy.

[0031] Data consistency monitoring primarily monitors whether the results of the same data are consistent across different links, cycles, and locations. Once a database system 20 reaches a certain level of complexity, the same data may be calculated in multiple locations, links, or cycles. This can easily lead to different results for the same data due to differences in calculation methods or developers. Therefore, the goal of data consistency monitoring is to ensure that the calculation results of this data remain consistent across different links, cycles, and locations.

[0032] The monitoring platform 10 can be a client, a user-facing interface that allows users to trigger data quality monitoring through the monitoring platform. The device (e.g., a computer) where the monitoring platform 10 resides is called a monitoring device or monitoring computer. In this application scenario, there can be multiple or a large number of monitoring platforms 10. For example, in a big data scenario, a large number of clients may need to monitor data quality.

[0033] The database system 20 may be a data cluster including multiple database servers, and data may be stored in a distributed manner on the multiple database servers.

[0034] The monitoring platform 10 can access the database system 20, read data from different tables of the database system 20, and perform consistency monitoring on the data.

[0035] In an embodiment of the present application, the monitoring platform 10 obtains the target monitoring item corresponding to the monitoring event from the monitoring pool based on the monitoring information of the monitoring event submitted by the user. The monitoring pool includes multiple generated monitoring items. The target monitoring item includes information about the monitoring object and information about the monitoring indicator. The target monitoring item is used to perform consistency monitoring on at least one group of monitoring objects using at least one monitoring indicator, and each group of monitoring objects includes two monitoring objects; when the target monitoring item does not exist in the monitoring pool, the monitoring platform 10 generates a target monitoring item based on the monitoring information; determines the target alarm configuration information of the target monitoring item based on the target monitoring item; generates a monitoring task based on the target monitoring item, and generates an alarm task based on the target alarm configuration information.

[0036] The monitoring platform 10 executes the monitoring task to obtain monitoring data from the database system 20, obtains the consistency monitoring results of the monitoring events based on the monitoring data, executes the alarm task based on the consistency monitoring results to obtain the alarm results; determines the monitoring display results based on the consistency monitoring results, and performs alarm processing based on the alarm results.

[0037] Exemplarily, the database system 20 may be a relational database. Common relational databases include MySQL, Oracle, SQL Server, DB2, Hive, HBase, Spark, and the like.

[0038] The present application provides a data consistency monitoring method. Exemplarily, the consistency monitoring method can be applied in the following four scenarios:

[0039] Scenario 1: Consistency of upstream and downstream data on the same data link

[0040] Upstream and downstream data refers to data from different stages or links in the data chain. Taking big data clusters as an example, upstream data may include various raw data, such as raw data from IoT devices, e-commerce transactions, and social media platforms. After being collected, cleaned, and integrated, this data forms downstream datasets for further processing and analysis.

[0041] For example, the weekly transaction statistics table is derived from the transaction count indicators in the daily transaction statistics table for the most recent week, while the daily transaction statistics table is directly derived from the transaction flow table. Therefore, the transaction count in the weekly statistics table should be consistent with the sum of the transaction counts (i.e., the sum value) for the most recent week, and also consistent with the count value in the transaction flow table for the most recent week.

[0042] Scenario 2: Data consistency across different downstream branches of the same source

[0043] Homogenous data refers to data derived from the same source or original dataset, while different downstream branches represent data that is distributed to different paths or components during subsequent processing, storage, or application. In practical applications, data in different downstream branches may be inconsistent due to various reasons.

[0044] For example, transaction flow tables all originate from the same business system table, but are synchronized to different tables in the big data cluster by different departments. This can lead to data consistency issues due to differences in synchronization methods, synchronization time points, and whether or not data is converted in between.

[0045] Scenario 3: Consistency of different data with the same business meaning

[0046] In actual business scenarios, the same business data may be stored in different systems or different data sources. However, due to system differences, data entry errors, or other reasons, the business data may be stored as different data in different systems or different data sources. For example, the field names of the business data in different systems are different.

[0047] For example, in the transaction process, there is data flow. After a user initiates a transaction, the data will be written into the transaction initiation system, and at the same time, the funds will be transferred to the transaction debit system. The transaction initiation system and the transaction debit system both record the user's payment behavior. In specific application scenarios, it is necessary to ensure the consistency of the two copies of data, for example, at least the quantity must be consistent.

[0048] Scenario 4: Consistency of the Same Data in Different Periods

[0049] Data consistency across different periods focuses on the stability and reliability of the same data at different points in time. Consistency across different periods means that despite changes in time, the information, structure, logical relationships, and business implications expressed by the data should remain relatively stable and consistent. This consistency is particularly important for scenarios such as time series analysis, trend forecasting, business comparison, and cross-period decision-making.

[0050] In actual applications, due to the influence of various factors, the same data may be inconsistent in different periods. These factors include differences in data collection methods, changes in data processing procedures, system upgrades or failures, human errors, etc. These inconsistencies may lead to a decline in data quality and affect the accuracy and reliability of analysis results.

[0051] For example, the user information table mainly stores basic user information, which generally does not change. Therefore, the difference in this information in different periods of the user information table (generally two adjacent periods) will not be particularly large, and the difference ratio should be within a very small range to be reasonable.

[0052] It should be clear that data consistency monitoring involves two monitoring objects, which may be two tables, two fields of two tables, two fields of one table, or one table and one field.

[0053] In the embodiment of the present application, the consistency of the data of the two monitored objects does not necessarily mean that the data of the two monitored objects are exactly the same. It is possible that there are differences in the data of the two monitored objects, but the differences are within a certain range, and the data of the two monitored objects are considered to be consistent.

[0054] When monitoring data consistency, what is often monitored is the inconsistency of the data of two monitored objects. The lower the inconsistency, the more different the data of the two monitored objects are.

[0055] When performing consistency monitoring on the monitored objects, it is necessary to define monitoring indicators, which are indicators or parameters for measuring data consistency.

[0056] In existing technology, multiple monitoring indicator names may exist for the same monitoring indicator within the same monitoring system. For example, if a user wants to monitor whether a certain field is empty under certain conditions, different users may name the monitoring indicator "Whether a certain field is empty under certain conditions," "Number of empty fields in a certain field," "Percentage of non-empty fields in a certain field," and so on. This results in inconsistent and confusing monitoring systems, making them difficult to manage.

[0057] To this end, in the embodiment of the present application, the monitoring platform provides unified, standardized and comprehensive monitoring indicators for users to choose from, and users select the monitoring indicators they need from the monitoring indicators provided by the monitoring platform.

[0058] For example, the monitoring platform provides three types of monitoring indicators: basic monitoring indicators, associated monitoring indicators, and custom monitoring indicators. Basic monitoring indicators and associated monitoring indicators are unified indicators provided by the monitoring platform, while custom monitoring indicators are user-defined monitoring indicators based on business needs or analysis purposes.

[0059] Basic monitoring indicators include the difference, ratio and difference ratio of the monitored objects. When calculating the value of the basic monitoring indicator, the values ​​of two monitored objects are directly compared to calculate the difference, ratio or difference ratio. For example, the calculation formula of the basic monitoring indicator is as follows:

[0060] Difference = value of the right source monitoring object - value of the left source monitoring object;

[0061] Ratio = value of the right source monitoring object / value of the left source monitoring object;

[0062] Difference ratio = (value of the right source monitoring object - value of the left source monitoring object) / value of the left source monitoring object.

[0063] A set of monitoring objects consists of two monitoring objects, one of which is called a right source monitoring object and the other is called a left source monitoring object. Optionally, the right source monitoring object and the left source monitoring object can also be replaced by other names, such as the first monitoring object and the second monitoring object.

[0064] The two monitoring objects corresponding to the associated monitoring indicators may be two fields, and the two fields corresponding to the associated monitoring indicators may be associated fields or non-associated fields.

[0065] When associating two fields, they are generally associated based on their business primary keys. If there is no business primary key, you can customize a unique primary key and associate them based on the unique primary key.

[0066] For example, the values ​​of all fields in a row of data are concatenated to obtain the MD5 value of the information, where MD5 refers to Message Digest Algorithm 5.

[0067] The correlation monitoring indicators corresponding to non-correlated fields include: the difference between the left and right sources of the non-correlated fields and the ratio of the difference between the left and right sources of the non-correlated fields. The specific calculation formula is as follows:

[0068] Difference between left and right sources (inner association) of non-association fields = sum (after full association, unequal fields are marked as 1);

[0069] The difference ratio of the left and right sources (inner association) of non-association fields = sum (after full association, if the field is not equal, it is counted as 1) / total data count after full association.

[0070] Sum represents a summation operation, and a full join means that all rows of records in two fields are joined. In a database, a field typically has three values: a real value, an empty string, and a null value. Null indicates that the field has no value, while an empty string indicates that the field has a value, but the value is meaningless.

[0071] In one implementation, two fields are not equal if their actual values ​​are not equal. In all other cases, the two fields are considered equal. That is, the two fields are considered equal if their values ​​are any of the following: both fields are null, both fields are empty strings, one field is null and the other is an empty string, and the actual values ​​of the two fields are equal.

[0072] In another implementation, two fields are not equal in the following cases: the actual values ​​of the two fields are not equal, the values ​​of both fields are null, the values ​​of both fields are empty strings, the value of one field is null and the value of the other field is an empty string. In other words, two fields are considered equal only when they are truly equal.

[0073] In actual application, you can choose any of the above methods to determine whether two fields are equal according to actual needs.

[0074] The associated monitoring indicators corresponding to the associated fields include: the difference between the left and right sources of the associated field, the ratio of the difference between the left and right sources of the associated field, the number of associated fields with left sources but not right sources, the ratio of associated fields with left sources but not right sources, the number of associated fields with left sources but not right sources, and the ratio of associated fields with left sources but not right sources. The specific calculation formula is as follows:

[0075] Difference between left and right source in the association field = sum (after full association, if the left or right source association field is null, it is recorded as 1);

[0076] The difference ratio between the left and right sources of the associated field = sum(after full association, if the left or right source associated field is null, it is recorded as 1) / total data count after full association;

[0077] The quantity of the associated field "left source has value and right source has no value" = sum (after full association, if the associated field of the left source has value and the associated field of the right source is null, it is recorded as 1);

[0078] The percentage of the number of associated fields with values ​​in the left source and not in the right source = numerator: sum(after full association, if the associated field in the left source has a value and the associated field in the right source is null, it is recorded as 1) / left source data count;

[0079] The quantity of the associated field "left source has value and right source has no value" = sum (after full association, if the associated field on the right source has value and the associated field on the left source is null, it is recorded as 1);

[0080] The ratio of the number of associated fields with values ​​in the left source and without values ​​in the right source = sum(after full association, if the associated field in the right source has a value and the associated field in the left source is null, it is recorded as 1) / right source data count.

[0081] After introducing some concepts involved in the embodiments of the present application, a data consistency monitoring method provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0082] Figure 2 This is a flow chart of the data consistency monitoring method provided in Example 1 of this application. The method in this embodiment can be executed by the monitoring platform. Figure 2 As shown, the method of this embodiment includes the following steps.

[0083] S101. According to monitoring information of a monitoring event submitted by a user, a target monitoring item corresponding to the monitoring event is obtained from a monitoring pool, where the monitoring pool includes a plurality of generated monitoring items.

[0084] The monitoring platform provides a configuration page for monitoring events. A monitoring event refers to a monitoring operation triggered by a user. The configuration interface includes setting entries for multiple configuration items of the monitoring items.

[0085] A monitoring item includes multiple configuration items related to consistency monitoring, which are the content of the monitoring item. The multiple configuration items include configuration items for the monitoring object and configuration items for the monitoring indicator. The setting entry is used for the user to select or enter the value of the configuration item. In consistency monitoring, the multiple configuration items include configuration items for a group of monitoring objects, and a group of monitoring objects includes two monitoring objects. Table 1 is a schematic diagram of the configuration item list of the monitoring item, and Table 1 is as follows:

[0086] Table 1

[0087] Field Name Field Comments db_name Left source library name tbl_name Left source table name field_name Left source field name left_monitor_cycle Left source monitoring cycle left_item_type Left source monitoring indicator type left_item_detail_type Left source monitoring indicator details left_item_name Left source monitoring indicator name right_db_name Right source library name right_tbl_name Right source table name right_field_name Right source field name right_monitor_cycle Right source monitoring cycle right_item_type Right source monitoring indicator type right_item_detail_type Right source monitoring indicator details right_item_name Right source monitoring indicator name monitor_cycle Monitoring cycle item_type Monitoring indicator type item_detail_type Monitoring indicator details item_name Monitoring indicator name item_context Monitoring rule items

[0088] The left column in Table 1 is the name of each configuration item of the monitoring item, which can be understood as the name used for internal processing of the monitoring platform. The right column is the comments or description of each configuration item of the monitoring item.

[0089] The configuration interface provides a setting entry for each configuration item. The user can select the value corresponding to the configuration item through this setting entry. If the value of the configuration item provided by the monitoring platform does not meet the user's needs, the user can customize the configuration and enter the value of the customized configuration item. The user sets the value of the configuration item through this configuration page. After completing the setting of each configuration item of the monitoring item, the user clicks a confirmation button to confirm the submission of the monitoring information of the monitoring event. The confirmation button can be a "Submit" button.

[0090] In one implementation, when the monitoring information includes information on all configuration items of the monitoring item, that is, the user sets a complete monitoring item, the monitoring platform directly matches the monitoring information submitted by the user with multiple generated monitoring items in the monitoring pool. If the monitoring information matches a monitoring item in the monitoring pool, the monitoring item is determined to be the target monitoring item, and the target monitoring item is obtained from the monitoring pool.

[0091] In another implementation, the monitoring information includes information on the configuration items of the monitored object, but does not include information on the configuration items of the monitoring indicators. At this time, the monitoring platform can supplement the default monitoring configuration information based on the monitoring information submitted by the user (i.e., the information on the configuration items of the monitored object) to obtain new monitoring information, and match the new monitoring information with multiple generated monitoring items in the monitoring pool. If the new monitoring information matches a monitoring item in the monitoring pool, the monitoring item is determined to be the target monitoring item, and the target monitoring item is obtained from the monitoring pool.

[0092] The configuration items of the monitoring object include the database name, table name, field name, monitoring period, monitoring indicator type, monitoring indicator details, and monitoring indicator name. The configuration items of the monitoring indicator include the monitoring indicator type, monitoring indicator details, monitoring indicator name, monitoring period, and monitoring rule items.

[0093] The default monitoring indicators used can include periodic data volume, number of null values, percentage of null values, minimum value, enumeration value distribution percentage, number of enumeration values, percentage of IP format anomalies, percentage of internal company IP addresses, and percentage of IP addresses starting with "::ffff:". The default monitoring uses the default values ​​for the monitoring indicator type, item, name, period, and monitoring rule configuration.

[0094] Unlike existing technologies, the embodiments of this application utilize a monitoring pool for unified management of monitoring items. This monitoring pool includes multiple generated monitoring items, each configured by a user who has already performed consistency monitoring on the database system. The monitoring items in the monitoring pool are unique. After a user submits monitoring information, if the corresponding monitoring item is already stored in the monitoring pool, the monitoring item in the monitoring pool is directly used. The monitoring platform does not repeatedly generate and store monitoring items, thus avoiding redundant monitoring items and thus avoiding resource waste.

[0095] The target monitoring item includes information about the monitoring object and information about the monitoring indicator. The target monitoring item is used to monitor a group of monitoring objects, where a group of monitoring objects includes two monitoring objects.

[0096] Exemplarily, the information of the monitoring object includes information of the left source monitoring object and information of the right source monitoring object. The information of the left source monitoring object includes: library name, table name, field name, monitoring period, monitoring indicator type, monitoring indicator details and monitoring indicator name. The information of the right source monitoring object includes: library name, table name, field name, monitoring period, monitoring indicator type, monitoring indicator details and monitoring indicator name. Among them, the fields in the information of the left source monitoring object and the fields in the right source monitoring object constitute a group of monitoring objects, or, the table in the left source monitoring object and the table in the right source monitoring object constitute a group of monitoring objects.

[0097] The monitoring platform provides basic monitoring, associated monitoring and custom monitoring. Basic monitoring is used to monitor basic monitoring indicators, associated monitoring is used to monitor associated monitoring indicators, and custom monitoring is used to monitor custom monitoring indicators.

[0098] Referring to Table 2 and Table 3, Table 2 is a configuration result list of monitoring items for basic monitoring, and Table 3 is a configuration result list of monitoring items for associated monitoring.

[0099] Table 2

[0100]

[0101]

[0102] Table 3

[0103]

[0104]

[0105] In Table 3, configuration value 1 is the value of a configuration item of an associated field, and configuration value 2 is the value of a configuration value of a non-associated field.

[0106] In the embodiments of the present application, unified configuration items are used for all monitoring objects and monitoring indicator types. However, for different monitoring indicator types and different monitoring objects, the configuration values ​​of some configuration items can be empty. When the value or configuration value of a configuration item is empty, the configuration item will not be effective during the monitoring process. Using unified configuration items makes the configuration of monitoring items simpler, easier to implement and manage.

[0107] Comparing Table 2 and Table 3, Table 2 monitors a single table and field. Specifically, the consistency between the left source table's trade_total_cnt field and the right source table's base_table_name is monitored. Therefore, the right source field name is empty. This indicates that the right source monitoring target is a single table. Similarly, when monitoring two tables, the field names of both tables are empty.

[0108] When performing basic monitoring, there's no need to configure monitoring rule items. The monitoring platform directly generates monitoring rules (also known as monitoring logic) based on the monitored object information and other monitoring indicator information. However, when performing correlation monitoring, you need to configure monitoring rule items. These items describe the monitoring rules and assist in generating them. The monitoring platform generates monitoring rules based on the monitored object information, monitoring rule items, and other monitoring indicator information.

[0109] When performing associated monitoring, the configuration values ​​of the left source monitoring period, left source monitoring indicator type, left source monitoring indicator details and left source monitoring indicator name of the left source monitoring object are empty, and the configuration values ​​of the right source monitoring period, right source monitoring indicator type, right source monitoring indicator details and right source monitoring indicator name of the right source monitoring object are empty.

[0110] Optionally, the key_left_format (i.e., the left table association field) in the monitoring rule item in Table 3 can have multiple field names, separated by commas. For example, the format of key_left_format is: "key_left_format": [fid, fcase_no], where fid and fcase_no are two different field names. Similarly, the key_right_format (i.e., the right table association field) in the monitoring rule item can have multiple field names, separated by commas. Multiple field names in key_left_format or key_right_format can form a new custom field to associate two tables. The key_struct value in the monitoring rule item is error, which is used for consistency.

[0111] S102: When the target monitoring item does not exist in the monitoring pool, generate the target monitoring item according to the monitoring information.

[0112] When the target monitoring item cannot be matched from the monitoring pool, a new monitoring item needs to be generated based on the monitoring information as the target monitoring item of the monitoring event. After the new monitoring item is generated, it needs to be reviewed or approved. Only after the review or approval is passed can it be used as the target monitoring item.

[0113] S103: Determine target alarm configuration information of the target monitoring item according to the target monitoring item.

[0114] The target monitoring item of this step may be a monitoring item obtained from the monitoring pool, or may be a newly generated target monitoring item. In the embodiment of the present application, the monitoring platform supports threshold alarms and abnormal point alarms for consistency alarms.

[0115] Threshold alarms primarily determine whether to trigger an alarm based on preset thresholds. These thresholds can be fixed or dynamically adjusted, and can be set based on the characteristics of the monitored object and business needs. When the monitored value exceeds or falls below the set threshold, the system triggers an alarm, notifying relevant personnel to take action. This alarm method is simple and intuitive.

[0116] Anomaly alerts focus on changes and correlations between monitored values. Using algorithms or models, they identify anomalies (i.e., outliers) in monitored values. These anomalies may be caused by factors such as system failures, equipment anomalies, or external interference. Once an anomaly is detected, the system triggers an alert. Compared to threshold alerts, anomaly alerts are more flexible and sensitive, capable of catching potential issues that are difficult to detect using thresholds.

[0117] Optionally, in an embodiment of the present application, the two alarm mechanisms can be used in combination to achieve better monitoring effects.

[0118] The target alarm configuration information for the target monitoring item can be generated based on user configuration operations, such as user-set monitoring indicators and corresponding thresholds. Optionally, the user-set monitoring indicators and corresponding thresholds are subject to review and approval before they can be used as final alarm information.

[0119] In this embodiment, the target alarm configuration information can use one or more alarm indicators to issue an alarm. In an exemplary manner, the target alarm configuration information includes: information about the monitored object, information about the alarm indicator, and blocking indication information, where the blocking indication information is used to indicate whether the monitored object is blocked when an abnormality occurs. The configuration information of the alarm indicator includes the alarm cycle, alarm indicator category, alarm indicator name, alarm rule item, alarm threshold source, threshold type, and normal threshold. Among them, the alarm indicator information can include information about multiple alarm indicators, thereby realizing the simultaneous use of multiple alarm indicators for alarming.

[0120] Refer to Table 4, which is a list of alarm configuration items:

[0121] Table 4

[0122]

[0123]

[0124] Referring to Table 5, Table 5 is an example of target alarm configuration information, which is the alarm configuration information corresponding to the monitoring items shown in Table 3 above.

[0125] Table 5

[0126]

[0127]

[0128] S104. Generate a monitoring task based on the target monitoring item and at least one monitoring item to be merged, execute the monitoring task to obtain the consistency monitoring result of the monitoring event, generate an alarm task based on the target alarm configuration information and the alarm configuration information corresponding to at least one monitoring item to be merged, execute the alarm task to obtain the alarm result of the monitoring event, wherein the monitoring table of the target monitoring item and each monitoring item to be merged is the same.

[0129] Multiple monitoring items may be generated simultaneously or asynchronously within the monitoring platform. When the monitoring tables for multiple monitoring items are identical, they can be merged to generate a monitoring task. Each monitoring task corresponds to a piece of monitoring logic, also known as a monitoring rule. A monitoring table refers to a table within a monitoring item. This monitoring logic, which can be a Structured Query Language (SQL) logic, is used to obtain consistent monitoring results.

[0130] When the monitoring logic is used to obtain monitoring results for multiple monitoring items, the monitoring logic includes multiple monitoring sub-operators, and each monitoring sub-operator is the monitoring implementation logic for a monitoring item. By merging multiple monitoring items, it is only necessary to access the table once to monitor multiple groups of monitoring fields or to monitor a group of monitoring fields using multiple monitoring indicators. For example, three fields in Table 1 and Table 2 can be monitored simultaneously through one monitoring logic, or two monitoring indicators, difference and ratio, can be monitored simultaneously for one field in Table 1 and Table 2 through one monitoring logic. Frequent access to the same table is avoided, computing resources are saved, and monitoring efficiency is improved.

[0131] In the prior art, a monitoring task is generated for each monitoring item, and each monitoring item requires an independent monitoring logic. When monitoring multiple fields in the same table, the same table needs to be accessed repeatedly, resulting in a waste of resources.

[0132] When the monitoring platform executes the monitoring task, it obtains the monitoring table from the database, and obtains the consistency monitoring results corresponding to the monitoring task from the monitoring table. The consistency monitoring results corresponding to the monitoring task include the consistency monitoring results of the target monitoring items and the consistency monitoring results of each monitoring item to be merged; the consistency monitoring results of the monitoring event are obtained from the consistency monitoring results corresponding to the monitoring task.

[0133] Taking the monitoring item configuration shown in Table 2 as an example, the right source table is a basic table, partitioned by day, storing transaction flows. The left source table is a statistical table that counts each user's daily transactions, also partitioned by day. This monitoring item is applicable to the scenario described above: upstream and downstream data consistency within the same data link. The monitoring rule reads the two tables, sum_table_name and base_table_name, from the database corresponding to db_name, merges the data from these two tables, then obtains the sum value of the trade_total_cnt field in the left table and the count value in the right table. The sum value of the trade_total_cnt field in the left table is compared with the count value in the right table to determine if they are consistent. If the sum value of the trade_total_cnt field in the left table and the count value in the right table are equal, the two are considered consistent. If the sum value of the trade_total_cnt field in the left table and the count value in the right table are not equal, the two are considered inconsistent, thus obtaining the consistency monitoring result.

[0134] Taking the configuration information of the monitoring items shown in Table 3 as an example, for configuration item 1, the monitoring rule is used to read two tables, table_name1 and table_name2, from the database corresponding to db_name. Then, the fid field of table_name1 is compared with the fid field of table_name2 to obtain the difference ratio between the left and right sources of the two related fields.

[0135] When the monitoring logic is used to obtain monitoring results for multiple monitoring items, the consistency monitoring results corresponding to the monitoring task include the consistency monitoring results of the multiple monitoring items, and the consistency monitoring results of the multiple monitoring items are a row of monitoring data. Accordingly, the consistency monitoring results corresponding to the monitoring task need to be converted from a row of monitoring data to multiple rows of monitoring results, each row of monitoring results being the consistency monitoring results of a monitoring item. For example, a row of monitoring data can be converted into multiple rows of monitoring results using the later view explode function.

[0136] If the target monitoring item and at least one monitoring item to be merged are combined to generate a monitoring task, the target alarm configuration information of the target monitoring item and the alarm configuration information of the at least one monitoring item to be merged can also be merged to generate an alarm task. The alarm task is executed to obtain the alarm result corresponding to the alarm task. The alarm task corresponds to a section of alarm logic. The alarm result corresponding to the alarm task includes the alarm result of the target monitoring item and the alarm results of each monitoring item to be merged. The alarm result of the monitoring event is obtained from the alarm result corresponding to the alarm task.

[0137] When the alarm logic is used to obtain the alarm results of multiple monitoring items, the alarm logic includes multiple alarm sub-operators, and each alarm sub-operator is the alarm implementation logic for a monitoring item. By merging the alarm configuration information of multiple monitoring items, only one monitoring logic needs to be executed to implement alarms for multiple groups of monitoring fields or multiple monitoring indicators of a group of monitoring fields. For example, the alarm results for three fields in Table 1 and Table 2 can be obtained simultaneously through a section of alarm logic, or the alarm results for two monitoring indicators, the difference and ratio, can be obtained simultaneously for a field in Table 1 and Table 2 through a section of alarm logic. This avoids the generation of multiple alarm tasks, which causes redundancy, saves computing resources, and improves alarm efficiency.

[0138] Monitoring alarms are based on consistency monitoring results. For example, Table 5 shows the alarm configuration information corresponding to the monitoring items shown in Table 3 above. For configuration item 1, the alarm rule determines whether the ratio of the left and right source differences between the fid field in table_name1 and the fid field in table_name2 exceeds the threshold. If the ratio is within the threshold [-0.0001, 0.0001], no alarm is required. If the ratio exceeds [-0.0001, 0.0001], an alarm is required. If the target alarm configuration information is configured to block, the monitored object is blocked.

[0139] When the alarm result corresponding to the alarm task includes the alarm results of multiple monitoring items, the alarm results of the multiple monitoring items are a row of alarm data. It is necessary to convert the alarm result corresponding to the alarm task from a row of alarm data to multiple rows of alarm results, each row of alarm results is the alarm result of a monitoring item. For example, the later view explode function can be used to convert a row of alarm data into multiple rows of monitoring results.

[0140] S105: Determine the monitoring display result according to the consistency monitoring result, and perform alarm processing according to the alarm result.

[0141] Optionally, the monitoring display results are displayed in a table. When displayed in a table, the monitoring display results include the target monitoring items and the consistency monitoring results, where the consistency monitoring results are the monitoring values. For example, a row of monitoring result items can be added to the tables shown in Table 2 and Table 3 to display the consistency monitoring results.

[0142] Optionally, the monitoring pool also includes monitoring results corresponding to the generated monitoring items. Accordingly, the monitoring items and consistency monitoring results obtained this time are written into the monitoring pool.

[0143] Optionally, when the target monitoring item is obtained from the monitoring pool, the monitoring result corresponding to the target monitoring item is obtained from the monitoring pool. If the monitoring result corresponding to the target monitoring item exists in the monitoring pool, it is determined whether the monitoring result corresponding to the target monitoring item is valid. When the monitoring result corresponding to the target monitoring item is valid, the monitoring display result is determined based on the monitoring result corresponding to the target monitoring item. When the monitoring result corresponding to the target monitoring item is invalid, the consistency monitoring result of the monitoring event is obtained based on the target monitoring item, and the obtained consistency monitoring result is written into the monitoring pool.

[0144] In one implementation, a monitoring time is set corresponding to the monitoring result in the monitoring pool. If the monitoring time corresponding to the monitoring result exceeds the preset time, the monitoring result is considered invalid. The monitoring time can be 1 hour, 8 hours or 24 hours.

[0145] In another implementation method, whether the monitoring result is valid is determined based on the update status and monitoring time of the monitoring object corresponding to the monitoring result. If the monitoring object corresponding to the monitoring result is not updated after the monitoring time, the monitoring result is determined to be valid; if the monitoring object corresponding to the monitoring result is updated after the monitoring time, the result is determined to be invalid.

[0146] When the monitoring pool stores monitoring results and the monitoring results are valid, the monitoring results can be used directly without the need for repeated monitoring, thereby saving monitoring resources.

[0147] When the monitoring pool does not store the target monitoring item of the monitoring event, and the monitoring platform generates a new monitoring item for the monitoring event, the new monitoring item and the monitoring results corresponding to the new monitoring item need to be stored in the monitoring pool. The new monitoring item is unique in the monitoring pool and will not be repeated with the generated monitoring item.

[0148] When the alarm result indicates that an alarm is required, an alarm can be pushed, and optionally, the alarm can be pushed to a designated device or designated person in the form of a graphic or text. This embodiment does not limit the form of the alarm.

[0149] Figure 3 A schematic diagram of the alarm page is shown below. Figure 3 As shown, the alarm result is a distribution diagram of the number of left source without right source in the two related fields. The statistical period is day. The alarm result shows the trend chart of the number of left source without right source in the two related fields for multiple consecutive days.

[0150] When the information of the monitoring indicator indicates that the monitoring indicator type is a basic monitoring indicator, optionally, monitoring data is read from the accuracy monitoring result of the database according to the monitoring rule, and the consistency monitoring result of the monitoring event is determined according to the monitoring data.

[0151] Reference Figure 4 As shown, Figure 4 This is an architectural diagram of the consistency monitoring method provided in an embodiment of the present application. Two monitoring pools are provided under this architecture: a consistency data monitoring pool and an accuracy data monitoring pool. The consistency data monitoring pool is used to store monitoring items and monitoring results of consistency monitoring. The data stored in the accuracy data monitoring pool are all accurate data obtained through accuracy monitoring, that is, inaccurate data is filtered out.

[0152] Basic monitoring is carried out based on the accuracy monitoring results, which improves the accuracy and credibility of the monitoring results of data consistency monitoring.

[0153] In this embodiment, based on the monitoring information of the monitoring event submitted by the user, the target monitoring item corresponding to the monitoring event is obtained from the monitoring pool, the monitoring pool includes multiple generated monitoring items, and the target monitoring item is used to perform consistency monitoring on a group of monitoring objects, each group of monitoring objects includes two monitoring objects; when the target monitoring item does not exist in the monitoring pool, the target monitoring item is generated based on the monitoring information; the target alarm configuration information of the target monitoring item is determined based on the target monitoring item; a monitoring task is generated based on the target monitoring item and at least one monitoring item to be merged, an alarm task is generated based on the target alarm configuration information and the alarm configuration information corresponding to at least one monitoring item to be merged, and consistency monitoring and alarming are performed based on the monitoring task and the alarm task. The monitoring pool is used to uniformly manage the monitoring items to avoid the generation of redundant monitoring items. By performing monitoring merging processing and alarm merging processing on multiple monitoring items, the generation of multiple monitoring tasks and alarm tasks is avoided, the storage resources and computing resources of the monitoring equipment are saved, and the performance of the monitoring system is improved.

[0154] Embodiment 2 of the present application provides a data consistency monitoring method, which is mainly used to describe in detail an implementation method of step S102 in embodiment 1. For the same content, please refer to the description of embodiment 1 and will not be repeated here. Figure 5 This is a flow chart of the data consistency monitoring method provided in Example 2 of this application, such as Figure 5 As shown, the method provided in this embodiment includes the following steps.

[0155] S201: Receive monitoring information of a monitoring event submitted by a user.

[0156] S202: Determine whether there is a target monitoring item corresponding to the monitoring event in the monitoring pool according to the monitoring information.

[0157] The monitoring pool includes multiple generated monitoring items and monitoring results of the generated monitoring items. When the monitoring pool contains a target monitoring item corresponding to a monitoring event, step S203 is executed. When the monitoring pool contains no target monitoring item corresponding to a monitoring event, step S204 is executed.

[0158] S203: Read the target monitoring item from the monitoring pool and determine the target alarm configuration information of the target monitoring item.

[0159] S204: Obtain basic information of the monitoring object required for monitoring the monitoring event based on the monitoring information.

[0160] When monitoring two tables, first determine whether the basic information for both monitoring tables exists in the basic monitoring configuration. The basic monitoring configuration is used to record the basic information of monitored tables and fields. If the basic information for both monitoring tables exists in the basic monitoring configuration, meaning that the basic information for both monitoring tables has already been registered, then the basic information for both monitoring tables is retrieved from the basic monitoring configuration. If the basic information for both monitoring tables does not exist in the basic monitoring configuration, then the basic information for both monitoring tables is registered.

[0161] Exemplarily, the basic information of the registered monitoring table includes: cluster name, library name, table name, whether partitioned, partition name, partition type, task cycle, table level, task id, task type, script name, follower, creation time, whether monitored, etc.

[0162] When registering the basic information in the form, some of the information is automatically generated or pulled by the program, such as calling the task platform interface to pull task information, and automatically supplementing the creation time according to the script creation time.

[0163] When the monitoring object is two fields, the two monitoring fields may be located in the same table or in different tables. The monitoring platform first determines whether the basic information of the monitoring table (one monitoring table or two monitoring tables) corresponding to the two monitoring fields exists in the basic monitoring configuration. If the basic information of the monitoring table does not exist in the basic monitoring configuration, the basic information of the monitoring table is registered in the basic monitoring configuration and the registration judgment process of the two monitoring fields is entered. If the basic information of the monitoring table exists in the basic monitoring configuration, no registration is required and the registration judgment process of the two monitoring fields is entered.

[0164] After entering the registration determination process for two monitoring fields, first determine whether the basic information for the two monitoring fields exists in the basic monitoring configuration. If the basic information for the two monitoring fields exists in the basic monitoring configuration, proceed to the next step. If the basic information for the two monitoring fields does not exist in the basic monitoring configuration, register the basic information for the two monitoring fields.

[0165] Exemplarily, the basic information of the registered monitoring field includes: field name, field type, field attention, whether it is a core table, whether it is a core field, whether it is an enumeration field, whether it is a primary key, etc.

[0166] S205: Generate candidate monitoring items according to the basic information and monitoring information of the monitoring object required to be monitored for the monitoring event.

[0167] If the monitoring information includes monitoring indicator information, candidate monitoring items are generated based on the basic information of the monitored object and the monitoring information. If the monitoring information does not include monitoring indicator information, a default monitoring indicator is obtained or the user is prompted to enter monitoring indicator information. The user selects the monitoring indicator based on the prompt information and can also configure monitoring rule items. The monitoring platform generates candidate monitoring items based on the default monitoring indicator and the monitoring indicator information entered by the user.

[0168] S206: Review the candidate monitoring items according to the preset monitoring item review rules.

[0169] S207: When the review is passed, generate target monitoring items based on the candidate monitoring items.

[0170] Exemplarily, candidate monitoring items are reviewed according to preset monitoring item review rules, including: determining whether non-custom monitoring indicators in the candidate monitoring items are necessary; when the candidate monitoring items include custom monitoring indicators, determining whether the custom monitoring indicators comply with grammatical rules; determining whether the custom monitoring indicators are repeated with existing indicators in the monitoring pool; and determining whether the custom monitoring indicators are necessary.

[0171] The monitoring indicators in the candidate monitoring items include non-customized monitoring indicators and / or customized monitoring indicators. Non-customized indicators refer to the above-mentioned basic monitoring indicators and associated monitoring indicators, and customized indicators are indicators defined by users themselves.

[0172] In actual situations, users may select multiple non-custom monitoring indicators, and multiple non-custom monitoring indicators may be repeated or similar. Therefore, it is necessary to determine whether the non-custom monitoring indicator is necessary. If it is not necessary, the non-custom monitoring indicator can be deleted and then a target price monitoring item can be generated.

[0173] When candidate monitoring items include custom monitoring indicators, the system determines whether the custom monitoring indicators conform to the grammatical rules. If the custom monitoring indicators do not conform to the grammatical rules, the system can prompt the user to modify them. After the user makes the modifications, the system will continue to review them. This ensures the standardization of the custom indicators and facilitates the unified management of the monitoring indicators by the monitoring platform. If the custom monitoring indicators conform to the grammatical rules, the system can continue to determine whether the custom monitoring indicators are duplicated with existing indicators in the monitoring pool.

[0174] User-defined monitoring indicators may be duplicates of existing monitoring indicators defined by the monitoring platform. For example, the actual meaning of user-defined monitoring indicators and existing monitoring indicators defined by the monitoring platform are the same, but the names are different. At this time, the user can be prompted to delete the customized monitoring indicator and use the existing monitoring indicator with the same meaning in the monitoring platform to avoid duplicate monitoring.

[0175] When the candidate monitoring items include custom monitoring indicators and non-defined monitoring indicators, the custom monitoring indicators may have the same meaning as the non-defined monitoring indicators. If the custom monitoring indicators have the same meaning as the non-defined monitoring indicators, the custom monitoring indicators are not necessary and can be deleted.

[0176] During the review process, the user may modify the non-compliant indicators so that the candidate monitoring items pass the review. At this time, the target monitoring items can be generated based on the modified candidate monitoring items.

[0177] S208: Determine target alarm configuration information of the target monitoring item according to the target monitoring item.

[0178] In this embodiment, based on the monitoring information submitted by the user, basic information about the monitoring object required for the monitoring event is obtained. Based on the basic information and monitoring information of the monitoring object required for the monitoring event, candidate monitoring items are generated. Based on the preset monitoring item review rules, the candidate monitoring items are reviewed. If the review passes, a target monitoring item is generated based on the candidate monitoring item. By reviewing the newly generated candidate monitoring items, the standardization and uniqueness of the resulting candidate items can be guaranteed, redundancy of monitoring items in the monitoring pool can be avoided, and unified management of monitoring items and monitoring indicators can be facilitated.

[0179] Embodiment 3 of the present application provides a data consistency monitoring method, which is mainly used to describe in detail an implementation method of step S103 in embodiment 1. The same content refers to the description of embodiment 1 and embodiment 2 and will not be repeated here. Figure 6 This is a flow chart of the data consistency monitoring method provided in Example 3 of this application, such as Figure 6 As shown, the method provided in this embodiment includes the following steps.

[0180] S1031. Determine whether the monitoring pool includes alarm configuration information corresponding to the target monitoring item.

[0181] In the prior art, a chimney-style monitoring alarm is used, in which monitoring alarms configured by different users cannot be shared, and users cannot share or subscribe to monitoring alarms configured by others. However, in this embodiment, the monitoring pool is used to realize the sharing of alarm configurations of different users.

[0182] In this embodiment, the monitoring pool includes not only the generated monitoring items and monitoring results, but also the alarm configuration information corresponding to the monitoring items. Optionally, in one implementation, each user's alarm configuration information can also be stored separately in a resource pool.

[0183] When the monitoring pool includes the alarm configuration information corresponding to the target monitoring item, step S1032 is executed; when the monitoring pool does not include the alarm configuration information corresponding to the target monitoring item, step S1033 is executed.

[0184] S1032. Obtain alarm configuration information corresponding to the target monitoring item from the monitoring pool.

[0185] In one implementation, the alarm configuration information corresponding to the target monitoring item obtained from the monitoring pool is used as the final target alarm configuration information. In another implementation, the alarm configuration information corresponding to the target monitoring item is provided to the user, allowing the user to confirm whether the alarm threshold in the alarm configuration information meets the user's requirements. If the alarm threshold meets the user's requirements, the user only needs to subscribe to the alarm configuration information and receive subsequent alarm push notifications. If the alarm threshold does not meet the user's requirements, the user can modify the alarm threshold, thereby realizing the sharing of alarm configuration information.

[0186] S1033. Provide an alarm configuration interface based on the target monitoring item.

[0187] S1034: Receive candidate alarm information input by the user through the alarm interface, where the candidate alarm information includes candidate alarm indicators and thresholds of the candidate alarm indicators.

[0188] The alarm configuration interface includes target monitoring items and alarm setting options. Users can operate the alarm setting options to select monitoring alarm indicators provided by the monitoring platform or customize monitoring alarm indicators. After the user selects or enters the monitoring alarm indicator, the user can select or enter the threshold value of the alarm indicator. In this embodiment, the user can select one or more candidate alarm indicators.

[0189] S1035. Review the candidate alarm information according to the preset alarm review rules.

[0190] Exemplarily, the candidate alarm information is reviewed according to the preset alarm review rules, including: determining whether the candidate alarm indicator is an existing alarm indicator; when the candidate alarm indicator is an existing alarm indicator, determining whether the threshold of the candidate alarm indicator is the same as the threshold of the existing alarm indicator.

[0191] S1036. Generate target alarm configuration information based on the audit results and candidate alarm information.

[0192] The candidate alarm indicator set by the user may be repeated with an existing alarm indicator. Therefore, it is necessary to determine whether the candidate alarm indicator is an existing alarm indicator. When the candidate alarm indicator is not an existing alarm indicator, the target alarm configuration information is generated based on the candidate alarm indicator and the threshold of the candidate alarm indicator.

[0193] If the candidate alarm indicator is an existing alarm indicator, the system checks whether the threshold of the candidate alarm indicator is the same as that of the existing alarm indicator. If so, the application is considered approved and the target alarm configuration information is generated using the candidate alarm indicator and the threshold of the candidate alarm indicator. If the threshold of the candidate alarm indicator is different from that of the existing alarm indicator, the user is prompted to select a threshold to use.

[0194] After the monitoring is completed, the generated target alarm configuration information can be stored in the monitoring pool. Through the above review, the uniqueness and standardization of the alarm configuration information in the monitoring pool can be guaranteed.

[0195] In this embodiment, it is determined whether the monitoring pool includes the alarm configuration information corresponding to the target monitoring item. When the monitoring pool includes the alarm configuration information corresponding to the target monitoring item, the alarm configuration information corresponding to the target monitoring item is obtained from the monitoring pool. When the monitoring pool does not include the alarm configuration information corresponding to the target monitoring item, an alarm configuration interface is provided according to the target monitoring item. The candidate alarm information input by the user through the alarm interface is received, and the candidate alarm information is reviewed according to the preset alarm review rules. The target alarm configuration information is generated based on the review results and the candidate alarm information. By reviewing the newly generated candidate alarm information, the standardization and uniqueness of the alarm configuration information finally generated can be guaranteed, the redundancy of the alarm configuration information in the monitoring pool can be avoided, and the unified management of the alarm configuration information and alarm indicators can be facilitated.

[0196] In order to facilitate better implementation of the data consistency monitoring method of the embodiment of the present application, the embodiment of the present application also provides a data consistency monitoring device. Figure 7 This is a structural diagram of the data consistency monitoring device provided in Example 4 of the present application, as shown in FIG. Figure 7 As shown, the data consistency monitoring device 300 may include:

[0197] An acquisition module 31 is configured to acquire, from a monitoring pool, a target monitoring item corresponding to a monitoring event submitted by a user, the monitoring event, the monitoring pool including a plurality of generated monitoring items, the target monitoring item being used to perform consistency monitoring on a group of monitoring objects, the group of monitoring objects including two monitoring objects;

[0198] A generating module 32, configured to generate the target monitoring item according to the monitoring information when the target monitoring item does not exist in the monitoring pool;

[0199] A determination module 33, configured to determine target alarm configuration information of the target monitoring item according to the target monitoring item;

[0200] A monitoring and alarm module 34 is configured to generate a monitoring task based on the target monitoring item and at least one monitoring item to be merged, execute the monitoring task to obtain a consistency monitoring result of the monitoring event, generate an alarm task based on the target alarm configuration information and the alarm configuration information corresponding to the at least one monitoring item to be merged, and execute the alarm task to obtain an alarm result of the monitoring event, wherein the monitoring table of the target monitoring item and each of the monitoring items to be merged is the same;

[0201] The display module 35 is used to determine the monitoring display result according to the consistency monitoring result, and perform alarm processing according to the alarm result.

[0202] In some implementations, the generating module 32 is specifically configured to:

[0203] According to the monitoring information, basic information of the monitoring object required to be monitored for the monitoring event is obtained;

[0204] Generate candidate monitoring items according to the basic information of the monitoring object required to be monitored for the monitoring event and the monitoring information;

[0205] Review the candidate monitoring items according to the preset monitoring item review rules;

[0206] When the review is passed, the target monitoring item is generated based on the candidate monitoring item.

[0207] In some implementations, the generating module 32 is specifically configured to:

[0208] Determine whether the non-customized monitoring indicators in the candidate monitoring items are necessary;

[0209] When the candidate monitoring items include a custom monitoring indicator, determining whether the custom monitoring indicator complies with grammatical rules;

[0210] Determine whether the custom monitoring indicator is repeated with an existing indicator in the monitoring pool;

[0211] Determine whether the custom monitoring indicator is necessary.

[0212] In some implementations, the determining module 33 is specifically configured to:

[0213] Determining whether the monitoring pool includes alarm configuration information corresponding to the target monitoring item;

[0214] When the monitoring pool includes the alarm configuration information corresponding to the target monitoring item, the alarm configuration information corresponding to the target monitoring item is obtained from the monitoring pool;

[0215] When the monitoring pool does not include the alarm configuration information corresponding to the target monitoring item, providing an alarm configuration interface according to the target monitoring item;

[0216] Receiving candidate alarm information input by a user through the alarm interface, the candidate alarm information including candidate alarm indicators and threshold values ​​of the candidate alarm indicators;

[0217] Review the candidate alarm information according to the preset alarm review rules;

[0218] The target alarm configuration information is generated according to the audit result and the candidate alarm information.

[0219] In some implementations, the determining module 33 is specifically configured to:

[0220] Determine whether the candidate alarm indicator is an existing alarm indicator;

[0221] When the candidate alarm indicator is an existing alarm indicator, it is determined whether the threshold of the candidate alarm indicator is the same as the threshold of the existing alarm indicator.

[0222] In some implementable embodiments, the target monitoring item includes information about the monitoring object and information about the monitoring indicator, the information about the monitoring object includes information about the left-source monitoring object and information about the right-source monitoring object, the information about the left-source monitoring object includes: library name, table name, at least one field name, monitoring period, monitoring indicator type, monitoring indicator details, and monitoring indicator name, the information about the right-source monitoring object includes: library name, table name, at least one field name, monitoring period, monitoring indicator type, monitoring indicator details, and monitoring indicator name, wherein a field in the information of the left-source monitoring object and a field in the right-source monitoring object constitute a group of monitoring objects, or a table in the left-source monitoring object and a table in the right-source monitoring object constitute a group of monitoring objects;

[0223] The information of the monitoring indicators included in the target monitoring item includes: monitoring indicator type, monitoring indicator details, at least one monitoring indicator name, monitoring period and monitoring rule items.

[0224] In some implementations, the monitoring indicator type includes: a basic monitoring indicator, an associated monitoring indicator, or a custom monitoring indicator;

[0225] When the monitoring indicator type is the basic monitoring indicator, the monitoring indicator item is a numerical indicator, and the monitoring indicator name of the basic monitoring indicator is ratio, difference or difference ratio;

[0226] When the monitoring indicator type is an associated monitoring indicator, the monitoring indicator item is a quantity indicator or a proportion indicator, the associated monitoring indicator is a non-associated field and an associated field, and the monitoring indicator name corresponding to the associated field includes the following information: the difference between the left and right sources of the associated field, the proportion of the difference between the left and right sources of the associated field, the quantity of the associated field with left source and right source but no quantity, the proportion of the associated field with left source and right source but no quantity, the quantity of the associated field with left source and no right source, and the proportion of the associated field with left source and no right source but no quantity;

[0227] The monitoring indicator name corresponding to the non-correlated field includes the following information: the difference between the left and right sources of the non-correlated field, and the proportion of the difference between the left and right sources of the non-correlated field.

[0228] In some implementations, the monitoring and alarm module 34 is specifically configured to:

[0229] Execute the monitoring task to obtain the monitoring table from the database, and obtain the consistency monitoring result corresponding to the monitoring task from the monitoring table, wherein the consistency monitoring result corresponding to the monitoring task includes the consistency monitoring result of the target monitoring item and the consistency monitoring results of each of the monitoring items to be merged;

[0230] Obtaining the consistency monitoring result of the monitoring event from the consistency monitoring result corresponding to the monitoring task;

[0231] Executing the alarm task to obtain an alarm result corresponding to the alarm task, wherein the alarm result corresponding to the alarm task includes the alarm result of the target monitoring item and the alarm results of each of the monitoring items to be merged;

[0232] The alarm result of the monitoring event is obtained from the alarm result corresponding to the alarm task.

[0233] In some implementations, when the information of the monitoring indicator indicates that the monitoring indicator type is a basic monitoring indicator, the monitoring alarm module 34 is specifically configured to:

[0234] Executing the monitoring task to read monitoring data from the accuracy monitoring results of the database;

[0235] A consistency monitoring result of the monitoring event is determined based on the monitoring data.

[0236] In some implementations, the consistency monitoring results of the multiple monitoring items included in the consistency monitoring results corresponding to the monitoring task are a row of monitoring data, and the alarm results of the multiple monitoring items included in the alarm results corresponding to the alarm task are a row of alarm data; the monitoring alarm module 34 is specifically used to:

[0237] The monitoring and alarm module 34 is specifically used to:

[0238] Converting the consistency monitoring result corresponding to the monitoring task from one row of monitoring data to multiple rows of monitoring results, where each row of monitoring results is a consistency monitoring result of one monitoring item;

[0239] The alarm result corresponding to the alarm task is converted from one row of alarm data to multiple rows of alarm results, where each row of alarm results is an alarm result for one monitoring item.

[0240] In some implementations, the monitoring pool also includes the monitoring results corresponding to the generated monitoring items. When the target monitoring item is obtained from the monitoring pool, the monitoring alarm module 34 is further configured to:

[0241] Obtaining the monitoring result corresponding to the target monitoring item from the monitoring pool;

[0242] Determine whether the monitoring result corresponding to the target monitoring item is valid;

[0243] When the monitoring result corresponding to the target monitoring item is valid, the monitoring display result is determined according to the monitoring result corresponding to the target monitoring item;

[0244] When the monitoring result corresponding to the target monitoring item is invalid, the consistency monitoring result of the monitoring event is obtained according to the target monitoring item, and the obtained consistency monitoring result is written into the monitoring pool.

[0245] In some implementations, the system further includes a configuration module configured to:

[0246] Providing a configuration page for monitoring events, the configuration page includes a setting entry for multiple configuration items of the monitoring items, the multiple configuration items including configuration items of the monitoring objects and configuration items of the monitoring indicators, and the setting entry is used for the user to select or enter the value of the configuration item;

[0247] Receive the value of the configuration item set by the user through the configuration page.

[0248] In some implementations, the target alarm configuration information includes: information about a monitored object, information about an alarm indicator, and blocking indication information, wherein the blocking indication information is used to indicate whether to block the monitored object when an abnormality occurs, and the information about the alarm indicator includes information about at least one alarm indicator;

[0249] The configuration information of the alarm indicator includes an alarm period, an alarm indicator category, an alarm indicator name, an alarm rule item, an alarm threshold source, a threshold type, and a normal threshold.

[0250] In some implementations, the set of monitoring objects is in any one of the following forms: two tables, two fields, one table and one field, the two fields are fields in two different tables, or the two fields are two different fields in the same table.

[0251] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here.

[0252] The above describes the device 300 of the embodiment of the present application from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps in the above method embodiment in conjunction with its hardware.

[0253] Figure 8 A schematic diagram of the structure of the monitoring device provided in the embodiment of the present application is shown in FIG. Figure 8 As shown, monitoring device 400 includes a processor 401 having one or more processing cores, a memory 402 having one or more computer-readable storage media, and a computer program stored in memory 402 and executable on the processor. Processor 401 is electrically connected to memory 402. Those skilled in the art will appreciate that the monitoring device structure shown in the figure does not limit the monitoring device and may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0254] The processor 401 is the control center of the monitoring device 400. It uses various interfaces and lines to connect the various parts of the entire monitoring device 400. By running or loading software programs and / or modules stored in the memory 402 and calling data stored in the memory 402, it executes various functions of the monitoring device 400 and processes data, thereby performing overall processing on the monitoring device 400.

[0255] In the embodiment of the present application, the processor 401 in the monitoring device 400 loads instructions corresponding to one or more application processes into the memory 402 according to the following steps, and the processor 401 runs the application stored in the memory 402, thereby achieving the following functions:

[0256] According to the monitoring information of the monitoring event submitted by the user, the target monitoring item corresponding to the monitoring event is obtained from the monitoring pool, the monitoring pool includes multiple generated monitoring items, and the target monitoring item is used to perform consistency monitoring on a group of monitoring objects, and the group of monitoring objects includes two monitoring objects; when the target monitoring item does not exist in the monitoring pool, the target monitoring item is generated according to the monitoring information; the target alarm configuration information of the target monitoring item is determined according to the target monitoring item; a monitoring task is generated according to the target monitoring item and at least one monitoring item to be merged, and the monitoring task is executed to obtain the consistency monitoring result of the monitoring event; an alarm task is generated according to the target alarm configuration information and the alarm configuration information corresponding to the at least one monitoring item to be merged, and the alarm task is executed to obtain the alarm result of the monitoring event, wherein the monitoring table of the target monitoring item and each monitoring item to be merged is the same; the monitoring display result is determined according to the consistency monitoring result, and alarm processing is performed according to the alarm result.

[0257] The specific implementation of the above operations can be found in the previous embodiments and will not be repeated here.

[0258] Optional, such as Figure 8 As shown, the monitoring device 400 further includes: a display screen 403, a radio frequency circuit 404, an audio circuit 405, an input unit 406, and a power supply 407. Among them, the processor 401 is electrically connected to the display screen 403, the radio frequency circuit 404, the audio circuit 405, the input unit 406, and the power supply 407 respectively. It will be understood by those skilled in the art that Figure 8 The monitoring device structure shown in the figure does not constitute a limitation to the monitoring device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0259] Display screen 403 can be used for displaying graphical user interface and receiving the operation instruction that user acts on graphical user interface generation.Display screen 403 can be a touch display screen, and touch display screen can include display panel and touch panel.Wherein, display panel can be used for displaying the information input by user or the information provided to user and various graphical user interfaces of monitoring equipment, and these graphical user interfaces can be made up of graphics, text, icons, videos and any combination thereof.Optionally, liquid crystal display (LCD, Liquid Crystal Display), organic light emitting diode (OLED, Organic Light-Emitting Diode) and other forms can be used to configure display panel.Touch panel can be used for collecting user's touch operation thereon or near it (such as user uses finger, stylus or any suitable object or accessory on touch panel or near touch panel operation), and generates corresponding operation instruction, and operation instruction executes corresponding program.Optionally, touch panel can include two parts of touch detection device and touch controller. Among them, the touch detection device detects the user's touch direction, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 401, and can receive the command sent by the processor 401 and execute it. The touch panel can cover the display panel. When the touch panel detects a touch operation on or near it, it is transmitted to the processor 401 to determine the type of touch event, and then the processor 401 provides a corresponding visual output on the display panel according to the type of touch event. In an embodiment of the present application, the touch panel and the display panel can be integrated into a touch display screen to realize input and output functions. However, in some embodiments, the touch panel and the touch panel can be used as two independent components to realize input and output functions. That is, the touch display screen can also be used as part of the input unit 406 to realize the input function.

[0260] The radio frequency circuit 404 may be used to transmit and receive radio frequency signals, so as to establish wireless communication with network devices or other monitoring devices through wireless communication, and to transmit and receive signals with the network devices or other monitoring devices.

[0261] Audio circuit 405 can be used to provide an audio interface between the user and the monitoring device via a speaker and microphone. Audio circuit 405 can convert received audio data into electrical signals and transmit them to the speaker, which then converts them into sound signals for output. Conversely, the microphone converts collected sound signals into electrical signals, which are then received by audio circuit 405 and converted into audio data. The audio data is then output to processor 401 for processing, then sent via RF circuit 404 to, for example, another monitoring device, or to memory 402 for further processing. Audio circuit 405 may also include an earphone jack to provide communication between external headphones and the monitoring device.

[0262] The input unit 406 may be configured to receive input digital, character information, or object feature information (such as fingerprint, iris, or facial information), and generate keyboard, mouse, joystick, optical, or trackball signal input related to user settings and function control.

[0263] Power supply 407 is used to power the various components of monitoring device 400. Optionally, power supply 407 can be logically connected to processor 401 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. Power supply 407 can also include one or more DC or AC power supplies, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and other arbitrary components.

[0264] although Figure 8 Not shown in the figure, the monitoring device 400 may further include a camera, a sensor, a wireless fidelity module, a Bluetooth module, etc., which will not be described in detail here.

[0265] The present application also provides a computer storage medium having a computer program stored thereon, which, when executed by a computer, enables the computer to perform the method of the above-mentioned method embodiment. In other words, the present application also provides a computer program product containing instructions, which, when executed by a computer, enables the computer to perform the method of the above-mentioned method embodiment.

[0266] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor of an electronic device reads the computer program from the computer-readable storage medium and executes the computer program, causing the electronic device to perform the corresponding processes in the above-mentioned method embodiments. For the sake of brevity, these processes are not further described here.

[0267] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules is merely a logical function division. In actual implementation, there may be other division methods, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0268] Modules described as separate components may or may not be physically separate, and components displayed as modules may or may not be physical modules, i.e., they may be located in one place or distributed across multiple network elements. Some or all of the modules may be selected based on actual needs to achieve the purpose of the present embodiment. For example, the functional modules in the various embodiments of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into a single module.

[0269] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A data consistency monitoring method, characterized in that: The method comprises: Obtaining, from a monitoring pool, a target monitoring item corresponding to a monitoring event submitted by a user, the target monitoring item being used to monitor consistency of a group of monitoring objects, the group of monitoring objects including two monitoring objects, based on monitoring information of the monitoring event submitted by the user; When the target monitoring item does not exist in the monitoring pool, generating the target monitoring item according to the monitoring information; Determining target alarm configuration information of the target monitoring item according to the target monitoring item; Generate a monitoring task based on the target monitoring item and at least one monitoring item to be merged, execute the monitoring task to obtain a consistency monitoring result of the monitoring event, generate an alarm task based on the target alarm configuration information and the alarm configuration information corresponding to the at least one monitoring item to be merged, execute the alarm task to obtain an alarm result of the monitoring event, wherein the monitoring table of the target monitoring item and each of the monitoring items to be merged is the same; The monitoring display result is determined according to the consistency monitoring result, and the alarm processing is performed according to the alarm result.

2. The method according to claim 1, characterized in that When the target monitoring item does not exist in the monitoring pool, generating the target monitoring item according to the monitoring information includes: According to the monitoring information, basic information of the monitoring object required to be monitored for the monitoring event is obtained; Generate candidate monitoring items according to the basic information of the monitoring object required to be monitored for the monitoring event and the monitoring information; Review the candidate monitoring items according to the preset monitoring item review rules; When the review is passed, the target monitoring item is generated based on the candidate monitoring item.

3. The method according to claim 2, characterized in that The review of the candidate monitoring items according to the preset monitoring item review rules includes: Determine whether the non-customized monitoring indicators in the candidate monitoring items are necessary; When the candidate monitoring items include a custom monitoring indicator, determining whether the custom monitoring indicator complies with grammatical rules; Determine whether the custom monitoring indicator is repeated with an existing indicator in the monitoring pool; Determine whether the custom monitoring indicator is necessary.

4. The method according to claim 1, wherein The determining the target alarm configuration information of the target monitoring item according to the target monitoring item includes: Determining whether the monitoring pool includes alarm configuration information corresponding to the target monitoring item; When the monitoring pool includes the alarm configuration information corresponding to the target monitoring item, the alarm configuration information corresponding to the target monitoring item is obtained from the monitoring pool; When the monitoring pool does not include the alarm configuration information corresponding to the target monitoring item, providing an alarm configuration interface according to the target monitoring item; Receiving candidate alarm information input by a user through the alarm interface, the candidate alarm information including candidate alarm indicators and threshold values ​​of the candidate alarm indicators; Review the candidate alarm information according to the preset alarm review rules; The target alarm configuration information is generated according to the audit result and the candidate alarm information.

5. The method according to claim 4, characterized in that The reviewing of the candidate alarm information according to the preset alarm review rules includes: Determine whether the candidate alarm indicator is an existing alarm indicator; When the candidate alarm indicator is an existing alarm indicator, it is determined whether the threshold of the candidate alarm indicator is the same as the threshold of the existing alarm indicator.

6. The method according to claim 1, characterized in that The target monitoring item includes information about the monitoring object and information about the monitoring indicator. The information about the monitoring object includes information about the left-source monitoring object and information about the right-source monitoring object. The information about the left-source monitoring object includes: library name, table name, field name, monitoring period, monitoring indicator type, monitoring indicator details, and monitoring indicator name. The information about the right-source monitoring object includes: library name, table name, field name, monitoring period, monitoring indicator type, monitoring indicator details, and monitoring indicator name. The information of the monitoring indicators included in the target monitoring item includes: monitoring indicator type, monitoring indicator details, at least one monitoring indicator name, monitoring period and monitoring rule items.

7. The method according to claim 6, characterized in that The monitoring indicator types include: basic monitoring indicators, associated monitoring indicators or custom monitoring indicators; When the monitoring indicator type is the basic monitoring indicator, the monitoring indicator item is a numerical indicator, and the monitoring indicator name of the basic monitoring indicator is ratio, difference or difference ratio; When the monitoring indicator type is an associated monitoring indicator, the monitoring indicator item is a quantity indicator or a proportion indicator, the associated monitoring indicator is a non-associated field and an associated field, and the monitoring indicator name corresponding to the associated field includes the following information: the difference between the left and right sources of the associated field, the proportion of the difference between the left and right sources of the associated field, the quantity of the associated field with left source and right source but no quantity, the proportion of the associated field with left source and right source but no quantity, the quantity of the associated field with left source and no right source, and the proportion of the associated field with left source and no right source but no quantity; The monitoring indicator name corresponding to the non-correlated field includes the following information: the difference between the left and right sources of the non-correlated field, and the proportion of the difference between the left and right sources of the non-correlated field.

8. The method according to any one of claims 1 to 7, characterized in that The executing the monitoring task to obtain the consistency monitoring result of the monitoring event includes: Execute the monitoring task to obtain the monitoring table from the database, and obtain the consistency monitoring result corresponding to the monitoring task from the monitoring table, wherein the consistency monitoring result corresponding to the monitoring task includes the consistency monitoring result of the target monitoring item and the consistency monitoring results of each of the monitoring items to be merged; Obtaining the consistency monitoring result of the monitoring event from the consistency monitoring result corresponding to the monitoring task; The executing the alarm task to obtain the alarm result of the monitoring event includes: Executing the alarm task to obtain an alarm result corresponding to the alarm task, wherein the alarm result corresponding to the alarm task includes the alarm result of the target monitoring item and the alarm results of each of the monitoring items to be merged; The alarm result of the monitoring event is obtained from the alarm result corresponding to the alarm task.

9. The method according to claim 8, characterized in that When the information of the monitoring indicator indicates that the monitoring indicator type is a basic monitoring indicator, executing the monitoring task to obtain a consistency monitoring result corresponding to the monitoring task includes: Executing the monitoring task to read monitoring data from the accuracy monitoring results of the database; A consistency monitoring result of the monitoring event is determined based on the monitoring data.

10. The method according to claim 8, characterized in that The consistency monitoring results of the multiple monitoring items included in the consistency monitoring results corresponding to the monitoring task are a row of monitoring data, and the alarm results of the multiple monitoring items included in the alarm results corresponding to the alarm task are a row of alarm data; The obtaining of the consistency monitoring result of the monitoring event from the consistency monitoring result corresponding to the monitoring task includes: Converting the consistency monitoring result corresponding to the monitoring task from one row of monitoring data to multiple rows of monitoring results, where each row of monitoring results is a consistency monitoring result of one monitoring item; The obtaining of the alarm result of the monitoring event from the alarm result corresponding to the alarm task includes: The alarm result corresponding to the alarm task is converted from one row of alarm data to multiple rows of alarm results, where each row of alarm results is an alarm result for one monitoring item.

11. The method according to any one of claims 1 to 7, characterized in that The monitoring pool also includes the monitoring results corresponding to the generated monitoring items. When the target monitoring item is obtained from the monitoring pool, the method further includes: Obtaining the monitoring result corresponding to the target monitoring item from the monitoring pool; Determine whether the monitoring result corresponding to the target monitoring item is valid; When the monitoring result corresponding to the target monitoring item is valid, the monitoring display result is determined according to the monitoring result corresponding to the target monitoring item; When the monitoring result corresponding to the target monitoring item is invalid, the consistency monitoring result of the monitoring event is obtained according to the target monitoring item, and the obtained consistency monitoring result is written into the monitoring pool.

12. The method according to any one of claims 1 to 7, characterized in that Before obtaining the target monitoring item corresponding to the monitoring event from the monitoring pool according to the monitoring information of the monitoring event submitted by the user, the method further includes: Providing a configuration page for monitoring events, the configuration page includes a setting entry for multiple configuration items of the monitoring items, the multiple configuration items including configuration items of the monitoring objects and configuration items of the monitoring indicators, and the setting entry is used for the user to select or enter the value of the configuration item; Receive the value of the configuration item set by the user through the configuration page.

13. The method according to any one of claims 1 to 7, characterized in that The target alarm configuration information includes: information about the monitored object, information about the alarm indicator, and blocking indication information, wherein the blocking indication information is used to indicate whether to block the monitored object when an abnormality occurs, and the information about the alarm indicator includes information about at least one alarm indicator; The configuration information of the alarm indicator includes an alarm period, an alarm indicator category, an alarm indicator name, an alarm rule item, an alarm threshold source, a threshold type, and a normal threshold.

14. The method according to any one of claims 1 to 7, characterized in that The group of monitoring objects is in any one of the following forms: two tables, two fields, one table and one field, the two fields are fields in two different tables, or the two fields are two different fields in the same table.

15. A data consistency monitoring device, characterized in that: include: an acquisition module, configured to acquire, from a monitoring pool, a target monitoring item corresponding to a monitoring event submitted by a user, the monitoring information of the monitoring event, the monitoring pool including a plurality of generated monitoring items, the target monitoring item being used to perform consistency monitoring on a group of monitoring objects, the group of monitoring objects including two monitoring objects; a generating module, configured to generate the target monitoring item according to the monitoring information when the target monitoring item does not exist in the monitoring pool; A determination module, configured to determine target alarm configuration information of the target monitoring item according to the target monitoring item; A monitoring and alarm module, configured to generate a monitoring task based on the target monitoring item and at least one monitoring item to be merged, execute the monitoring task to obtain a consistency monitoring result of the monitoring event, generate an alarm task based on the target alarm configuration information and the alarm configuration information corresponding to the at least one monitoring item to be merged, and execute the alarm task to obtain an alarm result of the monitoring event, wherein the monitoring table of the target monitoring item and each of the monitoring items to be merged is the same; The display module is used to determine the monitoring display result according to the consistency monitoring result and perform alarm processing according to the alarm result.

16. A monitoring device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 15.

17. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 15.

18. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 15 is implemented.

Images