Source
Alert delivery, routing & noise reduction — found from sitemap — ilert
Checked for ilert on 6 Nov 2026
- Page
- https://docs.ilert.com/alerting/configure-alerting/event-flows
- Checked
- 6 Nov 2026, 04:34 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:137ebc3b0c3895a37e871145bc38fdd895830ac0bbf113f0a7c387ca300b3433
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Event flows definition Report an error
“A routing layer in front of your alert sources: branch on the payload, wait for business hours, rewrite the event, and send it to the source that suits it.”
-
Event flows plan requirement Report an error
“Event flows require the Scale plan or higher, and are in beta.”
-
Event flow nodes Report an error
“Branch Sends the event down the first branch whose conditions match one per branch you add, up to 8, plus Else.”
-
Branch limit Report an error
“one per branch you add, up to 8, plus Else. The editor lets you add more, but ilert rejects the node when you save”
-
Route override Report an error
“Sends the event to an alert source, optionally overriding its escalation policy or notification priority”
-
Wait duration range Report an error
“Duration — hold for a number of seconds, minutes, hours or days, from 10 seconds up to 14 days.”
-
Wait alert key grouping Report an error
“An accept or resolve event ends the wait. When an ACCEPT or RESOLVE event with the same alert key reaches a Wait node in the same flow, the waiting event ends, and so does the accept or resolve event.”
-
Wait account limit Report an error
“If more than 1,000 events in your account are waiting at the same time, further events end at the Wait node instead of being routed, and the log gives the end reason LIMITED.”
-
Transform capabilities Report an error
“Rewrites the event before the next node runs: set a value, copy one field into another, map values onto new ones, compose text from a template, merge properties, or append to a list.”
-
Flow node limit Report an error
“A flow can hold up to 300 nodes, nested up to 75 levels deep.”
-
Terraform export Report an error
“Export to Terraform, in the header of a saved flow, produces the flow as Terraform configuration”
-
Incoming event keys Report an error
“ilert creates an integration key for each one as soon as you pick it. Point your tool at that key instead of at an alert source's”
-
API endpoint Report an error
“for the API integration, the endpoint stays https://api.ilert.com/api/events and only the key changes”
-
Branch conditions icl Report an error
“The code editor takes ICL directly.”
-
No dry run Report an error
“There is no dry-run mode. Send test events to the flow's integration key and read the event flow logs.”
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 SRE Lead Alert delivery, routing & noise reduction
- The SRE Lead Integrations, API & administration