PagerDuty Best Practices for On Call Teams Ops Guide
The always-on, always-available expectations of digital services have increased the requirements of technical teams to provide response and readiness around the clock. For teams new to this concept, introducing on-call ownership can be difficult and complex. On-call management is key to PagerDuty’s service, but the non-technical aspects are important for teams to consider.
While on-call allows organizations to better meet increasing customer expectations, there are also potential impacts to the wellbeing of your on-call engineers. Change can always cause stress, but with on call responsibilities, engineers worry about being woken up in the middle of the night in addition to their normal workloads. Managers should keep an eye on responders for burnout. Meeting concerns head on, while you are setting up your on call practice, will help you manage the overall health of the team. This guide will give you some suggestions for setting good guidelines with your teams.
In the most basic sense, on-call describes a state in which some employees are available to be notified for unplanned incidents, alerts, and issues for some number of systems, services, or applications. In the very early days of commercial internet—before many folks had access to reliable mobile data services—companies would provide their employees with a text-based, one-way, or two-way pager so they could be available around the clock in case they were needed.
That’s where PagerDuty gets its name.
Who is This For?#
This guide is a resource for individuals, managers, and teams to use when evaluating or making the shift to an on-call culture.
For a fast overview of on-call, there is a short but broad introduction in the Full Service Ownership Ops Guide.
What is Covered?#
Setting Team Norms#
Building an On-Call Culture#
Recommendations for Managers#
- Ettiquette and Setting Expectations
- Time Management
- Take Stock of Your Alerts
- Prioritize Projects
- Leverage Traditional NOCs
- Be Flexible
- Establish Good Behaviors
This documentation is provided under the Apache License 2.0. In plain English, that means you can use and modify this documentation and use it both commercially and for private use. However, you must include any original copyright notices and the original LICENSE file.
Whether you are a PagerDuty customer or not, we want you to have the ability to use this documentation internally at your own company. You can view the source code for all of this documentation on our GitHub account. Feel free to fork the repository and use it as a base for your own internal documentation.