>>LA from Las Vegas. It's the cube covering AWS reinvent 2019 brought to you by Amazon web services and along with its ecosystem partners. >>Hey, welcome back everyone. Live cube covers here at reinvent 2019 in Las Vegas. I'm John, your host extracting the signal from the noise with Stu Miniman analysts at Silicon angle, the cube and Wiki bond. We've got two great guests talking about the ecosystem and the future of software and how customers are consuming it in the cloud. Todd Osborne G VP of alliances and channels at new Relic and Josh Hoffman, GM and global lead of ISB partner ecosystem of AWS. Guys, welcome to the cube. Thanks so much for having us. So guys, we're the top story to me at this show. So far as I'll see infrastructure at scale. The software development life cycle is continuing to evolve. We are more automation, more as Andy says, heavy lifting's being done, which means that application developers are going to get more and more goodness. Dev ops created infrastructure as code check. Now we've got data, tons of data everywhere. So we're, we're seeing an ISB Renaissance more software. You guys are out there writing software. So what you guys take so far of the impact of the ISV here, Josh, to talk about that because this is a big story, does >>massive, I mean if you walk around the floor, you'll see folks that are automating new ways of doing dev ops. You're looking at new ways of securing serverless functions. Um, you're looking at new types of storage. So you could go across every category of technology in this room and you will see an incredible amount of batim innovation. Our partners are really driving that. >>Talk about the relationship with AWS, new Relic, longstanding partnership. Where is it now? Where's it going? It's, I mean, it's off the charts. So even just the last year, the amount of momentum we've built together as has been fantastic. So we participated in a whole bunch of different programs. We've got dozens, hundreds of joint customers that were doing things together. I mean, just look at this event. It's just a, it's just astonishing. We operate in a lot of different partner models, um, from, from reselling, uh, with, with various partners to building technology programs to participating, uh, with Josh and team and our friends. Uh, our friend Dave McCann and team on a eight of us marketplace. Just a whole host of different things that just continue to, to, uh, expand the partnership at scale. And the consumer is ation of the software, the procurement process she's had Teresa crossing off from public sector, whether you're in the public sector or commercial procurement still stuck in 1995 it feels like, right? >>I mean, like, are they modernizing? They've got a lot more ways to get software with the marketplace. What are you guys seeing with customers? Is it really that bad? Am I over over it? It's not that bad, but you know what I'm saying? I mean, so from my perspective, one of the cool we're seeing is, um, AWS in the cloud. Providers are driving a consolidation of budget of modern stuff, of cloud, of, of all the new things that companies want to do. That's all getting consolidated either in a new groups or new budget cycles and AWS is making it really easy to participate in those. So through programs like the marketplace, through various other other initiatives that we're doing, we can combine what we want to achieve with, with what the customer wants to achieve, which is speed to market with, which is with what AWS wants to achieve, which is faster adoption of all the different services and bringing the right ecosystem along with it. >>So the modernization of the procurement cycles along with the monetization of the technology is really cool to watch. Well, I wanted to ask that before. I want to get to the question that I'm that interested Andy Jassy his point on this keynote, Hey, this is the first time I heard him talk like this. We see two types of developers and two types of customers. People want the low level building blocks, the builders and then a new set of customers who want solutions. Yup. This is, this is your wheelhouse. This is where the solution network kind of ecosystem is evolving very quickly. Can you guys share your observations on what that, what he means by that and what does it mean for customers? >>I'll share it in the context of what we're doing with new Relic. Um, when you think of the concept of a solution, a lot of our customers, hundreds of our enterprise customers are going through our migration programs. They need help making sure that what they're doing on prem is translating to what's happening in the cloud, what the applications are doing on prem, and how they're performing in the cloud. So we've collaborated with NewRelic over the last year and a half on a number of new, not just migration programs, but windows or views into how the applications are performing. And we've designed those specifically for customers who are going through those migrations. So you just take that one little category. Um, and it's an area where we're collaborating together to bring something that is a full solution to the customer for those who are going through that migration journey. >>Your take on the whole solution thing. Yeah. So we, uh, last year at reinvent, we announced really the first solution that new Relic had ever launched trying to meet that market need and we, we announced the cloud adoption solution. So everybody knows we've got this great platform with all these cool features. We had never really gone to market and said, not only do we just address application monitoring or infrastructure mining, we actually address the business outcome of migrating to the cloud and all the benefits of doing that. So we announced that as a methodology last year. We added to that over this, this past year because we've enhanced our platform to, uh, have this new capability that we call programmability, which is the ability to write applications on top of the new Relic platform. So we've built, and we launched today a cloud adoption solution application. Kind of a mouthful. >>But what it is, is it is, it's the ability to use our technology and our platform to very easily drop that into a customer and help them very quickly get time to value of delivering on a solution and ultimately achieving the business outcome they're looking for. Yeah, I taught actually. So as you know, I was at your conference earlier this year in New York city where you really defined what a platform should be. And just like Amazon, what you want is you want builders and you want them putting solutions on Dabo. It gives a little bit of the momentum of what you've seen since new Relic one, and then the rollouts. So I don't know the formal count, but I know we're way past the dozen applications that we launched since then. Uh, we also added several different features including logging and some other technologies. We've closed a bunch of different deals with these new technologies since then. >>Um, and then a couple of the cool things from the partner ecosystem that we've done is with the platform capabilities we have, uh, firstly we're now, uh, getting ready to embark on building our first technology partner program. So we were talking to dozens of different partners in this room about how they can build with us on new Relic to make the platform even stickier, uh, for our customers that can now integrate NewRelic with various other technologies. And then the second, uh, thing we were proud to announce today is we've, we've actually just signed a three new managed service providers. So kind of another partner motion that we're driving in this ecosystem. And the new, all the new features of the neurotic platform helped enable us, uh, to do some really cool things with the platform and also evolving business model, uh, to close. Uh, so we were excited to to close three, top 80 best partners, which is best been global, uh, uh, blaze clan and out of California mission cloud as three new partners that we, uh, just, uh, signed agreements with. >>So we're happy to do that. Yeah. When we talk about the transformation, you know, one of the biggest challenges for customers is their application portfolio. I noticed new Relic has two boosts here. There's one specifically just focused on serverless, which I think is awesome. It's got some cool things. They're very focused on that developer app dev deployment there. Um, but you know, your customers, they've got a broad spectrum of applications and that journey to transformation in a modern nation is going to take time. How do you deal with the spectrum of what they're dealing with? But Todd, maybe start with you and then Josh would love your viewpoints too. I mean the spectrum. Massive. So our biggest challenge is keeping up with everything and continuing to innovate with all the things that are happening. But again, the benefits of the platform that we have enables us to do that in the enhancements. >>We wait and we made this year, this year. Um, now that our platform is, is more open, we can connect data, collect data from multiple entities, not just the new Relic, uh, agents that we've, that we were built on. So, uh, the concept of observability and being able to observe the entire application environment, um, is built on the fact that data's gotta come from all these different places. Then we need to turn that around and curate it, uh, into the right experience and the right use case that the customer's looking for. So, uh, all I can say is that, uh, our, our company is built on innovation. We try and stay on the cutting edge of all that. Try and stay current with that and meet the customer's needs as, as everyone here is innovating like S easy at scale. Todd, talk about what's going on in New York. >>What's the coolest thing going out with new Relic right now? Cause Lou always comes on the Q lose to CEO and he's cool. We love him, but he's always got his hands in something. Yes, he got the observability down. Cloud operations becoming standard. That's a tailwind for you guys as a company. But what cool things are you guys working on right now? Um, I certainly can't do Lou any justice. So the customer stories and things and he comes up with are amazing, but you know, from an industry's perspective, like gaming is hot. Um, and it's just like media and entertainment is hot. So we're just doing some really cool things with some really cool customers. Um, maybe not as cool as Lou would be, but you know, customers like, uh, are really adopting our migration story and we're really driving some significant business together. So customers like world fuel services and fleet complete, uh, we've recently come out and announced the stories of how we're helping these companies migrate. >>And frankly that's what's, that's what's cool about it is like everyone wants to get on the cloud faster, do more faster, and we're, we're enabling that, uh, in some really cool customers. So I'll to get your both reactions just to memes that we're developing on the cube this week. One is called, one is cloud native. If you take the T out, it's cloud naive. Okay. So, and the other one is something that I use on my post when my Andy story I did was you got born in the cloud, which is clear benefits. There's no, there's no discussion there. Check winning builder, but reborn in the cloud as companies are becoming reborn, this isn't the Mike, not just migration. There's a fundamental mind shift shift. Yeah. This is a reborn enterprise. And if you're not be born in the cloud and you're probably not going to be around longer, that seems to be the message. What's your reaction to cloud native without the T and reborn in the cloud? >>Well, I think it's, I think it's an accurate statement. It's funny. It's the first I've heard it. I may steal it. If I can use it, please pass it on. I will. Um, I would say that from an APM perspective, many of our partners are in different phases of their journey. Um, and so everything that we do is around three anchor points, which is helping those companies build great software if they haven't already, or if they're making that transition. Once they've made that transition, how do we help them market the software? And then the third piece is really how do we help them sell it? So in the case of new Relic, um, we've got a number of folks around the world that are helping with that co-sale process based on the solutions that we've jointly defined. Um, and then we also help build out the channel because as AWS, we've got tens of thousands of consulting partners. So the idea when you talk about that journey of becoming cloud native is how do you help a partner through that? You've got to hit on all three of those pillars to do it right. The leadership's got to be there for the top. Totally. You've got to have board alignment. You've got to have executive sponsorship, you've got to have technical buying, all of it. >>You guys have a very savvy customer base, Bray cloud native observability. What is the naivety uh, um, issue? What are people mostly naive about? Cause if you don't do it right with instrumentation observability if you're naive about that, you're going to get bitten in the, you know what? Well being, being naive there is not having your observability platform in place. So, but, but you really can't anymore. The old world of if you had a monolithic application running on servers monitoring, sometimes it was optional or a nice to have something today. You couldn't, you could only afford on your most mission critical applications as soon as you flipped a dev ops, a bunch of cloud native technologies, um, modern applications, but on the most modern frameworks with entities that are, that have all these dependencies to make sure that application works. Monitoring is a must, must have an observability is a must have. >>So that's now even in day one, out of the box, out of the one and two, the in to the reborn comment. As soon as you cross that path, you report, you rebirth yourself every day. Like it's constant. You're releasing code daily or multiple times a day, and so there's no like reborn statement anymore. It's a completely agile process. System changeover. This is not just saying it. You got to really believe what you're doing. You have to measure improvement, which is what new Relic is great at because if you take what's happening now on premise and you go to that transformation, you've got to show that you've actually achieved not just savings, but you're helping developers be more efficient and so you, you can't prove that story without the before and after. Yeah, yeah. Love talking to the cloud native gurus that you guys are, congratulations on your marketplace and ISV success. It's only getting the beginning of that run. It's kicking butt. Congratulations. Hundreds of thousands of customers are buying and hundreds of thousands more talk congratulates a new rule. Always great to have you guys on X. Great, impressive company, great results. Always great team, great product cloud, native ashore. Props to that. Thanks for coming on. Appreciate shit. Thanks so much. I'm John here in the cube, extracting the signal in the noise day. Two of three days of wall-to-wall coverage. Two sets here on the ground. Thanks for watching. We'll be right back.

>>From San Francisco. It's the cube covering PagerDuty summit 2019 brought to you by PagerDuty. >>Hey, welcome back everybody. Jeff Frick here with the Q. We're a PagerDuty summit. It's the fourth year of the show. He's been here for three years. It's amazing to watch it grow. I think it's finally outgrown the Western Saint Francis here in lovely downtown San Francisco and we're really excited to be joined by our next guest. He's Alex Solomon, the co founder, co founder and CTO PagerDuty. Been at this over 10 years. Alex, first off, congratulations. And what a fantastic event. Thank you very much and thank you for having me on your show. So things have changed a lot since we had you on a year ago, this little thing called an IPO. So I'm just curious, you know, we have a lot of entrepreneurs. I watch a show as a founder and kind of go through this whole journey. What was that like? What are some of the things you'd like to share from that whole experience? >>Yeah, it was, it was incredible. I I, the word I like to use is surreal. Like just kind of going through it, not believing that it's real in a way. And adjoining by my, my lovely wife who came, came along for this festivities and just being able to celebrate that moment. I know it is just a moment in time and it's not, it's not the end of the journey certainly, but it is a big milestone for us and uh, being able to celebrate. We invited a lot of our customers, our early customers have been with us for years to join us in that, a celebration. Our investors who have believed in us from back in 2010. Right, right. We were just getting going and we just, we just had a great time. I love it. I love 10 year overnight success. 10 years in the making. >>One of my favorite expressions, and it was actually interesting when Jenn pulled up some of the statistics around kind of what the internet was, what the volume of traffic was, what the complexity in the systems are. And it's really changed a lot since you guys began this journey 10 years ago. Oh, it has. I mean back then, like the most popular monitoring tool is Nagios and new Relic was around but just barely. And now it's like Datadog has kind of taken over the world and the world has changed. We're talking about not just a microservices by containers and serverless and the cloud basically. Right. That's the kind of recurring theme that's changed over the last 10 years. But you guys made some early bets. You made bets on cloud. He made bets on dev ops. He made bets on automation. Yeah, those were pretty good. >>Uh, those, those turn out to be pretty good places to put your chips. Oh yeah. Right place, right time and um, you know, some, some experiential stuff and some just some raw luck. Right. All right, well let's get into it. On top of some of the product announcements that are happening today, what are some of the things you're excited to finally get to showcase to the world? Yeah, so one of the big ones is, uh, related to our event intelligence release. Uh, we launched the product last year, um, a few months before summit and this year we're making a big upgrade and we're announcing a big upgrade to the product where we have, uh, related incidents. So if you're debugging a problem and you have an incident that you're looking at, the question you're gonna ask is, uh, is it just my service or is there a bigger widespread problem happening at the same time? >>So we'll show you that very quickly. We'll show you are there other teams, uh, impacted by the same issue and we'll, we, we actually leveraged machine learning to draw those relationships between ongoing incidents. Right. I want to unpack a little bit kind of how you play with all these other tools. We, you know, we're just at Sumo logic a week or so ago. They're going to be on later their partner and people T I think it's confusing. There's like all these different types of tools. And do you guys partner with them all? I mean, the integration lists that you guys have built. Um, I wrote it down in service now. It's Splunk, it's Zendesk, it goes on and on. And on. Yeah. So explain to folks, how does the PagerDuty piece work within all these other systems? Sure. So, um, I would say we're really strong in terms of integrating with monitoring tools. >>So any sort of tool that's monitoring something and we'll admit an alert, uh, when something goes down or over an event when something's changed, we integrate and we have a very wide set of coverage with all, all of those tools. I think your like Datadog, uh, app dynamics, new Relic, even old school Nagios. Right. Um, and then we've also built a suite of integrations around all the ticketing systems out there. So service now a JIRA, JIRA service desk, um, a remedy as well. Uh, we also now have built a suite of integrations around the customer support side of things. So there'll be Zendesk and Salesforce. That's interesting. Jen. Megan had a good example in the keynote and kind of in this multi system world, you know, where's the system of record? Cause he used to be, you want it, everybody wanted it to be that system of record. >>They wanted to be the single player in the class. But it turns out that's not really the answer. There's different places for different solutions to add value within the journey within those other applications. Yeah, absolutely. I, I think the single pane of glass vision is something that a lot of companies have been chasing, but it's, it's, it's really hard to do because like for example, NewRelic, they started an APM and they got really good at that and that's kind of their specialty. Datadog's really good at metrics and they're all trying to converge and do everything and become the one monitoring solution to the Rooney rule them all right. But they're still the strongest in one area. Like Splunk for logs, new Relic and AppDynamics for APM and Datadog for metrics. And, um, I don't know where the world's going to take us. Like, are they, is there going to be one single monitoring tool or are, are you going to use four or five different tools? >>Right. My best guess is your, we're going to live in a world where you're still gonna use multiple tools. They each can do something really well, but it's about the integration. It's about building, bringing all that data together, right? That's from early days. We've called pager duty, the Switzerland monitoring, cause we're friends with everyone when we're partners with everyone and we sit on top right a work with all of these different roles. I thought her example, she gave him the keynote was pretty, it's kind of illustrative to me. She's talking about, you know, say your cables down and you know, you call Comcast and it's a Zendesk ticket. But >>you know then that integrates potentially with the PagerDuty piece that says, Hey we're, you know, we're working on a problem, you know, a backhoe clipped the cable down your street. And so to take kind of that triage and fix information and still pump that through to the Zen desk person who's engaging with the customer to actually give them a lot more information. So the two are different tracks, but they're really complimentary. >>Absolutely. And that's part of the incident life cycle is, is letting your customers know and helping them through customer support so that the support reps understand what's going on with the systems and can have an intelligent conversation with the customer. So that they're not surprised like a customer calls and says you're down. Oh, good to know. No, you want to know about that urge, which I think most people find out. Oh yeah. Another thing >>that struck me was this, this study that you guys have put together about unplanned work, the human impact of always on world. And you know, we talk a lot in tech about unplanned maintenance and unplanned downtime of machines, whether it's a, a computer or a military jet, you know, unplanned maintenance as a really destructive thing. I don't think I've ever heard anyone frame it for people and really to think about kind of the unplanned work that gets caused by an alert and notification that is so disruptive. And I thought that was a really interesting way to frame the problem and thinking of it from an employee centric point of view to, to reduce the nastiness of unplanned work. >>Absolutely. And that's, that V is very related to that journey of going from being reactive and just reacting to these situations to becoming proactive and being able to predict and, and, uh, address things before they impact the customer. Uh, I would say it's anywhere between 20 to 40 or even higher percent of your time. Maybe looking at software engineers is spent on the some plant work. So what you want to do is you want to minimize that. You want to make sure that, uh, there's a lot of automation in the process that you know what's going on, that you have visibility and that the easy things, the, the repetitive things are easy to automate and the system could just do it for you so that you, you focus on innovating and not on fixing fires. Right? Or if you did to fix the fire, you at least >>to get the fire to the right person who's got the right tone to fix the type. So why don't we just, you know, we see that all the time in incidents, especially at early days for triage. You know, what's happening? Who did it, you know, who's the right people to work on this problem. And you guys are putting a lot of the effort into AI and modeling and your 10 years of data history to get ahead of the curve in assigning that alerted that triage when it comes across the, the, uh, the trans though. >>Yeah, absolutely. And that's, that's another issues. Uh, not having the right ownership, get it, getting people, um, notified when they don't own it and there's nothing they can do about it. Like the old ways of, of uh, sending the alert to everyone and having a hundred people on a call bridge that just doesn't work anymore because they're just sitting there and they're not going to be productive the next day I work cause they're sitting there all night just kind of waiting for, for something to happen. And uh, that's kinda the, the old way of lack of ownership just blasted out to everyone and we have to be a lot more target and understand who owns what and what's, what, which systems are being impacted and they only let getting the right people on the auto call as quickly as possible. The other thing that came up, which I thought, you know, probably a lot of people are thinking of, they only think of the fixing guy that has to wear the pager. >>Sure. But there's a whole lot of other people that might need to be informed, be informed. We talked about in the Comcast example that people interacting with the customer, ABC senior executives need to be in for maybe people that are, you know, on the hook for the SLA on some of the softer things. So the assembly that team goes in need, who needs to know what goes well beyond just the two or three people that are the fixing people? Right. And that's, that's actually tied to one of our announcements, uh, at summit a business, our business response product. So it's all about, um, yes, we notify the people who are on call and are responsible for fixing the problem. You know, the hands on keyboard folks, the technical folks. But we've expanded our workflow solution to also Lupin stakeholders. So think like executives, business owners, people who, um, maybe they run a division but they're not going to go on call to fix the problem themselves, but they need to know what's going on. >>They need to know what the impact is. They need to know is there a revenue impact? Is there a customer impact? Is there a reputational brand impact to, to the business they're running. Which is another thing you guys have brought up, which is so important. It's not just about fixing, fixing the stuck server, it's, it is what is the brand impact, what is the business impact is a much broader conversation, which is interesting to pull it out of just the, just the poor guy in the pager waiting for it to buzz versus now the whole company really being engaged to what's going on. Absolutely. Like connecting the technical, what's happening with the technical services and, and uh, infrastructure to what is the, the impact on the business if something goes wrong. And how much, like are you actually losing revenue? There's certain businesses like e-commerce where you could actually measure your revenue loss on a per minute or per five minute basis. >>Right. And pretty important. Yeah. All right Alex. So you talked about the IPO is a milestone. It's, it's fading, it's fading in the rear view mirror. Now you're on the 90 day shot clock. So right. You gotta keep moving forward. So as you look forward now for your CTO role, what are some of your priorities over the next year or so that you kind of want to drive this shit? Absolutely. So, um, I think just focusing on making the system smarter and make it, uh, so that you can get to that predictive Holy grail where we can know that you're going to have a big incident before it impacts our customers. So you can actually prevent it and get ahead of it based on the leading indicators. So if we've seen this pattern before and last time it causes like an hour of downtime, let's try to catch it early this time and so that you can address it before it impacts for customers. >>So that's one big area of investment for us. And the other one I would say is more on the, uh, the realtime work outside of managing software systems. So, uh, security, customer support. There's all of these other use cases where people need to know, like, signals are, are being generated by machines. People need to know what's going on with those signals. And you want to be proactive and preventative around there. Like think a, a factory with lots and lots of sensors. You don't want to be surprised by something breaking. You want to like get proactive about the maintenance of those systems. If they don't have that, uh, you know, like say a multi-day outage in a factory, it can cost maybe millions of dollars. Right. >>All right, well, Alex, thanks a lot. Again, congratulations on the journey. We, uh, we're enjoying watching it and we'll continue to watch it evolve. So thank you for coming on. Alright, he's Alex. I'm Jeff. You're watching the cube. We're at PagerDuty summit 2019 in downtown San Francisco. Thanks for watching. We'll see you next time.