Turn any signal into insight and action. See how PagerDuty Digital Operations Management Platform integrates machine data and human intelligence to improve visibility and agility across organizations.
Check out the latest capabilities we released.
Flexible schedules, escalations, & alerting
Automated, best practice incident response
Powerful context & noise reduction at scale
Quantify real-time business & technical impact
Improve with modern, prescriptive insights
Over 300 Integrations
Discover DevOps best practices with our library of webinars, whitepapers, reports, and much more.
Learn best practices and get support help with resources from our award-winning support team.
See how PagerDuty works with our live product demo — twice a week, every week.
We've created a maturity model to assist on the journey to digital operations excellence. Take our short assessment to find out where your team falls!
Interactive, simple-to-use API and technical documentation enables users to easily try updates and extend PagerDuty.
Engage with users and PagerDuty experts from our global community of 200k+ users. Become a member, connect, and share insights for success.
Get all your PagerDuty-related questions answered by exploring our in-depth support documentation and community forums.
In part 2 of our postmortem series, we dig into how to establish a culture of continuous learning, from getting leadership on board to invoking...
PagerDuty helps organizations transform their digital operations. Learn more about PagerDuty's mission and what we do.
Meet our experienced and passionate executive team.
We are risk-taking innovators dedicated to delivering amazing products and delighting customers. Join us and do the best work of your career.
With the PagerDuty Foundation, we are committed to doing our part in giving back to the community.
The on-call engineer has a critical role to play in incident management. Since on-call engineers are the first responders, they can mean the difference between a critical incident or one that is resolved quickly.
Smaller companies have few choices regarding who should be on call, but as the organization grows and incident management becomes complex and critical, it’s important to have a structured process for the on-call engineer.
Whether you’re a small business or an enterprise, you can benefit from having a clear process for selecting and equipping your on-call engineer. Here are a few guidelines.
In the first few minutes of the incident occurring, the on-call engineer needs to know the severity and extent of the incident. Based on that, they must gauge who is needed to resolve the incident and how to onboard them quickly. This requires having a working knowledge of how the system functions, so that when something breaks, they are able to identify what is normal versus what is broken.
In the case of small to mid-sized teams, the role of the on-call engineer would be rotated. This way, the load is shared and everyone is aware of how to handle incidents and don’t lose their touch. In the case of a larger team, they have the luxury of having dedicated incident managers who can initiate the first response. In either case, the primary goal of the on-call engineer is not to resolve the incident, but to sound the alarm and get the necessary resources looped in to resolve the incident.
It’s crucial to have a secondary on-call engineer ready for escalation. This means that there needs to be a schedule for rotation of roles within the team. It’s easy to set up automated rules so PagerDuty escalates to the backup engineer if there’s no response from the primary engineer.
Since there’s a lot at stake when an incident occurs, your on-call engineer needs to be a developer who can follow protocol and think on the go. They need to be aware of different strategies for point-of-care marketing and customer support. It is also useful to hand the on-call engineer a checklist or flowchart to follow when incidents occur.
Here are the steps an on-call engineer needs to take during an incident:
Choosing an on-call engineer must not be ignored or put aside. Having one with sufficient backups and a well-thought-out plan can mean efficiency when things go south. If your on-call engineer follows these basic steps, your team can spend more time creating and less time fixing.
This blog was co-authored by myself and Simon Darken. Once a year, PagerDuty’s SREs get together for a three-day, in-person offsite. With the team spread...
A release is a set of customer visible and operational features that together provide a completely new or improved product capability. It’s something that’s meaningful...
600 Townsend St., #200
San Francisco, CA 94103
905 King Street West, Suite 600
Toronto, ON, M6K 3G9, Canada
1416 NW 46th St., St. 301
Seattle, WA 98107
5 Martin Place
1 Fore St,
London EC2Y 9DT
© 2009 - 2019