Mortgage giant Fannie Mae shared their AIOps adoption journey from the stage at Moogsoft User Conference 2019

Did you know ringtones in the PagerDuty mobile app are one of the most-requested features customers contact us about? And have you ever wondered what makes a good ringtone and how we come up with them? Imagine the following: You’re on an on-call rotation with no end in sight. There might be a trusted responder you can page in for help, but they’re already burnt out. The Incident Commander won’t be any assistance, because you are the Incident Commander.

Pavlos is a Site Reliability Engineer based in Munich, Germany. He likes building software and expanding his knowledge around the reliability of services and their infrastructure. He has created a few open-source SRE projects such as the awesome-sre, Wheel of Misfortune, Availability Calculator, and awesome-chaos-engineering to assist teams and individuals in getting on board with the SRE culture.

When we announced the launch of our Retrospectives Guide, we wrote about the value of scaling the continuous improvement mindset to beyond Product Development at PagerDuty by establishing the RetroDuty community. In this installment of our blog post series on retrospectives, I highlight the differences between postmortems and retrospectives. You might have heard of postmortems and/or retrospectives before reading our guides.

OnPage is pleased to announce a new, innovative two-way dispatcher and user communications feature launching next month, allowing system administrators to communicate with on-call healthcare providers. OnPage wanted to launch a feature, where a console dispatcher can initiate and send secure messages to the right providers. After receiving a dispatcher message, on-call providers can reply back to the message. This new feature converts one-way communications into two-way threaded exchanges.

Rich Lane, Forrester Research’s senior analyst for AIOps, had a simple and unequivocal message for attendees at the Moogsoft User Conference 2019 in Chicago.

Traditional Runbooks can become 10x more useful if they were automated or at least made executable (partly, if not fully). Shreyash Naithani from Microsoft Azure SRE team and author of "Practical Site Reliability Engineering" talks about how to take advantage of runbooks to eliminate toil.

Site reliability engineering was a term coined by Google engineer Benjamin Treynor in 2003 when he was tasked with making sure that Google services were reliable, secure and functional. He and his team eventually wrote the book on SRE which is available online for free for anyone interested in research and implementation of SRE best practices.

We’re on a mission to make responding to incidents a bit less chaotic. One of the best features we offer (we’re definitely not biased, no way) is a simple way to define how a severity gets determined when you open an incident. We call it the severity matrix, and today it has a new look. Previously, we had a preset list of conditions and impact that allowed you to pick a severity that matched them.

Let’s face it, managing a critical incident has never been a walk in the park. Even, in the “good old days,” before the great cloud revolution and the onslaught of digital transformations, an incident often meant mayhem. Processes were manual, time consuming, difficult to execute, document, and learn from. Getting all the right people in the “same room” at the right time – was nearly impossible. Lots of time was wasted chasing down the right folks.