-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #473 from Qualytics/qua-156-update-volumetric-chec…
…k-user-guide-to-reflect-the-latest-release Qua156: Update "Volumetric Check" userguide
- Loading branch information
Showing
35 changed files
with
181 additions
and
11 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,32 +1,202 @@ | ||
# Volumetrics Check | ||
# Volumetric Check | ||
|
||
The Volumetric Check has been introduced to help users monitor and maintain the stability of data volumes across various datasets. This feature ensures that the size or volume of your data (either in terms of rows or bytes) remains within an acceptable range based on historical trends. It is designed to detect significant fluctuations by comparing the current data volume against a moving daily average. | ||
Volumetric Check ensures data stability by monitoring dataset size fluctuations in rows or bytes. It detects anomalies by comparing current volumes against historical trends (daily, weekly, monthly). Users can configure rules for precise control, while automated threshold adjustments enhance accuracy over time. | ||
|
||
Let's get started 🚀 | ||
|
||
## Configure Volumetric Check | ||
|
||
**Step 1:** Login into your Qualytics account and select the **datastore** from the left menu on which you want to add a volumetric check. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/datastore-light-1.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/datastore-dark-1.png#only-dark) | ||
|
||
**Step 2:** Click the **Add** button and select **Checks**. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/check-light-2.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/check-dark-2.png#only-dark) | ||
|
||
**Step 3:** A modal window appears. Enter the required details to configure the **Volumetric Check.** | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/modal-light-3.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/modal-dark-3.png#only-dark) | ||
|
||
**Step 4:** Enter the details to configure the volumetric check**:** | ||
|
||
| No. | Field | Description | | ||
| :---- | :---- | :---- | | ||
| **1.** | Rule Type | Select the Volumetric Rule type from the dropdown. | | ||
| **2.** | Table | Select the table for the rule to apply. | | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/name-light-4.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/name-dark-4.png#only-dark) | ||
|
||
**3. Comparison:** Specifies the type of comparison: Absolute Change, Absolute Value, or Percentage Change: | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/comparision-light-5.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/comparision-dark-5.png#only-dark) | ||
|
||
!!! note "Details" | ||
### Comparison Options | ||
|
||
**Absolute Value** | ||
|
||
The `Absolute Value` comparison works by comparing the change in a numeric field's value to a pre-set limit `between` Min and Max values. If the field's value changes by more than this specified range since the last relevant scan, an anomaly is identified. | ||
|
||
??? example "Illustration" | ||
_The value of the record in each scan should be within 100 and 300 to be considered normal_ | ||
|
||
**Thresholds**: Min Value = 100, Max Value = 300 | ||
|
||
| Scan | Current Value | Anomaly Detected | | ||
|------|---------------|------------------| | ||
| #1 | 150 | No | | ||
| #2 | <div class="text-negative">90</div> | <div class="text-negative">Yes</div> | | ||
| #3 | 250 | No | | ||
| #4 | <div class="text-negative">310</div> | <div class="text-negative">Yes</div> | | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/absolute-light-6.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/absolute-dark-6.png#only-dark) | ||
|
||
!!! note "Details" | ||
### Comparison Options | ||
|
||
**Absolute Change** | ||
|
||
The `Absolute Change` comparison works by comparing the change in a numeric field's value to a pre-set limit (Min / Max). If the field's value changes by more than this specified limit since the last relevant scan, an anomaly is identified. | ||
|
||
??? example "Illustration" | ||
_Any record with a value change smaller than 30 or greater than 70 compared to the last scan should be flagged as anomalous_ | ||
**Thresholds**: Min Change = 30, Max Change = 70 | ||
|
||
| Scan | Previous Value | Current Value | Absolute Change | Anomaly Detected | | ||
|------|----------------|---------------|-----------------|------------------| | ||
| #1 | - | 100 | - | No | | ||
| #2 | 100 | 150 | 50 | No | | ||
| #3 | 150 | 220 | 70 | No | | ||
| #4 | 220 | <div class="text-negative">300</div> | <div class="text-negative">80</div> | <div class="text-negative">Yes</div> | | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/change-light-7.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/change-dark-7.png#only-dark) | ||
|
||
!!! note "Details" | ||
### Comparison Options | ||
|
||
** Percentage Change** | ||
|
||
The `Percentage Change` comparison operates by tracking changes in a numeric field's value relative to its previous value. If the change exceeds the predefined percentage (%) limit since the last relevant scan, an anomaly is generated. | ||
|
||
??? example "Illustration" | ||
_An anomaly is identified if the record's value decreases by more than 20% or increases by more than 50% compared to the last scan._ | ||
|
||
**Thresholds**: Min Percentage Change = -20%, Max Percentage Change = 50% | ||
|
||
**Percentage Change Formula**: ( (current_value - previous_value) / previous_value ) * 100 | ||
|
||
| Scan | Previous Value | Current Value | Percentage Change | Anomaly Detected | | ||
|------|----------------|---------------|-----------------------------|------------------| | ||
| 1 | - | 100 | - | No | | ||
| 2 | 100 | 150 | 50% | No | | ||
| 3 | 150 | 120 | -20% | No | | ||
| 4 | 120 | 65 | <div class="text-negative">-45.83%</div> | <div class="text-negative">Yes</div> | | ||
| 5 | 65 | 110 | <div class="text-negative">69.23%</div> | <div class="text-negative">Yes</div> | | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/percentage-light-8.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/percentage-dark-8.png#only-dark) | ||
|
||
**4. Measurement Period Days:** Enter the number of days for measurement. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/measurement-light-9.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/measurement-dark-9.png#only-dark) | ||
|
||
**5. Threshold:** At least the Min or Max value must be specified, and including both is optional. These values determine the acceptable range or limit of change in the field's value. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/threshold-light-10.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/threshold-dark-10.png#only-dark) | ||
|
||
**Min Value** | ||
|
||
* Represents the minimum allowable increase in the field's value. | ||
|
||
* A negative Min Value signifies an allowable decrease, determining the minimum value the field can drop to be considered valid. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/min-light-11.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/min-dark-11.png#only-dark) | ||
|
||
**Max Value** | ||
|
||
* Indicates the maximum allowable increase in the field’s value, setting an upper limit for the value's acceptable growth or change. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/max-light-12.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/max-dark-12.png#only-dark) | ||
|
||
| No. | Field | Description | | ||
| :---- | :---- | :---- | | ||
| **6.** | **Description** | Enter a description for the check. | | ||
| **7.** | **Tag** | Add tags for categorizing the check. | | ||
| **8.** | **Additional Metadata** | Add custom metadata for additional details. | | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/last-light-13.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/last-dark-13.png#only-dark) | ||
|
||
**Step 4:** After completing all the check details, click on the "Validate" button. This will perform a validation operation on the check without saving it. The validation allows you to verify that the logic and parameters defined for the check are correct. It ensures that the check will work as expected by running it against the data without committing any changes. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/validate-light-14.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/validate-dark-14.png#only-dark) | ||
|
||
If the validation is successful, a green message will appear saying "Validation Successful". | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/msg-light-15.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/msg-dark-15.png#only-dark) | ||
|
||
**Step 5:** Once you have a successful validation, click the **"Save"** button. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/save-light-16.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/save-dark-16.png#only-dark) | ||
|
||
After clicking on the **“Save”** button your check is successfully created and a success flash message will appear saying **“Check successfully created”.** | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/success-light-17.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/success-dark-17.png#only-dark) | ||
|
||
### How It Works | ||
|
||
The system automatically infers and maintains volumetric checks based upon observed daily, weekly, and monthly averages. These checks enable proactive management of data volume trends, ensuring that any unexpected deviations are identified as anomalies for review. | ||
The system automatically infers and maintains volumetric checks based upon observed daily, weekly, and monthly averages. These checks enable proactive management of data volume trends, ensuring that any unexpected deviations are identified as anomalies for review. | ||
|
||
### Automating Adaptive Volumetric Checks | ||
|
||
The following Volumetric Checks are automatically inferred for data assets with automated volume measurements enabled: | ||
|
||
* **Daily**: the expected daily volume expressed as an absolute minimum and maximum threshold. The thresholds are calculated as standard deviations from the previous 7-day moving average. | ||
* **Daily**: the expected daily volume expressed as an absolute minimum and maximum threshold. The thresholds are calculated as standard deviations from the previous 7-day moving average. | ||
|
||
* **Weekly**: the expected weekly volume expressed as an absolute minimum and maximum threshold. The thresholds are calculated as standard deviations from the previous four weeks’ weekly volume moving average. | ||
* **Weekly**: the expected weekly volume expressed as an absolute minimum and maximum threshold. The thresholds are calculated as standard deviations from the previous four weeks’ weekly volume moving average. | ||
|
||
* **Monthly**: the expected 4-week volume expressed as an absolute minimum and maximum threshold. The thresholds are calculated as standard deviations from the previous sixteen weeks’ 4-week volume moving average. | ||
* **Monthly**: the expected 4-week volume expressed as an absolute minimum and maximum threshold. The thresholds are calculated as standard deviations from the previous sixteen weeks’ 4-week volume moving average. | ||
|
||
#### Scan Assertion and Anomaly Creation | ||
|
||
Volumetric Checks are asserted during a [Scan Operation](../source-datastore/scan.md) just like all other check types and enrichment of volumetric check anomalies is fully supported. This enables full support for custom scheduling of volumetric checks and remediation workflows of volumetric anomalies. | ||
Volumetric Checks are asserted during a [Scan Operation](https://userguide.qualytics.io/source-datastore/scan/) just like all other check types and enrichment of volumetric check anomalies is fully supported. This enables full support for custom scheduling of volumetric checks and remediation workflows of volumetric anomalies. | ||
|
||
## Adaptive Thresholds and Manual Adjustments | ||
|
||
Each time data volume is measured for an asset, the system automatically updates the inferred Volumetric Checks. | ||
|
||
**1.Automatic Threshold Adjustment:** | ||
|
||
* The system sets initial thresholds at **2 standard deviations** from the moving average. | ||
|
||
* Over time, these thresholds adjust automatically using **historical data trends** to improve accuracy. | ||
|
||
**2.Continuous Learning:** | ||
|
||
### Adaptive Thresholds and Human Adjustments | ||
* The system **monitors past data** and **adapts thresholds** to detect unusual data volume changes. | ||
|
||
Each time a volume measurement is recorded for a data asset, the system will automatically infer and update any inferred Volumetric Checks for that asset. | ||
**3.Why It Matters:** | ||
|
||
By default, thresholds are set to 2 standard deviations from the moving average, but the system will adapt over time using inference weights to fine-tune these thresholds based on historical trends. | ||
* Helps maintain **data integrity** by identifying unexpected volume changes. | ||
|
||
This feature is essential for maintaining data integrity and ensuring that any deviations from expected data volumes are quickly identified and addressed. | ||
* Ensures quick detection and response to potential data issues. | ||
|
||
![volumetric-check](../assets/checks/volumetric-check/volumetric-check-light.png#only-light) | ||
![volumetric-check](../assets/checks/volumetric-check/volumetric-check-dark.png#only-dark) |