We’re pleased to announce improvements to our reporting capabilities that enable teams to gain even greater insight. Now, teams can optimize their monitoring by visualizing metrics such as common incidents, SLA performance, and noisy incidents.
Here at PagerDuty, reliability is our business, and we aim to prove it with our actions, not just our words. We’ve spent over six years bulletproofing our software for our customers, and we’ve operated under a strict reliability SLA ever since. Now, we’re backing our code and infrastructure by becoming the first company to extend customers a multi-million dollar downtime insurance guarantee. We have put so many failsafes into our product that, if we have an outage, we’ll compensate you for lost revenue that that occurs a result of our downtime.
Transparency and collaboration are at the core of DevOps philosophy, and ChatOps is an important aspect of both. ChatOps puts an entire team or organization’s work in one place – everyone’s actions, notifications and diagnoses happen in full view. A native PagerDuty chat client would be designed for use during incidents, and wouldn’t replace the chat client you use every day. Having two different chat records, which a native chat client would encourage, runs counter to the DevOps philosophy.
The site is down. Alarms are going off. Before you can fix anything, you first have to understand what’s going on. And gaining context can be hard as you look across multiple systems and metrics. We’re pleased to announce Rich Incidents, a new feature for PagerDuty that helps incident responders gain additional context. Now, responders can go straight from an alert to a conference bridge, chat room, or runbook, giving them instantaneous access to each other and to any documentation they might need. Additionally, embedded graphs give more context into an incident, helping you respond faster and maintain a dependable product for your customers.
No matter what team you’re on, PagerDuty helps you resolve incidents faster. DevOps involves collaboration across multiple teams for better reliability and quality assurance. Having a central, shared tool like PagerDuty to manage incidents across the company makes that collaboration a heck of a lot simpler. Our new team organization feature makes it even easier for different teams like Operations, Development, and Customer Support to work together. Here’s how
Making mobile incident response even easier More and more, responders are using the PagerDuty mobile app as their first response tool to critical incidents. Just this past fall, push overtook email as our most popular alerting method, and customers continue to tell us our mobile app is one of their favorite parts of PagerDuty. We’ve […]
Last year, we launched Single Sign-On (SSO) to make it easier and more secure to manage your PagerDuty users. We’re excited to add Google Apps as an SSO partner alongside Okta, OneLogin, Ping Identity, Active Directory, and more. Get the details in this post.
Our newest feature, Email Parsing, enables you to automatically resolve incidents from your email integrations. With this feature, you can now automatically resolve email incidents, and you can add custom text from the emails into the incident. This helps keep everybody in the loop when your systems recover, as well as improves the accuracy of […]
We love hackday here at PagerDuty – it’s a great opportunity for everyone at the company to work on projects they’re passionate about, get the creative juices flowing, and see how we can mix up the tools and technologies we know to help out our users and each other. Last month was one of PagerDuty’s […]
Getting paged for an incident and rushing to your computer only to find that the incident was auto-resolved or acknowledged by another team member is incredibly frustrating. We’ve heard the feedback loud and clear, and we’ve recently released incident status update notifications – now you can customize how you’d like to be alerted when the […]