Email Digest
The Email Digest section displays all digests associated with your account or shared with you. When you set up a digest for an account, you will receive an email at your specified time, summarizing key activities. These digests act as alerts, providing updates and information about the quality of the data. You can receive daily or weekly updates regarding the data quality, which will be included in the overall summary sent via email.
Creating a New Email Digest
-
Access the Email Digest Page: Go to the page that lists all your existing email digests, including those created from your account or shared with you.
-
Initiate Digest Creation: Click on “Create a new digest” located at the top right corner of the page (OR) if you have not created any, click on “Create a new digest” in the middle of the page.
-
Fill Out Digest Details:
-
Email Digest Name: Enter a name for your new digest.
-
Schedule Type: Choose how often the digest will be sent (e.g., daily, weekly).
-
Time: Specify the time of day for the digest to be sent.
-
Select the Account: Choose the account for which this digest will be created.
-
Select the Report: Choose the specific report under the selected account.
-
Apply to Future Reports: Check this option if you want the digest to apply to all future reports under the selected account.
-
Recipients: Enter the email addresses of the recipients who should receive the digest.
-
-
Finalize Creation:
-
Click Create to save and activate the digest.
-
Click Discard if you wish to cancel and not create the digest.
-
Alert Categories
| Category | Description |
|---|---|
| Data Alerts | Triggered when the current data count or fill rate increases or decreases by more than 10% compared to the average historical count or fill rate. |
| Failed Runs | Triggered when a report run fails or when the run status shows as successful but the record count is 0. |
| Missed Runs | Triggered when a scheduled run does not start before the next scheduled run time, indicating the expected run was missed. |
| Long Running Crawlers | Triggered when a crawler takes significantly longer than expected to complete, exceeding its average run time. |
| Data Validation | Triggered when a QA rule configured for the selected report fails. |
| Failed Tasks | Triggered when any child task within a report run fails to execute successfully. |
| Crawler Anomalies | Triggered when issues are detected in the crawling process, indicating abnormal crawler behavior or operational problems. |
| Profiler Anomalies | Triggered when inconsistencies, incomplete records, incorrect values or unexpected data patterns are detected during profiling. |
Sections of the Email Digest
- My Daily Digest: This section displays all email digests that you have created personally. It includes digests specifically configured for your individual use.
- Shared Daily Digest: This section shows email digests that have been shared with you by others. These digests are accessible to you but were not created by your account.
Additional details
- If a child task fails during a report run, it will appear in the Failed Tasks section of the email digest, allowing you to quickly identify and address the issue.
Long Running Crawlers
A Long Running Crawler alert is triggered when a crawler takes significantly longer than its average runtime. Instead of using the same threshold for every crawler, the platform uses different thresholds based on how long the crawler usually takes to complete.
The excess crawl time is calculated as:
Excess Crawl Time = Current Runtime − Average Crawl Time
If the excess crawl time exceeds the applicable threshold, the crawler is considered long running, and an alert is generated.
| Average Crawl Time | Excess Crawl Time | Example | What It Means |
|---|---|---|---|
| 2 hours or less | More than 4 hours | Average: 1 hour; Excess: 5 hours; Total runtime: 6 hours | The crawler usually finishes in 1 hour, but this run has taken 6 hours. Since it has run 5 hours longer than usual, it has exceeded the allowed extra time of 4 hours. |
| More than 2 hours and up to 12 hours | More than 8 hours | Average: 6 hours; Excess: 9 hours; Total runtime: 15 hours | The crawler usually finishes in 6 hours, but this run has taken 15 hours. Since it has run 9 hours longer than usual, it has exceeded the allowed extra time of 8 hours. |
| More than 12 hours and up to 48 hours | More than 12 hours | Average: 24 hours; Excess: 13 hours; Total runtime: 37 hours | The crawler usually finishes in 24 hours, but this run has taken 37 hours. Since it has run 13 hours longer than usual, it has exceeded the allowed extra time of 12 hours. |
| More than 48 hours | More than 24 hours | Average: 60 hours; Excess: 25 hours; Total runtime: 85 hours | The crawler usually finishes in 60 hours, but this run has taken 85 hours. Since it has run 25 hours longer than usual, it has exceeded the allowed extra time of 24 hours. |
Note
- The examples above are illustrative. The platform compares how long the crawler has been running with how long it usually takes to finish. If it has been running longer than the allowed threshold for its bucket, a Long Running Crawler alert is triggered.