Skip to content

Conversation

@DianaIgnatescu
Copy link
Contributor

No description provided.

@netlify
Copy link

netlify bot commented Sep 18, 2025

Deploy Preview for snowplow-docs ready!

Name Link
🔨 Latest commit bcb07fd
🔍 Latest deploy log https://app.netlify.com/projects/snowplow-docs/deploys/690b741a2511e00008e34521
😎 Deploy Preview https://deploy-preview-1414--snowplow-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 18 (🟢 up 1 from production)
Accessibility: 91 (no change from production)
Best Practices: 100 (no change from production)
SEO: 95 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@DianaIgnatescu DianaIgnatescu added the do not merge Flag to denote a Issue or PR which should not yet be merged (usually pending a release) label Sep 18, 2025
Copy link
Contributor

@gibbok-snowplow gibbok-snowplow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR, few suggestions:

  • rename the image with full name, so instead of dq please consider data_quality, this is better for SEO
  • I would add few uses cases describing the value

Copy link
Contributor

@jborlase-snowplow jborlase-snowplow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nitpick, but otherwise I think it looks good

Choose from the available trigger options:

- **When above value**: Set an absolute threshold for failed events (e.g., 1,500 failed events per hour)
- **On any issue**: Alert immediately when any failed events are detected
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Immediately" makes it sound like it overrides the delivery window - we could remove it.


![Value threshold configuration with insights panel](images/data_quality_absolute_threshold.png)

#### Insights from historical data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A sligly modified version here, up to you if you would like to use it:


#### Insights from recent data



When you configure a threshold alert, the Insights panel displays data from the last 7 days to help you choose an appropriate threshold:



- **Average event volume** – Shows the average counts of valid and failed events (per relevant time unit).  

- **Suggested threshold** – Provides a recommended value based on recent patterns.  

- **Apply suggestion** – Click to insert the suggested value into the threshold field.  



Use these insights to set realistic thresholds that reflect your actual event patterns.



**Alert delivery:** If the trigger condition is met, the alert is sent at most once per delivery interval you selected.

@DianaIgnatescu DianaIgnatescu force-pushed the feature/DPS-1424-absolute-thresholds-for-alerts branch from 1829976 to bcb07fd Compare November 5, 2025 15:58
@DianaIgnatescu DianaIgnatescu removed the do not merge Flag to denote a Issue or PR which should not yet be merged (usually pending a release) label Nov 6, 2025
@DianaIgnatescu DianaIgnatescu merged commit a74787f into main Nov 6, 2025
4 checks passed
@DianaIgnatescu DianaIgnatescu deleted the feature/DPS-1424-absolute-thresholds-for-alerts branch November 6, 2025 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants