CN116562715A

CN116562715A - Index data monitoring method, device, computer equipment and storage medium

Info

Publication number: CN116562715A
Application number: CN202310831528.2A
Authority: CN
Inventors: 智苏朋; 杨哲
Original assignee: Meiyun Zhishu Technology Co ltd
Current assignee: Meiyun Zhishu Technology Co ltd
Priority date: 2023-07-07
Filing date: 2023-07-07
Publication date: 2023-08-08
Anticipated expiration: 2043-07-07
Also published as: CN116562715B

Abstract

The embodiment of the specification provides an index data monitoring method, an index data monitoring device, computer equipment and a storage medium. The index data monitoring method comprises the following steps: determining an index model comprising index fields and logical operational relationships thereof in response to an index modeling operation for a target data table in a target database; if a monitoring rule configuration operation based on the index field is received, determining a monitoring rule corresponding to the index model; responding to data conversion configuration operation based on the monitoring rule and the index model, and obtaining a data conversion task; wherein the data conversion task references at least some of the monitoring rules; in the execution process of the data conversion task, acquiring corresponding index data from service data of an external service database based on an index model; if the index data is monitored to not meet at least part of the rules, the target event to be handled aiming at the data conversion task is displayed, so that the accuracy of monitoring the index data aiming at the data conversion task can be improved.

Description

Index data monitoring method, device, computer equipment and storage medium

Technical Field

The embodiment of the specification relates to the technical field of data processing, in particular to an index data monitoring method, an index data monitoring device, computer equipment and a storage medium.

Background

With the development of computer internet technology, it has become common knowledge to manage and control index data as assets, and enterprises can make more intelligent and effective decisions depending on the index data, so as to provide better products and services, and reduce cost and risk control. Because the index data is often complicated, the index data acquisition process needs to be monitored in order to ensure the subsequent utilization value of the index data.

However, in the related art, when monitoring the index data, the corresponding monitoring rule cannot be determined for the acquisition process of different index data, and the monitoring accuracy needs to be improved.

Disclosure of Invention

In view of this, various embodiments of the present disclosure are directed to providing an index data monitoring method, apparatus, computer device, and storage medium to improve the accuracy of index data monitoring.

The embodiment of the specification provides an index data monitoring method, which is applied to a data platform connected with an external service database, wherein the data platform comprises a target database; the index data monitoring method comprises the following steps: determining an index model in response to an index modeling operation for a target data table in a target database; wherein, the index model comprises an index field and a logic operation relation corresponding to the index field; if a monitoring rule configuration operation based on at least part of the index fields is received, determining a monitoring rule corresponding to the index model; responding to data conversion configuration operation based on the monitoring rule and the index model, and obtaining a data conversion task; wherein the data conversion task references at least some of the monitoring rules; in the execution process of the data conversion task, acquiring corresponding index data from the service data of the external service database based on the index model; if the index data does not meet the at least partial rule, displaying a target to-do event aiming at the data conversion task; and re-executing the index data acquired by the data conversion task to meet the at least partial rule after the target to-do event is processed.

Further, the indicator field includes a base indicator field; the determining an index model in response to an index modeling operation for a target data table in a target database, comprising: configuring an index attribute in response to an index registration operation for an index configuration component; wherein the index attribute comprises an index category; if the index attribute comprises a basic index category, determining a target database in response to a specified operation aiming at the database name; determining a target data table from the target database in response to a designation operation for the data table; determining the basic index field corresponding to the target data table and determining a value operation relation for taking the basic index field from the target data table in response to basic index modeling operation aiming at the index configuration component, so as to obtain a basic index model; wherein the logical operation relationship includes the value operation relationship; the index model includes the base index model.

Further, the number of the basic index fields is a plurality; the determining the basic index field corresponding to the target data table and determining a value operation relation for taking the basic index field from the target data table in response to a basic index modeling operation aiming at the index configuration component comprises the following steps: determining a plurality of base index fields corresponding to the target data table in response to a base index modeling operation for the index configuration component; wherein a plurality of the base metrics fields include at least one dimension field for sizing and one metric field for quantification; and respectively configuring the value operation relation of any one of the basic index fields in response to the configuration operation aiming at the index formula configuration component.

Further, the indicator field further comprises a composite indicator field; the determining an index model in response to an index modeling operation for a target data table in a target database, further comprises: if the index attribute comprises a composite index category, responding to composite index modeling operation aiming at the index configuration component, determining the composite index field based on a target basic model in the basic index models and determining an association operation relation for associating the target basic models to obtain a composite index model; wherein the logical operation relationship further comprises the association operation relationship; the index model also includes the composite index model.

Further, the responding to the composite index modeling operation aiming at the index configuration component, determining the composite index field based on a target basic model in the basic index models and determining an association operation relation for associating the target basic models, and obtaining a composite index model comprises the following steps: determining the composite index field based on a plurality of the target base models of the base index models in response to a composite index modeling operation for the index configuration component; and configuring the association operation relation among a plurality of target basic models in response to the configuration operation of the index formula configuration component to obtain the composite index model.

Further, the monitoring rule corresponding to the index model includes at least one sub-rule; and if a monitoring rule configuration operation based on at least part of the index fields is received, determining a monitoring rule corresponding to the index model, including: if a monitoring rule configuration operation based on at least part of the index fields in the index model is received, determining at least one sub-rule according to at least part of the index fields; wherein the monitoring rule includes the at least one sub-rule; any of the sub-rules includes query statements, monitoring logic rules, and index thresholds; the query statement is used for acquiring index data corresponding to at least part of the index fields from a target database, and the index threshold is used for comparing and judging the index data with the corresponding index data through the monitoring logic rule.

Further, the index data monitoring method further comprises the following steps: if a basic information configuration operation aiming at the monitoring rule is received, determining basic information of the monitoring rule; the basic information of the monitoring rule at least comprises a monitoring rule name and a monitoring rule code.

Further, the responding to the data conversion configuration operation based on the monitoring rule and the index model obtains a data conversion task, which comprises the following steps: in response to a data conversion configuration operation for a data conversion configuration component, configuring a data conversion task corresponding to the index model, and determining at least some of the monitoring rules referenced by the data conversion task; the data conversion task at least comprises a task name, a task code, a task starting time, a task ending time and a conversion expression; the conversion expression is used for representing the data conversion task to acquire mapping information of corresponding service data from an external service database based on the index model.

Further, if it is detected that the index data does not meet the at least part of rules, displaying a target to-do event for the data conversion task, including: if the index data does not meet the at least partial rule, generating a target to-do event corresponding to the at least partial rule aiming at the index data of the data conversion task; displaying the target event to be handled; the target to-do event at least comprises: and the data conversion task is abnormal, and the occurrence time and the processing state of the abnormal problem are determined.

The embodiment of the specification provides an index data monitoring device, which is applied to a data platform connected with an external service database, wherein the data platform comprises a target database; the index data monitoring device comprises: an index model configuration module for determining an index model in response to an index modeling operation for a target data table in a target database; wherein, the index model comprises an index field and a logic operation relation corresponding to the index field; the monitoring rule configuration module is used for determining a monitoring rule corresponding to the index model if a monitoring rule configuration operation based on at least part of the index fields is received; the data task configuration module is used for responding to the data conversion configuration operation based on the monitoring rule and the index model to obtain a data conversion task; wherein the data conversion task references at least some of the monitoring rules; in the execution process of the data conversion task, acquiring corresponding index data from the service data of the external service database based on the index model; the monitoring display module is used for displaying a target to-do event aiming at the data conversion task if the index data does not meet the at least partial rule; and re-executing the index data acquired by the data conversion task to meet the at least partial rule after the target to-do event is processed.

The embodiment of the present specification provides a computer device, including a memory and a processor, where the memory stores a computer program, and the processor implements the index data monitoring method according to any one of the embodiments above when executing the computer program.

The present specification provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the index data monitoring method according to any one of the above embodiments.

According to the embodiments provided by the specification, the index model comprising the index field and the corresponding logical operation relation is determined by responding to the index modeling operation aiming at the target data table in the target database, the monitoring rule corresponding to the index model is determined under the condition that the monitoring rule configuration operation based on at least part of the index field is received, then the data conversion task referencing at least part of the rules in the monitoring rule is obtained by responding to the data conversion configuration operation based on the monitoring rule and the index model, so that in the execution process of the data conversion task, the corresponding service data can be obtained from the external service database, the index data corresponding to the index model is obtained, and the target to-be-handled event aiming at the data conversion task is displayed under the condition that the index data does not meet the at least part of the rules is monitored, so that after the target to-be-handle event is processed, the index data acquired by re-executing the data conversion task can meet the at least part of the rules, and the accuracy of monitoring the index data aiming at the data conversion task can be improved.

Drawings

Fig. 1 is a schematic diagram of an index data monitoring system according to an embodiment of the present disclosure.

Fig. 2 is a flow chart of an index data monitoring method according to an embodiment of the present disclosure.

Fig. 3 is a flowchart of a method for determining an index model according to an embodiment of the present disclosure.

Fig. 4 is a schematic diagram of an index registration component provided in an embodiment of the present disclosure.

Fig. 5 is a schematic diagram of a basic index configuration component according to an embodiment of the present disclosure.

Fig. 6 is a flowchart of a method for determining a basic index model according to an embodiment of the present disclosure.

Fig. 7 is a schematic diagram of a composite index configuration component according to an embodiment of the present disclosure.

Fig. 8 is a flow chart of a method for determining a composite index model according to an embodiment of the present disclosure.

Fig. 9 is a schematic diagram of a monitoring rule configuration component provided in an embodiment of the present disclosure.

Fig. 10 is a schematic diagram of a data conversion configuration component according to an embodiment of the present disclosure.

Fig. 11 is a flowchart of an index data monitoring method according to an embodiment of the present disclosure.

Fig. 12 is a schematic diagram of an index data monitoring device according to an embodiment of the present disclosure.

Fig. 13 is a schematic diagram of a computer device according to an embodiment of the present disclosure.

Detailed Description

In order to make the technical solution of the present specification better understood by those skilled in the art, the technical solution of the present specification embodiment will be clearly and completely described below with reference to the accompanying drawings in the embodiment of the present specification, and it is apparent that the described embodiment is only a part of the embodiment of the present specification, but not all the embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

Therefore, it is necessary to provide an index data monitoring method, by establishing an index model, determining a monitoring rule corresponding to the index model, and configuring a data conversion task referencing at least a part of the rule, so that when the data conversion task is executed, index data corresponding to the index model can be obtained from an external service database, and when the index data is monitored to not meet the at least a part of the rule, a target event to be handled for the data conversion task is displayed, so as to prompt an operation and maintenance person to maintain the data conversion task, and thus, the accuracy of monitoring the index data for the data conversion task can be improved.

Referring to fig. 1, fig. 1 is a schematic diagram of an index data monitoring system according to an embodiment of the present disclosure. The index data monitoring system may include a data platform 110 and a plurality of external business databases 120 coupled to the data platform 110, wherein the data platform 110 may include a plurality of platform databases. Any one of the plurality of platform databases may be a target database and the plurality of data tables of the target database may include a target data table. An output terminal 130 may also be connected to the data platform. Specifically, the data platform 110 may be connected to the external service database 120 and the output terminal 130 through a network.

Referring to fig. 2, fig. 2 is a schematic flow chart of the method for monitoring index data according to the embodiment, and the method according to the embodiment provides the steps of the method according to the flow chart, but may include more or less steps based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one implementation of a plurality of step execution orders and does not represent a unique execution order. In actual system or server product execution, the methods illustrated in the embodiments may be performed sequentially or in parallel (e.g., in parallel processors or in the context of multi-threaded processing). The index data monitoring method can be applied to a data platform, and particularly as shown in fig. 2, the index data monitoring method can comprise the following steps.

Step S210: determining an index model in response to an index modeling operation for a target data table in a target database; the index model comprises an index field and a logic operation relation corresponding to the index field.

In some cases, the data platform may be provided with a target database, and an index model may be established based on a target data table selected from the target database, so that a monitoring rule and a configuration data conversion task may be configured according to the established index model, and index data corresponding to the index model, which is acquired by the data conversion task, may be monitored by the monitoring rule.

In this embodiment, the data platform may determine the index field in response to the index modeling operation, determine the target data table from the target database in response to the index modeling operation, and determine the logical operation relationship corresponding to the index field and capable of being associated with the target data table, that is, may associate the index field with the target data table through the logical operation relationship of the index field, to obtain the index model including the index field and the logical operation relationship thereof.

Step S220: and if a monitoring rule configuration operation sent based on at least part of the index fields is received, determining the monitoring rule corresponding to the index model.

In some cases, an index model may be used to determine corresponding index data, and in order to enable monitoring of the index data, a monitoring rule corresponding to the index model may be configured.

In this embodiment, after the index model is established, the monitoring rule corresponding to the index model may be determined based on the monitoring rule configuration operation. Specifically, for example, in the case where a monitoring rule configuration operation issued based on an index field of an index model is received, a monitoring rule corresponding to the index model may be determined. For example, the monitoring rule corresponding to the index model may be configured based only on at least a part of the index fields in the index model, i.e., the monitoring rule corresponding to the index model may be determined in case a monitoring rule configuration operation based on at least a part of the index fields in the index model is received.

Step S230: responding to data conversion configuration operation based on the monitoring rule and the index model, and obtaining a data conversion task; wherein the data conversion task references at least some of the monitoring rules; in the execution process of the data conversion task, corresponding index data is obtained from service data of an external service database based on an index model.

In this embodiment, after the index model is established and the monitoring rule corresponding to the index model is configured, a data conversion task referencing at least some of the monitoring rules may be obtained in response to a data conversion configuration operation performed based on the monitoring rule and the index model, so that the index data corresponding to the index model may be obtained from the service data of the external service database by executing the data conversion task, and the obtained index data may be monitored by referencing at least some of the rules.

Specifically, the number of external service databases connected to the data platform may be plural, and the number of external service data tables of any external service database in the plurality of external service databases may be plural. In response to the data conversion configuration operation, a data conversion task including a mapping relationship between the index model and any external service data table in any external service database may be configured so that service data of any external service data table in any external service database having a mapping relationship with the index model may be obtained, index data corresponding to the index model may be obtained, and the corresponding index data may be stored in a target data table corresponding to the index model.

Step S240: if the index data is monitored to not meet at least part of the rules, displaying a target event to be handled aiming at the data conversion task; after the target to-do event is processed, the index data acquired by the data conversion task is re-executed to meet at least part of rules.

In this embodiment, during execution of the data conversion task, at least some of the monitoring rules cited by the data conversion task may be used to monitor the index data corresponding to the index model, and when it is monitored that the index data corresponding to the index model does not meet the cited at least some of the rules, a target to-do event for the data conversion task may be determined based on the index data that does not meet the at least some of the rules, and the target to-do event may be displayed, so as to prompt an operation and maintenance staff to maintain the data conversion task according to the target to-do event, so that the index data obtained based on the maintained data conversion task may meet the cited at least some of the monitoring rules.

In the above embodiment, by responding to various index models flexibly configured by index modeling operation, flexibly configuring the monitoring rules corresponding to the index models by the monitoring rule configuration operation, and flexibly configuring the data conversion tasks capable of referring to at least some of the monitoring rules by the data conversion configuration operation, when the data conversion tasks are executed to obtain index data, the data conversion tasks can be monitored based on at least some of the referenced rules, and when the index data which does not meet the at least some of the rules is determined, the target to-do event for the data conversion tasks is determined, and the target to-do event is displayed, so that an operation and maintenance person can be prompted to maintain the data conversion tasks according to the target to-do event, so that the index data obtained based on the maintained data conversion tasks can meet the at least some of the referenced monitoring rules, and thus, the accuracy of monitoring the index data can be improved while the flexibility of monitoring the index data for the data conversion tasks is improved.

In some implementations, the indicator field may include a base indicator field. Referring to FIG. 3, in response to an index modeling operation for a target data table in a target database, determining an index model may include the following steps.

Step S310: configuring an index attribute in response to an index registration operation for an index configuration component; wherein the index attribute includes an index category.

In some cases, the index attributes may be configured first to build an index model based on the index attributes.

In the present embodiment, the index attribute including at least the index category may be configured in response to the index registration operation for the index configuration component. In particular, referring to FIG. 4, the data platform provided metrics configuration components may include a metrics registration component 410 for configuring metrics attributes, at least a metrics category may be configured in response to a metrics registration operation for the metrics registration component 410 in the metrics configuration component.

In particular, the index attributes may include an index business attribute and an index management attribute. The index service attribute refers to a metric attribute, and can provide algorithm information for the establishment of an index model. The index management attribute can provide supervision objects for data conversion tasks or index data corresponding to the index model so as to complete closed-loop tracking and monitoring. With continued reference to fig. 4, the data platform may configure at least the metrics management attributes and metrics business attributes including metrics categories in response to the metrics registration operation for the metrics registration component 410.

Illustratively, the index business attribute may further include at least one of a business classification, an index name, a unit of measure, an index definition, an index caliber, and an index value type. The measurement unit may be a measurement unit used in statistical analysis of a reporter service, the index definition may be a service definition, that is, a meaning and use of reflection, and the index caliber may be an applicable range and statistical mode.

Specifically, the index management attribute may include at least one of an index affiliated section, an index responsible section, an index development section, a business responsible person, an index development responsible person, an index data responsible person, and an index online state. As an example, the index business attribute may further include at least one of an index english name and an index english abbreviation. The index management attribute may also include index security level information.

Step S320: if the index attribute includes a base index category, a target database is determined in response to a specified operation for the database library name.

The basic index category may be used to describe a basic index field of the index fields, where the basic index field refers to an index field that can be directly associated with the target data table, or, in other words, index data corresponding to the basic index field may be directly obtained from the target data or stored in the target data table.

In particular, referring to FIG. 5, the index configuration component provided by the data platform may include a base index configuration component 510. A determination may be made regarding an index category in the index attribute, and in the event that the index attribute includes a base index category, a target database may be determined from a plurality of platform databases provided by the data platform in response to a designation operation of the database library name for the base index configuration component 510.

Step S330: a target data table is determined from the target database in response to a specified operation for the data table.

Specifically, after determining the target database from the plurality of platform databases, referring still to fig. 5, a target data table for association with the base index field may be determined from the plurality of data tables of the target database in response to a designation operation of the data table for the base index configuration component 510.

Step S340: determining a basic index field corresponding to the target data table and determining a value operation relation for taking the basic index field from the target data table in response to basic index modeling operation aiming at the index configuration component, so as to obtain a basic index model; wherein the logical operation relationship comprises a value operation relationship; the index model includes a base index model.

In this embodiment, after determining the target data table for associating with the base index field, please continue to refer to fig. 5, the base index model may be obtained in response to the base index modeling operation for the base index configuration component 510, determining the base index field corresponding to the target data table, and determining the value operation relationship for taking the value of the base index field from the target data table based on the target data table.

Illustratively, the sequence number information, the index specification information corresponding to the base index field may also be determined in response to a base index modeling operation for the base index configuration component.

As an example, referring to fig. 5, in response to a designating operation on a database library name for a base index configuration component, a target database with a library name of "DM" may be determined, in response to a designating operation on a data table for a base index configuration component, a target data table may be determined to be "gd_update_0920", in response to a base index modeling operation for a base index configuration component, a base index field may be determined to be "gdname", and corresponding sequence number information, index specification information, and value operation relationships may be determined to be "1", "cargo name", "gd_update_0920. Gdname", respectively.

In the above embodiment, by responding to the index registration operation, the index attribute including at least the index category may be configured, and in the case that the index attribute includes the basic index category, the target database is determined in response to the designating operation for the database library name, the target data table is determined in response to the designating operation for the data table, and the basic index field and the corresponding value operation relationship are determined in response to the basic index modeling operation for the target data table, so as to obtain the basic index model, so that the basic index field capable of being directly associated with the target data table through the logic operation relationship may be established.

In some embodiments, the number of base index fields may be multiple. Referring to fig. 6, in response to a basic index modeling operation for an index configuration component, determining a basic index field corresponding to a target data table and determining a value operation relationship for taking a value of the basic index field from the target data table may include the following steps.

Step S610: determining a plurality of base index fields corresponding to the target data table in response to a base index modeling operation for the index configuration component; wherein the plurality of base metrics fields includes at least one dimension field for categorizing and one metric field for quantifying.

In this embodiment, with continued reference to fig. 5, the data platform provided base index configuration component 510 may further include a base dimension field addition component 520 and a base metric field addition component 530. Specifically, at least one base indicator field for categorization as a dimension field may be determined in response to a dimension field addition operation for the base dimension field addition component, and at least one base indicator field for quantification as a measure field may be determined in response to a measure field addition operation for the base measure field addition component.

For example, referring to fig. 5, in response to the dimension field adding operation for the base dimension field adding component, it may be determined that one base index field as the dimension field is "gdname" and corresponding sequence number information and index specification information are "1" and "cargo name", respectively.

For example, in response to the dimension field adding operation for the base dimension field adding component, it may be determined that one base index field as a dimension field is "id" and corresponding sequence number information, index specification information are "2" and "goods number", respectively.

For example, in response to the metric field adding operation for the basic metric field adding component, it may be determined that one basic index field as the metric field is "up" and corresponding sequence number information, index specification information are "1", "unit price for selling goods", respectively.

Step S620: and respectively configuring the value operation relation of any basic index field in the plurality of basic index fields in response to the configuration operation aiming at the index formula configuration component.

In this embodiment, referring to fig. 5, the basic index configuration component 510 provided by the data platform may further include an index formula configuration component 540, which may configure a value operation relationship of any one of the plurality of basic index fields in response to a configuration operation for the index formula configuration component. Specifically, the number of index formula configuration components may be plural, and the plural index formula configuration components may correspond to the plural base index fields one by one. The value operation relationship of any corresponding base index field may be determined in response to a configuration operation for any index formula configuration component.

Illustratively, the value operation relationship corresponding to the base indicator field "gdname" may be determined to be "gd_UPace_0920. Gdname" in response to a configuration operation for the indicator formula configuration component corresponding to the base indicator field "gdname". Illustratively, the value operation relationship corresponding to the base index field "id" may be determined to be "gd_update_0920.id" in response to a configuration operation for the index formula configuration component corresponding to the base index field "id". For example, the value operation relationship corresponding to the base index field "UPace" may be determined to be "gd_UPace_0920. UPace" in response to a configuration operation for the index formula configuration component corresponding to the base index field "UPace".

In particular, with continued reference to FIG. 5, the data platform provided base index configuration component 510 may further include a base index field refresh component 550. Any basic index field and corresponding sequence number information, index description information and value operation relation thereof can be refreshed and displayed in response to the refreshing operation aiming at the basic index field refreshing component. For example, the number of basic index field refreshing components may be plural, and the plural basic index field refreshing components may be in one-to-one correspondence with the plural basic index fields. The corresponding basic index field, the corresponding serial number information, the index description information and the value operation relation can be refreshed and displayed in response to the refreshing operation of any basic index field refreshing component.

In particular, with continued reference to FIG. 5, the base index configuration component 510 provided by the data platform can further include a base index field deletion component 560. Any basic index field and corresponding sequence number information, index specification information and value operation relation thereof can be deleted in response to the deletion operation of the basic index field deletion component. For example, the number of the base index field deletion components may be plural, and the plural base index field deletion components may be in one-to-one correspondence with the plural base index fields. The corresponding basic index field, the corresponding serial number information, the index description information and the value operation relation can be deleted in response to the deleting operation of any basic index field deleting component.

In the above embodiment, the basic index model including the plurality of basic index fields may be configured by determining the plurality of basic index fields corresponding to the target data table in response to the basic index modeling operation for the index configuration component, and configuring the value operation relationship of any one of the plurality of basic index fields in response to the configuration operation for the index formula configuration component, respectively.

In some implementations, the indicator field may also include a composite indicator field. After configuring the index attribute, determining an index model in response to an index modeling operation for a target data table in the target database may further include: if the index attribute comprises a composite index category, responding to composite index modeling operation aiming at an index configuration component, determining a composite index field based on a target basic model in a basic index model and determining an association operation relation for associating the target basic models to obtain a composite index model; wherein the logical operation relationship further comprises an association operation relationship; the index model also includes a composite index model.

The composite index category may be used to describe a composite index field in the index fields, where the composite index field refers to an index field that cannot be directly associated with the target data table, or, the index data corresponding to the composite index field may be determined after association operation based on the corresponding basic index data, and cannot be directly stored in the target data table.

In this embodiment, referring to fig. 7, the index configuration component provided by the data platform may further include a composite index configuration component 710. Specifically, the method comprises the steps of judging an index category in an index attribute, determining a plurality of target basic models from a plurality of established basic index models in response to a composite index modeling operation of a composite index configuration component under the condition that the index attribute comprises the composite index category, determining composite index fields corresponding to the plurality of target basic models, associating at least one basic index field of each of the plurality of target basic models, and determining an association operation relation among the plurality of target basic models to obtain the composite index model. Illustratively, the sequence number information, the index specification information corresponding to the composite index field may also be determined in response to a composite index modeling operation for the composite index configuration component.

Specifically, with continued reference to FIG. 7, a composite index configuration component 710 provided by the data platform may include a base index model selection component 720 that may be provided with a plurality of established base index models. The base index model selection component may be provided with a plurality of established base index models in a hierarchical or regional manner based on index attributes. A plurality of target base models may be determined from a plurality of established base index models in response to a selection operation for the base index model selection component. For example, the base metric model selection component 720 may include a base metric model providing component 730 for providing a base metric model and a base metric model association component 740 for determining a plurality of target base models, and the selection operation for the base metric model selection component may refer to a drag-in operation of dragging the base metric model provided by the base metric model providing component into the base metric model association component. Multiple target base models may be quickly determined in response to a drag-in operation.

Illustratively, referring to FIG. 7, the base index model providing component 730 may perform base index models for providing planning classes, purchasing classes, production operations classes under supply chain services according to the service classification in the index attributes. As one example, the base index model providing component may provide a base index model of a production planning class, a plant scheduling class, an inventory planning class, a production inventory class, and a demand planning class under a planning class. For example, basic index models such as "work order number", "prediction number", and "prediction accuracy" of the demand plan class may be provided, and a "material complete set" basic index model of the production stock class may be provided. The "work order number" and "material flush" base index models may be determined as target base models by responding to selection operations of the "work order number" and "material flush" base index models for the base index model association component.

Illustratively, the base index field of the "number of worksheets" target base model may include "mo_num" and the base index field of the "material kit" target base model may include "no_kit". With continued reference to fig. 7, after determining a plurality of target base models, in response to a pulling operation of the providing component and the base index model association component for the base index model in the composite index configuration component, determining that the composite index field corresponding to the "work order number" target base model and the "material alignment" target base model is the "work Shan Jitao rate", and then, in response to the association between the "mo_num" of the "work order number" target base model and the "no_kit" of the "material alignment" target base model, determining the association operation relationship between the "work order number" and the "material alignment" to obtain the composite index model.

In the above embodiment, in the case where the index attribute includes the composite index category, the target base model may be determined from the base index models by responding to the composite index modeling operation, and the composite index model may be obtained by determining the composite index field corresponding to the target base model and determining the association operation relationship for associating the target base model, so that the composite index model may be established by associating at least some of the base index fields of the plurality of base index models.

In some embodiments, referring to fig. 8, in response to a composite index modeling operation for an index configuration component, determining composite index fields based on a target base model in a base index model and determining an associative operational relationship that correlates between the target base models, a composite index model may include the following steps.

Step S810: in response to a composite index modeling operation for the index configuration component, composite index fields are determined based on a plurality of target base models of the base index models.

The number of the composite index fields can be multiple, and the multiple composite index fields can comprise at least one dimension field for classifying and one metric field for quantifying.

In this embodiment, with continued reference to FIG. 7, a composite metrics configuration component 710 provided by the data platform can include a composite dimension field addition component 750 and a composite metrics field addition component 760. In particular, at least one composite indicator field for categorization as a dimension field may be determined in response to a dimension field addition operation for the composite dimension field addition component, and at least one composite indicator field for quantification as a metric field may be determined in response to a metric field addition operation for the composite metric field addition component.

For example, referring still to fig. 7, in response to a metric field addition operation for the composite metric field addition component, it may be determined that one composite metric field is "worker Shan Jitao rate" and that the corresponding sequence number information is "1" and the corresponding metric specification information is null.

Step S820: and configuring the association operation relation among the plurality of target basic models in response to the configuration operation of the index formula configuration component to obtain the composite index model.

In this embodiment, referring to fig. 7, the composite index configuration component 710 provided by the data platform may further include an index formula configuration component 770, which may respectively configure the value operational relationships of any one of the plurality of composite index fields in response to a configuration operation for the index formula configuration component. Specifically, the number of index formula configuration components may be plural, and the plural index formula configuration components may correspond to the plural composite index fields one by one. The associative operational relationship of the corresponding any one of the composite index fields may be determined in response to a configuration operation for any one of the index formula configuration components.

Specifically, the composite metrics configuration component 710 includes a metrics formula configuration component 770 that can provide basic metrics fields for a plurality of target basic models and a plurality of preset functions. The plurality of preset functions may include a string function, a condition function, a date function, a composite function, and the like, wherein the composite function may include at least one of an average function, a count function, a maximum function, a minimum function, and a sum function. Illustratively, the index formula configuration component of the composite index configuration component may provide a base index field as a dimension field and a base index field as a metric field of any target base model.

In particular, with continued reference to FIG. 7, the composite index configuration component 710 provided by the data platform can further include a composite index field refresh component 780. Any composite index field and corresponding sequence number information, index specification information and association operation relation thereof can be refreshed and displayed in response to a refreshing operation aiming at the composite index field refreshing component. For example, the number of the composite index field refreshing components may be plural, and the plural composite index field refreshing components may be in one-to-one correspondence with the plural composite index fields. The corresponding composite index field, the corresponding sequence number information, the index description information and the association operation relation can be refreshed and displayed in response to the refreshing operation of any composite index field refreshing component.

In particular, with continued reference to FIG. 7, the composite index configuration component 710 provided by the data platform can further include a composite index field deletion component 790. Any composite index field and its corresponding sequence number information, index specification information, and associative operational relationship may be deleted in response to a delete operation for the composite index field delete component. For example, the number of the composite index field deletion components may be plural, and the plural composite index field deletion components may be in one-to-one correspondence with the plural composite index fields. The corresponding composite index field, the corresponding sequence number information, the index specification information and the association operation relation can be deleted in response to the deleting operation of any composite index field deleting component.

For example, the association relationship corresponding to the composite indicator field "worker Shan Jitao rate" may be determined to be "(work order number. Mo_num-material alignment. No_kit)/work order number. MO. NUM. 100") in response to a configuration operation for the indicator formula configuration component corresponding to the composite indicator field "worker Shan Jitao rate".

In the above embodiment, by determining one or more composite index fields corresponding to the plurality of target base models in response to the composite index modeling operation for the index configuration component, and configuring the association operational relationship of any one of the one or more composite index fields in response to the configuration operation for the index formula configuration component, respectively, it is possible to configure the composite index model including the one or more composite index fields.

In some implementations, the base index model and the composite index model may be two-dimensional table structures.

In some embodiments, if a monitoring rule configuration operation based on at least a portion of the indicator fields is received, determining a monitoring rule corresponding to the indicator model may include: if a monitoring rule configuration operation based on at least part of the index fields in the index model is received, at least one sub-rule is determined according to at least part of the index fields.

Wherein the monitoring rule may comprise at least one sub-rule. Any of the sub-rules may include query statements, monitoring logic rules, and index thresholds. The query statement may be used to obtain index data corresponding to at least a portion of the index fields from the target database, and the index threshold may be used to compare and determine with the corresponding index data by monitoring the logic rules.

In this embodiment, referring to fig. 9, the data platform may provide a monitoring rule configuration component 910, and the monitoring rule configuration component 910 may include a sub-rule configuration component 920 for configuring sub-rules of the monitoring rule. Specifically, based on the sub-rule configuration component, a query statement may be determined in response to a monitoring rule configuration operation based on at least a portion of the indicator fields, and monitoring logic rules and indicator thresholds corresponding to the query statement are determined, resulting in sub-rules. In particular, in response to a monitoring rule configuration operation for the sub-rule configuration component, the sub-rule name, sub-rule type, and index field data source of at least a portion of the index field of the sub-rule may also be configured. The index field data source may refer to a target data table corresponding to a basic index model to which the at least part of index fields belong, or refer to a target data table corresponding to a basic index model associated with a composite index model to which the at least part of index fields belong. Thus, index data in the target data table corresponding to the index field data source can be obtained through the query statement.

In particular, at least one sub-rule of the monitoring rule may be determined in response to a plurality of monitoring rule configuration operations for the sub-rule configuration component.

Illustratively, with continued reference to FIG. 9, the sub-rule configuration component 920 may include a sub-rule name configuration component 921, a sub-rule type configuration component 922, an index field data source configuration component 923, a query statement configuration component 924, a monitoring logic configuration component 925, and an index threshold configuration component 926. One sub-rule of the monitoring rule may be obtained in response to configuration operations for the sub-rule name configuration component, the sub-rule type configuration component, the index field data source configuration component, the query statement configuration component, the monitoring logic configuration component, and the index threshold configuration component, respectively.

In the above embodiment, by configuring the operation based on the monitoring rule of at least part of the index fields in the index model, the query statement of the sub-rule in the monitoring rule, the monitoring logic rule and the index threshold value can be configured, and the sub-rule name, the sub-rule type and the index field data source of the sub-rule can be configured, so that the sub-rule in the monitoring rule can be configured, that is, the sub-rule can be flexibly configured for any index field or at least part of the index fields in the index model, and the flexibility of monitoring the index data can be improved.

In some embodiments, the index data monitoring method may further include: if a basic information configuration operation aiming at the monitoring rule is received, basic information of the monitoring rule is determined; wherein, the basic information of the monitoring rule at least comprises the name of the monitoring rule and the code of the monitoring rule.

In this embodiment, with continued reference to fig. 9, the monitoring rule configuration component 910 provided by the data platform may further include a rule base information configuration component 930 for configuring base information of the monitoring rule. Specifically, based on the rule base information configuration component, a monitoring rule name and a monitoring rule code may be determined in response to a base information configuration operation for the monitoring rule. Illustratively, the rule base information configuration component may include a rule name configuration component and a rule code configuration component, may configure a monitoring rule name of the monitoring rule in response to a configuration operation for the rule name configuration component, and may configure a monitoring rule code of the monitoring rule in response to a configuration operation for the rule code configuration component. In this way, the basic information of the monitoring rule may be configured such that at least one sub-rule of the monitoring rule may be managed or referenced based on the basic information of the monitoring rule, and flexibility in sub-rule management or referencing of the monitoring rule may be improved.

Illustratively, with continued reference to fig. 9, the monitoring rule name of the monitoring rule may be configured as "device OEE", where device OEE refers to the device integrated efficiency (Overall Equipment Effectiveness), and the monitoring rule of the monitoring rule may be configured as "opm_sboee".

In some embodiments, in response to a data conversion configuration operation based on the monitoring rules and the index model, obtaining a data conversion task may include: in response to a data conversion configuration operation for the data conversion configuration component, a data conversion task corresponding to the metrics model is configured, and at least some of the monitoring rules referenced by the data conversion task are determined.

The data conversion task at least comprises a task name, a task code, a task starting time, a task ending time and a conversion expression; the conversion expression is used for representing the data conversion task to acquire mapping information of corresponding service data from an external service database based on the index model.

In this embodiment, referring to FIG. 10, a data platform can provide a data conversion configuration component 1010, which can include a conversion task underlying information configuration component 1020. Specifically, the task name, task code, task start time, task end time, and conversion expression of the data conversion task may be configured in response to the basic information configuration operation for the conversion task basic information configuration component. For example, the conversion expression may be configured based on the index model such that index data corresponding to the index model may be acquired from service data of the external service database based on the conversion expression.

Specifically, with continued reference to fig. 10, the data conversion configuration component 1010 provided by the data platform may further include a monitoring rule determination component 1030, a sub-rule selection component 1040. The monitoring rules that the data conversion task needs to refer to may be selected from the plurality of monitoring rules that are already configured in response to a monitoring rule determination operation for the monitoring rule determination component. The sub-rule selection operation for the sub-rule selection component may be responded, and at least one sub-rule of the determined monitoring rules to be referred to may be selected, so at least one sub-rule of the monitoring rules referred to by the data conversion task may be configured, so that the index model corresponding index data may be monitored based on the referred at least one sub-rule.

In some embodiments, a data conversion task may be executed, and in the execution process of the data conversion task, execution condition data of the data conversion task is displayed, and index data corresponding to an index model is obtained, where the index data meets an index business attribute in the corresponding index model and corresponds to an index management attribute in the index model. The execution condition data may include at least one of a task name, a corresponding index model, a task execution frequency, and a task execution state of the data conversion task. The task execution frequency may be determined based on a conversion expression of the data conversion task, and the task execution state may include at least a ready state, an execution state, and a suspended state.

In some embodiments, referring to fig. 11, if it is monitored that the index data does not meet at least a portion of the rules, displaying the target to-do event for the data conversion task may include the following steps.

Step S1110: if the index data does not meet at least part of the rules, generating a target to-do event corresponding to at least part of the rules aiming at the index data of the data conversion task; the target to-do event may at least include: abnormal problems of the data conversion task, occurrence time and processing state of the abnormal problems.

In some cases, a data conversion task may be performed to obtain index data corresponding to an index model from service data in an external service database connected to the data platform. The data conversion task references at least some of the monitoring rules. The index data corresponding to the index model obtained based on the data conversion task can be monitored based on at least part of the monitoring rules.

In this embodiment, the index data acquired by the data conversion task may be monitored based on at least some of the monitoring rules, and if it is monitored that the index data does not meet the at least some of the monitoring rules, the abnormal problem corresponding to the at least some of the monitoring rules, the occurrence time and the processing state of the abnormal problem may be generated according to the index data and the corresponding index management attribute of the data conversion task, so as to obtain the corresponding target to-do event.

Step S1120: and displaying the target event to be handled.

In this embodiment, after the target to-do event is determined, the target to-do event may be displayed through the output terminal, so as to prompt the operation and maintenance personnel to maintain the data conversion task based on the target to-do event, so that after the target to-do event is processed, the index data acquired by re-executing the data conversion task can meet the at least partial rule, and thus, the accuracy of the index data can be improved, and the benign operation capability of the index data can be improved.

The embodiment of the specification provides an index data monitoring method, which can be applied to a data platform. The index data monitoring method may include the following steps.

Step S1201: determining an index model in response to an index modeling operation for a target data table in a target database; the index model comprises an index field and a logic operation relation corresponding to the index field.

Specifically, the index attribute may be configured in response to an index registration operation for the index configuration component; wherein the index attribute includes an index category. If the index attribute includes a base index category, a target database is determined in response to a specified operation for the database library name. A target data table is determined from the target database in response to a specified operation for the data table. Determining a basic index field corresponding to the target data table and determining a value operation relation for taking the basic index field from the target data table in response to basic index modeling operation aiming at the index configuration component, so as to obtain a basic index model; wherein the logical operation relationship comprises a value operation relationship; the index model includes a base index model.

Specifically, a plurality of base index fields corresponding to a target data table may be determined in response to a base index modeling operation for an index configuration component; wherein the plurality of base metrics fields includes at least one dimension field for categorizing and one metric field for quantifying. And respectively configuring the value operation relation of any basic index field in the plurality of basic index fields in response to the configuration operation aiming at the index formula configuration component.

Specifically, a composite metric field may be determined based on a plurality of target base models of the base metric models in response to a composite metric modeling operation for the metric configuration component. Configuring an association operation relation among a plurality of target basic models in response to configuration operation aiming at an index formula configuration component to obtain a composite index model; wherein the logical operation relationship comprises an association operation relationship; the index model includes a composite index model.

Step S1203: and if a monitoring rule configuration operation sent based on at least part of the index fields is received, determining the monitoring rule corresponding to the index model.

Step S1205: responding to data conversion configuration operation based on the monitoring rule and the index model, and obtaining a data conversion task; wherein the data conversion task references at least some of the monitoring rules; in the execution process of the data conversion task, corresponding index data is obtained from service data of an external service database based on an index model.

Step S1207: if the index data is monitored to not meet at least part of the rules, displaying a target event to be handled aiming at the data conversion task; after the target to-do event is processed, the index data acquired by the data conversion task is re-executed to meet at least part of rules.

Specifically, if the index data is monitored to not meet at least part of the rules, generating a target to-do event corresponding to at least part of the rules aiming at the index data of the data conversion task; the target to-do event may at least include: abnormal problems of the data conversion task, occurrence time and processing state of the abnormal problems. And displaying the target event to be handled.

Step S1209: and displaying the target to-do event through the output terminal so as to prompt an operation and maintenance personnel to maintain the data conversion task based on the target to-do event.

The embodiment of the specification provides an index data monitoring device. The index data monitoring device can be applied to a data platform. Referring to fig. 12, the index data monitoring device may include an index model configuration module 1210, a monitoring rule configuration module 1220, a data task configuration module 1230, and a monitoring presentation module 1240.

An index model configuration module 1210 for determining an index model in response to an index modeling operation for a target data table in a target database; the index model comprises an index field and a logic operation relation corresponding to the index field;

The monitoring rule configuration module 1220 is configured to determine a monitoring rule corresponding to the indicator model if a monitoring rule configuration operation based on at least a part of the indicator fields is received;

the data task configuration module 1230 is configured to respond to the data conversion configuration operation based on the monitoring rule and the index model, and obtain a data conversion task; wherein the data conversion task references at least some of the monitoring rules; in the execution process of the data conversion task, acquiring corresponding index data from service data of an external service database based on an index model;

a monitoring display module 1240, configured to display a target to-do event for the data conversion task if it is monitored that the index data does not meet at least a portion of the rules; after the target to-do event is processed, the index data acquired by the data conversion task is re-executed to meet at least part of rules.

The specific functions and effects achieved by the index data monitoring device may be explained with reference to other embodiments of the present specification, and will not be described herein. The various modules in the index data monitoring device may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in hardware or independent of a processor in the computer device, or can be stored in a memory in the computer device in a software mode, so that the processor can call and execute the operations corresponding to the modules.

Referring to fig. 13, in some embodiments, a computer apparatus may be provided, including a memory and a processor, where the memory stores a computer program, and the processor implements the index data monitoring method in the foregoing embodiments when executing the computer program.

The present specification also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a computer, causes the computer to perform the index data monitoring method of any of the above embodiments.

The present description also provides a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method for monitoring index data according to any of the above embodiments.

In one embodiment, a computer device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 13. The computer device includes a processor, a memory, and a communication interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program, when executed by a processor, implements an index data monitoring method.

It will be appreciated that the specific examples herein are intended only to assist those skilled in the art in better understanding the embodiments of the present disclosure and are not intended to limit the scope of the present invention.

It should be understood that, in various embodiments of the present disclosure, the sequence number of each process does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present disclosure.

It will be appreciated that the various embodiments described in this specification may be implemented either alone or in combination, and are not limited in this regard.

Unless defined otherwise, all technical and scientific terms used in the embodiments of this specification have the same meaning as commonly understood by one of ordinary skill in the art to which this specification belongs. The terminology used in the description is for the purpose of describing particular embodiments only and is not intended to limit the scope of the description. The term "and/or" as used in this specification includes any and all combinations of one or more of the associated listed items. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It will be appreciated that the processor of the embodiments of the present description may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital signal processor (Digital SignalProcessor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The methods, steps and logic blocks disclosed in the embodiments of the present specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present specification may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in the embodiments of this specification may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash memory, among others. The volatile memory may be Random Access Memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present specification.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system, apparatus and unit may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.

In addition, each functional unit in each embodiment of the present specification may be integrated into one processing unit, each unit may exist alone physically, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present specification may be essentially or portions contributing to the prior art or portions of the technical solutions may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present specification. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.

The foregoing is merely specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope disclosed in the present disclosure, and should be covered by the scope of the present disclosure. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. The index data monitoring method is characterized by being applied to a data platform connected with an external service database, wherein the data platform comprises a target database; the index data monitoring method comprises the following steps:

determining an index model in response to an index modeling operation for a target data table in a target database; wherein, the index model comprises an index field and a logic operation relation corresponding to the index field;

if a monitoring rule configuration operation based on at least part of the index fields is received, determining a monitoring rule corresponding to the index model;

responding to data conversion configuration operation based on the monitoring rule and the index model, and obtaining a data conversion task; wherein the data conversion task references at least some of the monitoring rules; in the execution process of the data conversion task, acquiring corresponding index data from the service data of the external service database based on the index model;

if the index data does not meet the at least partial rule, displaying a target to-do event aiming at the data conversion task; and re-executing the index data acquired by the data conversion task to meet the at least partial rule after the target to-do event is processed.

2. The index data monitoring method of claim 1, wherein the index field comprises a base index field; the determining an index model in response to an index modeling operation for a target data table in a target database, comprising:

configuring an index attribute in response to an index registration operation for an index configuration component; wherein the index attribute comprises an index category;

if the index attribute comprises a basic index category, determining a target database in response to a specified operation aiming at the database name;

determining a target data table from the target database in response to a designation operation for the data table;

determining the basic index field corresponding to the target data table and determining a value operation relation for taking the basic index field from the target data table in response to basic index modeling operation aiming at the index configuration component, so as to obtain a basic index model; wherein the logical operation relationship includes the value operation relationship; the index model includes the base index model.

3. The index data monitoring method according to claim 2, wherein the number of the basic index fields is plural; the determining the basic index field corresponding to the target data table and determining a value operation relation for taking the basic index field from the target data table in response to a basic index modeling operation aiming at the index configuration component comprises the following steps:

Determining a plurality of base index fields corresponding to the target data table in response to a base index modeling operation for the index configuration component; wherein a plurality of the base metrics fields include at least one dimension field for sizing and one metric field for quantification;

and respectively configuring the value operation relation of any one of the basic index fields in response to the configuration operation aiming at the index formula configuration component.

4. The metric data monitoring method of claim 2, wherein the metric field further comprises a composite metric field; the determining an index model in response to an index modeling operation for a target data table in a target database, further comprises:

if the index attribute comprises a composite index category, responding to composite index modeling operation aiming at the index configuration component, determining the composite index field based on a target basic model in the basic index models and determining an association operation relation for associating the target basic models to obtain a composite index model; wherein the logical operation relationship further comprises the association operation relationship; the index model also includes the composite index model.

5. The method of claim 4, wherein the determining the composite index field based on the target base model in the base index models and determining the association relation for associating the target base models in response to the composite index modeling operation for the index configuration component, to obtain the composite index model, includes:

determining the composite index field based on a plurality of the target base models of the base index models in response to a composite index modeling operation for the index configuration component;

and configuring the association operation relation among a plurality of target basic models in response to the configuration operation of the index formula configuration component to obtain the composite index model.

6. The method for monitoring index data according to claim 1, wherein determining the monitoring rule corresponding to the index model if a monitoring rule configuration operation based on at least part of the index fields is received comprises:

if a monitoring rule configuration operation based on at least part of the index fields in the index model is received, determining at least one sub-rule according to at least part of the index fields; wherein the monitoring rule includes the at least one sub-rule; any of the sub-rules includes query statements, monitoring logic rules, and index thresholds; the query statement is used for acquiring index data corresponding to at least part of the index fields from a target database, and the index threshold is used for comparing and judging the index data with the corresponding index data through the monitoring logic rule.

7. The index data monitoring method according to claim 6, characterized in that the index data monitoring method further comprises:

if a basic information configuration operation aiming at the monitoring rule is received, determining basic information of the monitoring rule; the basic information of the monitoring rule at least comprises a monitoring rule name and a monitoring rule code.

8. The method for monitoring index data according to claim 1, wherein the obtaining a data conversion task in response to a data conversion configuration operation based on the monitoring rule and the index model includes:

in response to a data conversion configuration operation for a data conversion configuration component, configuring a data conversion task corresponding to the index model, and determining at least some of the monitoring rules referenced by the data conversion task; the data conversion task at least comprises a task name, a task code, a task starting time, a task ending time and a conversion expression; the conversion expression is used for representing the data conversion task to acquire mapping information of corresponding service data from an external service database based on the index model.

9. The method for monitoring the index data according to claim 1, wherein if the index data is not monitored to meet the at least partial rule, displaying the target to-do event for the data conversion task comprises:

if the index data does not meet the at least partial rule, generating a target to-do event corresponding to the at least partial rule aiming at the index data of the data conversion task; the target to-do event at least comprises: abnormal problems of the data conversion task, occurrence time and processing state of the abnormal problems;

and displaying the target to-be-handled event.

10. The index data monitoring device is characterized by being applied to a data platform connected with an external service database, wherein the data platform comprises a target database; the index data monitoring device comprises:

an index model configuration module for determining an index model in response to an index modeling operation for a target data table in a target database; wherein, the index model comprises an index field and a logic operation relation corresponding to the index field;

The monitoring rule configuration module is used for determining a monitoring rule corresponding to the index model if a monitoring rule configuration operation based on at least part of the index fields is received;

the data task configuration module is used for responding to the data conversion configuration operation based on the monitoring rule and the index model to obtain a data conversion task; wherein the data conversion task references at least some of the monitoring rules; in the execution process of the data conversion task, acquiring corresponding index data from the service data of the external service database based on the index model;

the monitoring display module is used for displaying a target to-do event aiming at the data conversion task if the index data does not meet the at least partial rule; and re-executing the index data acquired by the data conversion task to meet the at least partial rule after the target to-do event is processed.

11. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the index data monitoring method of any one of claims 1 to 9 when executing the computer program.

12. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when executed by a processor, implements the index data monitoring method of any one of claims 1 to 9.