We’re proud to introduce our latest addition to iLert’s advanced reporting capabilities. On-call reports give on-call engineers and managers insights into all-things on-call and report three metrics:
The data can be filtered by data range and schedules. If a user is on two or more schedules at the same time, that time is counted once.
This information can be used in various ways. To name a few examples:
We’ve updated our notification to report to match the style and capabilities of our other advanced reports.
Now you can select the users, filter by date range, and have a beautiful graph that is shareable and can be exported as CSV and PDF.
You can now have iLert remind you via SMS, push and email before any of your on-call shifts begin.
We’ve recently launched a Terraform provider for iLert. You can now provision iLert resources with Terraform and manage your iLert configuration in code. This blog post from our engineering blogs walks you through an example using Grafana and iLert to setup an automated metrics alert which will trigger phone call alerts during support hours.
We’ve changed our caller IDs for voice alerts to match the target country code for the following countries:
Every time iLert calls you, we use a number from the target country where possible. As always, our caller IDs rarely change, so you’re able to recognize that the call is from iLert. By saving our phone numbers in your address book, you can configure your phone to let calls from iLert bypass DND mode.
See this page for an overview of all our phone numbers (including SMS).
Keep it quiet during maintenance. With maintenance windows, you can temporarily disable one or multiple alert sources for a set period of time. An alert source with an ongoing maintenance will not create any incidents.
With Priority-Based Alerting, you can set different notification rules for high and low priority incidents. That way, you can use more obtrusive alerting methods for incidents that require immediate attention and less obtrusive methods for the ones that don’t. Low priority incident also do not escalate automatically. The incident priority is set on the alert source level. Moreover, the incident priority can be dynamically set based on Support Hours. This gives you the flexibility to be notified differently based on the time of day. You could, for example, configure your alert source to receive voice alerts during the night and push notifications only during work hours.