When things go wrong, your users need to know – but it’s not always easy to determine what to say or how to say it. If you’re responsible for getting the word out to hundreds or thousands of users, it can feel like a heavy weight on your shoulders. The task at hand is urgent, yet must be handled delicately. As someone who’s handled incident communication on Statuspage’s status page – the mother of all status pages – I know how difficult these moments are.

Continuous improvement is one of the fundamental tenets of Agile methodology that PagerDuty’s product development teams emphasize. This already works fairly well at the individual team level via retrospective meetings and postmortems but sometimes we don’t notice larger or systemic issues that are outside the control of a single team. This blog will share the process that we use at PagerDuty to uncover those issues, the outcomes we have seen, and how we have evolved that process.

Our August update makes SIGNL4 fit for the new “Payment Services Directive 2”. In addition, we have added extended the mobile alert dashboard and added new metrics. The enhanced dashboard of the SIGNL4 mobile app now shows alert counters per ‘services & systems’ category. Here come the details….

Emergency callouts are some of the most important notifications a user can receive. With the optional ‘Emergency Callout’ add-on, the capability to reliably alert and notify large numbers of employees can become part of your Enterprise Alert installation. These callouts can tell users about dangerous situations such as inclement weather, fires in the building, or even security issues like active shooter in the building. It is imperative that users receive these notifications.

Managed service providers (MSPs) simplify IT for global organizations of all sizes — and cloud services present new opportunities that enable these service providers to grow their revenues. Now, let’s take a closer look at MSPs and how they can capitalize on cloud services.

Most technical incident response plans typically account for stakeholder communications—for both internal teams and external customers. But at PagerDuty, what we’ve learned from our customers is that there’s still a painful and expensive gap in alignment between IT and business teams. To close that gap, we need to focus on what incident response means for business teams.

The current business environment requires organizations to implement cybersecurity safeguards to avert disasters associated with breaches, loss of data and hefty fines. Simply implementing a cybersecurity plan isn’t enough, it’s also important to incorporate the right solutions and workflows to prevent a disaster. This post will discuss the current state of cybersecurity, highlighting what organizations should be mindful of to successfully defend against malicious parties.

Are you a practitioner looking to attend the speaking sessions at PagerDuty Summit 2019 and want to get into the weeds with the PagerDuty developer community? This year, the PagerDuty Community Team is drumming up many special activities that puts users at the front lines of real-time operations.

The underlying infrastructures behind IT systems have become complex and overloaded. A single incident in today’s IT stack can shut down large chunks of a business and cost it millions – or even billions. Because of that, many businesses consider implementing AIOps in their IT operations an important part of their future.

Incident escalation is one of those seemingly mundane issues, the importance of which is often underestimated. Simply put, the escalation process is used to flag issues so that the relevant personnel can respond to situations. Implementation of a well-designed escalation process, however, is anything but simple.