On Call


A New Bee’s First Oncall

I’m Honeycomb’s newest engineer, now on my eighth week at Honeycomb. Excitingly, I did my first week of oncall two weeks ago! Almost every engineer at Honeycomb participates in oncall, and I chose to join in the tradition. This may seem unconventional for a Developer Advocate — surely my time might be better spent holding more meetings with customers and giving more talks? Yet, I found that being oncall was the right decision for me.


Being On-Call: The Future of Incident Management

Software developers and IT teams are deploying code faster than ever. DevOps principles are giving way to improved collaboration and transparency across the entire software delivery lifecycle (SDLC) – helping teams maintain agile CI/CD pipelines and driving service reliability. In a globalized world of software, customers are using applications and services 24 hours a day, 7 days a week – with expectations of constant uptime.


Benefits of On-Call Scheduling Software

Being on-call sucks. But it’s a requirement for any effective DevOps or IT team – no matter the size. While your infrastructure and applications get more complicated, issues come up more often. From the ground up, teams need to be thinking about the scalability, reliability and security of the products they’re building, not just the development speed. On-call scheduling software integrated with your monitoring and alerting systems will lead to more efficient teams.


Shadow Like A Dutonian: Onboarding Engineers With On-Call Shadowing

On-call shadowing is an essential practice at PagerDuty. For a new engineer, a shadowing period serves as a kinder, smoother ramp-up to going on-call, with none of the stress or responsibility for diagnosing and fixing the issue. When we configure shadowing in PagerDuty, our goal is to simulate the process and actions of going on call as precisely as we can while making sure that actions of the “Shadow User” do not affect the primary engineer who is actually on call.


The New Team On-Call Checklist

Efficient DevOps and IT teams are constantly getting better at maintaining a CI/CD pipeline and deploying new code quickly – sometimes thousands of times per day. But, without a focus on reliability, the speed at which you release new products and services doesn’t mean much of anything. With great delivery speed comes great on-call responsibility (Sorry – bad Spider-Man reference).


U.K. Calls a “Brexit” on Pagers

National Health Service’s (NHS) recent announcement on the ban of the pager represents great news for U.K. healthcare organizations and their practitioners. The ban not only represents a transformative move, it also showcases pagers’ lackluster performance in providing secure, clinical communications. Now that pagers are making their way out of U.K.


Things That Suck About Being On-Call

Being on-call is a necessary evil for DevOps and IT teams maintaining complex systems in an environment dedicated to CI/CD. Systems will break, services will experience outages. Software developers, operations support and IT teams need to take accountability for the services they build and maintain – which means taking on-call responsibilities. And, of course, these on-call responsibilities come with a set of horror stories and sleepless nights.


The On-Call Template: Everything to Know

Being on-call sucks. Every DevOps or IT operations incident manager has heard or said this at one point or another. But, incidents are inevitable in the new world of CI/CD and rapid development. In order to maintain highly reliable systems, being on-call is an essential part of DevOps and IT operations workflows. So, we’ve written this post to be your on-call template, a guide dedicated to making on-call suck less for your employees and improving overall incident response and remediation workflows.