New Notification Reports
Connectors and Connections are now available via API
New Go Client with full API support
New Terraform Provider with full API support
New: Jira Inbound Integration
New: Server Density Inbound Integration
Updated Email integration: email deduplication now also works for email threads
Updated Pingdom integration: incidents created by Pingdom now include a backlink to Pingdom
Added new Responder role
On-call duty notifications
Call routing: added mailbox transcription to incident details and made voicemail links easier accessible in the incident links section
Support for outbound connections in Call Routing Numbers
Support Hours for Call Routing Numbers
Datadog Outbound Integration now supports regions
Prometheus incident detail formatting has been updated
Slack channels (connections) can now be managed in iLert directly
Ability to select incident events in outbound integrations. Example: trigger webhooks for incident creation and resolution events, but ignore remaining incident event types.
Every call routing number is now referenced to an alert source, helping you connect incoming calls to e.g. Slack. You can now also manage support hours for your call routing number.
Optimized bulk incident actions like accept and resolve
Uptime monitor TCP and UDP modes now support first packet and expected packet
Further improvements on our API to optimize response time and delivery for our mobile app
New API endpoint /numbers
Ability to re-route incidents to escalation policies and on-call schedules
Suggested responders: when re-routing an incident, iLert now suggests you the best responder based on historic data
Zabbix (updated): Starting Zabbix 4.4, iLert can be integrated as a media type into Zabbix. Zabbix 5.0.4+ includes iLert as a media type by default. See also Zabbix blog post: Working with multiple on-call teams using Zabbix and iLert
Prometheus (updated): improved readabiltiy of prometheus incidents
Alert source overview page now includes outbound connections
User profile: low priority notifications rules are entirely optional, i.e. a user can now chose to not receive any notification for low priority incidents
Email: added ability to resolve incidents via email
Stakeholder engagement: stakeholders can now unsubscribe from incident update notifications
Email login: Users can now login via email (in addition to username) . Usernames in iLert are deprecated and will be removed in the future.
JIRA (updated): When you setup a connection from your alert source in iLert to your JIRA instance, projects and issue types are now dynamically fetched from your JIRA instance, so you can select the issue types when iLert syncs an incident to JIRA. You can even include custom fields.
Webhook (updated): you can now fully customize the payload for outbound webhooks.
API end point for uptime monitors
Uptime monitors: support for milliseconds in check timeout (blog post)
Flexible periods in repeating on-call schedules: set an arbitrary period length and chose between days and weeks as the period unit (blog post)
Single Sign On: Single sign on makes it easy to manage access to your iLert account using an identity provider of your choice.
Incident Reporting includes key metrics such MTTA and MTTR (blog post).
Auto raise incident priority lets you delay notifications and escalations until support hours start (blog post)