Welcome to ilert
Get started with ilert - the complete incident management platform for reliable alerting, on-call management, and status pages.
ilert is a complete incident management platform that provides reliable alerting, on-call management, and status pages to help DevOps teams, SREs, and IT administrators respond to incidents faster and more effectively.
Quick start (5 minutes)
Sign up at app.ilert.com
Create your first alert source - connect your monitoring tool
Set up an escalation policy - define who gets notified
Configure notifications - choose your preferred channels
Test the integration - send a test alert
Key features
Reliable Alerting: Never miss critical incidents with SMS, phone calls, push notifications, Slack, Teams, and more
On-Call Management: Automated escalations, schedules, and coverage requests to ensure the right person is always notified
Mobile App: Full incident response capabilities on iOS and Android for on-the-go incident management
Status Pages: Communicate incidents to stakeholders and customers with professional status pages
100+ Integrations: Connect with your existing monitoring, ticketing, and collaboration tools
AI-First: Smart alert grouping, automated root cause analysis and post mortem creation to reduce noise and improve response times
Documentation Sections
Quick setup guides and FAQs
Configure alert sources and reliable notifications
Set up schedules and escalation policies
Connect your tools and workflows
Communicate incidents to stakeholders
iOS and Android app documentation
REST API and client libraries
Popular Use Cases
Infrastructure Monitoring: Connect Prometheus, CloudWatch, or Datadog for reliable infrastructure alerting
Application Monitoring: Integrate with Sentry, New Relic, or AppDynamics for application incident management
Uptime Monitoring: Use Pingdom, UptimeRobot, or StatusCake for website and service monitoring
Security Alerts: Connect AWS GuardDuty, Azure Sentinel, or CrowdStrike for security incident response
CI/CD Pipelines: Monitor deployments with GitHub, GitLab, or ArgoCD for deployment incident management
Core Concepts
The most important concepts are explained in the following sections.
Alert
An alert is an event that requires immediate attention and needs to be resolved. Alerts are created by an alert source and immediately trigger the notification process using the alert source's escalation policy to ensure reliable incident response.
An alert can have the following states:
PENDING
The alert hasn't been acknowledged yet and will escalate until the alert is either acknowledged or resolved.
ACCEPTED
The user to whom the alert is assigned to is working on resolving the alert and the escalation process is halted.
RESOLVED
The alert is resolved and no more notifications are sent. A resolved alert cannot be opened again.
Alert source (aka inbound integration)
An alert source represents the connection between your tools (usually a monitoring system, a ticketing tool, or an application) and ilert. We often refer to alert sources as inbound integrations.
Deployment events
The deployment events view gives you a live overview of all deployments related to your account. If a deployment event can be correlated to an alert, ilert will enrich your alert's context with the most relevant deployment information to improve incident response.
Connector and alert action (aka outbound integration)
Connectors and alert actions allow you to extend your incident response and communication to other tools. They allow you to either manually or automatically perform actions on alerts, such as
Update your ilert status page
Create a ticket in JIRA
Post a message in Slack
Post a webhook to a defined HTTP end point
A connector is created globally in ilert and contains all the information to connect with the target system (e.g. a URL, an API key or username and password, etc.). An alert action can be created at the team-level and assigned to alert sources. An alert action uses its connector to perform a concrete action. Example: Let's say we want to create an issue in JIRA for every alert in ilert. We need to create ...
... a JIRA connector that contains the URL of the JIRA server and the credentials to connect to it.
... an alert action that contains information such as whether to trigger the connection manually or automatically for every alert, the JIRA project ID and issue type, and any custom fields that we might want to set in the JIRA issue.
We often refer to connectors and alert actions as outbound integrations.
Escalation policy
An escalation policy connects an alert source with the users that are responsible for this alert source. It defines which users or on-call schedules should be notified when an alert is created to ensure reliable incident response.
On-call schedule
On-call schedules determine who will be notified when an alert is created based on the time of day. Only one user per schedule can be on-call at a time. You can reference an on-call schedule in an escalation policy.
Incident, Status update, Service and Status page
An incident is the coordination record for a significant event. Declare an incident to link alerts, page responders, track a timeline, and run the response to resolution.
A status update is the public-facing message you post from an incident. Status updates appear on your status pages and are also delivered directly to subscribed ilert users—such as those with the VIEWER role—based on their service and status page subscriptions.
Services model the business capabilities your users care about. Incidents and status updates reference services, and users can subscribe to them to receive notifications.
Status pages help you inform users about the current status of your services and the history of recent status updates. Any ilert user can subscribe to status updates, services, and status pages.
The incident coordination features are available for ilert accounts created after May 18, 2026, and are rolling out to existing accounts over the coming weeks and months. To opt in sooner, contact support@ilert.com.
Notification
A notification is a message that is sent to a user to inform them about alerts, incidents or on-call shifts. Users manage how they want to be notified in their notification settings to ensure reliable incident response.
Last updated
Was this helpful?
