We’re excited to announce a new set of updates and enhancements to the PagerDuty platform. Recent updates from the product team include On-Call Management, Event Intelligence, and Mobile Products, to PagerDuty Community & Advocacy Events.
Hello and welcome to the fourth post in our EI Architecture series focusing on Intelligent Alert Grouping. Previously we have talked about how to train Intelligent Alert Grouping using incident merges (here) and how to configure your alert titles to improve default matching. In this post, we’re going to cover how service design can also impact your experience with Intelligent Alert Grouping as well as the PagerDuty app in general.
We’re continuing on with our third piece about how to utilize and improve your Intelligent Alert Grouping (IAG)! In case you missed it, the first two blog posts describe the feature (here) and explain how it uses merging to group alerts (here). We alluded to today’s post at the end of last: today we’ll be discussing how to use alert titles to improve IAG matches.
We often hear from customers that they’re dealing with unmanageable levels of noise and complexity, which makes it harder to pinpoint root cause and get to resolution quickly. All this effort spent on sifting through noise, processing events, and gathering context results in a lot of wasted time. That’s why we’ve launched Event Orchestration, which became generally available to our Event Intelligence and Digital Operations customers on Monday.
Incidents happen. Things go wrong. Systems fail. Sometimes they fail in unexpected and dramatic ways that create Major Incidents. PagerDuty makes a very specific distinction between an incident and an Incident. Your organization may also make such a distinction. Determining if an incident is major or not can come down to a number of factors, or a specific combination of factors, like the number of services affected, the customer impact, and the duration of the incident.
After two years of sky-high spending on cloud and related technologies, 2022 is the crunch point for corporate IT and digital leaders. Investments in technology helped facilitate the rapid shift to mass hybrid working and supported businesses to embrace the digital-first models of the new normal. But beyond merely investments to support new working styles, leaders also must ensure their organization continues to innovate.
At PagerDuty, we are committed to championing the customer — it’s a core company value. Our product has to provide great value, we have to provide excellent service, and we need to make it simple to do business with us. The Winter 2022 G2 Grid for AIOps Platforms Relationship Index showcases these values and highlights PagerDuty as a leading player in the AIOps space.
PagerDuty is excited to introduce Round Robin Scheduling. Round Robin Scheduling allows teams to equitably distribute on-call shift responsibilities amongst team members. Automatically assigning new incidents across different users or on-call schedules on an escalation level ensures that teams are resolving incidents as efficiently as possible. And, by balancing the workload across multiple users, there’s less risk of burnout.
Most support organizations today adopt some form of the traditional tiered support model. It is one that is based on a process of escalations and customer handoffs. Under this model, customer issues get escalated through multiple levels of a support hierarchy, with three tiers being a common workflow.
PagerDuty’s Operations Cloud helps organizations with critical work across the entire business, from IT teams to customer service to human resources, marketing, sales, and more. With PagerDuty, organizations can prioritize accurately, respond efficiently, and reduce operational overhead. In this blog post, we’ll share examples of how PagerDuty can be used for critical work in all departments, not just IT, using our new Solution Guides for Business.
A Scrum Ceremony is a type of scrum event or meeting that is intended to help move projects forward in a more timely and efficient manner. These ceremonies occur at key points in the production process, emphasizing organized collaboration and communication between team members to help simplify complex development processes and queues. For example, Daily Scrum is a ceremony held every morning to go over which items have been completed, which are being worked on, and which are coming up.
Within DevOps, we talk a lot about the on-call process—but what about the human side of being on-call? For example, what are effective ways of managing stress and anxiety during a shift? How can one manage life situations that make being on-call difficult—such as being responsible for watching the kids during an on-call rotation? And how can an empathic team culture help prevent burnout and turnover?
