DataFinder presets common data warehousing verification rules for you. When the event warehousing does not meet the verification rules, the corresponding event will be intercepted. At the same time, DataFinder also supports you to customize data verification rules according to business needs. This article introduces the configuration points for creating custom verification rules.
Configuration basic information.
Parameter | Configuration instructions |
|---|---|
rule name | Custom rule name for subsequent identification of custom validation rules. |
rule type | Currently supports event quantity, event attribute validation, user attribute validation three types of rules.
|
Validation Object & Validation Rules | Select the validation object according to the interface prompts and configure the validation rules. The validation rules of the event attribute need to specify the event before selecting the event attribute. Details of event and attribute validation rules can be found in the following Reference: Validation rule descriptionsections.
|
Configure alarm settings.
You can choose whether to turn on the monitoring alarm of the verification rule as needed. After opening, when the subsequent data is put into storage, if the abnormal data that does not meet the verification rule reaches a certain amount, an alarm message will be triggered according to the alarm rule.
tip
Event property/user property rules need to be configured, event volume rules do not need to be configured.
After the custom verification rule is created, you can view the list of custom verification rules on the verification rule page, and support operations such as opening and closing the verification rule.
warning
Event volume verification is used to monitor the amount of reported data for a specific event tracking, and to trigger an alarm when the amount of event reports is greater than or less than a certain number within a specific time range.
For example, an alarm will be raised when the order payment event exceeds 10,000 within 5 minutes.
The time interval for verification can be divided into minutes, hours, and natural days, with a minimum interval of 10 minutes.
Event/User Properties The following validation rules can be selected on demand according to the interface prompt.
Rule type | Rule description | Supported attribute data types |
|---|---|---|
mandatory verification | Indicates that the property is a required field, and that the property is not uploaded (missing key) or null (missing value) is an exception. | All types |
enumeration validation | You can enter all enumeration values for this property, or an exception if the value reported by the property is not in the enumeration value configured by the rule. Attribute not uploaded or null is not within the scope of the exception. | STRING、INT |
Regular Match Check | You can enter a regular expression that the property value should match, or an exception if it does not match. Attribute not uploaded or null is not within the scope of the exception. | STRING |
interval check | A field of a numeric type can define a range of values for the property. If the value reported by the property is not within this range, it is an exception. Attribute not uploaded or null is not within the scope of the exception. | INT,float |
include validation | The property value contains a check for a specific value, or an exception if the reported property value does not contain the specific value set. Attribute not uploaded or null is not within the scope of the exception. | STRING |
Verification rules are used to control data quality and ensure that the content of data reports after event tracking is online continues to meet the design specifications.
For example, if the value of the "whether or not a member" attribute must be passed, and the reported content must be 0 or 1, then the data that has not been reported as "whether or not a member" attribute or the reported content is incorrect can be intercepted and alerted through rule verification, and the researchers will be notified to correct it in time.
The data verification alarm is a monitoring alarm for the original reported data, which can only monitor the quality of the data and cannot monitor the indicators (for example: click through rate).
Kanban monitoring is the monitoring and alerting of the data built into the warehouse (ie: the data intercepted after processing), which is suitable for business indicator monitoring.