Operations | Monitoring | ITSM | DevOps | Cloud

On Call


On-call compensation in IT

On-call is a special working hour arrangement under employment law. It comes into effect when the employee is obliged to be contactable at least by phone, so they can start work in an emergency. On-call duty is generally counted as time specifically meant for work purposes. In practice, this means that employees are normally not allowed to work while on-call. However, there may be exceptions. For example, on-call employees may also work from home if they can be reached through their work device.


Product metrics @ incident.io, a year (and a half) in

We’ve been celebrating a few big milestones 🎉 at incident.io in the last few months. We were recently discussing product metrics (as you do for fun on a Friday afternoon 🤓) , and Lawrence was very surprised with a particular stat around the number of workflows that have been run using incident.io.


Is being on-call a reason to quit?

“Well, that’s the job.” Have you ever heard that from your colleagues or bosses when it came to being on-call? Imagine you started a new job 3 months ago and were looking forward to it from the start. You are on-call one weekend a month and thought there wouldn’t be many incidents from Friday evening to Monday morning. But by now you’ve noticed how much being on-call duty actually stresses you out. You get restless as soon as your shift starts.


On-Call Schedules: Striking the Perfect Balance

DevOps, and Site Reliability Engineers - your prayers have been answered! 🙏 With Lightstep Incident Response, you can finally orchestrate all your on-call schedules, precise notifications, smart alert grouping, and automated incident response in one place. Finally, everything is under control. While engineers have continued to develop ways to make our systems more available and robust, downtime is still an unfortunate reality for just about every product or service.


Round Robin Escalation: An Efficient Way to Distribute On-Call Responsibilities

Nowadays, organizations address a high volume of incidents everyday. With so much happening, responders can be overwhelmed by the volume of incidents and may end up de-prioritizing certain important incidents. Hence, it is important to have an efficient on-call scheduling and escalation process in place. In this blog, we will explore how Round Robin Escalations can help distribute on-call load and set up efficient on-call schedules. This blog covers the following pointers.


On Counting Alerts

A while ago, I wrote about how we track on-call health, and I heard from various people about how “expecting to be woken up” can be extremely unhealthy, or how tracking the number of disruptions would actually be useful. I took that feedback to heart and wanted to address the issues they raised, and also provide some numbers that explain the position I took with these metrics on alerts.

Sponsored Post

Top Five Pitfalls of On-Call Scheduling

On-call schedules ensure that there's someone available day and night to fix or escalate any issues that arise. Using an on-call schedule helps keep things running smoothly. These on-call workers can be anyone from nurses and doctors required to respond to emergencies to IT and software engineering staff who need to fix service outages or significant bugs. Being on-call can be challenging and stressful. But with the proper practices in place, on-call schedules can fit well into an employee's work-life balance while still meeting the organization's needs.