| description | This page contains release notes for new features and improvements released after April, 2020. |
|---|
- Incident Actions
- Ability to select incident events in outbound integrations. Example: trigger webhooks for incident creation and resolution events, but ignore remaining incident event types.
- 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
- 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).
- AWS Personal Health Dashboard
- StatusCake
- Serverless outbound integrations:
- 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).
- Auto raise incident priority lets you delay notifications and escalations until support hours start (blog post)