iLert Release Notes
​My on-call shifts page
Avatar upload (in user contact details)
Microsoft Teams Chat (new bot)
Microsoft Teams Meeting (new bot)
updates for on-calls API
updates for schedule shifts API
Zendesk inbound integration now supports attaching comments to incidents
Zammad inbound integration now supports attaching comments to incidents
Zendesk inbound integration
Additional DingTalk Action that does not require a connector setup
Added
team-contextHTTP header to control team context on a per request basis when using api keysEscalation policy detail view has been added
Attaching comments to incidents is now additionally possible through the events API​
Improved team details in settings view
Preventing ongoing call routing sessions from intervention through accept and resolve actions through mobile
Email bounces are now made visible in the user contact information
Updated algorithm to improve search results in list views
The incident priority of Zammad, ServiceNOW and SearchGuard Inbound Integrations is now fully managed in the alert source
DingTalk Outbound Integration
Added option for account owners to disable report sharing
Added API keys, which may now be created by each user and provided during API calls instead of basic auth
Added option to logout of all mobile devices using the web UI
New: Zoom Chat Integration
New: Zoom Meeting Integration
New: Microsoft Teams Chat Integration
New: Microsoft Teams Meeting Integration
New: MXToolBox Integration
New: Azure Alert Sentinel Integration
On-calls REST API resource​
New: Azure Alerts Integration for Azure Activity Logs​
New: Azure Alerts Integration for Budget Alert​
New: Azure Alerts Integration for Azure Logs​
New: Azure Alerts Integration for Azure Metric​
New: Azure Alerts Integration for Azure Sentinel​
New: Azure Alerts Integration for Service Health​
New: SignalFx Inbound Integration
New: Terraform Cloud / Terraform Enterprise Inbound Integration
New: Sentry Inbound Integration
New: Kubernetes Inbound Integration
​Advanced support hours routing for call routing numbers
Auto provision teams and mobile numbers with SSO
New: Zammad Inbound and Outbound Integration
New: Mattermost Outbound Integration
New: Splunk Inbound Integration
New: Elastic Search Guard Inbound Integration
New: ServiceNow Inbound Integration
Updated PRTG integration: custom incident summary and details based on PRTG placeholders.
Call Routing Number User Interface rework
​Team based organisation​
New on-call schedule styles for all schedule views
SAML2 SSO auto-provision now supports custom provision attributes​
Irregular Schedules new calendar UI
Call Routing: You may now choose if an incident is resolved on agent/caller hang-up
New: Autotask Outbound Integration​
Links and Images for Incidents with automatic connections
Adedd international caller IDs for voice alerts for USA and Canada, UK, Australia, Belgium and Netherlands
​
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
New: Consul 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
Incident Actions
Support for outbound connections in Call Routing Numbers
Support Hours for Call Routing Numbers
​Kentix AlarmManager​
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
​Autotask​
​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
​Heartbeat Monitoring​
​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.
​Stakeholder engagement: keep stakeholders in the loop during critical incidents (blog post).
​StatusCake​
Serverless outbound integrations:
​AWS Lambda​
​Google Cloud Functions​
​Icinga v2.x (updated): there is a dedicated plugin for Icinga now on our GitHub repo. You can now override the incident priority from within Icinga and we include the comments that you enter in Icinga when ack’ing a problem in the event log of the incident.
​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).
​AppDynamics​
​TopDesk​
​Discord​
​GitHub​
​Dynatrace​
Auto raise incident priority lets you delay notifications and escalations until support hours start (blog post)
​
