Optimize Your Services - October 2019
Interested in how to tune-up your services to derive even more benefit from your PagerDuty implementation? Easy and simple changes can have a huge impact on how much time and money you spend.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
Making the Most of PagerDuty + Datadog
For your team to effectively respond to incidents, you need a shared, unambiguous incident definition so you can recognize when an incident has occurred and assign the appropriate severity. Definitions of an incident differ across teams, but whatever definition you use, identifying and monitoring key service level indicators (SLIs) can help you understand when your service is operating normally—and when its performance has degraded to the point where you need to trigger an incident.
PagerDuty + Customers: Hear Why the UK Loves PagerDuty, Too!
At PagerDuty Connect London, customers shared their stories of how PagerDuty is helping lead digital transformation at their companies. We got a chance to take some of these customers aside to ask them why they love PagerDuty!
Vodafone Utilizes PagerDuty to Better Understand Their Real-Time Operations
Vodafone is a telecommunications company providing 4G network coverage for 18 million customers and 99% of the United Kingdom’s population. Ben Connolly, Head of Digital Engineering at Vodafone, details the challenges that his engineering teams were facing and why PagerDuty was the perfect fix. PagerDuty helps Vodafone deliver a better customer experience by allowing their teams to see the impact that they're having in real time.
Summit Day Two: New Integrations and Developer Platform to Bring Real-Time Work to More People
Yesterday, we kicked off PagerDuty Summit by launching new features that support the themes of Visibility and Intelligence. If you missed the keynotes or want to know more, check out this blog post. Today, we are making several announcements around two other themes that our CEO Jennifer Tejada touched on during her keynote yesterday: Platform and People. In fact, these themes are so closely related that we refer to them as one—that PagerDuty is a platform for people to do real-time work.
Connect the Right Teams and Work Together to Quickly Resolve Customer Issues
Today at PagerDuty Summit 2019, we announced PagerDuty for Customer Service—a powerful new way to connect Customer Service teams to engineering and IT teams. We were also excited to debut two new partner integrations with Zendesk and Salesforce Service Cloud, and we can’t wait to show users how PagerDuty and our customer service ecosystem partners help connect the right teams so they can work together and resolve issues quickly to reduce customer impact.
Summit Day One: Delivering New Machine Learning Capabilities to Cut Costs and Outages
At PagerDuty, we continually innovate every month (check out our What’s New page for the latest updates). But while we ship product continuously, we also save a plethora of new and improved capabilities to share with our customers at PagerDuty Summit, our annual customer event.
PagerDuty Slack Integration
Integrate Slack with PagerDuty for greater incident resolution agility. Create slack channels and drive on-call and real-time ops from slack. Check out the integration today to experience how PagerDuty together with Slack make real-time digital operations simple.
Announcing General Availability of PagerDuty's Slack Integration
When PagerDuty’s VP of Product Management Rachel Obstler announced the beta version of our new Slack integration in April in her “Anticipating, Monitoring, and Managing Incidents via Slack” panel at Slack Frontiers, we expected significant interest in the integration among our customers.
Service-Based vs. Team-Based Approach: Which Is Better?
How is the incident response process set up at your organization? At PagerDuty, our approach is to holistically look at your infrastructure, your customer-facing applications, and your products. We distinguish these by describing these items as “services” that roll up to and make up a “business service.” This setup allows teams to better manage these services so that when incidents do happen, responders can gain context much faster. But how?