Source
Alerting, integrations & developer workflow — found from sitemap — TrackJS
Checked for TrackJS on 17 Nov 2026
- Page
- https://docs.trackjs.com/notifications/
- Checked
- 17 Nov 2026, 13:03 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:047bae449265fcb5e826eda9f36d26e6c9beb574c6c9915cf6c0bda346203c13
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Notification channels Report an error
“We currently support Email, Slack and Microsoft Teams.”
-
Notification config per application Report an error
“Both the type of Notifications and Channels are configurable per application.”
-
Daily summaries Report an error
“Sent daily at a configurable time via email. This notification contains error rate, error delta, top errors for various categories and other information. It’s a rollup view of the previous 24 hours. It can only be sent to email channels.”
-
New errors notification Report an error
“Sent when TrackJS records a never-before-seen error message in your account. You may also customize this, and have it only alert if more than one user is affected.”
-
Trending errors notification Report an error
“The Trending Notification will be sent if an error gains more than 10 places or if a new error is in the top 10 most common errors on your site. In order to keep noise to a minimum, we require an error to be seen a minimum of 10 times before an alert is sent.”
-
Error rate increase notification Report an error
“Sent when the overall error rate for an application increases 20% above the previous high. We look back several days to ensure it’s not just a cyclical traffic increase.”
-
Saved filter notifications Report an error
“In addition to the options above, it’s also possible to make custom notifications using saved filters.”
-
Notification threshold config Report an error
“The Lookback Period is how large of a time window to use when considering a filter’s error volume. The Error Threshold is the minimum number of errors that must occur during the lookback period before an alert is sent.”
-
Notification strategies Report an error
“We use four different strategies when determining whether to alert. Each strategy will decide to trigger or not based on the filter’s error volume over time. Two of the strategies must be triggered in order for a notification to be sent”
-
Notification strategy names Report an error
“Simple Historical Average: This simple strategy compares the filter’s historical average error volume to the lookback period’s current volume and, if the current volume exceeds a multiple, triggers.”
-
Ml detection confidence Report an error
“If the confidence is over 99.9% the strategy triggers.”
Scores citing this record
- The Agency Tech Lead Alerting, integrations & developer workflow
- The Data Protection Officer Alerting, integrations & developer workflow
- The Mobile Team Lead Alerting, integrations & developer workflow
- The SaaS CTO Alerting, integrations & developer workflow
- The Skeptic Alerting, integrations & developer workflow
- The Site Reliability Engineer Alerting, integrations & developer workflow