ilert Release Notes
This page contains release notes for new features and improvements released after April, 2020.
- You may now backfill incidents via the API
- New on-call widget in mobile apps for iOS and Android
- Improved maintenance window creation
- Improved 2FA login experience
- Further improvements to the ServiceNOW bidirectional integration
- Metric data source credentials are now validated during creation
- Status pages now support service groups
- Dozens of new schedule override features that make it easier and faster to add overrides on the fly
- Reworked My-on-calls features to take and pass on-call shifts
- New end-of-escalation reached events for alert actions
- Status page SMS and Webhook subscriptions
- checkmk alert detail parsing has been improved
- checkmk now supports custom detail labels
- We have updated our platform to our new logo and CI
- automation rules (alert -> incident) have been integrated into alert actions and may now be manually triggered or configured with conditional execution
- Status pages will now automatically collapse large amounts of services, SLA data and uptime graph are fetched on demand by opening collapsed services
- Prometheus metrics data source
- Prometheus inbound integration now supports the custom url and urlLabel labels (added as links to alert)
- New major milestone: metrics for status pages
- HashiCorp Cloud (HCP) Consul support
- Terraform client now supports mulitple responders in escalation policies
- Datadog metrics data source
- ilert Backstage plugin has been updated to support mulitple responders, services and status pages
- An initial delay can be configured for escalation policies
- Private status pages now support IP whitelists
- Service uptime history can now be managed and overwritten
- Alert submit UI supports additional fields to overwrite: priority, policy or responders
- Added MFA reset for Admin users
- Jira alert sources now support Service Desk Events
- Grafana alert sources now support Grafana V9 events
New features
- This feature has been long-awaited by many customers: we have added support for Multiple Responders
- => Escalation policy rules now support multiple users and schedules
- => During the escalation of an alert all responders will be added to the alert
- => A user may request additional help of another responder on any open alert
- We have added a new messenger for alert notifications: Telegram, users may connect their ilert account to their Telegram app and respond to alerts on their favorite messenger
- We have added live updates to our alert list view
- Status pages of a team can now be managed in the team admin view
Improvements
- We have completely reworked the alert list view, users will now see additional information and improvements such as responders and their individual alert status, escalation policy filter, aggregation status of events for a specific alert, bulk resolve comments, highly reduced load and response times, deep links for filter configurations
- We have completely reworked the user list view, admins have now access to new tools and filters that should help them with their day to day tasks: filter for roles, mfa status and team membership, pagination, highly reduced load and response times, deep links for filter configurations
- Increased status page service limit from 30 to 100
- Doubled the API rate limits for Terraform clients
- Improved response time of team edit view
New and updated integrations
- Increased amount of fetched companies for Autotask connectors to 1000 and added a search view to the selection
Other
- Alert reports are now available in the professional plan, on-call reports stay a premium only feature
- Maintenance windows now support services and appear on related status pages
- Maintenance window now offer different types of notifications along their lifecycle when affecting services or status pages with private or public subscribers
- ilert will now inform the owner of incidents (via email) that are publicly visible on status pages in case they have been pinned there for longer than 4 hours
- Alert actions may now be cloned to other alert sources
- We now support conditional execution for alert actions making it possible to filter and tune alert streams to webhooks or tools like Microsoft Teams and Slack
- Now support incident list and detail views
- Now support status pages and services
- We have reworked the navigation as well as the stakeholder user experience
- We have improved the performance for customers with a large amount of teams and users
- we have introduced a new region field for users and adjusted all calendar and date/time relevant components to deliver a seemless localized experience
- Our Zabbix native integration now supports severity mapping and bidirectional problem/alert acknowledgement
- All public facing incident communications emails now support beautifully crafted html email versions
- We have introduced a new feature for private status pages to make them available to any user within an organization even if the entity itself is owned by a private team or hidden from stakeholders "Account Wide View"
- we have launched a completely new onboarding experience for new accounts
- added a new subscription API endpoint for status pages to add or remove a single subscriber
- the MFA status is now visible in the user list
- browser caching of certain script and style resources has been optimized for faster page load
- Conditional alert actions; you may now add additional filters to alert actions
- Alert action duplication, you may now easily copy and paste an alert action to other alert sources
- Call routing numbers may now use uploaded audio files to playback greeting, waiting and mailbox messages
- New endpoints have been added to the API to support add and remove operations for single user/team private subscribers
- Overall page load times have been reduced for the web-ui, especially for accounts with large user and team bases
- Sentry inbound integration has been improved to support alert metric events
- Autotask inbound integration has been improved to support new webUrl attribute for ticket link generation
- SignalFX inbound integration has been improved to support better alert detail extraction
- Call routing is now available in Italian
- Hyperping Integration
- Paoloalto Networks Prisma Cloud Integration
- We have launched private and public status pages in closed BETA.
- User shift color (profile settings) is now used in all schedule visualisations
- Status page editors now receive update notifications when the domain status of their page changes
- IXON alert source now supports dynamic routing
- We have launched the ilert developer platform, which enables you to create your own applications on top of ilert's uptime platform and share them with other ilert users.
- Support for WhatsApp as a notification channel
- Event API: routingKey may now be used to re-assign alerts during ALERT events
- Alerts API: escalationPolicy attribute is now included in the response payload
- Services of teams can now be managed in the teams admin UI
- Our ServiceNow bidirectional integration now supports dynamic mapping of assignmentGroups and escalation policies (as well as re-assignment)
- we have launched our Incident Communications 2.0 BETA, reach out to us to join during the testing phase
- On-call schedules: we now allow you to create more complex recurring schedules with schedule layers.
- New alert view: as part of our new Incident Comms 2.0 feature, a brand new revamp of our Alert Detail View has been launched, including live updates for Alerts and Alert related information.
- as part of our Incident Com 2 Feature, Stakeholder users may now use the web login (they were previously limitted to the Mobile App only)
- the
GET /api/log-entriesresource now supports?include=varsand?filter-types=ALERT_UPDATESparameters, as well as pagination for more advanced and detailed alert timeline access - Microsoft Teams Alert Actions have been rebuild to support a direct Teams query for enterprise customers with > 10k Teams.
- the (Support) Live Chat has been made available to EU customers (see Account Settings
- users may now choose their personal shift color that is rendered in schedules
- Humio Inbound
- Apifortress Inbound
- Freshdesk Inbound
- AppSignal Inbound
- Lightstep Inbound
- IBM Cloud Functions Inbound
- Crowdstrike Inbound
- critical alert push notifications are no longer triggered for update notification types
- update type notifications are now fanned out to all registered push token devices
- call routing numbers now support blacklists for incoming callers
- assign to policy action no longer sends two notifications but one
- added re-authorize option for Slack bot
- updated all alert source and connector icons to newest version with increased resolution
- the resolving user will no longer receive a resolve notification
- new inbound integration IXON
- new inbound integration Salesforce
- new inbound integration Jumpcloud
- new inbound integration StatusHub
- new inbound integration AWS GuardDuty
- rendering performance of timelines of schedules has been improved
- added a new uptime monitor type: SSL
- added response keywords check for HTTP uptime monitors
- added option to delete user avatar
- increased displayed team name sizes in action dropdowns and list views
- 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 alerts
- Zammad inbound integration now supports attaching comments to alerts
- 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 keys - Escalation policy detail view has been added
- 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 alert 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
- Updated PRTG integration: custom alert summary and details based on PRTG placeholders.
- Call Routing Number User Interface rework
- New on-call schedule styles for all schedule views
- Irregular Schedules new calendar UI
- Call Routing: You may now choose if an alert is resolved on agent/caller hang-up
- Links and Images for Alerts with automatic connections
- Adedd international caller IDs for voice alerts for USA and Canada, UK, Australia, Belgium and Netherlands
- New Notification Reports
- On-call duty notifications
- Call routing: added mailbox transcription to alert details and made voicemail links easier accessible in the alert links section
- Alert Actions
- Support for outbound connections in Call Routing Numbers
- Support Hours for Call Routing Numbers
- Datadog Outbound Integration now supports regions
- Prometheus alert detail formatting has been updated
- Slack channels (connections) can now be managed in ilert directly
- Ability to select alert events in outbound integrations. Example: trigger webhooks for alert creation and resolution events, but ignore remaining alert 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 alert 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 alerts to escalation policies and on-call schedules
- Suggested responders: when re-routing an alert, 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
- 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 alerts
- Email login: Users can now login via email (in addition to username) . Usernames in ilert are deprecated and will be removed in the future.
- Serverless outbound integrations:
- Icinga v2.x (updated): there is a dedicated plugin for Icinga now on our GitHub repo. You can now override the alert 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 alert.
- 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 alert to JIRA. You can even include custom fields.
- 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.
- Auto raise alert priority lets you delay notifications and escalations until support hours start (blog post)
Last modified 2mo ago