Comment on page
ilert Release Notes
This page contains release notes for new features and improvements released after April, 2020.
- Support hours have been moved out of alert sources into their own entity, you can now share a support hour across multiple sources and use team ownerships to controll access
- We have added a new Mute notifications feature in web and mobile app, responders can now mute their notifications for specified or customized time periods
- The AI assisted incident postmortems feature has reached closed BETA, reach out if you are interested in using before its GA
- We have introduced a feature that autmatically archives historical layers of large repeating on-call schedules, to keep performance steady no matter the use-case
- Integration icon and logo generation has been reworked for web and mobile to improve performance of the UI
- Autotask alert actions via API
- MicrosoftTeams alert actions via API
- Reworked SMS notifications to allow for a better focus on alert summary content
- Alerts in state ACCEPTED may now be accepted by responders that are not yet added to the responder list of the alert
- Auvik alert creation has been improved (new fields)
- The Grafana inbound integration now supports custom priority mapping based on label values
- The Microsoft Teams bot now supports a new who is on call command (@iLert oncall) that can be customized for teams and channels using a Microsoft Teams alert source
- The Microsoft Teams Activity Feed display information for the bot's cards has been improved
- New alert action filter types have been added
- Alert source templates (text form) are now available in Terraform
- delayMin field for escalation policies
- New alert source time based grouping options are now available in Terraform
- The schedule detail view calendar mode now creates shareable URLs that include your calender configuration
- Static schedules received multiple improvements for QoL and a new default shift start setting that is remembered for your user profile
- Call routing speech detection has been improved for certain scenarios where the input was not properly detected
- The alert comment (messages) UI has been reworked
- Alerts can now be manually linked to incidents (and also unlinked from them)
- Last activity in (admin's) user list is updated more frequently for web UI activity
- Status page enduser facing email communication now resolves the status page name as friendly email from address
- We have relaxed the view permission checks for Maintenance Windows a little (Note: edit permissions stay the same) it is no longer required to have a permission to access every single related alert source and service, but now sufficient to have access to a single one of those related entities
- You can now provide custom time ranges for overrides in my-oncalls, giving you more flexibility if you want to override partial shifts
- The subscription button on private status pages now adjusts its state asynchronously depending on the current viewer
- We have added an additional step to prevent accidental deletion of resource like alert sources
- Alerts with linked incidents are now marked with aicon🔥
You no longer need to lookup who's next in the escalation chain. You can now manually escalate alerts to an escalation level of your choice. The escalation process will resume from the selected level.
Ever wanted to take someone else's on-call, but not their entire week long shift, but only for a day? Now you can do this from the My on-call shifts (both in the web and mobile app) page when taking someone else's on-call and overriding your shifts. Until now, this was possible only on the on-call schedule itself.
This has been in the making for a while: we have completely overhauled our alert actions and connector UIs and APIs, giving tons of new QoL features like multi alert source assignments or team management to alert actions. We have launched the closed BETA and would love to hear your feeback on it - so if you are interested in trying it out just reach out via email or live chat.
- A new inbound integration has been added for Particle
- The Grafana inbound integration now supports the cluster alert label to build alert summaries by default
- Create dedicated channels in Microsoft Teams to communicate alert updates
- New /il-alert command to create alerts from within Slack - you can customize this feature for your team and Slack channels using a Slack alert source
- The Slack bot now supports further alert based interactions such as raise, reroute, escalate etc.
- You may now choose your primary phone number, if you are using multiple contacts. The primary phone number will be preferred when making call routing agent calls or showing your number to other users in on-call requests
- You can now choose a specific timed window to group your alerts in your alert source e.g. group all incoming events for 5 minutes, until creating the next alert
- The alert source creation process has ben overhauled, there is a now a wizard that guides through the most important steps of the setup
- New inbound integration Twilio Errors
- New inbound integration Uptime Kuma
- We have overhauled and enhanced our Github inbound integration, you may now choose specific alert action types and event types for which to create or resolve alerts, we also do support Github Advanced Security type webhook events now
- Grafana v9 Links have been optimized, instead of showing general instance links we prefer to show specific dashboard links now
- It is now possible to turn an alert source bidirectional even though it was already created
- You can now choosen to enhance Autotask inbound alerts with company details, by enabling the specific setting for your Autotask alert source in ilert
- You may now choose if you want to receive full text alert details or short forms in Microsoft Team channel notifications, by adjusting the longDetails field in your MS Teams connector
- Create dedicated channels in Microsoft Teams to communicate alert updates
- Added new create alert feature to Microsoft Teams bot (note: you may optionally customize the behaviour using ilert Microsoft Team alert sources)
- It is now possible to re-authorize your Microsoft Teams bot without removing your existing alert actions
- Added a new text mode for alert source templates, you can use the top right icon in the input area to switch between text and block mode when creating alert templates
- API key analytics are now available showing live API key resource usage for every user (Navi -> Profile -> Manage API keys) this feature also ships with an API resource for ADMINs to fetch account wide API usage information see https://api.ilert.com/api-docs/#tag/Reports/paths/~1reports~1api-keys~1usage/get
- The alert creation view has been reworked to match the features of the web UI
- Migrated the platform to a new infrastructure, improving performance, scalability and availability
- New session management, allowing for more secure and longer running sessions
- Added remember me option for even longer running web sessions
- 2-FA codes are now supported by the mobile app's login
- We launched ilert AI, which adds advanced generative artificial intelligence features for responders along the incident management lifecycle
- Updated Slack bot
- Added new create alert feature to Slack bot (note: you may optionally customize the behaviour using ilert Slack alert sources)
- New navbar widget for user onboarding and product updates
- Improved performance of schedule UIs
- Google Cloud Security Command Center inbound integration
- Brand new alert source list and edit UI
- Brand new call routing number list UI
- Brand new maintenance window list UI
- User list CSV export
- Improved the Sentry inbound integration
- New status field for Autotask outbound integration
- Improved Autotask outbound company search, now dynamically fetching based on search input
- Upgraded Jira outbound integration to dynamically detect Jira Cloud, Jira Server and other Jira versions and switch the API automatically so that old and new installations are seemlessly supported
- We have launched a new feature for notification preferences: live test notification status
- We have added additional states to our alert notification timeline events, that now allow you to (live) track the status of outbound alert notifications and see if they have been delivered to or (e.g. Whatsapp) read be the responder, they work seemlessly for all notification channels
- We have launched an overhowl of our escalation policy list and detail views
- We added additional details to delete dialogs across the platform
- We have introduced the new ilert Free billing plan
- The user list search has been improved
- Alert email notifications links now come with an additional confirmation step
- New Checkly inbound integration
- Optimized Appdynamics inbound integration
- Generic alert summary, details and routingKey templating with our new template editor for alert sources.
- We have launched a complete re-work of our Notification Preferences feature
- shiftColor is now supported in API
- Public status pages may now receive unlimited subscriber imports in state INACTIVE, during activation a license with a fitting range of subscriptions is needed however.
- We have enhanced the information in our /api/integrations resource
- Cisco Meraki has been added as new inbound integration
- We have optimized our PRTG inbound integration
- 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