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.
This month is a big month for PagerDuty—we turned 10 on February 18! I never imagined we’d reach this milestone, honestly. A lot of Dutonians...
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.
As a developer, I’m a huge fan of continuous integration. For the uninitiated, continuous integration is a software engineering practice in which code changes are tested as soon as they are committed. This enables early problem detection. It also provides immediate feedback on code quality, allowing for issues to be identified and fixed immediately.
Often mentioned in the same breath as continuous integration is continuous deployment. Continuous deployment is an extension of continuous integration in that, as soon as the unit tests pass, the code is immediately released to production. By continuously integrating and deploying code changes, developers can reduce risk and quickly adapt the product to the business’ needs. This process, while incredibly valuable to both developers and users, does have some room for improvement.
As in a production environment, integrating your team’s incident management process into your continuous integration workflow is an excellent way to improve communication and transparency around failed builds. Sending the details of failed builds to an incident management platform such as PagerDuty can provide a number of benefits that go way beyond the standard notifications many continuous integration tools provide.
One of the biggest benefits that incident management techniques can bring to continuous integration is the concept of the “premortem.” A postmortem, in project management terms, is the process of examining and identifying the elements of a project launch that were successful or unsuccessful. While this process is often done at the successful completion of a project, in terms of incident management, it involves understanding and communicating the root cause of a critical failure.
By integrating this process into the continuous integration workflow, you perform a premortem. With a premortem you are looking for problems in advance. What problem may potentially occur that may disrupt service and trigger an incident. Testing for failures and potential service disrupting incidents during the the continuous integration phase allows teams to evaluate potential threats and make changes before things even reach the end user.
Training junior developers is an important part of running a successful development team. Unfortunately, successful incident management in a production environment can be fast-paced and stressful. While the team can run a postmortem the morning after a late-night issue occurs and is mitigated, the information that can be conveyed during those postmortems might not be as easy to consume by the more novice members of the team. By pushing issues raised in the continuous integration workflow directly into your incident management process, you can provide junior developers with an opportunity to learn more about the process in a significantly less stressful environment.
I’m a big fan of code reviews. I have always found them to be an important tool for the professional growth of every member of the development team, no matter what level of experience they have. By pairing an incident management platform with the continuous integration workflow, you can use the details of failed builds as a supplement to the code review process to identify specific areas of the code that should be discussed in more detail. This is an excellent opportunity to not only improve the code quality, but also keep the importance of the test suite at the top of the team’s mind.
Incident management is often thought of as a reactive process, but by incorporating a continuous integration toolset and mindset, you can turn it into a proactive one. Responding to and mitigating incidents before they actually happen will allow you and your team to stay two steps ahead, which will serve to reduce code debt, and improve the overall stability and reliability of your product.
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