Operations | Monitoring | ITSM | DevOps | Cloud

In recent weeks, I’ve spoken with several Opsgenie customers who are evaluating a migration to ilert after Atlassian’s decision to phase out Opsgenie and fold its functionality into other products. Atlassian is giving Opsgenie users “two options: move to Jira Service Management for robust end-to-end incident management, or move to Compass for alerting and on-call management.” This has raised a broader question in our industry: ‍

We’re excited to announce the launch of our bi-directional integration between OnPage and Jira! This integration is designed to bridge the gap between ticket creation and incident response, ensuring that IT, DevOps and other tech teams who rely on Jira to manage their incidents can automatically identify and engage the right on-call staff—ensuring critical incidents are addressed in real time without delay.

If you haven’t heard already (which would be shocking considering the numerous posts I’ve seen on Reddit) Opsgenie’s end of life is right around the corner. This means there is no better time for Opsgenie users to explore alerting and on-call management tools outside of the limited alternatives provided by Atlassian. So, I felt now is a better time than any to address the needs of those affected by the dissolution of Opsgenie and reveal why OnPage should be your new platform of choice.

A common problem in monitoring and alerting systems is not just alerting on what you’re seeing but preventing alert storms from overwhelming operators. When a system generates multiple notifications for the same incident, it leads to alert fatigue and can mask other important issues. For time series data, alert fatigue can result in missed anomalies, delayed responses to critical trends, and difficulty distinguishing real performance degradations from noise.

When an incident happens—your systems go down, a critical service fails, or your end users start flooding support channels—what you need is fast, reliable alerting and an on-call team that can respond immediately. But if you’re using Jira Service Management (JSM) for this, chances are you’re paying for a lot more than just that.

If you’ve been relying on Opsgenie for real-time incident alerts and on-call scheduling, you’ve likely seen the writing on the wall: Opsgenie is being absorbed into Jira Service Management (JSM). For some teams, that may sound like a logical step forward. But for others, it poses a much more critical question.

‍ Learn how to set up Zabbix Cloud for AWS Auto-Discovery and receive critical alerts via SMS, phone calls, or push notifications. ‍ During the last Zabbix Summit, the company presented a cloud version of its well-known monitoring platform. We at ilert constantly see the growing popularity of Zabbix as more and more teams across the globe utilize it for their monitoring needs. To help users quickly adopt the new cloud version, we delivered this guide.

A few weeks ago, we introduced anomaly alerts to early adopters. Today, we’re excited to announce that anomaly alerts are officially in open beta and available to all Sentry users on the Trial, Business, or Enterprise plans.

In Industrial IoT for real-time monitoring, timely alerts are crucial. While Slack and email notifications are common, they can be easily missed or buried in a flood of other notifications. SMS and WhatsApp on the other hand, offer a level of immediacy and directness that’s hard to ignore.

Let's face it – not all notifications are created equal. That paper cut of a CSS bug probably doesn't need the same response as your production database doing its best impression of a black hole. Today, we're thrilled to announce Priority-Based Escalation Policies, a powerful new way to ensure your team's response matches the notification severity.