Source
Alert delivery, routing & noise reduction — found from sitemap — Spike.sh
Checked for Spike.sh on 6 Nov 2026
- Page
- https://docs.spike.sh/alerts/alert-rules
- Checked
- 6 Nov 2026, 04:48 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:da2d1afe42e245bf5ed166b92208307047f022233854326f2972db0615bda46b
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Routing rules description Report an error
“Alert routing rules apply automated actions to every incoming incident based on conditions you define with AND/OR logic.”
-
Rule templates Report an error
“Not sure where to start? Spike offers alert routing rule templates with pre-built configurations.”
-
Conditions Report an error
“Apply to all incidents Incident title Incident details Incident has repeated Incident has repeated within Incident suppressed Incident suppressed within Priority Severity Time of day Days of week”
-
Actions Report an error
“Reassign incident to Load escalation policy Change integration Ignore incident Mark priority as Mark severity as Trigger outbound webhook Acknowledge incident Resolve incident Resolve by Timer Route to other team”
-
Ignore incident Report an error
“Ignore incident Prevents the incident from being created. No alerts are sent and the incident doesn't appear on the dashboard.”
-
Outbound webhook action Report an error
“Trigger outbound webhook Sends a webhook to a URL you specify when the conditions are met.”
-
Resolve by timer action Report an error
“Resolve by Timer Automatically resolves the incident after a set duration.”
-
Route to other team Report an error
“Enable the Route to other team toggle in the Actions section to send an incident from one team to another. Select the source team, destination team, and destination integration.”
-
Multiple rulesets limit Report an error
“No more than 5 alert routing rulesets apply to a single incident.”
-
Acknowledge action Report an error
“Acknowledge incident Creates the incident in the acknowledged state. No alerts are sent, but the incident appears as open on the dashboard.”
-
Change integration example Report an error
“For example, an incident arrives under the API integration. If the title contains "payments", Spike moves it to the Payments integration and alerts the payments team instead.”
Scores citing this record
- The Engineering Manager Alert delivery, routing & noise reduction
- The ICT Risk Officer Alert delivery, routing & noise reduction
- The IT Operations Manager Alert delivery, routing & noise reduction
- The MSP NOC Lead Alert delivery, routing & noise reduction
- The Skeptic Alert delivery, routing & noise reduction
- The Skeptic Incident response, status pages & post-incident review
- The SRE Lead Alert delivery, routing & noise reduction