Operations | Monitoring | ITSM | DevOps | Cloud

On December 4th, 2025, we discovered an issue where the person shown as on-call on the dashboard didn’t match who was scheduled in the calendar. When we started investigating, we learnt that this only affected schedules with weekly rotations or weekly layers combined with custom timings.

Today, we are introducing some new on-call features: Add Gaps to on-call, Scheduled Layers, Handoff Days, and more. Flexibility in on-call schedules has been the single focus point in this release. These features give you much finer control over when people are on-call, how handoffs work, and what your schedule looks like around holidays and time off.

When the issue settles, and systems are back, one question always remains: What actually happened, and how do we stop it from happening again? That’s where incident postmortems come in. Not just as documentation, but as a structured way to learn, improve reliability, and replace guessing with clarity. A good postmortem isn’t about blame, heroics, or perfect narratives. It’s about truth, learning, and building systems that get stronger with every failure.

Incident response teams deal with several challenges. Alert noise, unclear ownership, lack of automation, and more. It’s important to keep an eye on these challenges and resolve them from time to time because they can turn minor issues into major outages. In this blog, we’ll discuss some of the common incident response challenges, how they affect, and how you can resolve them. Let’s dive in!

Incidents don’t wait. They hit production, disrupt users, and pull teams into long recovery cycles. And a well-structured incident response team helps you move fast, limit damage, and restore services without chaos. In this blog, we’ll explain what an incident response team is, its key functions, team composition, and different types of teams. Let’s get started!

Modern systems produce endless streams of metrics. CPU usage, request volume, cache hit rates, node counts, queue depth, the list keeps growing. With this much data, it’s easy for teams to get lost in dashboards without knowing what actually matters. That’s why DevOps and SRE teams rely on the 4 Golden Signals of System Reliability. They provide the simplest and clearest way to understand user experience and system health.

The Incident Management vs. Change Management are two such moments that highlight a core difference teams face every day. One is a reaction to failure. The other is a planned improvement. That’s the heart of incident management vs. change management. Both keep systems reliable, and both help teams move faster without breaking things. Let’s explore how they differ and how they work together.

Atlassian is shutting down OpsGenie. New sales stopped on June 4, 2025. Complete shutdown happens on April 5, 2027. Atlassian wants you to migrate to Jira Service Management (JSM). But like many OpsGenie users, you probably have questions. What is JSM? How does it handle alerting, escalation policies, and on-call schedules? What automation options does it have? Is it the right fit? And more. This blog breaks down everything you need to know.

Atlassian is shutting down OpsGenie. New sales already stopped on June 4, 2025, and the platform will be completely offline by April 5, 2027. As an OpsGenie user, you now face a critical decision: Migrate to Jira Service Management (JSM), Atlassian’s recommended path, or choose a different solution. And if you’re not sure JSM is the right fit for your team’s incident management needs, this review will help you decide. I signed up for JSM and put it through real-world testing.

OpsGenie is shutting down. And Atlassian recommends migrating to Jira Service Management (JSM). But if you’re not sure JSM is the right fit for your team’s on-call management needs, this review will help you decide. I signed up for JSM and put it through real-world testing. I created on-call schedules, rotations, and overrides. Then, I reviewed JSM’s on-call management across 4 key criteria. For each criterion, I shared what I liked and what I didn’t.