Source
Documentation — ilert
Checked for ilert on 6 Nov 2026
- Page
- https://docs.ilert.com/
- Checked
- 6 Nov 2026, 04:30 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e855693e4c1720709c908909234efa1f00454b18df048ee40806b1f298c7823f
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Overview Report an error
“ilert receives events from your monitoring, ticketing, and other tools, turns them into alerts, and notifies whoever is on call, escalating if that person does not respond.”
-
Quickstart duration Report an error
“It takes you from an empty account to a real notification on your phone in about 10 minutes.”
-
Inbound count Report an error
“ilert has more than 150 inbound integrations.”
-
Events API email Report an error
“If your tool is not listed in the inbound integrations, it can still reach ilert through the Events API or by email.”
-
Deployment tools Report an error
“To see what changed before an alert, connect your CI/CD tooling as well: GitHub, GitLab, or Argo CD. These send deployment events, not alerts.”
-
Example tools Report an error
“Infrastructure monitoring Prometheus, Amazon CloudWatch, Datadog”
-
Alert states Report an error
“PENDING Nobody has accepted the alert yet.”
-
Notification channels Report an error
“A notification is one message to one user over one channel: push, SMS, phone call, WhatsApp, Telegram, or email.”
-
On call schedule rule Report an error
“Only one user per schedule is on call at a time.”
-
Status pages visibility Report an error
“It can be public or private.”
-
Actions outbound Report an error
“An action runs work when an alert or incident changes, or when someone starts it: it opens a Jira issue, calls a webhook, or sends an email. Actions are also called outbound integrations.”
-
Connectors Report an error
“A connector stores how ilert reaches the target system: its URL and its credentials. Create it once, and reuse it in as many actions or alert actions as you need.”
-
Deployment events Report an error
“A deployment event is a report from your CI/CD tooling of what it shipped. ilert matches these reports to alerts, so a responder sees what changed before the alert.”
-
Developers resources Report an error
“Developers: the REST API reference, client libraries, the Terraform provider, and building ilert apps.”
9 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Engineering Manager Integrations, API & administration
- The ICT Risk Officer Alert delivery, routing & noise reduction
- The ICT Risk Officer Integrations, API & administration
- The IT Operations Manager Integrations, API & administration
- The MSP NOC Lead Alert delivery, routing & noise reduction
- The MSP NOC Lead Integrations, API & administration
- The Skeptic Integrations, API & administration