Topic 1 - When I used to work in support, being on pager duty was something we all dreaded, and it was often low-man on the totem-pole. Now a days, with modern DevOps teams and customers expecting 24x7 availability, pager duty is part of normal life. What is the overall approach that PagerDuty brings to today’s challenges?

Topic 2 - What is a typical environment these days? How to teams usually manage the diversity of resources? How much does they rely on outside services/data to drive their visibility?

Love the concept of Failure Friday. Do your teams ever post the results or post-mortems to public forums?

Topic 3 - Where does Analytics and more advanced insight play a role for the types of monitoring and resolution that Pager Duty delivers?

How much do you teach customers your best practices, or about trends you’re seeing across customers?

Topic 4 - When analytics come into the picture, is there a line between being functionally specific (eg. what “this tool/service” does) and trying to be a single pane of glass across many services? Is it still good to have best of breed services or do you think we’ll see more merged capabilities?

Topic 5 - Let’s talk about how this applies to teams vs individuals. Part of the complexity of Ops is how to deal with handoffs, localized vs. centralized knowledge. How much information is a individualized/personalized view vs. how much gets centralized?

Topic 6 - We’ve talked to alot of SaaS vendors lately (Loggly, DataDog, Evident, etc.) about how they plug into PagerDuty to deliver a complete offering for their service. What are some of the unique integrations you’ve seen with PagerDuty that are doing unique things for Ops teams?