(upbeat music) >> Welcome back to theCUBE's continuous coverage of AWS re:Invent 2021 I'm Lisa Martin. This is our third day here on set We've got two live sets, two remote studios, over a hundred guests on the program and a lot going on with AWS and its ecosystem of partners am pleased to welcome back one of our Cube alumni, Buddy Brewer, the GVP & GM of product partnerships at New Relic. Welcome back, Buddy. Good to have you. >> Thanks it's great to be here >> Great to be in an in-person event isn't? >> No kidding it's really amazing to see everybody out here and after spending so much time on zoom calls, we had a lot of really great moments among the team and the booth playing the game of seeing if people's height matched up with >> (laughs) >> What your expectation was because so many of the people we work with >> Never mind. >> We've only known over zoom. >> Yes ,and zoom has been a savior for all of us we've been doing so much recording on zoom at the same time it's great to be here in person and seeing what a safe job AWS has done with getting I from hearing upwards of 30,000 people in here that are here in person. So talk to me about you lead the technology partnerships at New Relic. Talk to me about your role, and then we'll get into the partnership with AWS. >> Yeah, absolutely. Well, you know, the point about zoom, it's fascinating. Like you said, that just having the ability to communicate with people has been such a key enabler of being able to make progress and to continue to lead our personal and our professional lives despite the pandemic I mean, imagine what it would have been like if this had happened 10 years ago, even, but certainly 50 years ago >> Right. or something like that, right? Like everything would have ground to a halt and technology took on such an amazing, you know, critical role in allowing us to do all of these things and so at New Relic, we're all about helping people make sure that all of this software works correctly. And so observability helps people understand the detail level about everything from the front end, the end user experience to every single piece that happens along the path of delivering that experience all the way down to the infrastructure into the network. But my role at New Relic is also to help all of the other tools that software developers use every day to create those experiences that they connect into their observability platform so that they can understand all of those details and make sure that people are able to continue doing things that have become really so basic to life like ordering groceries or getting food, or, you know, communicating with a loved one over something like zoom. >> Yeah the things that to your point, if this had happened, you know, five, 10 years ago, it would have been a completely different story. We've been able to function really well and one of the things too, that, you know, I noticed yesterday and today, you probably did as well with the plethora, typical AWS the plethora of announcements, the amount of innovation that's going on, the customer flywheel that we've just seen this acceleration of technology and what it's enabling, but the observability portion is really key you talk about, you know, the developers need to the whole SDLC they need to be able to understand exactly what's going on because at the end of the day, whether it's a consumer or an enterprise of the other end of the spectrum, we need to know exactly what's going on because people's patience is far thinner these days the pandemic showed is that there is really no having access to real-time data. Isn't a luxury anymore it's really a necessity. >> Right, yeah, absolutely. >> Talk to me about some of these so a lot of announcements coming up from AWS, you guys talk to me about the partnership, what you guys are doing there. And some of the things that are exciting on that front. >> Yeah, AWS is a really key partner for us. We're big users of AWS ourselves for our observability platform and all of our infrastructure and, you know, we've had our own journey as a 13 year old business that started out pre cloud and moving our own infrastructure to the cloud. And then along that journey, we've worked closely with AWS and we've built a lot of joint solutions to help people who are moving to the cloud themselves or who are cloud native to understand all of the details about what's happening in that software so we have over 60 different integrations to all of the different tools with Amazon that you can use on the cloud from data storage, to EKS on Fargate and all of that stuff. And then we recently announced a five-year strategic agreement with Amazon to make it even easier for customers to adopt New Relic if they're building in Amazon AWS and so you know, we're in their marketplace, we have an offering for startups, for people who are just getting started that, you know, provides really simple and fast on-ramps with discounts and things like that. That's all designed to help people, software developers in particular, focus on what matters most to them, which is building great experiences for their customers. You know, you mentioned that the SDLC and this is one of the things that, you know, our mission at New Relic is to make observability a daily data-driven habit for developers across all phases of the software delivery life cycle. The problem with observability and how it's used today is that it's only used in the run phase by most people they use it when the software is on fire to put the fire out we believe that, that telemetry has tremendous strategic value in the plan, build and deploy phases of software development as well. And so partnerships like AWS allow us to unlock the accessibility of that data across all of those different phases for people who software developers are as a result in many ways that the things that we were talking about earlier with the expectations that the pandemic has placed on how software has to work, it's not an option they're busier, they're under more pressure than they've ever been before and so we want to help them relieve that pressure with tools that help them do their jobs better. >> Relieving that pressure is key there is so much pressure on developers I mean, these days from observability to security and that sort of thing, but it sounds like one of the things that you're also fundamentally doing is really shifting that observability left and helping them from a cultural perspective, it seems like almost a shift, but you're trying to make things easier for them giving them more tools and to unlock what they're not seeing right now. >> That's right and you know, the interesting thing about it is everyone realizes that observability is critical to, you know, successful software businesses so for example, we did a survey recently of 1300 software developers and IT decision makers and executives, and found that among the C-level executives that were surveyed 80% of them expected to increase their observability budget and 20% of those expected to increase it significantly. However, that same survey found that a very small percentage of those who we actually surveyed feel that they have a mature observability practice today. And when we unpack the reasons why in the survey, we found that most of them reduce down to basically this issue of they just don't have enough time to instrument all of the software, especially in a world where the shift to the cloud has driven a change in architecture where monoliths have been torn down and replaced by hundreds, or may be even thousands of microservices. >> Right. >> And we're in an era now where if observability isn't really, really easy and incredibly fast and simple to execute on then software developers can no longer instrument fast enough to keep up with the pace of the software that they're delivering and so what that leads to is visibility gaps, visibility gaps lead to poor customer experiences. And so what we're trying to do, and we've been on this massive simplification of our own platform to make it, you know, incredibly cost-effective at just 25 cents a gigabyte for ingestion and really simple licensing seat based licensing, where you get access to all of our tools to make it really simple and to take simply minutes to get observability on all those different pieces. >> If simplicity is a word that we throw around a lot, but it's really critical element and it's interesting to understand how do you actually facilitate that? You talked about, you know, kind of the 80 20 rule there. >> Yeah. >> A lot of the organization's not on that maturity curve with observability, how does New Relic and its ecosystem of partners like AWS how do you help have those conversations within organizations in any industry tell them, understand how you can actually simplify that and unlock that visibility, knowing that it's not only a matter of software development, but it's a competitive differentiator. It's also something that can damage a brand if they're not top of it. >> Yeah, we launched a re-imagined version of our partner ecosystem really our entire integration ecosystem about six weeks ago on October 13th called New Relic Instant Observability. And one of the central goals of New Relic IO, which we call it for short is to make it take just like five minutes for people to instrument something. So in the old way, what people had to do is if they wanted observability, they had to go learn about an observability vendor then they had to go install it, figure out how all that works and then they could get to solving their problem, which might've just been simply instrumenting a Kafka you know and so what we want to do is just keep people in that mode if all you wanted to do is instrument Kafka, then go find the Kafka instrumentation tile on New Relic and observability and then there's a guided install process that takes you through that and at the end you've instrumented Kafka and if you want to add something else like EKS Fargate from Amazon, or if you want to add something else like a Java service, you can simply click more of those guidance installs and add within minutes in an incremental way without having to stop and do a whole vendor evaluation to do so in fact, one of the other things that we launched recently is a free tier that's free forever. So there's no trial process or anything you don't have to put in a credit card if all you want to do is instrument this one thing right now, you can go through this process provision a free account you get access to all of our functionality for one user and ingest up to a hundred gigabytes of telemetry data for free within minutes. And so what we're trying to do is take all of that adoption friction out so that people aren't fighting with their instrumentation so much, and again, they can get back to doing what they really want to do in the first place, which has built great experiences for their end users. >> Great experiences for the end users but that translates to employee experience that translates to an end user customer experience, which translates back to brand reputation. I'm just wondering, you know, you're focused on the developers and we've been hearing a lot about the last two and a half days, a big focus on developers has observability kind of escalated up and its evolution up the stack within organizations is this a C-suite concern? Is this a board level concern? where does this fit now? and what's the vision of New Relic to deliver on that? >> With observability? >> Yes. >> Yeah, 90% of those in the survey that I was talking about felt that observability was not just a tool that they needed to use, but strategically critical to their business and, you know, this goes back to, as we know, and especially as a result of the intensity on the importance of software coming out of the pandemic, your digital business is your business these days. And so if you don't understand what's happening in that software and you can't move quickly, then you know you're really in trouble in terms of trying to succeed in a highly competitive environment and that goes back to again, one of our core beliefs is that all of this telemetry data that people have been collecting about how their software operates is so useful in contexts outside of just when there's a problem in production. Imagine if you could take that information and you could actually put it inside the IDE, which is something that we did with a recent acquisition of a company called CodeStream. We can take this telemetry data and put it inside the IDE so that as developers are writing the software, they know where those issues are. You can click straight from a stack frame, for example, inside of our, where we show all of our errors in a capability called Error's inbox and shoot right into your IDE and go see where the line of code is that caused that error, shortening that feedback loop and unlocking this really big investment that a lot of companies make in telemetry data earlier in the software life cycle, we believe is the future of observability and we want to help people get there. >> Well, the observability is really key for organizations these days because we've been hearing every company these days has to be a data company. >> Yeah. >> And it's one thing to say that it's a whole other thing to be able to implement it and observability is absolutely critical to that as being able to take that data and apply it in different contexts to really enable that business to be digital which is absolutely table-stakes these days to be successful and to deliver that customer experience ultimately. >> Yeah. >> That's what it all do. >> Yeah, absolutely. And you know, the other thing is really hard about this problem when I talk with our customers and we found this in the survey as well, is that, you know, software developers, don't just use one tool to create software they use a lot of tools in fact, 13% of those that we surveyed use 10 or more tools. >> Whoa. >> Just for the observability piece. And so, you know, obviously we're always trying to expand organically what we do inside of our platform to cover more and more use cases, but an equally important part of our strategy, if we really want to make observability a data-driven daily habit for people is to find all of those other, you know, really well-built amazing tools that those developers use and find valuable ways to integrate with them. And so that's the other part of our ecosystem that we've built out is this ability to take all of the other tools that you use and wire them into New Relic so that, for example, if you're using, let's say Lacework for security then you can, you know, if someone's installed a Bitcoin miner on your infrastructure somewhere, you can quickly navigate because of that integration from a poor customer experience through the infrastructure that's suffering may be with, you know, a lot of memory pressure, and a lot of CPU being used for this Bitcoin miner and then find out that, you know, through the integration where the miner was installed, how it got installed so that you can remediate those types of issues and connecting those pieces together, making software truly interoperable is another thing that's really critical to our mission at New Relic. >> It is critical to not only to the developers, but to the organizations and their success as businesses these days Buddy thank you for joining me, talking about what's going on at New Relic What's new, how you're really empowering those developers and all of the downstream positive effects that, that leads to we appreciate your time. >> Thank you ,thanks for having me. >> All right, you are Buddy Brewer I'm Lisa Martin you're watching theCUBE, the global leader in live tech coverage. (soft music)

>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS and our community partners. >>Hello and welcome to the Cube virtual here with coverage of aws reinvent 2020. I'm your host, Justin Warren. And today I'm joined by J. Snyder, who is the chief chief customer officer at New Relic J. Welcome to the Cube. >>It is fantastic. Me back with the Cube. One of my favorite things to do has been for years. So I appreciate you having me. >>Yes, a bit of a cube veteran. Been on many times. So it's great to have you with us here again. Eso you've got some news about new relic and and Amazon away W s strategic collaboration agreement. I believe so. Maybe tell us a bit more about what that actually is and what it means. >>Yes. So we've been partners with AWS for years, but most recently in the last two weeks, we've just announced a five year strategic partnership that really expands on the relationship that we already had. We had a number of integrations and competencies already in place, but this is a big deal to us. and and we believe a big deal. Teoh A W s Aziz Well, so really takes all the work we've done to what I'll call the next level. It's joint technology development where were initially gonna be embedding new relic one right into the AWS management console for ease of use and really agility for anyone who's developing and implementing Ah cloud strategy, uh, big news as well from an adoption relative to purchase power so you can purchase straight through the AWS marketplace and leverage your existing AWS spend. And then we're gonna really be able to tap into the AWS premier partner ecosystem. So we get more skills, more scale as we look to drive consulting and skills development in any implementation for faster value realization and overall success in the cloud. So that's the high level. Happy to get into a more detailed level if you're interested around what I think it means to companies but just setting the stage, we're really excited about it as a company. In fact, I just left a call with a W S to join this call as we start to build out the execution plan for the next five years look like >>fantastic. So for those who might be new to new relic and aren't particularly across the sort of field of observe ability, could you just give us a quick overview of what new relic does? And and then maybe talk about what the strategic partnership means for for the nature of new relics business? >>Yes, so when I think about observe ability and what it means to us as opposed to the market at large, I would say our vision around observe ability is around one word, and that word is simplification. So, you know, I talked to a lot of customers. That's what I do all the time. And every time I do, I would say that there's three themes that come up over and over. It's the need to deliver a customer experience with improved up time and ever improving importance. It's the need to move more quickly to public cloud to embrace the scale and efficiency public cloud services have to offer. And then it's the need to improve the efficiency and speed of their own engineering teams so they can deliver innovation through software more quickly. And if you think about all those challenges And what observe ability is it's the one common thread that cuts across all those right. It's taking all of the operational data that your system admits it helps you measure improve the customer, experience your ability to move to public cloud and compare that experience before you start to after you get there. The effectiveness of your team before you deploy toe after you get there. And it's all the processes around that right, it helps you be almost able to be there before your there there. I mean, if that makes sense right, you'll be able to troubleshoot before the event actually happens or occurs. So our vision for this is like I talked about earlier is all about simply simplification. And we've broken this down into literally three piece parts, right? Three products. That's all we are. The first is about having a much data as you possibly can. I talked about admitting that transactional telemetry data, so we've created a telemetry data platform which rides on the world's most powerful database, and we believe that if we can take all of that data, all that infrastructure and application data and bring it into that database, including open source data and allow you to query it, analyze it and take action against it. Um, that's incredibly powerful, but that's only part one. Further, we have a really strong point of view that anybody who has the ability to break production should have the ability to fix production. And for us, that's giving them full stack observe ability. So it's the ability to action against all of that data that sits in the data platform. And then finally, we believe that you need to have applied intelligence because there's so many things that are happening in these complex environments. You wanna be able to cut through the noise and reduce it to find those insights and take action in a way that leverages machine learning. And that, for us, is a i ops. So really for us. Observe ability. When I talked about simplification, we've simplified what is a pretty large market with a whole bunch of products, just down to three simple things. A data platform, the ability to operationalize in action against that data and then layer on top in the third layer, that cake machine learning so it could be smarter than you can be so it sees problems before they occur. And that And that's what that's what I would say observe, ability is to us, and it's the ability to do that horizontally and vertically across your entire infrastructure in your entire stack. I hope that makes sense. >>Yeah, there's a lot of dig into there, So let's let's start with some of that operational side of things because I've long been a big believer in the idea of cloud is being a state of mind rather than a particular location on. A lot of people have been embracing Cloud Way Know that for we're about 10 or so years. And the and the size of reinvent is proven out how popular cloud could be. Eso some of those operational aspects that you were talking about there about the ability to react are particularly like that. You you were saying that anyone who could break production should be able to fix production. That's a very different way of working than what many organizations would be used to. So how is new relic helping customers to understand what they need to change about how they operate their business as they adopt some of these methods. >>Well, it's a great question. There's a couple of things we do. So we have an observe ability, maturity framework by which we employ deploy and that, and I don't want to bore the audience here. But needless to say, it's been built over the last year, year and a half by using hundreds of customers as a test case to determine effectively that there is a process that most companies go through to get to benefits realization. And we break those benefit categories into two different areas, one around operational efficiency and agility. The other is around innovation and digital experience. So you were talking about operational efficiency, and in there we have effectively three or four different ways and what I call boxes on how we would double, click and triple click into a set of actions that would lead you to an operational outcome. So we have learned over time and apply to methodology and approach to measure that. So depending on what you're trying to do, whether it's meantime to recover or meantime, to detect, or if you've got hundreds of developers and you're finding that they're ineffective or inefficient and you want to figure out how to deploy those resource is to different parts of the environment so you can get them to better use their time. It all depends on what your business outcome and business objective is. We have a way to measure that current state your effectiveness ply rigor to it and the design a process by using new relic one to fill in those gaps. And it can take on the burden of a lot of those people. E hate to say it because I'm not looking to replace any individual. It's really about freeing up their time to allow them to go do something in a more effective and more effective, efficient manner. So I don't know if that's answering the question perfectly, but >>e don't think there is a perfect answer to its. Every customer is a bit different. >>S So this is exactly why we developed the methodology because every customer is a little different. The rationale, though, is yeah, So the rationale there's a lot of common I was gonna say there's a lot of common themes, So what we've been able to develop over time with this framework is that we've built a catalog of use cases and experiences that we can apply against you. So depending on what your business objectives are and what you're trying to achieve, were able to determine and really auger in there and assess you. What is your maturity level of being able to deliver against these? Are you even using the platform to the level of maturity that would allow you to gain this benefit realization? And that's where we're adding a massive amount of value. And we see that every single day with our customers who are actually quite surprised by the power of the platform. I mean, if you think traditionally back not too far, two or even three years. People thought of new relic as an a P M. Company. And I think with the launch this summer, this past July with new relic one, we've really pivoted to a platform company. So while a lot of companies love new relic for a PM, they're now starting to see the power of the platform and what we can do for them by operationally operationalize ing. Those use cases around agility and effectiveness to drive cost and make people b'more useful and purposeful with their time so they can create better software. >>Yeah, I think that's something that people are realizing a lot more lately than they were previously. I think that there was a lot of TC analysis that was done on a replacement of FTE basis, but I think many organizations have realized that well, actually, that doesn't mean that those people go away. They get re tasked to do new things. So any of these efficiency, you start with efficiency. And it turns out actually being about business agility about doing new things with the same sort with the same people that you have who now don't have to do some of these more manual and fairly boring tasks. >>Yeah, just e Justin. If this if this cube interview thing doesn't work out for you were hiring some value engineers Right now it sounds like you've got the talk track down perfectly, because that's exactly what we're seeing in the market place. So I agree. >>So give us some examples, if you can, of maybe one or two off things that you've seen that customers have have used new relic where they've stripped out some of that make work or the things that they don't really need to be doing. And then they're turning that into new agility and have created something new, something more individual. Have you got an example you could share with us? >>You know, it's it's funny way were just I just finished doing our global customer advisory boards, which is, you know, rough and tough about 100 customers around the world. So we break it into the three theaters, and we just we were just talking with a particular customer. I don't want to give their name, but the session was called way broke the sessions into two different buckets, and I think every customer buys products like New Relic for two reasons. One is to either help them save money or to help them make money. So we actually split the sessions into those two areas and e think you're talking about how do we help them? How do we help them save money? And this particular company that was in the media industry talked at great length about the fact that they are a massive news conglomerate. They have a whole bunch of individual business units. They were decentralized and non standardized as it related to understanding how their software was getting created, how they were defining and, um, determining meantime to recover performance metrics. All these things were happening around them in a highly complex environment, just like we see with a lot of our customers, right? The complexity of the environments today are really driving the need for observe ability. So one of the things we did with them is we came in and we apply the same type of approach that we just discussed. We did a maturity assessment for them, and we find a found a variety of areas where they were very immature and using capabilities that existed within the platform. So we're able to light up a variety of things around. Insights were able to take more data in from a logging perspective. And again, I'm probably getting a little bit into the weeds for this particular session. But needless to say, way looked at the full gamut of metrics, events, logs and traces which was wasn't really being done in observe, ability, strategy, manner, and deploy that across the entire enterprise so created a standard platform for all the data in this particular environment. Across 5th, 14 different business units and as a byproduct, they were able to do a variety of things. One, the up time for a lot of their customer facing media applications improved greatly. We actually started to pivot from actually driving cost to showing how they could quote unquote make money, because the digital experience they were creating for a lot of their customers reduced the time to glass, if you will, for clicking the button and how quickly they could see the next page, the next page or whatever online app they were looking to get dramatically. So as a byproduct of this, they were about the repurpose to the point you made Justin. Dozens of resource is off of what was traditionally maintenance mode and fighting fires in a reactive capability towards building new code and driving new innovation in the marketplace. And they gave a couple of examples of new applications that they were able to bring to market without actually having to hire any net New resource is so again, I don't want to give away the name, the company, it maybe it was a little too high level, but it actually plays perfectly into exactly what what you're describing, Um, >>that is a good example of one of those that one of the it's always nice to have a specific concrete customer doing one of these kinds of things that you you describe in generic terms. Okay. No, this is this is being applied very specifically to one customer. So we're seeing those sorts of things more and more. >>Yeah, and I was gonna give you, you know, I thought about in advance of this session. You know, what is a really good example of what's happening in the world around us today? And I thought of particular company that we just recently worked with, which is check. I don't know if you're familiar with keg, if you've heard of them. But their education technology company based in California and they do digital and physical textbook rentals. They do online tutoring an online customer services. So, Justin, if you're like me or the rest of the world and you have kids who are learning at home right now, think about the amount of pressure and strain that's now being put on this poor company Check to keep their platform operational 24 77 days a week. So that students can learn at pace and keep up right. And it's an unbelievable success story for us and one that I love, because it touches me personally because I have three kids all doing online, learning in a variety of different manners right now. And, you know, we talked about it earlier. The complexity of some of the environments today, this is a company that you would never gas, but they run 500 micro services and highly complex, uh, technical architectural right. So we had to come in and help these folks, and we're able to produce their meantime to recover because they were having a lot of issues with their ability to provide a seamless performance experience. Because you could imagine the volume of folks hitting them these days on. Reduce that meantime to recover by five X. So it's just another example we're able to say, you know, it's a real world example. Were you able to actually reduce the time to recover, to provide a better experience and whether or not you want to say that saving money or making money? What I know for sure is is giving an incredible experience so that folks in the next generation of great minds aren't focused on learning instead of waiting to learn right, So very cool. >>That is very cool. And yes, and I have gone through the whole teaching kids >>about on >>which is, uh, which it was. It was disruptive, not necessarily in a good way, but we all we adapted and learned how to do it in a new way, which is, uh, it was a lot easier towards the end than it was at the beginning. >>I'd say we're still getting there at the Snyder household. Justin, we're still getting >>was practice makes perfect eso for organizations like check that who might be looking at JAG and thinking that that sounds like a bit of a success story. I want to learn more about how new relic might be able to help me. How should they start? >>Well, there's a lot of ways they can start. I mean, one of the most exciting things about our launch in July was that we have a new free tier. So for anybody who's interested in understanding the power of observe ability, you could go right to our website and you can sign up for free and you can start to play with new relic one. I think once you start playing for, we're gonna find the same thing that happens to most of the folks to do that. They're gonna play more and more and more, and they're gonna start Thio really embrace the power. And there's an incredible new relic university that has fantastic training online. So as you start to dabble in that free tier, start to see with the power and the potential is you'll probably sign up for some classes. Next thing you know, you're often running, so that is one of the easiest ways to get exposed to it. So certainly check us out at our website and you can find out all about that free tier. And what observe ability could potentially mean to you or your business. >>And as part of the AWS reinvent experience, are they able to engage with you in some way? >>It could definitely come by our booth, check us out, virtually see what we have to say. We'd love to talk to them, and we'd be happy to talk to you about all the powerful things we're doing with A. W. S. in the marketplace to help meet you wherever you are in your cloud journey, whether it's pre migration during migration, post migration or even optimization. We've got some incredible statistics on how we can help you maximize and leverage your investment in AWS. And we're really excited to be a strategic partner with them. And, you know, it's funny. It's, uh, for me to see how observe ability this platform can really touch every single facet of that cloud migration journey. And, you know, I was thinking originally, as I got exposed to this, it would be really useful for identity Met entity relationship management at the pre migration phase and then possibly at the post migration flays is you try to baseline and measure results. But what I've come to learn through our own process, of moving our own business to the AWS cloud, that there's tremendous value everywhere along that journey. That's incredibly exciting. So not only are we a great partner, but I'm excited that we will be what I call first and best customer of AWS ourselves new relic as we make our own journey to the cloud >>or fantastic and I'm I encourage any customers who might be interested in new relic Thio definitely gone and check you out as part of the show. Thank you. J. J. Snyder from New Relic. You've been watching the Cube virtual and our coverage of AWS reinvent 2020. Make sure that you check out all the rest of the cube coverage of AWS reinvent on your desktop laptop your phone wherever you are. I've been your host, Justin Warren, and I look forward to seeing you again soon.

>>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.

>> Narrator: From New York City, it's theCUBE, covering New Relic FutureStack 2019, brought to you by New Relic. >> Hi, I'm Stu Miniman and this is theCUBE at New Relic FutureStack 2019 here in New York City. It's our first year of the event, but the event itself has been around for seven years and to help us end our coverage, no better person than the founder and CEO of New Relic, and the one who the name of the company came from, Lew Cirne. Of course, Lew Cirne is an anagram for New Relic. >> Indeed it is. >> Lew, thank you so much for having theCUBE at the event here and thanks for hosting us. >> I'm a huge fan of theCUBE. I've been watching it for a long time and it's such a pleasure to have you guys here. Thank you for coming. >> All right, so Lew, you're known as the coding CEO >> Lew: I am. >> And you come out with a vision of making software better. It's a great goal. Give us a little bit about the state of the industry. You know the internet challenge these days. It's going to fragment into a bunch of pieces and Open Source isn't what it used to be. There's so many changes going in the industry. Just kind of macro view before we get into New Relic. >> Yeah, from a macro view at New Relic we do this for the love of software. It's not just me, it's the whole company. We believe in software. We think it unquestionably is changing the world, transforming every industry. It's not enough just to build software that's great. You have to deliver more perfect software. That's now become almost obvious whereas when we first started out that was actually a bit of an evangelical sale where we had to convince people that they needed to observe their software. Now it's become a must-do thing, and that's why observability has become a household term. Everybody recognizes that anything that runs in production in internet scale needs to be observed, needs to be measured in real time. And so, that's been going on and has become a must-do thing for our customers. What we're so excited about is that we're delivering the first observability platform. What do we mean by that? Well, we see with this proliferation of tools, you might have metrics going to one place and logs going to another place and traces going to Zipkin or logs going to Elasticsearch. You want it all in one place, and more important, you want it to be connected so that you can see the relationship between the application and its server or infrastructure and the user experience all in one connected platform. That's what we're delivering with New Relic One today that's so exciting. >> Yeah. So, Lew, the IT industry in general is known for its fragmentation. >> Lew: Yeah, it is. >> When I want to build my application in the old days, I talk to the CIO. He's like, "Give me a million dollars and 18 months "and I will build you the Taj Mahal of my application." And we've got it beautifully designed and pull it out. Well, today things are moving much faster, but I've got everything from that Taj Mahal to the Kubernetes and Serverless, Microservice Architectures-- >> Lew: All that compartment-based stuff, yeah. >> There's usually a lot of different teams, and a lot of different tools in there. How does New Relic fit across that landscape and how are you helping to pull things together? >> Well, certainly the industry's moving from the monolithic application to the component-based application, often running in smaller and smaller services, usually running in something like Kubernetes or a containerized environment and with that comes a proliferation of things to monitor, and often a proliferation of tools. We have enterprise customers that have 20, 30 different monitoring and telemetry tools. It's not because they want it, it's because there might be one particular feature that one tool does that gives them the visibility they need. And what they want is a single platform. What people have historically used New Relic for is dropping our agents into their application or their infrastructure. Then our agents automatically put visibility in and then they report on the health of that system. We do that really well, but what we're announcing today is that we're opening up our platform to consume telemetry from Open Source, agentless sources. So that, if you've got something like Prometheus that's gathering data from Kubernetes, that can go straight into New Relic and be treated as first class data, so that you don't have to switch between a bunch of tools. None of our customers want that. They want it all in one place, but they need an open platform that's connected and most importantly programmable so that they can actually have one tool to see it all. And that's New Relic. >> A lot of the logging and tracing information out there isn't agent-led. What do you see as the future of agents, and what are some of the challenges of pulling all of these various data types together? >> Well, the most important thing for the future is that our customers have complete control in a choice. What we see particularly in large enterprises is they want both. They have a portfolio of more than a thousand applications. They want to observe them all. Most of them they'll want to drop an agent in because they don't have time to reinstrument them, but they still need to see them. Some of them they may want to manually instrument because they want a higher level of control or they want to adopt an Open Source API like OpenTelemetry. But then, if they're adopting that for some of their portfolio, when a transaction reaches across these different services, you don't want to lose visibility. We're delivering best of both worlds. You can manually instrument what you want. You can use OpenTelemetry in parts of your environment. And then you can also use our automatic instrumentation that comes from our agents. Our customers get to decide, and that's the future. >> So, Lew, you've laid out the case in a strong way as to why New Relic One should be the platform for the monitoring observability. I think you undersold a little bit the NRDB piece. When I look inside my business or I talk to customers, being able to see my data and act on my data can be challenging. You showed a demo of 10 terabytes and being able to change it in a snap. >> You know, NRDB is pretty magical. At some risk, let's see if this will show up on my phone right now. Just give you a sense of how fast NRDB is performing right now. Okay. One more time. So we've got-- >> Hold it up a little bit and show the camera this way. >> NRDB right at this moment is inserting 18 million events every second. Every second, 17.89 million pieces of data coming into NRDB in real time. And our customers are querying that in real time. Right now, in this moment, they're reading 24 billion pieces of data per second. Those pieces of data could be log messages. They could be someone pressing something on their app, could be a request going through a server. It's all in the same database. And the last one is a hundred millisecond response time on those queries, which is mind-blowing for these analytics queries. >> You actually showed the press an analyst this at lunch and it was over 20 million-- >> I think it was at 40 billion at that moment. >> 40 billion coming out and the same response time. A hundred milliseconds is Google good as to how fast I get a response. >> For this kind of data processing, it's mind-blowing. Now, the thing that our customers need to know is that all your metrics, all your events, all your logs, all your traces going into the same database with one query language. That's so much better than going to Elasticsearch and using its query language for logs, then using a totally different query language for getting at your metrics, and then trying to stitch it all together. We put it all not only in one cloud but in one database. That is the most powerful telemetry database in the world, which is NRDB. >> Lew, give us a little bit of the journey to the announcement today. Observability's been talked about in the industry for a while. VC money has been pouring into startups. There's been some acquisitions in this space already. Give us a little bit as to how we got to today. >> So how we got to today was when we started off as a company, we were championing the whole idea of observability, putting visibility into application code. As I said, that was a bit evangelical in the early days. People were wondering if they needed it. Now there's no question they need it. In fact, some people need it so badly they want complete control, and so they're manually instrumenting. OK, I've talked about that. Now where we see people going is now that all of this telemetry data is coming ideally into one place like New Relic, our customers are saying, "I need to go beyond dashboards. "Dashboards are good, but often dashboards are incomplete "to get the most out of the data we're collecting." That's why we're claiming we have the first and only platform for observability, with a capital P. What do I mean by that? It's only a platform if you can build software on it, and New Relic One is the first software development platform for observability applications. Our customers can take all this data and build real-time applications that leverage all the value out of it. When a customer buys something online, New Relic's database could be the first piece of, certainly, analytics database that sees that data. So you could a navigation that shows real-time sales for your business people all based on New Relic One. We can also solve all sorts of IT operations problems by building applications on this platform. And to prove it out, we're offering 12 free Open Source applications to anyone. They can download, they can clone them off of GitHub and push them into their New Relic account and they can use that as inspiration to build their own applications on top of our platform. >> Right. This is, if I understand, the first twelve, and you expect both New Relic and your customers will build many more. >> Yes, and actually it's thirteen already. We just added another one today. Some of those have been built by our customers already, and we're already seeing customers deploying these applications into their New Relic One accounts in production today. >> It really goes back to the promise of SaaS is that when customers need something and make a change or build on it, it's not just that customer that gets to be able to leverage that, but everybody else that is on the platform-- >> They can share and benefit. The way to think of it is, you're absolutely right, and without Force.com, Salesforce is just a CRM system. But with Force.com, companies could really leverage all the data inside Salesforce. Without programmability, ServiceNow is just a ticketing system, right? But how does ServiceNow become strategic? By allowing people to build applications tailored to their business. We believe the world needs an observability platform and the only one of its kind is New Relic One. >> All right. So, Lew, it sounds like this should be something that should accelerate growth for the company going forward. I read through your last earnings report. You're growing at 30, 35%, which is reasonable but less than the overall cloud marketplace itself is growing. So, how come the AWS, Azure, GCP tailwind isn't pushing New Relic faster? >> Well, it is a good tailwind for us, and I can't go into too much detail. We're a public company in a quiet period so I can't speak to specifics. What I can tell you is history has shown that people tend to adopt platforms at a certain rate and then, a few years later, they adopt the management technologies for those platforms. So we tend to be a little bit behind the adoption of cloud but then when people standardize and they go all in on it, then they really increase their investment in New Relic. I believe that things like our platform capabilities take our customers that might be spending... We have 850 plus customers that spend more than 100,000 a year with New Relic, and I believe when they start to adopt our platform and go strategic with us, many of them will be million-dollar customers, and that ought to be the basis of durable growth for the company. >> All right. So, Lew, there was some news leading up to the event. Some management changes. Let you speak a little bit of that, and you've got some history with, of course, Mike was already on the board, but-- >> We're so thrilled about Mike Christenson joining the company as President and COO. I've known Mike since 2006, when he acquired my last company, Wily Technology, which was really the very first APM company. Mike was the President and COO of CA, and so he had a similar role there to what he has here. Mike is, I think, one of the most brilliant operational minds I've ever met. He's been involved with New Relic for nine years. He's been one of the first investors in the company. He's been on our board of directors, and he's always had a keen mind for how to think about growing our business. I've been thinking for a long time on how to get him more involved as a member of the team and finally I convinced him to come join. Mike joined us as our President and COO. He's going to be my partner in growing the business. I think those that know me know that I love technology and products and thinking about where we are five years from now. Mike will be my partner to help make sure we're operating the company and growing the business on a day-to-day basis. >> Lew, you and your team helped create and democratize this wave of APM, Application Performance Management. As you look at it today, we talked about microservices. You talk about the dispersed nature of everything going on. How would you reframe the market today and New Relic, where it needs to be today and going forward? >> Phase 0 was people-monitored servers, back in the Stone Ages. Monitoring was just "Is the server up or down "and does it have enough CPU?" >>Blinking lights. >> Right. Then came APM. APM really was the precursor to observability. It was the notion that these are complex systems. They need to be observed at high granularity. APM gave birth to observability, so when New Relic first came along, we're "Let's democratize APM." And as observability came along, we saw this as an opportunity to open up the platform. Now where we are, if you look at our track record, first of all, my first company created the category of APM. New Relic then democratized APM, and now we're delivering the first observability platform. I believe that the future is programmable, and that New Relic is the future. >> Lew, you've always been enthusiastic when it comes to the vision that you put out, but it's been noted by some of my peers that your energy level and enthusiasm is even higher today than usual. So many things that you talked about, some of the things that you highlight, maybe behind the scenes, or things that might get missed beyond the headlines that you want to share. >> The idea for New Relic One was born two years ago. I took some of the brightest people in New Relic offsite and we fleshed out the thinking and the early prototype of what's become this. This is my life's work. This company's my life's work. I believe so much in this platform. I believe in its capabilities. I'm seeing our customers ripping it out of our hands, saying, "This is going to enable us "to fully achieve our goal of complete visibility "and completely tailored to the needs of our business." Why I'm so fired up and passionate is when you put your heart and soul into something that's new, that no one else has done before... There's been a handful of times I've done that in my life. The first time became APM. The second time became New Relic. The third was when I created NRDB. And now the fourth is New Relic One. And we're just getting started. >> Well, Lew, I want to let you have the final word as to what you want your customers taking away here from FutureStack 2019. >> My belief is that the future of observability is you need a platform. That platform needs to be open, connected, and programmable. We have such a beautiful, easy... It's a Heroku-like developer experience. So within seconds, you can be building an application that takes the telemetry data in New Relic and turns it into actionable business insights for your company. And if you want inspiration, there's 13 applications now up on GitHub that you can install right into your New Relic account, and maybe modify and tailor to your needs and republish to share with our other customers. >> I know you and your team are making sure that New Relic doesn't become a relic of the past. Thank you so much for having us here-- >> We're always in the future. >> And congratulations. I look forward to watching the progress going forward. >> Thank you, I enjoyed it. Thank you. All right, bye-bye. >> Thank you so much. And that's a wrap theCUBE's coverage of New Relic FutureStack 2019. I'm Stu Miniman, of course. Go to theCUBE.net for all of the coverage. A big thanks to the team here and everyone supporting and as always, thank you for watching theCUBE. (Electronic Music)

(electronic music) >> From New York City, it's theCUBE. Covering, New Relic Futurestack 2019. Brought to you by New Relic. >> Hi, I'm Stu Minamin and we're here at New Relic's Futurestack 2019 in the middle of Manhattan. Right next door to Grand Central Station at the Grand Hyatt. Right next door to Grand Central Station at the Grand Hyatt. Happy to welcome to the program, first time guest, Nadya Duke Boone, who's the vice president and general manager of application monitoring here at New Relic. Thanks so much for joining us. >> You're welcome, it's great to be here. >> All right, so, a lot of announcements this morning. Of course, observability front and center Lou talking about how that fits into this space. You have handled really kind of the APM product inside New Relic, so I'm hoping you can help us understand kind of the journey that New Relic's going on. And I've heard in the marketplace, you know, there's AI ops, and there's observability in all of these things. And, you know, APM was the old world for the monolith. So, you know, how does New Relic help live across all of these environments that customers are living in today, and you know, undergoing so much change and new things? >> So as Lou talked about this morning, we think to be an observability platform like New Relic 1, you've got to be open, connected and programmable. That is, we think about that within the application monitoring space, um, we really think it comes down to the matter and issue of like, what are the questions you need to ask. And that really depends on like what stacks you need to see and what are the questions you need to ask. And so, I think it's a false dichotomy to say you need to like, pick a side in observability or monitoring. I think it's really a yes/and. You don't have to pick a side. And with New Relic, what we're able to do whether using our agents and all the rich data they give you or they're using our open platform, the important thing is that we're able to bring it all together in one place. So you can get all your questions answered. >> Yeah, I spent lots of time in my career trying to help break down silos. You know, the traditional infrastructure world, the networking and storage and compute teams. >> Sure >> You know, virtualization helped pull some things together. Software tends to be a unifying factor, but when I look at, you know, the people that own application and the developers. I mean, you've got monoliths, you've got this containerization in microservices coming. You've got the new serverless environments here. You've got a lot of fragmentation inside the customers. How does that impact your business today and are we going to see those, you know, pulled together over time? >> Yeah, what we hear from customers is that, you know, they're going to be running heterogenius environments for a long time. If you're over a year old company, you're not running a single tech stack. You've made choices for your business needs and you need to be able to see across your whole estate. And where New Relic's adding value for our customers, is by bringing this all together and connecting it. So, you can actually see, let's say from a lambda function and our lambda agents, all the way back through your Java monolith and down to the server whether it's running containers or on bare metal, you can see all the way down. And then you can connect it out to you front end as well. And I think it's that ability to see across, is where we're playing. >> All right, uh, can you bring us inside your customers? What are some of the challenges they're facing? And how do you help them along those transformations that they're undergoing? Cause, as you've said, they're going to have this heterogenius environment for quite a long time. >> Yeah, well I think one of the thing they're saying is that they're trying to move faster. And one of the ways they're moving faster is by changing the process by which they build software. So, you know, we've been talking about DevOps for years. We've been talking about Agile for much longer than years. Um, but those changes bring about new needs also, for observability. Cause now, you've got a team that maybe wants to see very deeply with, um, the things they're on call for. But software refuses to break neatly at team boundaries. It just won't, it's going to break wherever it wants to break. So you need to be able to quickly assess, across your whole enterprise what's going on and help those teams talk to you. So, that's definitely a problem we're solving for our customers now. And if I were to pick one more, that I'm hearing, um, well, I'll pick one from this morning and that's cost management, right. As people move to the Cloud, um, its so powerful and easy to be able to start up new services in the Cloud but then, do you know what you have, do you know what is costs, do you know how to optimize? Um, we announced 12 new applications this morning. One of them is addressing exactly that point. >> Yeah, um, okay, what are some of the challenges customers have really monitoring across these different environments? I think cost, it's, well, the promise of Cloud is to help me understand and control my cost quite a bit. But, you know, I understand my data center cost and, in general, much more than I do what I have in the Cloud. >> So, you mean, trying to understand in their software? >> So, I guess, just, if they have these different environments that need to span from a monitoring standpoint what are some of the challenges that customers have and the differences and how does New Relic pull those together for them? >> Well, I think some of it is bringing their teams together. If you've got folks that have a Dev accent and an Ops accent, they may have different points of view about monitoring right? And so, a Dev team might be saying lets go all in on this method or this tool. But an Ops team might be saying something else. And then as you introduce new technologies and maybe now people don't always want to run an agent. They want to have complete visibility over their software. And so, with New Relic, we're giving them those choices. We're giving them, like, hey, you can run an agent, you can, if you've already got stuff at Zipkin, cause maybe, internally, you've got like a great Zipkin champion. Like, great, we're going to be there with you on that too. So, we want to be able to help these teams come together. Um, rather than forcing them to sort of live in silos. >> All right, uh, Lou put a real emphasis talking about platform. And he said platform with a capital 'P'. >> Yeah >> Help us understand a little bit about that and the impact that's going to have for your customers. >> Yeah, absolutely, I think, you know, anyone can say I've got more than one product, therefore I have a platform I think. When we talk about a Platform, we think of software engineers, a Platform is something I can build on. So, I think a capital 'p' Platform is the ability to build apps, to be able to extend it, to be able to add data because you're open. Um, and then the power that we bring, you know, I got to put in my plug, is by connecting it all together. Um, but I think the power of the Platform, um, has been really showing off in the work that we've been doing with our customers to build these new applications. >> All right, um, you mentioned open, which was one of the three features of the Platform itself. Uh, there's open and with API'S and then there's open source can you help us tease through a little bit because there's the openness and then there's some open source pieces. How do those go together and um, I guess, more importantly, what does it mean for the customers? >> Mhmm, thanks for asking, cause I do think those words kind of got tumbled up. So, let's first, let me like tease it apart a little bit. So, first part of open, you sort of already mentioned this, is like, we're open to all data. So, metrics, vents, logs, traces, you can send that data. That's, that's the first thing. You don't have to be running a New Relic agent to use New Relic. The second part though, uh, is that we are actually building and contributing to the open source community software development kits and exporters to make it easy for our customers. And so, we've shipped, we're shipping Open Census and Drop Wizard and Micrometer and exporters and Prometheus scrapers so that these are open source tools that our customers can get, can extend if they need to, to get that data in. So, we're making it easy to get the open data in by providing these open source tools. Um, and we're in there with the communities contributing to the communities as well. And then, finally, you know, the last one is with our new programmable Platform, we are also all in on open source on that. So, we're contributing to open source for folks building on New Relic and our customers are telling us that they're excited to also be able to do that and to share and exchange with each other. >> There's value to the customer and I guess the question is, your relationship with your customer is going to change though. As they're building applications not just, you know, more than just a tool. And I've heard from many of the customers that use New Relic, is, they talk about the partnership. And it really is taking that partnership to the next level. What I say is, New Relic is not coming out and saying oh, we're an open source company and we're building our company around open source. So, you know, it seems that somewhat a maturation of the model but not open source being the be all and end all of New Relic's mission. >> Our mission is to help customers build more perfect software. I mean, that's why we come to work. Is to help them do that and we think this is the right step. Um, to be able to do that and our community around New Relic, as you said, is excited and dynamic. It's great to be here at Futurestack and hear them talking to each other and hear the buzz. I was at our customer advisory board meeting yesterday which is 11 execs from some of our biggest customers and they were talking about how excited they are to see how this is going to help them with their business cause they can connect, now their telemetry data to sort of higher order business problems. Um, and they're also excited to share. So, I think it's the right step for New Relic and our customers. >> There's a lot of startups out there that attack pieces of what New Relic's trying to deliver. Um, you know, how does New Relic look at the landscape out there and the challenge when you're trying to be a platform is, are you providing good enough solutions? Or, you know, are you providing, you know, best solutions across all of these environments? >> Yeah, I think any of our point solutions could go head to head with anything on the market. Um, you know, and the fact that the market is so dynamic is because it's a real problem space for people who are building software. So, folks are going to keep innovating and coming up with new ideas and my mission is to make sure that everyone writing software, is instrumenting it and able to observe it. So I think, I love that more and more folks are joining this conversation. I think it's a great time to be working on monitoring observability. >> Okay, uh, let's start at the top talking a little bit about observability, what should customers be looking at, should they be thinking about that? What feedback are you getting from some of your key customers? Uh, in the space in general and how New Relic's looking to address it? >> Yep, well I think comes down to, a little bit of what we talked about earlier, visibility and answerability and if I were talking to an exec or if I was talking to an engineer, and I was looking at their tools, you know, whatever level you're at and saying, what do you need to monitor how can you get that data in and can you answer the questions? Do you have the tools, the ability to query, to connect the data. Um, to see, hey there's an event that happened and how did my systems change? So I think a lot of it comes down to, is it visible, can I ask the questions? And then for every stack, and no matter what job I'm doing. >> All right, um, when we look at this broad term which gets overused some, but, digital transformation Um, the comment I've made is the long pole in the tent of going through that transformation, really is the application portfolio. You know, I can modernize my platform, I can go to Cloud, but, you know, changing my applications, especially the ones that run my business, is really tough you know. If I'm a company that's been around 15-20 years, you know, I probably have applications that are as old as the company, if not longer. >> Yep. >> Uh, just broadly, how are your customers doing, uh, are they being able to kind of, you know, move along that modernization journey of the application uh, better today than they might have a couple of years ago, or just kind of macro level? >> I think so, I think, you know, between what the Cloud vendors are doing and what we're doing, folks are getting both tools and they're also getting support. I think, you know, the community, the software engineering community is really leaning into this moment. And talking about how to do these types of trasnformations. So I think there's a lot of just, knowledge sharing going on, there's a lot of advice and consulting that you can get. And then I think the tools are lending themselves to being able to do, you know, some people move to the Cloud or lift and shift. Some people use it as an excuse to re-architect. A lot of folks pick and choose. Because not every apps work the same and some apps are, you know, are, um. For some given app, it might be a more relevant time to change it, a more relevant time to let it stay put and you can make those choices. And I think people are approaching it with a certain rational sense. >> Yeah, uh, one last question for you, New Relic's a leader in, according to, the analyst firms that look at the APM market. New Relic's doing a lot of the things that I hear from, you know, the startups getting lots of money thrown at them, so, how should customers think of New Relic today? >> I think, we're the best leading APM product on the market for a reason. And we can never rest our laurel. So I think customers should at us as a trusted partner. Who's going to continue to grow and meet them wherever they are. Our customers are going to Cloud, we want to be there first to meet them there and welcome them in the door. And that comes back to how do we help customers through digital transformation? We're a big software company. We get it, like, we are going through the same, we go through these same questions ourselves. Um, and we talk to our customers all the time. So I think for our customers, it's like, we're the platform and the right partner. Because we're never going to stop. >> Nadya, thank you so much for sharing the updates. Congratulations on the launch today and, uh, best of luck going forward. >> Thanks a bunch. >> All right, lots more here at New Relic Futurestack 2019, I'm Stu Minamin, thanks for watching theCUBE. (electronic music)

>> Narrator: From New York City It's theCUBE covering New Relic FutureStack 2019. Brought to you by New Relic. >> Hi, I'm Stu Minimen and we're here at New Relic's FutureStack 2019 at the Grand Hyatt, next to Grand Central Station, here in New York City. Happy to welcome to the program a first time guest, Roger Scott who's the Chief Customer Officer at New Relic. Roger, thanks so much for joining us. >> Thanks, Stu. Thanks for having me on. Good to be here. >> Alright so, I love this morning actually in addition to hearing all of the announcements, my first hand full of guests on theCUBE were customers. So I got to hear from them and we know your team is always excited about the announcements, but definitely enthusiasm from the customers, things in the keynote that got people. >> Fired up! Yeah. >> Clapping, and fired up. >> Great to see. >> Things like, oh wait! 10 terabytes of data, pressure thing, refresh for like a second, and >>oh my gosh! There's results. Yeah >> Pretty impressive so maybe give us a little bit of insight into customer engagement and how it's let to the bevy of announcements here at the show. >> Oh it's a great question actually and I think in my capacity as Chief Customer Officer and the functions I'm responsible for, we're continually engaging with customers as you can imagine. And one of the things we take a lot of pride in is being a proxy for the voice of the customer back into the organization. So we have a pretty rigid process. Not rigid, a pretty discipline process, I would argue, that allows us to get feedback from the field, listen to our customers, understand what's important to them, and reflect that in our product roadmap. And I'll let you know that's on a weekly cadence we do that. Now we're not doing that in a reactive fashion such that our roadmap diverts every single week in there, but we hear that constant feedback from the field as to what our customers are lacking. So lot of what you hear today, in terms of those six great announcements that we have were a combination of feedback that we've had over the last couple of years, I would argue. Because it's a dramatic shift to go from what we were previously, which was essentially six individual products that work really well together. But through the release of New Relic 1 in May earlier this year and what we announced today has truly developed us in to a observability platform. So monitoring with six different products to a true observably platform that's open, connected and programmable is a dramatic shift. And that's a combination of a bunch of feedback from our customers over the years. >> Yeah. I'm sure it's pretty much feedback from all customers. They're not asking for more tools and more interfaces and more things that they need to learn. >> Roger: Not at all, right. >> In many ways software can be a unifying feature especially that term platform who spend a bunch of time emphasizing what's needed from platform. >> Maybe, what were your costumers struggling with that kind of New Relic 1 in general is looking to solve as well as the observability piece? What went into that launch that was costumer pinpoints and things that they'd been asking for. >> Yeah maybe to stand back a little bit and understand some of the challenges that costumers had and then why they were asking for different solutions or evolution of our solution. If you think about today's world, there's this rapid development an deployment of software, so it's almost got to the point of continuous software deployment. And so your speed of needing to be able to react to problems in your environment, your costumer experience are degrading, ect. Being able to respond to that really quickly is essential, understanding the costumer experience is essential. You talked about operational efficiency of reducing the number of tooling sets or data sets that I'm looking at continually. So anything that we could provide to our costumers that allowed them to get to answers quicker, understand the why, and then be able to remediate that really easily so that the costumers have a greater experience. And at the same time reduces this friction that's unnecessarily introduced when you're going from one product to another, one tool to another and you're spending too much time rationalizing data sets across those tool sets. So consolidation is a big theme, ability to get to your answers really quickly is a big theme and that's really been the genesis of being able to create a platform. But not just a platform for consolidation, for better visibility, and observability but we believe it's not truly a platform until you can develop on it. If you think back in technology history of all the different peradams we've had throughout the history of technology, those who've won the platform wars over the years have been really good at being able to provide tools and ease of adoption of the platform by virtue of being able to build things on top of it. The ability to give people tools that allow them to build technology is really a therasense of the platform as well. >> You know, Roger, there's a certain trust level that costumers have to have if they're going to be building on top of your platform. >> When I've talked to costumers in New Relic they do talk about a partnership >> and the good back and forth but there's definitely a certain amount of stickiness once they've built something on your platform. >> Roger: Right, yeah. >> Any concerns from them as to, you know there's that term lock in out there as to the how do I know that this is going to work for me, and that I'm not going to have my pricing kind of crank up over time and be like oh my gosh, a year or two later, what did I get myself into? >> Right. It's a really important point that I'd like to start off by actually reemphasizing the point you made. I think we pride ourselves on the relationship we have with our costumers. It truly is the heart of everything at my organization does. We have this saying that we are because they are. In the realization that if we don't serve our costumers really well they have choices frequently, we're a saas vendor, the contracts come up for renewal frequently. And if you're unable to deliver on the promises that you made in the sales process, once they implement your solutions and try to use those in production, environments and everyday work if you can't deliver on those promises then you're going to breakdown that level of trust. And trust is at the center of all relationships as you know. Whether it's a personal relationship, you're playing on a sports team, whether you're working with your costumers. And so we want to make sure that we can deliver on those promises once we've sold them the product. So I haven't heard any specific concerns about lock in or anything, I think what they regularly come to us though with is they want us to have a really strong point of view, want us to be opinionated, tell them how this should work effectively together, what does best practice look like, what's the gold standard, what are some of the artifacts, tools, frameworks, reusable templates that we can share with them that accelerates their time to value. So I think the value significantly outweighs the concerns around lock in or reduction of the number of vendors that they're working with. >> If I look at really the enterprise space, you've got costumers working through their application modernization. They've got their modelist their going after micro services. I heard a stat that only about five to ten percent of apps are monitored at the app level today. >> Yeah, pretty scary, isn't it? >> Yeah, how many of your costumers are dealing with the installed state versus new deployments and what are some of the challenges you're hearing from costumers there? >> Yeah and I think it's important to pause that number because I think it's five to ten percent or growing to twenty percent as I think got indicated. If you look at those organizations Born In The Cloud or Born Digital it's significantly higher percentage of that which is possibly an indictment of the low level of instrumentation we see in a lot of legacy software technology stacks. And so I think in today's world we're tryna get that level of instrumentation observability up as much as possible. But maybe to link back to your previous question as well I think there's an important aspect here of when we move to a platform. When you're a product company your differentiation comes through product, comes through the capability of that product features and functions and we've certainly found ourselves in a significant number of those battles against competition where it's feature and function based. That's not a great comfort for the costumer. I think when you move to a platform it's very much around the networks differentiation. When I say network differentiation I think it's about getting the users of your service access to third party applications to third party data sources be they open source data emitters, opentelementry, open sensors, Zipkin any of those data sets that we are now in support for today. Giving them access to those data sets and being able to enrich the experience that we provide them that network effects and that's really where we see the opportunity to deliver significantly more value to our costumers with the ability to then build your own applications on top of the platform. That's second to none in the industry in my opinion. >> Roger, what's New Relic's role in helping costumers as really they're modernizing their work force? When I talk to so many companies it's like they need to retrain and they have to have new skill sets they need to make sure as certain cloud in automation changes where they focus on things and embrace devops and new ways of doing things. There are a lot of challenges there. Where does New Relic play in that modernization for costumers? >> You know what I think it's in a couple ways. The ways that we, my organization, can help the costumer in terms of just sheer understanding of the capability of the platform, what are best practices, how we can drive better accountability as you move to these new technology stacks and new ways of working much more agile environments. And so I think we can do a combination of that just sheer skills development, working really tightly with the likes of AWS you would've heard Dave McCann this morning talking about how when costumers migrate the application work goes to the AWS cloud environment. Hopefully they're not just doing that by way of compute lift and shift but they were actually looking at modernizing and refactoring those applications and when they do that, you heard Dave talk through a number of assets and frameworks and models and reusable best practices that we're trying to work with them on that we can give to our costumers that accelerate their journey 'cause it's not easy. We were talking to Chris Dillon this morning from Cox Automotive and when you think of an organization like that that's forty, fifty years old and has had to transform itself in terms of digital experience for it's costumer base, it's a significant cultural adjustment quite often to get teams to work in fundamentally different ways. So it's not an insignificant challenge but that's partly why we've invested so heavily in costumer success. Taking the costumers on the journey, thinking about their maturity over time, and constantly look for them to get better value from the platform. >> Roger, there are a number of things that have jumped out at me. Things like oh hey, we can save you potentially millions of dollars on your AWS cloud bill. You've already got costumers building on top of the platform, you had the future Haka event just a couple of weeks ago. Any other kind of interesting or exemplary costumer outcomes that you might be able to share? Either doesn't have to be about the new stuff but just that you've recently with your costumers. >> You know, one of the things that's most gratifying for me when talking to costumers is when we've been able to see when you work with older, more traditional companies that are undergoing some form of digital transformation and they're trying to shift a lot of the applications into a more modern stack and environment, become more agile, etc. they frequently sort of peel off part of the business and will have a digital division that will build some innovative, typically mobile based, apps. We've seen a number of different retailers that we've worked with. Number of different travel organizations where we've started out intrumenting the mobile application because they've built a new application to give their consumers or costumers access through to their services, and at some point that application is going to merge into the backend and have to connect back into older technology. And it's been the beauty of being able to connect those two different environments together. Not starting off at what we would've got as slightly easier place to start which was the more modern application environment where we are really well suited to. But then seeing the full value of being able to instrument the front end all the way through to the backend, link that back to the costumer's experience and to the impact on the business in terms of funnel analysis from number of people using the mobile application to actually ordering something to once they've ordered it, feeling satisfied in actually receiving the goods that they ordered. Being able to instrument all of that and understand the impact of performance and availability on the overall business arcam, that's when it's been truly transformational in working with costumers and that's certainly where we'd love to help more of our costumers in that fashion. >> Alright, Roger, want to give you the final word. Of course you bring together a number of costumers here at FutureStack in the U.S as well there's a few of those run in other geographical areas but throughout the year, any other key things you want to highlight as to how costumers can get engaged even more. >> Yeah, I mean, we've got a sort of what I would argue is a tiered approach to costumer success. At the very high end of our engagement model we have a significant number of resources. Solution architects, costumer success managers that we can deploy directly with our costumers. We typically do that in conjunction with them, build out success plans, etc. What we looking at investing Heavily at the moment is also having a good understanding of what the ideal costumer journey is like. Realizing that a costumer can come to an event like this and learn about our product but the best way for them to experience that is in the course of using the product. So heavy focus on product lead growth and how we actually deliver better value through the product itself, remove friction and adoption and getting to better value. We want to automate some of that costumer journey so that we know that if you've just signed up and, for instance, you've configured you're agent and you've done your learning policy but you haven't yet configured a custom apdex on that application or you haven't understood what your key transactions are, we've got all that data in the backend. So we're working really hard to understand how we get that information back out to costumers and go hey we know you haven't necessarily done this yet, here's some access to great assets. A short video clip, a self paced learn guide that somebody can get on demand from an LMS system. So trying to use a combination of direct resource investment, events like this where it's great to make announcements like we did about the six grade innovations and then increasingly using digital through the products but also through just the general costumer journey to say hey this is really important content and information, you should look at this now 'cause it's going to add value in what you're doing today. >> Alright, well Roger Scott, Chief Customer Officer at New Relic, thanks so much for joining us. >> Thanks so much, it's been great talking to you. >> All right. I'm Stu Minimen back with lots more here at New Relic FutureStack 2019 in New York City. Thanks for watching theCUBE. (outro music)

>> From New York City It's theCUBE covering, New Relic FutureStack 2019 brought to you by New Relic. >> Hi I'm Stu Miniman and this is theCUBE's coverage of FutureStack 2019. Happy to welcome to the program, first time guest, Buddy Brewer, who's the GVP and GM of client side monitoring with New Relic, going to talk about customer experience and especially the digital customer experience. Buddy, maybe explain for audience who may not know client side monitoring tell us as to where that fits in to the entire picture of new relic. >> Yeah for sure great to chat with you Stu. You know client side monitoring for us, is the part of our observability platform that extends all the way out to where the user actually is. So people think of New Relic as this really great platform for understanding everything that is going on in the application logic, and the servers, but our client side monitoring does is extend it all the way out to the phone that is in the consumers hand or the laptop that's right in front of them. >> Stu Miniman: All right so obviously there is a direct connection between that and that digital customer experience. Maybe explain some of the challenges there and how new relic is helping to work on solving those. >> Yeah you know, digital customer experience is all about collecting and understanding the relationship between two different types of data. There are the technical metrics, all of that information about how long people are waiting, latencies and pieces of the software everything from how long it takes to connect to the server, how long it takes to build the response to the web page, Deliver it, render it, all that stuff. There's lots and lots to collect on the technical side. But the other half of DCX is the personal side, the human side. The person who is on the receiving end of all that stuff, how's it affecting their behavior? How long are they spending on the site? Are they buying? Are they clicking on a second webpage? Are they engaging in the game? Are they booking that travel reservation? And so collecting all of those business metrics, and then collecting right next to them all of the technical metrics and bring that back in a way that you can understand the relationship between those two things is what DCX, digital customer experience is all about. >> Yeah it is fascinating the expectation that we have today in 2019 is so different then the past. It used to be like "Okay, I know if a website doesn't load in this long, they are going to leave me" But you know what are those expectations, what is that ultimate end user. What is a good customer experience for them? >> Buddy Brewer: Yeah it's changing all the time, and it changes depending on what part of the world people are in, it changes depending on the type of device and this is why it is important for customers to actually collect the information and understand their relationship with their customers. It's really hard to put a single number on it. Because what's true for a commerce site, might not be true for a media site. What's true for a site in Australia, might not be true for a site in The Americas, or in the UK. There are certain patterns that certain people have seen, Google had a statistic out awhile ago that said that over half of people will leave a mobile site that takes longer than three seconds to load. And so there are some patterns out there, but a big belief, for us, is that one of the most important relationships our customers have, is the relationship with their customers. That is why it is so important for them to collect their own metrics around how long people are waiting, and how that waiting is affecting their behavior. >> Stu Miniman: Yeah, so it seems obvious that you know having data to back up what's going on is important. Bring us inside a little bit the importance of monitoring in this space though. >> Yeah, absolutely and this is why it's so important. We are so excited to be talking about our observability platform that we have here today at FutureStack. The fact that it's open, you can bring all of this information in. We've got all of this agent technology that collects things about what's happening in the servers what's happening in the info structure, information that's happening on the client side. As well as this ability to absorb information from third parties, then connecting it all together to give you that context. So there is the context that is being solving problems from the front end to the back end of the application stack. There is also the context like we were talking earlier, the digital customer experience. The connection between the technical metrics and the human metrics, and how they are actually experiencing the application. And then making all of that stuff, the connected stuff, programmable. So then our customers were the first observability platform that you can actually build applications on top of. And so we've released twelve of those today that folks can use. It's going to continue to expand, and it's something that our community can contribute to, our customers can actually take our visualizations, and our analytics and customize them to do exactly the things that they need to do. >> Stu Miniman: All right, Buddy observability is still a relatively new term for a lot of people. Help us dig down, you actually did a blog post even, about, you know, the principals of observability and modern applications. What, how should customers be looking at observability and how do they sort between you know, what is a good solution versus, you know, an okay solution? >> Buddy Brewer: Yeah, well there are some really important pieces that we think people need if they want observability about what's happening in their application. It starts with getting all of that information in one place. You know we have this really fast database, in our DB that store all of the telemetry that we collect on behalf of our customers. And it's getting larger and larger as we continue to open that up to things like these third party data sources. Then there is context that is really important to layer on top of that. Bringing the information together in ways that start to make sense out of those little individual pieces. One of the things that we found though, is that our customers are running applications that are so complicated, there is so much going on in these applications today, that even with the context there is still forty or fifty things that are happening at the same time when a customer has an issue. That's where our applied intelligence, which is another piece of what we are launching today at FutureStack, comes into play so that you can take those things and condense them down into smaller more manageable related chunk of information that folks can act on and fix their applications. >> Stu Miniman: Yeah, it was actually really impressive to see, you know, in the demo this morning, being able to poke through and get meaningful results off of tens of terabytes of data. In, I would say, much faster than I can run a report on the industries leading CRM tool where all of our customer data lives today. So you know, pretty interesting stuff is to how you can enable customers and it kind of almost will change the expectations as to what a good experience is like. >> Yeah that's right and you think about how there's that use case of things where normal and then they got bad, and so you logged in and diagnosed to get things back to normal. And having that speed, that ability to get that information quickly is really key there. There's also a whole other use case, this is the digital customer experience user case, where things are normal, but we want our customers to be able to play offense with software. To be able to take what's normal for them today, and to get better and better and better in ways that drive better business outcomes for them and allow them to compete and win in a space where, consumer expectations are just getting tougher everyday. >> Yeah, you know always look at there. How can, how can you just, you know, exceed what customers expecting and give them so that they will, you know, love your solution even more because you gave them more than expecting? How's New Relic helping customers, you know, move along that journey. >> Yeah, you know nobody likes to be kept waiting. At the end of the day the customer always has a unified view. So we want to give our customers, the consumer always have a unified view, we want to give our customers the unified view with all of the details. So that they can deliver a better experience for their customers. And it has to do with, again like I was saying collecting the technical information, also collecting the information about how that's affecting customer behavior and then looking at those two things next to each other in context. So that they can see how one affects the other. >> Stu Miniman: All right so, Buddy give us some of the outcomes that customers will see based on the announcements, today at the show. >> Buddy Brewer: Yeah so for the customer experience, one of those programmable pieces that we launched is this really simple application that you can just drop in to New Relic and it shows you right away the difference between engagement when people are getting good experiences, versus when customers they are getting bad experiences. And when we show this to people often times they are shocked. For example take a metric like bounce rate. What's the likelihood that someone who comes to your site is going to stay on your site? When people think about it, usually they are thinking about it in aggregate, across the entire site. But when you separate it out into the good experiences, and the bad experiences, maybe you've got an overall bounce rate of forty-percent, but when you give those really fast experiences to your users they are only bouncing at twenty-percent, so they are twice as engaged. Then conversely the folks who are getting the bad experiences, because let's be honest on any given day, websites are, you know delivering good and bad experiences to different groups of users, that bounce rate might be seventy-percent. And when you see the disparity between these two things it's a motivator to action. Now what's really important after that is that you've got the data underneath so that you can actually do something about it. And that's where this end to end observability platform that collects all of the information from the front end to the back end is so useful. >> Stu Miniman: Yeah, I have to think that it's pretty powerful not just for the customer experience, but I can get accountability from my partners, so where it be my ISP or my cloud provider, I can be like "Hey, uh, you promised me this response, this bandwidth and here's the data, we need to make sure that I'm actually getting what I'm paying for" >> Yeah that's right and at the end of the day what the customer saw, what our customers customers, the consumer at the end of that connection sees, is the truth. And so collecting that data, whether they are on a mobile device using an application or they are using a browser. Any of that stuff. Having that information is not only useful for internal accountability, and things that are in peoples direct control, but also absolutely, there's so many, so many third parties that people are using, to make their application's go today. >> Stu Miniman: Yeah, we know the visibility of actual data to help us not only make decisions but, inform everything that we doing is so critically important today. All right Buddy, why don't you give the final word, digital customer experience. What do you want people coming out of FutureStack 2019 here in New York City, really understanding? >> Yeah, I think that when it comes to New Relic, it's that we providing folks the ability to have exactly the view that they need of all of the data that's relevant to the performance of their application. So that they can solve technical problems, so that they can solve business problems. Because at the end of the day, your digital business is your business increasingly. The digital experience is what defines peoples brands. And so we want our customers to have complete control and visibility over all of that. >> Stu Miniman: All right, Well Buddy Brewer thanks so much for joining and sharing what's going on with New Relic and that digital customer experience >> Thanks so much Stu. >> All right, little bit more left here at FutureStack 2019, I'm Stu Miniman and thanks for watching theCUBE. [Outro Music]

>> From New York City, it's theCube covering New Relic Feature Stack 2019. Brought to you by New Relic. >> Stu: Hi, I'm Stu Miniman and this is theCube's first year of coverage at the seventh year of New Relic's Futurestack 2019 here in New York City and happy to welcome back to the program two Cube alumni. So, Todd Osborne is the GVP of Alliances and Channel with New Relic and Dave McCann is the Vice President of Migration Services, Marketplace and Control Services with AWS. Gentlemen, thanks so much for joining us. >> Dave: Great seeing you again, Stu. >> Todd: Thanks for having us. >> Allright, um, Todd, let's start with you uh, you know, quite a bit of a relationship with, between New Relic and AWS. I know we've had Lou on our program at the AWS shows a couple of times. So, set us up with the, the partnership and how it's been evolving. >> Todd: Yeah, it's been a, uh an unbelievable partnership, um, for many, many years we've worked together starting with technology integrations, we've got dozens of them that, that natively monitor a bunch of different AWS services but the most exciting thing of late ah, really came to life middle of last year when we started working with, uh, a bunch of different folks at AWS. Our, basically, our biggest thing that we need help with is migrations. We know we have this massive opportunity, uh, to, for more and more applications more and more workloads to move to the cloud. There's lots of different ways in which customers, partners and Amazon needed help in doing that. They brought us several different challenges related to that and we responded by, ah, at Reinvent Launch last year, launching what we call the Cloud Adoption Solution. That really was how, um, a process that linked up with the Amazon Migration Acceleration Program and used New Relic as the platform to help with migrations from beginning to end. So, starting with the planning, uh, phase of the process, getting the information you need to have a successful migration and design a successful migration, troubleshooting that may, of anything tat may occur during the migration and then post migration, really helping to optimize the performance and cost of how that migration, uh, or that post migration, ah, optimization and run phase. So, it started with that. It's really evolved. What's been really amazing, just since we launced last November December at Reinvent, the whole, we've seen a massive shift already, just the last nine months, where it's not about just simple lift and shift anymore, almost all customers that are migrating now, are also thinking about modernizing their software stack, running on containers, using kubernetes, running micro services, which is New Relic's sweet spot, really, at the application space. So, as we've evolved, starting with migration, evolving into modernization, it's been an amazing partnership working with AWS. >> Stu: So, Dave, migration services, obviously something we hear a lot about from AWS. Every time I go on one of these shows, it's one of the key steps that gets thrown out. Uh, you have a very broad ecosystem, the marketplace, uh, you know is, is the closest I call to the kind of the enterprise app store, uh, of today. Tell us what's, you know, special and, really, you know the effort that goes together between AWS and New Relic here. >> Dave: So, I think, from a migration point of view, um, you know we've spent a lot of time in AWS designing a migration methodology. Our professional services team, let by Tom Weatherby is really delivering a playbook directly to our customers on how to migrate. And, also, we've certified over fifty consultant partners who are certified to do the migration. But all the migrations hinge on a customer knowing what they have and whether they want to migrate it. And, so, to necessarily know what you have, you have to go through application discovery. So, if you've got a larger server fleet, you've got four or five thousand instances, you have a thousand apps, you've actually got to discover and analyze what you have. And, clearly New Relic's tool is widely installed. So they actually have the visibility to a lot of the installed apps. So, last year, at the end of last year, we bought a Canadian company called TSO Logic. And TSO Logic is a business case tool from building the business case on whether to move an application running on PRIM. What would it look like on The Cloud? So, we need to have that data in the tool. And, so, New Relic's been a great partner, integrating New Relic into TSO Logic, so we cal actually take the instrument in visibility that New Relic brings to the table and pop it right into the tool. And, so, the New Relic, TSO tool integration is a great new mechanism that we have. And we just acquired TSO in Q1 of 2019. So that we're now giving the TSO tool to all of our solution architects and all of our consulting partners and New Relic feeds the data right into the TSO tool. So that's a huge, um, uh, mechanism for accelerating migration. >> Okay, uh, can, can you speak to, you know, how, are you, who and what customers and how are you targeting them, uh, for, for this solution? >> So, first of all, customer are moving to AWS. You know, thousand of enterprises are moving applications. I think you have to assume that most enterprises are moving to The Cloud. And the question is, "At what speed?" So, as our sales teams engage with the customer, the sales team have a notion to discuss migration we run migration methodology. And so, as we engage with the teams, the solution architect brings TSO to the tool, to the discussion. And that's happening all around the world. And we've trained our solution architects on TSO. And as we've done that, the second thing we've done is, you know, New Relic engineered engine marketplace over two years ago. But we've launched a new capability called Private Offers. And Private Offers is where the customer, while they're planning the migration, may also need to license more New Relic and New New Relic. And, so, how do we make licensing really easy? And, so, New Relic worked with us on, the, what we call the Private Offers Workflow. And that Private Offer Workflow allows a New Relic sales executive to generate the quote right in the marketplace portal. And you, an AWS customer, and you receive that private quotation right in your AWS account. So not only are we business casing on TSO, but New Relic is quoting through marketplace. So that's happening into lots of large customers. >> Stu: Yeah, uh, you know, what if you talk about the adoption of Cloud we need to make it simpler for customers to move those. And the financial piece has always been one of the promises of Cloud, but things like this Private Offer, it sounds like it helps accelerate, uh, that simplicity, and, and you know, reduces any, you know, perceived barriers there are between some of the software vendors and what you're offering. >> Dave: Well, it flows the New Relic software supply right through marketplace and more and more large companies are using marketplace for software supply. And, so, New Relic's in there. It means that our sales teams are working together So, we talked this morning at the conference with the VP of Cloud architecture who was in the conversation. And so, Chris has been working with the AWS team and with the New Relic team and we're joined at the hip as they expand their use of New Relic. And they announced this morning that they've now moved over thirty percent of all of the Cox application onto the AWS Cloud. And New Relic's been the center of that visibility. >> Stu: All right, so, Todd, a lot of announcements at the show, especially uh, you know, the capital p platform as Lou talked about in the keynote this morning. Well, you know, AWS is one of the largest platforms out there today. Help us understand how these fit together, both platforms as well as just, just the announcements in general as to how they work with AWS. >> Yeah, what every single thing we announced today had some sort of AWS tie to it. So, I mean first of all with New Relic, one, being a platform, it's open, connected, and, um, and, and programmable. And, so, the open part of that means that not only can we just inject data with New Relic agents, now we, we now are an observability platform that will take date from all kinds of sources, so think of what that opens up in working with AWS and AWS's other partners and getting data from a bunch of different sources, to then make the observability even better. We announce a log in solution. We're already connected with AWS, uh, cloud watch logs and, and, uh, working on some other new feature solutions in the log in space. And then from a programmability perspective, um, we can now take what we have, we can write all kinds of applications on top of the New Relic platform. And some of the initial couple of, of the dozen application that have already been opensource, one is a cost optimization play which looks at Amazon data, uh, both utilization performance data, some other sources of data that New Relic has, and then pulls in the Amazon cost data, can actually look at, in the New Relic platform, as a free opensource application, how do I optimize my cost in the AWS environment? And the second one, which we didn't talk about too much this morning but it's out there, but we can take some of VienMore data and some of the on PRIM data that we have visibility to today and help design that landing zone to help migrations do better, So, it's just two really quick examples of how we can take data from all these different sources and program it, write new applications on top of it, create an awesome customer use case and work with Amazon and, uh, help migrations and optimization along the way. >> Stu: All right, Dave, I'm wondering if you have any customer examples that might highlight some of the joint work that's being worked on between New Relic and AWS. >> Dave: Also, You Know, obviously I've just made some Cox We stood on stage this morning with the press where Cox has said that they've now got nine thousand work loads under New Relic visibility. And so that nine thousand work loads is across hundreds of development teams and, I think, Cox is just an illustration of many customers that we have in common. Um, you know, we're, AWS has got thousands of enterprises, so does New Relic. I think you've said you have over one hundred thousand five hundred enterprises using you. So, some large number. So there's a high overlap in many customers at this conference. And as we sat in the room this morning, um, I would say more than half the room held up their hands when I said, "Who in this room is using AWS?" Half of the audience here are AWS customers and New Relic customers. >> Todd: If I could maybe just add on the Cox story a little bit, because I've been very involved with that one. The beauty of the partnership we have there was multiple, on multiple phases. First, Cox has been a customer of ours for a number of years. Both on PRIM and in the cloud as they have accelerated their cloud, we've helped a lot with that. What was great about that partnership was that our field teams got together and, and actually really sat down and, and mapped out the migration, multiple migration scenarios. We had data on a bunch of on PRIM stuff that was valuable to AWS. AWS was the standard on a couple of divisions on cloud that we weren't monitoring all the applications there. So the teams really worked really well together and then at the end of the day, we came together and said, um, there's a bunch of benefits for the customer, for AWS and us, if the, if uh, if a transaction, the last transaction we did there, went though the marketplace, which was a significant transaction that we did with, ah, on the marketplace. So it was just such a win, win, win that tied together the, uh, all the aspects of the strategic nature-natureship, nature of our partnership. >> Stu: All right, so, you know, it's clear you're teams have been working close tother, iterating and adding a lot of the last kind of year, year or two or so. Give us a little bit look forward. What more should we expect of, a, from, from this partnership? >> Dave: So the area I think I would talk about next, that I think all customers are paying attention to, is spam management. So, you migrate your application to the cloud, you establish a could operating modem, um, we license out software through marketplace, you're now running it, at last week we have another product that I run called Service Catalog. And last week what we launched in Service Catalog was a new ability, and Service Catalog is a library of templates, so those templates are launched as Jason Templates using something called cloud formation and we've versioned the templates and what we launched last week was an integration between Service Catalog and another tool our customers have called AWS Budgets. So now what you actually want to do is you want to grant the team access to a resource and on the tag of the template, you actually want to give that resource template a budget. So that is actually under an API, so there's an AWS Budget API, there's a Service Catalog API, Lou's team today announced a whole raft of New Relic tools. But one of the things that they announced was the ability to essentially build these new widgets, using a React widget, and pull data from other sources. So that's the area some of the customers are looking at as far as taking your spam widget and connecting it into both AWS Budgets and Service Catalog. I don't know if you want to give us your thoughts on that. >> Todd: I, I already talked a little bit about it but it's, it's, it's where we can go. Like the future if almost, almost, uh, infinity right now. What we can go do together. We are trying to align to several of the programs Dave mentioned around Service Catalog, Migration Hub, focus on a couple different use cases of what, um, ever migration has a bunch of nuances and every optimization story has a bunch of nuances. But how can we create the right application, which are a starting point, opensource, put, put the repository up on get up and then allow customers and partners to go and fork that, do what they want to match, kind of of standard use case and maybe eighty percent of the way there. But then it needs a little but of tweak, a little bit of customization basesd on whatever that customer's situation is. We've enabled the entire, uh, community of millions apps that are going to migrate to the AWS cloud over the next couple of years. We've enabled that with what we've launched today. So, the, uh, the future is, is infinity and beyond. >> Stu: All right, well, Todd and Dave, thank you so much for the update. We look forward to seeing what gets announced at AWS Reinvent, which, of course, it'll be our seventh year of having theCube there. Big presence, uh, please reach out if you want to talk to us ahead of time. And check out theCube.net, of course, where you can see, uh, where we will be, including, of course, AWS Reinvent, uh, in December, uh, in Las Vegas. So, This is theCube at Future Stack 2019. I'm Stu Miniman. Thanks for watching theCube.

>> Reporter: From New York City, it's theCUBE, covering New Relic FutureStack 2019, brought to you by New Relic. >> I'm Stu Miniman, we're here in New York City right next door to Grand Central Station, at the Grand Hyatt. This first year of theCUBE, attending New Relic's Futurestack, the seventh year of the show, and happy to welcome to the program, Guy Fighel, who's the vice president and general manager of New Relic AI of course, CEO was up on stage this morning announcing New Relic AI, it's in beta, Lew said expect early 2020 for to come out, so thank you so much for joining us. >> Thank you for being here. >> All right, so Guy, you came to New Relic by way of the acquisition of signifAI. And that ends in AI of course, even though we pronounce it signify, so help us understand is this a repackaging, rebranding you know, New Relic-izing the product that was through the acquisition, tell us how we've gotten here. >> Yes, sure, so New Relic AI is a whole new set of capabilities, it's a suite of capabilities that we are launching today in beta that pretty much augments the site reliability engineers with AI and ML capabilities. It runs on top of the New Relic One platform, which is the first observability platform that is connected, open, and programmable so you have all of the existing information and data that you already have inside New Relic. And we've incorporated a lot of the technologies and the techniques that we have developed as part of signifAI with existing capabilities that New Relic already had, and pretty much integrated all of that into single user experience and single type of capabilities across the stack. >> All right so, Guy, AI is a really broad category you know, you got your AI and ML and cognitive and you know all these things, what was kind of the core IP of SignifAI when they came in. >> Sure, so we really focused on correlating and reducing the noise of all of your different alerts and incidents but not just that, we've actually built a recommendation engine on top of that, to provide you much faster context to get into potential root cause of all of your different information focused on events. And now we're combining that with all the time series data that New Relic as a platform has to offer, so you're getting a much broader capabilities for understanding. >> Yeah, you know, definitely there's that promise of AI as we know that humans alone or my traditional tooling just can't keep up, you know, talk about all the different sources of data, the volume of data. I just saw Lew talking about the amount of the millions of items being ingested into the New Relic database, and the billions of items that are being read basically per second. So, help us understand. You say we love, we talk about our videos or extracting the signal from the noise, so, did I hear it was like 80, 85% your early customers are helping to reduce that noise Bring us in a little bit more. >> True, yes, so definitely early results shows us over 80% noise reduction for some of the customers and it is important to understand this is automatic relations, so this is truly based on the engines with no human interaction. Now, we actually have even greater results when some user input is driven into the system and that raises the capabilities as well. In terms of the number of events, yes, we are dealing with huge amount of events and information in the platform and I think it's, all around, not replacing the humans, but actually augmenting the site reliability engineers, so you talked about how systems, you know, there is a great promise for those capabilities. We believe that applied intelligence is a much better term, because it gives really enabling the augmentation for the site reliability engineers. We don't believe that site reliability engineers needs to go away or can even be replaced anytime soon. We definitely think that we can help them understand better and faster, what is the type of problems that they see in their production environments, and then help them resolve that much faster and better. >> Yeah, absolutely, we're huge supporters of really, the best solutions are when you have the people plus machines, there are certain things the machines are going to do on their own, but it's the marrying, so help us understand who's going to be using New Relic AI how is it going to change their day-to-day life and maybe even kind of organizationally, what the impact will be. >> Sure, so if you're a site reliability engineer, or a DevOps themed depending on, how you want to call yourself and, you know, there's a big debate in the industry, whether it's DevOps or site reliability engineers. Pretty much anyone who is responsible for Op time in the digital production environments you're a relevant user, If you carry the pager, if you're on call, you're a relevant user, so you're going to be interacting with the system to be able to actually see what are the problems with potential recommendations and then, you can infuse the system with your own logic. Whether it's based on the logic, we also provide very easy user experience we'd like thumbs up, thumbs down, different types of feedbacks as part of the workflow and I think the most important piece is that we're connecting to users where they are. Meaning, we don't believe we need to change the workflows so, if you're a user and you're already using with a specific internet management providers and you've already connected some of the additional monitoring tools to those providers, we now offer you a streamline of syncing to those instant management platforms and then, in reaching them with all of the information that we already have on the platform. >> So Guy, we've talked about AI but, let's talk a little bit about AI Ops. So, you know I've talked to the number of the vendors I actually went to an AI ops conference earlier this year and some of the talk track was, APM is the old way, AI ops is going to replace what you were doing before Let's take all your scattered tools and consolidate them down. some of the messaging reminds me of what I heard this morning, the New Relic One platform is going to replace a number of tools, pull everything together. Help us kind of, you know, square that circle of APM and AI ops and where you see New Relic compared to some of those competitors out there today. >> Sure, so APM is application performance monitoring. it's all about monitor and have that visibility to your application layer, it has nothing to do with AI ops it has nothing to do with replacing the tools. We believe that everyone should have visibility into their application, and that's, a lot of that messaging came through Lew's key note this morning, and opening it up to any type of open source instrumentation so we can bring it to the platform whether you want to drop an agent, whether you want to use any other open source SDK, we allow you to do that. Pretty much opening up the platform and giving you the option. AI ops is a term coined by Gardner actually, and it is pretty much applying some automation, AI capabilities, ML capabilities, statistical analysis capabilities on huge amount of data that you have in a centralized place. It has nothing to do with the monitoring, per se, so, I definitely think that the industry's going into a new space, where there is a consolidation obviously with different vendors. I believe that New Relic is giving customers the choice to make, whether they want to go and continue using their old tools, and that's okay, and we are an open platform so we will sync up with their data as part of New Relic AI we'll be able to bring in the new data whether by, again inter-connecting with their incident management platform or through a rest API or native integrations or if customer choose to do that, they can just send us all of the data directly and then, we apply the AI ops capabilities on top of the existing platforms. So, it's really opening up for the choice of the customer. >> All right it's been less than a year since the acquisition of SignifAI we know that some of the things when you do an acquisition it's an area of investment, you're going to get more resources, more people but, you've mentioned customers a couple of times, maybe give us a little bit of insight as to how the customer conversations have changed now working for New Relic, as opposed to being a customer understanding that piece of the New Relic ecosystem. >> Oh absolutely, I think, you know, as you transition from a small start up into a company like New Relic you get much more exposure to enterprise customer, your scaling capabilities are much better so we're in serious conversations with a lot of the enterprises customers that have a lot of interest in what we do. A lot of it is part of the branding recognition and all of the great capabilities that New Relic has already, and then marinade that with all of the capabilities that we're bringing or that we brought into New Relic as a young start-up with all of the latest technologies and a lot of the AI capabilities which are truly innovative ones, so definitely see a lot of traction from the enterprise customers, the more sophisticated ones as well. >> All right, so the solution announced today is in beta give us a little bit of a look forward as to what we should expect to see and what feedback you're hoping to get from customers along the way and how they might get engaged if they want to. >> Yeah so definitely we are in beta today. We've engaged with customers prior to the beta, so, we already got a lot of feedback and great feedback and we make some tweaks to the product based on that. We're actually announcing AGI of a small feature today which is enhanced incident context, which provides you active detection for time series data all the way to your slack channels but the overall solution is currently in beta and as we are progressing, within every month we're going to get more and more customers engaging with the platform, and then we're going to release a much more advanced capabilities even than what we have today in GA coming early next year. >> All right great, last thing, big mention and push about observability this morning, help us understand where AI fits into the broader discussion of observability. >> So again, as I mentioned before the observability will allow you to see all of your data in a centralized place. So, it's combining matrix, events, logs and traces in a specific place that now algorithms and different techniques such as AI and ML based algorithms really, really be successful in gathering, understanding, because you have all of that different information for the human brain, it's very hard to actually go and crawl and kind of ingest all of that vast amount of different data points for machines, they're very good at that. They're starving for broad amount of data and so having that capability, building on top of a true observability platform is what makes the AI and ML so successful and drive value to customers in really understanding what the data means. >> All right well, Guy thank you so much for sharing best of luck on the journey towards GA for the the full New Relic AI in the future. We look forward to, launching it. >> Thank you so much. >> All right and once more here, walking through at the New Relic Futurestack 2019, here in New York City. I'm Stu Miniman and thanks for watching theCUBE. (upbeat music)

>> from New York City. It's Theo Cube covering new relic Future Stack 2019. Brought to you by new relic. >> Welcome back on stupid a minute. This is the cubes coverage here of future stack 2019 new relics. 70 year they're doing the show is the U. S. Show. They actually bring these few locations around the globe, right next door to Grand Central Station and about 600 in attendance. And been really excited to kick off with the number of the users here at the show and happened. Welcome program. First time guests. Another cut. Who is the technical fellow in chief? Architect with Genesis. You been at the event a number of times. You're speaking at the event today, but let's start with Genesis. Customer experience is something that I think a lot of people been hearing about on. That is the product. The Genesis has tell us a little bit about the company itself. Sure. >> Yeah. So, Genesis, uh, brain that Maybe not. Everybody knows, but they certainly transitive Lee know us. We're a customer experience platform. We like to say that we're a technology company, but we power. The experience is about 25 billion customer experiences every year for 11,000 plus customers. About 1000 different countries around the world s So we are all about having a connection between brands and their customers, and we enable that >> s o not only some of the cloud shows. I was an enterprise connect earlier this year and definitely was, you know, something I heard a lot about see Exit really important Not only how customers interact with the brand, but internally how you know we treat the employees and that interaction is something that that is raised up. People are kind of important inside, but we're going to talk too much about the people here. We're gonna talk about the technology as the chief architect of this gives a little bit about what you have your arms around in a responsible for >> sure s o for for me, of the project. Your cloud was the name for for a long time, Genesis Cloud as of yesterday. So we are a public cloud offering as a CX platform and I say platform because we made the transition from just being a product to a platform. In my opinion last year, more than half of our FBI work is actually code we didn't right? So I think people using you as a programmable thing is when you become a platform. So I'm responsible for things like cloud architecture for understanding. Let's say industry trends. What technologies? We're gonna use a lot of eight of us service designed technical vetting, general cat hurting that sort of thing, >> Right? So you said your public cloud, but you said it sits on top of AWS. But it's a platform that your customers can then build on top. >> That's right. That's right. So we like to think of ourselves as C X. As a service. We've had some that use us still like a product all shrink wrapped, ready to go, others that want to extend us either writing their own. You guys writing their own back ends their own integration points. We make all of that possible. >> All right, so I'm expecting you have a bit of an opinion when it comes to that platform, As Lou said with a capital P A, and it's gotta be programmable, it's gonna be open. Tell us what your thoughts about new relic kind of entering, you know, new relic one being they said today the first, and only if their claim of observe ability platform s o give us your thoughts around. >> Absolutely. Yeah. S O. I like to think that we have been using the relic as a platform for awhile, whether they knew it or wanted it or not way have a fairly rigorous continuous delivery pipeline. And we are very big believers in infrastructure is code and develops principles. So for us, the engineering teams don't just own the code that they write, but they own the infrastructure definitions. They even own alert definitions, dashboard configurations. And we push that information directly into the relic as our deployments happen. Live hundreds of times a week around the globe. >> All right, so how do these modern architecture's enable you to run a team? >> I can't imagine trying to manage 350 plus Micro service is in production, which is roughly what we have today over 1000 Lambda Functions way can't improve what we don't measure. Everyone likes to say that, but it's true. I have a little bit of an a p m background from from places past. So I was a firm believer that you need to invest early and observe ability and metrics. So we've been a day one kind of new relic subscriber in the cloud space. Everything from understanding how the infrastructure parts work now to serve earless. It's all been about moving up the value stack like commodity metrics of servers is great and still needed. But transactional information and now trace information is absolutely essential. >> Okay, in the Kino this morning, they walk through their metrics events, logs and traces. Where are you with, you know, these various sources of data and harnessing the value of that. >> So I would say, with fairly early towards the tracing part before new relic headed as a managed thing they had cross at tracing. I'm sure you're familiar with that sort of the prior incarnation of distributed tracing on. We leverage that pretty pretty heavily, but it obviously doesn't have quite the same utility a cz what the new open tracing standards provide s so we do things like having correlation i d. S. That let us tag and follow things around. Now we just get to off load that from our team's being as responsible for it. And now the platform gives it to us. >> Yeah. Glen is open source important to your organization? >> Absolutely. We try Thio, give back some ourselves. In fact, one of the one of the nerd lets the nerd packs that Lou mentioned on stage was one that our team wrote s Oh, yeah, way believe not only that, we need a p i's and programmatic access to do our jobs, but we like toe enable and help other people with the same >> Eric Spence got a shout out on the Maquis note was that the thing that you were talking about it is >> I expect to see us probably released two or three more nerd packs before the end of the year Way, way are eager to do that rather than just investing in all of our own. You I that we had glass over the top of the relic. Now we actually just get to put those components deeper inside of new relic proper. >> Okay, eyes there. Anything else from the announcements this morning that you're looking forward to leveraging? >> So I think there's there's definite changes in the A p M space. You'll hear a little bit more, probably in the deep dives one of the talks I'm having later with not even she will be talking about. Some of those things were definitely interested in that. Open telemetry has some value. Greater Genesis definitely has investments around things like Prometheus and other sorts of monitoring. So if I'm not talking about just the public cloud side of it and other aspects there definitely things we can leverage. >> All right, Glenn gives us share a little bit, if you can. About what? What you're talking about here at the show. So one of >> the big mitts is entity centric. Observe, ability. The idea again that we're not just looking at servers and static infrastructure. We're looking at things that are very ephemeral. We have a lot of dynamics scale on our platform on. We need ways to actually frame what we're looking at at the level of Micro Service's but often level like business applications. So even when we're creating some of these extension points like the one you just mentioned way framed that within the context of a service that does a particular vertical slice on dhe, that's that's kind of where we like to invest. So we like to live. >> Okay, um, you know what's what's on your road map of? You know where you're going with your journey and is there anything that you're looking for? Beyond what was announced today from new relic ER from the ecosystem at large, >> I think there's lots of refinements of what was announced today that will help us theeighty I ops side, I think not just for noise reduction, but also for like, early early signal detection. It's a pretty fascinating space. Will likely invest some of our own dollars in times trying to help that along. Definitely Ah, lot of distributed tracing and Maur investment. There is a big piece for us. I think the A PM space. There are areas that I'd like to see a peon vendors invest in that goes beyond what now, I guess, is becoming more, more traditional, like transaction information. We have a lot of a i machine learning ourselves, and I think monitoring those types of workloads is going to be very different. As big of a paradigm shift as it was to go from classic monitoring Transactional. I think we're about to see that happen again in the >> industry. Yeah. What can you share some of the kind of the A I journey that you're going through a genesis where you are, You know what the maturity level is of solutions that you're using and >> sure way have a fairly robust aye aye team on products range from in the W m space back to the people that you mentioned at the first part of the talk way have workforce optimization, workforce management, and we brought a I algorithms to that a lot of time. Siri's forecasting that used certain machine learning techniques. We've invested a fair amount in until you and Opie any are so everything from sentiment detection to live transcription that we built in house to our own body engines that d'oh the new dialogue management. So we have a fairly robust bit there and some on the management side on the operational back in that we used to try to improve our quality of service on reduced any sort of incidents on the platform. >> All right, it's your third year. Third time coming to this show was what brings you back? What you excited about? I kind of dig in and take away from the event this year. >> I think the relics always been a partner in my stance, not just a vendor we believe so deeply in the observe ability message that one I want to be part of shaping that narrative. Eso coming to future sack actually talking to a lot of other executives, seeing where they're going and kind of sharing that use case, but also trying to be a little bit of a lighthouse. Thio, the new relic team as well, is what brings me back every year. >> Observe ability is something that it hurt. A number of startups talking about in the last couple of years were, in your opinion, does new Rolex it compared to the marketplace overall, obviously, they just kind of announced the observe ability, you know, full suite with new relic one. But you know what your viewpoint is? Toe have their wealth, their position? >> Where did I think their position? I think they are best of breed for what we're currently seeing. Owners of ability. There are other things, I think, where we could cobble together bits from multiple vendors but frankly, having application performance monitoring along with infrastructure, along with data being cold from the cloud platforms that we're all in, like, eight of us. They've got a unique place. I think the power of their agent technology has proven itself over time as well. My guidance to most other other companies that I speak with about this subject is don't just trust that it's all magic invest on. And I think they make themselves easy to invest in on. I think this platform play is a good one for them. >> All right. Well, another cut. Thank you so much for joining us. Sharing your journey, What we're doing in the best of luck on your presentation today. Thank you, sir. All right. Be back with lots more coverage here from a new relic. Future stack 2019. I'm still Minutemen. And thank you for watching the Cube.

(upbeat techno music) >> Announcer: From New York City, it's theCUBE, covering New Relic FutureStack 2019, brought to you by the New Relic. >> Hi, I'm Stu Miniman and this is theCUBE's exclusive coverage of New Relic's Futurestack 2019 here in New York City, seventh year of the show. Our first year here, about 600 or so in attendance, and real excited, because we've had some of the users here to help kick off our coverage. And joining us, first time guest on the program, Josh Biggely is a senior engineer of Enterprise Monitoring, with Cardinal Health coming to us from a little bit further north and east than I do, Prince Edward Island, thank you so much for coming here to New York City and joining me on the program. >> Yeah, thanks for having me Stu, I'm excited to be here. I haven't been in New York, it's probably been more two decades. So it's nice to be back in a big city, I live in a very small place. >> Yeah, so if you go to Times Square, it's now Disneyland, is what we call it. It's not the 42nd street that it might've been a couple of decades ago. I grew up about 45 minutes from here, so it's gone through a lot, love the city, especially gorgeous weather we're having here in the fall. >> I'm excited for it. >> All right, so Josh, Cardinal Health, health is in the name so we think we understand a little bit about it, but tell us a little bit about the organization itself and how it's going through changes these days. >> Sure, so Cardinal Health is a global healthcare solutions provider. We are essential to care, which means we deliver the products and solutions that your healthcare providers need to literally cure disease, keep people healthy. So we're in 85% of the hospitals in the United States, 26,000 pharmacies, about 3,000,000 different home healthcare users receive products from us. Again we're global, so we're based in Dublin, Ohio, just outside of Columbus. But obviously, I live in Canada so I work for the Cardinal Health Canada Division. We've got acquisitions around the world. So yeah, it's an exciting company. We've recently gone through a transformation not only as a company, but from a technology side where we've shifted one of our data centers entirely into the cloud. >> All right, and Josh, your role inside the company, tell us a little bit about, you said it's global, what's under your purview? >> So my team is responsible for Enterprise Monitoring, and that means that we develop, deploy, support and integrate solutions for monitoring both infrastructure applications and digital experience for our customers. We have a number of tools, including New Relic, that we use. But it's a broad scope for a small team. >> Stu: Okay, and you've talked about that transformation. Walk us through a little bit about that, what led to, as you said, some big moves into public cloud? >> Yeah, our team is part of an overall effort to allow Cardinal Health to be more adaptive, to be more agile. The move to cloud allows teams that are developing applications and platforms to make a decision how to respond to the needs of their customers more rapidly. Gone are the days of, "I need a new server, "I need to predict six months from now "that I'm going to need a new server, "put the order in, get it delivered, "get it racked, get it wired." We watch a lot of people, the provision on demand. I mean, our senior vice president, or my senior vice president, likes to say, "I want you to fail fast, fail cheap." He does not say fail often. Although sometimes I do that, but that's okay. As long as you recognize that you're failing and can roll that back, redeploy, It's been really transformative for my team in particular, who was very infrastructure focused when I started with the company five years ago. >> Stu: All right, and can you bring us inside from your application portfolio, was it a set of applications, was it an entire data center? What moved over, how long did it take, and can you share what cloud you're using? >> Sure, so it's been about a two year journey. We're actually a multicloud company. We've got a small footprint in Azure, small footprint in AWS, but we're primarily in Google Cloud. We are shutting down one data center, we are minimizing another data center, and we've moved everything. We've moved everything from small bespoke applications that are targeted on team to entire ecommerce platforms and we've done everything from lift and shift, which I know you don't like to hear. But we've done lift and shift, we've done rehosting, we've done refactoring and we have re-architected entire platforms. >> Yeah, so if you could expand a little bit when we say lift and shift, I'm fine with lift and shift as long as there's another word or plan after that which I'm expecting you do have. >> Josh: Yeah, absolutely. So the lift and shift was, "Hey, let's move from our data centers into GCP. "Let's give teams the visibility, the observability "that they need so that they can make the decisions on "what they need to do best." In a lot of cases, or in fact, in 15% of the 6,500 severs that we touch, we actually full out decommed the instance. Teams had them, they were running at our data centers but they weren't actually providing any value to the company. >> So you said your team before was mostly concerned about infrastructure and a lot of what you did is now on GCP so you fired the entire team and you hired a bunch of PhDs to be able to manage Google environments? >> Absolutely not. (laughter) The principals of enterprise monitoring as a practice still apply in a cloud. We are, at heart, data geeks. And I would fair say that we're actually data story tellers. Our job is to give tools and methodologies to application teams who know what the data means in context, but we give the tools to provide that data to them. >> Stu: All right, love that. I believe I've actually seen data geek shirts at the the New Relic shows itself. But data story tellers, that was kind of thing that you heard, "I have a data scientist "that's going to help us to do this." Is that data scientist in New York or are you actually enabling who is able to tell those data stories today? >> So that is the unique part. Data story telling is not a data science. I wish that I could be a data scientist, I like math, but I'm not nearly that good at it. A data story teller takes the data and the narrative of the business, and weaves them together. When you tell someone, "Here's some data." They will look at it and they will develop their own narrative around it. But as a story teller you help craft that narrative for them. They're going to look at that data and they're going to feel it, They're going to understand it and it's going to motivate them to act in a way that is aligned with what the business objectives are. So data story tellers come in all forms. They come as monitoring engineers, they're app engineers, but they're also people who are facing the customer, they're business leaders, they're people in our distribution centers who are trying to understand the impacts of orders in their order flow, in their personnel that they have. It is a discipline that anyone can engage in if we're willing to give them the right tools. >> All right, so Josh, you got rid of a data center, you're minimizing a data center, you're shifting to cloud, you're making a lot of changes and now being able to tell data stories. Can you tell us organizationally everything goes smoothly or are their anythings that you learned along the way that maybe you could share with your peers to help them along that journey? And any rough spots, with hindsight being what it is, that you might be able to learn from? >> Yeah, so hindsight definitely 20/20. The one thing that I would say to folks is get your data right. Metadata, trusting your data is key, it's absolutely vital. We talk a lot about automation and automation is one of those things that the cloud enables very nicely. If you automate on garbage data, you are going to automate garbage generation. That was one of our struggles but I think that every organization struggles with data fidelity. But teams need to spend more time in making sure that their data, specifically their metadata, around, "Hey is this prod, is it non-prod, "what stack is this running, who built it?" Those things definitely need to be sorted out. >> Okay, talk about the observability and the monitoring that you do, how long have you been using New Relic and what products? And tell us a little about that journey. >> Sure, so we've been using New Relic for about two years. It was a bit of a slow run up to its adoption. We are a multi-tool company so we have a number of tools. Some of them are focused primarily on our network infrastructure, our on-prem storage. Although Cardinal had moved predominantly to the cloud, we have distribution centers, nuclear pharmacies all around the world. And those facilities have not gone into the cloud. So you've got network connectivity. New Relic for us has filled our cloud niche and observability, as Lou announced, is going to give us context to things that we're after. You hear the term dark data, we call them obs logs. It's data that we want to have, we only need it for a very short period of time to help us do post-op or RCAs as well as to look at, overall in our organization, the performance of the applications. For us, New Relic is going to give us an option to put data for observability. Observability is really about high fidelity data. In its world of cloud, everyone wants everything right now. And they also want it down to the millisecond. A platform that can pull that off, that's a remarkable thing. >> Yeah, Veruca Salt had it right, "I want it now." So are you using New Relic One yet? >> We have been using New Relic One for at least a couple of months going back into March this year. It's exciting, we're one of those companies that Lou talked about in his key note, we have hundreds of sub accounts. And we did so very intentfully, but it was a bit of a nightmare before we got to New Relic One. That ability for a platform team to see across multiple sub accounts, really powerful. >> Okay, so you saw a lot of announcements this morning. Anything particular that jumped out, you were excited? Because Lou kept saying over and over, and if you're using New Relic One, "This is free, this is free, this is free." That platform where it's all available for you now. >> I think the programmability is one of the things that really got me excited. One of the engineers on my team had a chance to go and sit with Lou and team, two weeks ago, and was part of that initial Hackathon. Made some really interesting things. That's exciting so shout out to Zack and the work he did. Logging, for me, is something that is huge. I know we've got data that we should have in context. So that Lou announced five terabytes of ingestion for free, all I could do was tap my fingers together and think, "Oh, okay. You're asking for it, Lou. Challenge accepted." (laughter) >> Stu: That's exciting, right. So you feel that you're going to be building apps, it sounds like already, at the FutureHack. That you're starting to move down that path. >> Definitely, and I'm really excited. Not to necessarily give it to my team. We build the patterns for teams that needs patterns, but there are so many talented individuals at Cardinal Health who, if we give them the patterns to follow, they're just going to go execute. Open sourcing that is a brilliant idea and really crowd sourcing development is the way to go. >> Yeah, I think you bring up a really interesting point. So even though your team might be the one that provides the platform, you're giving that programmability, sensibility to a broader audience inside the team and democratizing the data that you have in there. >> Yes, you keyed in on one of the things I love to talk about which is democratized access to data. Over and over again you'll hear me preach that, "I know what I know but I also know what I don't know "and more particular I don't know what I don't know. "I need other people to help me recognize that." >> We've really talked about that buzzword out there about digital transformation. When it is actually being happened, it goes from, "Oh, somebody had an opinion," to, "Wait, I actually now can actually get to the data, "and show you the data and leverage the data "to be able to take good actions on that." >> That's right, data driven decision making is not just just an idiom. It's not something that is a buzzword, it is a practice that we all need to follow. >> Stu: All right, so Josh, you're speaking here at the show. Give our audience just a quick taste, if you will, about what you're going to be sharing with your peers here at the show. >> We've actually talked about a lot of it already so I hope that people are not going to watch this session before my session later. But it really is around the power of additional transformation, the power of observability, what happens when you do things right, and the way the cloud makes teams more nimble. I won't give you it all because then people won't watch my session on Replay but, yeah, it'll be good. >> Well, definitely they should check that out. I'm hoping New Relic has that available on Replay. Give the final word here, what you're really hoping to come out of this week. Sounds like your team's deeply engaged, you've done the Hackathon, you're working with the executive teams. So FutureStack 2019, what are you hoping to walk away with? >> For me, it's about developing patterns. My team, in addition to our enterprise architecture team, is responsible for mapping out what we're going to do and how we're going to do it. Teams want to go fast and if we're not going to lay down the foundation for them to move quickly, especially in the realm of enterprise monitoring, they're going to try do it themselves. Which may or may not work. We don't want to turn teams away from using specific tools if it fits, but if there's a platform that will allow them to execute and to keep all that data centralized, that is really the key to observability. Having that high fidelity data, but then being able to ask questions, not just of the data you put in, but the data that put in maybe by a platform team or by a team that supported Kubernetes or PCF. >> All right, well, Josh Biggely, thank you so much for sharing all that you've been going through in Cardinal Health's transformation. Great to talk to you. >> Thanks so much, Stu. >> All right, lots more here at New Relic's FutureStack 2019. I'm Stu Miniman and as always, thank you for watching theCUBE. (light techno music)

(upbeat music) [Narrator] - From New York City, it's theCUBE. Covering New Relic Futurestack 2019. Brought to you by New Relic. >> Hi, I'm Stu Miniman and the theCUBE's exclusive coverage of New Relic Futurestack 2019. We're here at the Grand Hyatt which is right next to Grand Central Station in beautiful Manhattan, New York City. We're going to be speaking to a number of customers as well as the executives. It's the seventh year of the show, our first year here and helping me kick off the event, always happy to have a customer on. Dirkie Gertenbach, who's the global B2B engineering lead at AB InBev, a local customer here. Dirkie, thank you so much for joining us. >> Thanks, nice to be here. >> Alright, so, nothing better than getting together with a bunch of your peers you know, downtown New York City, talk about, you know, some cool technology. Before we get into the tech though, I think most people understand AB InBev you know, global beverage brand, really well-known, I know I saw beer trucks when I was making my way through New York City. But tell us a little bit about, kind of, the company and your role inside it. >> Yeah, sure. So, yeah, we're a global beer company, we sell beer. My main focus is the engineering lead at InBev and we look specifically at the e-commerce side of it. So, the digital sales. We've been going through a large transformation these last couple of years, where we flew from more traditional sales to like, digital sales, and we've been implementing our e-commerce platform in a couple of countries the last couple of years. >> So, transformation, it's not just that AB InBev goes from a couple of the largest known brands, you know, in the beverage to "oh boy, now there's so many different micro beers and and different things, I know I can't keep up with all the locals", but even a large brewery like your company - has all little brands, a similar thing I guess is happening on the technology side. >> Yeah. >> Yeah, maybe, tell us a little bit about you know, what that transformation, you know, what's causing that transformation and what is happening inside your or, to support this transformation? >> Yeah sure. So when we started off the digital transformation obviously, it was much simpler. We had a couple of applications in only one or two countries. And in these last two years we've been expanding and we've been implementing it in other countries and we've started moving from a monolithic to a more micro service central so obviously it's like not only one application now, it's like, it's hundreds of applications. In the beginning, it was quite tough because we were moving, we were developing stuff much more quicker than what we could support and that's when we started talking to New Relic. And we looked at their product and looking at a couple of ways of streamlining this operational and having more of a a stability on our products overall. Like, there's still have a lot, we are still immature in a lot of spaces. >> Yeah, so bring us in. You talked about you applications. You know, so many customers are going from their monolist to their micro services but they usually have, you know, that transition is not something that's done overnight, and they need to be able to manage all of that environment. Give us a little bit of view into, you know, what you can about your application portfolio, where you are on that journey and then, you know, what tool sets are you using to be able to manage, monitor and you know, the word of the day of course is observability, so you know, what that means to you and your-- >> Yeah sure, so like I said we've (mumbles) into micro services which is (mumbles) There's a lot of different applications that's running and the main thing that it showed is just having visibility on infrastructure as well as application performance. And application where it's optimal or not. So those are the most basic. We got New Relic involved and that's one of the main tools that we use for observability today. We were using a couple more but we are, like, putting everything into one bucket now. So, it's interesting, the new stuff. What they announced today, that's one of the stuff that we've been missing that's really going to help us. Especially the data base monitoring and the network monitoring. That's something to all our stuff is on Azure so we rely a lot on Azure monitoring. But it doesn't always give you that granularity of like, observability. One of the other things that we are excited about is the, what's the other thing? Sorry, I forgot, I'll come back to you. >> That's all right. So first of all, you know, are you using New Relic One from New Relic? >> We're starting to use it now, so we still use-- >> So walk us through a little bit the journey with New Relic. What products were you using? And tell us where you are with the platform and what you think of the vision of, as Lou said, it's a capital P platform in certain characteristics, that New Relic built when they had in mind? >> Okay, yeah, sure. So in the beginning we were using the browser and Sonetics just like a normal looking whether that website is up or down, and then we started looking so we've got ABM running on every single server we've got now, that gives us like a lot of visibility and we use the insights a lot, so just dashboards. What we found in the new One platform is the dashboard so we can create the linear of data and the visibility that we can give to our stakeholders. It's much better. Just the visibility on the different. I can give you a couple of used cases that we've gone through in these last couple of weeks. So for example, on one of our applications we're having like, login failure, a lot of login failures. And we are really struggling to look at locks and stuff and just pinpointing with that. So on all the data that's coming into New Relic, we started creating dashboards where we can actually see what's the different causes of these login failures and we can actually pinpoint where do we need to put our focus? So it was a good example. And then the other nice thing that I like about the one that we are using actively is the Kubernetes monitoring. It gives you visibility of your entire cluster every single product that's on there and you can just quickly see if there's a part that's struggling or not. >> All right. If you can, I was wondering if you could bring us inside your Kubernetes? How long have you been using it? Do you build your own or using one of the cloud or some other solutions? Tell us a little bit about your stack. What that solution, and where New Relic fits into it? >> Yeah, we started off the Kubernetes just over a year ago. We're using Azure AKAs. So all our stuff is in Azure. And so yeah, in the beginning, we built all of the applications and everything ourselves, so it's all out set. And again, just coming back to monitoring within Kubernetes, it's all controlled. Like (murmurs) It's difficult to have clear visibility so yeah, when they brought out the Kubernetes like monitoring that was like a life changer for us. It's just operations, we're being much more productive now in terms of if we need to scale up and whether our reports are healthy or not that definitely helps a lot. And I think that we've been working (mumbles) It's just the DevOps, we're very new in DevOps, and just the visibility that New Relic gives us helps us a lot in like, pinpointing where we need to focus our DevOps effort. So that's also a good help. >> Stu: Okay. You'd mentioned that there was some things announced that had you excited, things that you'd been looking for. Maybe you can explain, you know, which items jumped off the board at you this morning. >> Yeah, so again, just the database monitoring and the network traffic. That's very important. And then the one thing that's, we were just busy investigating a lock analyser. And the lock ingestion that they announced today that's very exciting. So I mean, we're already in New Relic so I think we're definitely going to look at that. That's going to be a big help. And then it just brings all our data together. And after you've used different tools for locks and monitoring, that's something that makes me very excited. And the other thing is, we're also use SAP in (murmers) and the partnership that New Relic is staring with SAP now, that's also very exciting. Something I'm seeing forward to. >> Stu: Okay. Was there anything you were hoping for that you haven't seen yet? Or anything on your wishlist that you want from either New Relic or from Azure, or from the industry as a whole? >> Nothing yet. I mean, like I said, we're still at early stages. I think maybe in the next year or so we're probably going to start saying, "Hey guys, maybe you need to build this as well" but for now it's just like they keep delivering stuff that before we can even think about it. So that's great. >> Uh, Dirkie, it's your first year coming to Futurestack. What specifically bought you hear? What are you hoping to get our of the day? >> Yeah, it's my first time here. Hopefully I'll come, like I said, I've only got a couple of hours today but I think just in terms of seeing the new stuff that can help us in our operations, our business operations and as well as Stave Apps, it's exciting to see how this can transform our business going forward. In terms of what else I want to see, I don't have high expectations at this stage. Like I said again, they keep delivering before we can actually say what we want so that's just great. >> You mentioned that you're early in your DevOps journey inside the company. Any other color you want to share about, just kind of organizationally what's changing in your business? You know, there's so many new things coming on. You know, you've watched Kubernete's a year ago, you're getting into logging, so the roles and responsibilities that your team members have, and keeping up with all of these various technologies, how's that impacting the work force and the jobs that they do? >> Yeah that's great. So again on our services that we've got we've got a lot of new teams as well, and we've been in a kind of a hyper growth stage, and we're building a lot of micro servers and stuff. We struggle to know whether the performance of that micro service is good enough or not. So that's one thing that our developers struggle with and that's something that New Relics has helped us with. Every single service that we've built, we put it on New Relic, and we've got a, like, you can see three days ago what has been average performance of this API. And that helps us also to type back to (murmurs). So we've got this arranged with each of our services, for our API inpoints , and this gives us a easy way to see whether we're on track or not, and it then translates back to the developer on whether they need to do something to increase that. Another great thing that we've been doing with New Relic with the VP of engineering is they've been helping us a lot in setting up our sites reliability teams. So we've had a couple of discussions with them these last couple of weeks and they've helped us a lot in just identifying what's the different teams that we need to bring to our organization to keep operating in this way and the growth that we are. Also something that's great that we've been looking at, and New Relic has also helped us a lot there, we had a lot of monitoring, we're monitoring everything, but the data doesn't, we don't make a lot of use with the data. So what we've started doing now is to say, "Okay, what's the most (murmurs) path on our application?" "What is it the customer needs to do?" "What's the journey he needs to go to get his (murmurs)" And that's our most critical. So then we went and we worked with New Relic to say that, "Okay guys." "so help us map this to what's the infrastructure." "What's the application that needs to be up to support this journey?" and we created thresholds on that, and alerting. We're almost at a place now where we've got all the stuff mapped and alerted, and proper actions on that, which is also great. It's helping us to be more pro-active and we rely less and less on our customers to tell us, "Hey, there's a problem on the application." >> Stu: Alright. Lou was talking about all the applications that can be built on top of this platform. I saw the network flows, do we think we're going to see the beer flows by the time we come back a year from now? >> The network flows is great. So I need to do a little bit more deep dive onto the application build, but I can start thinking of a couple of examples where we can really use that to deep a little bit deeper into what the data that we've got day to day. So yeah, that's also exciting in the future. >> Well Dirkie Gertenbach, thank you so much for sharing what your groups going through at InBev. Thanks so much for joining us. >> Great. Thank you Stu. >> Alright, and lot's more coverage here at New Relic, Futurestack, in New York city. I'm Stu Miniman and thanks for watching theCUBE.

Oh from Las Vegas it's the cube covering AWS reinvents 2018 brought to you by Amazon Web Services Intel and their ecosystem partners well good morning welcome back to AWS reinvent this is day three of our coverage here on the cube we made it we have survived the show here that been a great show and still a lot of energy out here on the show floor Justin Morin John wall's we're with loose Ernie who is the CEO and founder of New Relic and and Luffy look just over your left shoulder there's that really impressive New Relic Pavillion you've got there we've been admiring it all week so that's a great show for us and you know our our theme this yours is billed fast and break nothing because that's really the objective of moving to the cloud is building software that customers value as rapidly as possible when you're building stuff fast there's risk and so how do you build fast with breaking nothing it's measuring everything in real time everything in that environment seeing exactly what's going on so you can make sure the stuff you're building works for your customers and that's what we do for so many people were adopting the Amazon Cloud kind of reminds me of John Wooden yield UCLA basketball coach had said be quick but don't hurry that's all right so that's right so it was all about pace and I understand putting that culture in the team so how do you put that culture and into with your well I you know it's it's one of the great truths how can you manage what you can't measure so we're a company that makes it trivially easy to measure software infrastructure digital customer experience our customers come to us every day and say what I love about New Relic is within seconds of setting up my account and and deploying the agent all of a sudden production is lit up I can see what's going on that measurement helps our customers have more confidence moving to the cloud faster deploying more frequently delivering customer value more rapidly now one of the themes that we've had over the last couple of days and John and I were talking just before we came on this morning that complexity yeah we've been hearing that time and time the amount of change it's happening so quickly and we've got all of these different systems we got micro services we've got containers we've got serverless it's a really complicated environment yeah how do you help the humans understand how how do you get them to understand what's going on in this really complex environment that's moving so fast you're you're absolutely hitting on the key challenge and what we're great at what our customers tell us they love about us is we simplify that complexity and and there's how do we simplify it well we have a deep understanding of how these systems work and we've fought very hard about how do you surface the interesting information that's most relevant to understanding the health and application and really in that moment when there's a problem how do you make it as easy as possible to understand the cause that problem as rapidly as possible this is like our customers they're right in the you know right in the pit of the most high pressure situations when there's a production issue every second counts every second counts you got to find that issue as rapidly as possible and what our customers tell us is they're sick of having to juggle around between three four five many of our customers have dozens of tools that are intended to watch production they turned a new rally platform cause it's all in one platform and when seconds matter you don't want to be switching between tools and context to understand what the nature the problem is and that's that's super important it's kind of like we all become pack rats in a way right yeah we save things we just keep putting them in this room and this room in this room and it comes time to kind of clean up or yeah get our act together and that's what you're doing for people is helping them get their act together absolutely and once you've got an understanding of how the system provides you go from overly cautious and timid to confident and with that confidence you can start playing offense with software we talk about all the time 15 20 years ago IT leaders thought of software as a defensive mechanism when I say defense I mean it's a way to reduce costs how do I reduce the cost of billing how do I reduce the cost of handling a support call now it's offense it's the growth engine for these companies right the digital customer experience is driving top-line growth and so when you're confident your ability to move fast with your software you're actually participating to growth your company that's why it's so strategic that's why the cloud is growing so rapidly so if you've got a customer who's not with you really clearly you want them to they should be going with you what if what does it feel like to go from not having New Relic in there and dealing with this complexity and having those struggles and then as you've put in New Relic for the first time what's what's that onboarding experience feel like I once was blind and now I see John Newton America it's truly that our customers tell us that before I discovered new relic I had no idea was going on production and it was opinions that we're telling us what was going on and when you've got a bunch of teams working on a complex system and there's a problem and it's like the loudest opinions gonna determine how you go forward that results in chaos and it results in organizational misalignment and with data all of a sudden people are lying on how you move forward yeah so with all that data that's there I mean that that can actually be complex itself if I'm trying to see everything all at once that that can be overwhelming so how do you help customers dial in on what's actually important within this this sea of information that they can now now look at well you know we have a variety of ways in which we approach that problem um the first is an opinionated user interface okay we have more experience in the realm you know my first company I founded in 1998 created the category of application performance management and so I've been thinking about this problem might ease the think about this problem for a long time we come to our customers with an opinion on what matters in the application environment but even then beyond that we're layering on well AI but we call it applied intelligence because artificial intelligence people overuse the term and honestly our customers don't care whether we're using a collaborative filter or good old-fashioned algorithms but they want to split more smarts in our platform to tell them what's anomalous tell them what's abnormal tell them what to pay attention to in this sea of data you really collects about 15 million data points every second off of our customers applications and infrastructure and digital customer experiences 15 million data points every second coming to the New Relic Cloud and we analyze all of it in real time to service to our customers what's important what's anomalous and what's interesting yeah so let's get into that let's go about what's anomalous and what's interesting yeah how do you differentiate that because as you said out of 15 million data points every second yeah I mean you're gonna develop trends but but it's by the time you evaluate it seems like one set of data you're off to a completely different set of data and you're right this is a very dynamic environment well the combination of an understanding of how applications work in general but then the flexibility to recognize you know how an e-commerce application might be very different from a Content application like USA Today networks is a big New Relic customer and so we need to provide enough of a platform that our customers can give New Relic some guidance on the nature of their application and and and we can discover its architecture and we can discover things about it but we we really can't discover its business purpose and so there's a combination of what we do out of the box with the customizability that that get our customers the point where the software's doing the work for them you're on so having been in the show now for three four days what have you seen around here what a customer's looking at that they're gonna bring it bring it on to their environment next what are some of the things I think you know lambda is coming mainstream right right and so when we think about where where the world is going you know micro services are going to be here for a while just like all the other technologies you said like the packrat analogy is true but future in the future when someone starts a brand new project they won't even think about infrastructure they'll just think about their code and new relics philosophy on visibility is you start with the software because the software is that the whole the business logic the whole point of all this infrastructure is to run software and so our most important starting point for visibility is the software itself we just made an announcement this week about delivering the first product that automatically instrument lambda to tell you if your lambda function is misbehaving exactly how is it doing that and so as the world continually moves from the old IT used to obsess on infrastructure and and and and new ideas is obsesses on how do we deliver more software faster and that that aligns very well with what we're great what our philosophy is on delivering his ability it starts and ends with the software and it feels like people are going into lambda really quite quickly because absolutely moving with some meetings this morning that they were saying that there's enterprises in particular may not have actually jumped onto the container bandwagon yet but they've looking at laminate is going you know what we're just gonna skip leapfrog to that yeah I'm seeing quite a bit of that containers still have an awful lot of value there they're wonderful lightweight ways to host what used to be on you know in a virtualized environment and get that isolation all that benefit kubernetes is also a big deal we made an acquisition of a company called coast scale that we announced last quarter that accelerates our capability to do work in kubernetes environments we're always inspired by what our customers are doing to accelerate how they build their software and that inspires us to make sure our platforms continually their tool a choice to make sure they can see the entire environment so you're getting as much for them as they're getting from you absolutely it's a great partnership we have with our customers we learn from them and then we provide them with thought leadership on how do you think about making sure you're seeing the entire environment so you can spend more time delivering great software and less time debugging it excellent well let's get back to that great booth of your awesome great for being with us we're sharing our a relic story and success on the the last day of the show all right well mate ok all right excellent right loser T joining us you from New Relic back with more here with AWS reinvent you're watching the cube from Las Vegas

>> Live, from Washington, D.C., it's theCUBE, covering AWS Public Sector Summit 2018, brought to you by Amazon Web Services and it's ecosystem partners. >> Welcome back to the District, everybody. This is theCUBE, the leader in live tech coverage. My name is Dave Vellante, and I'm here with my cohost, Stu Miniman. Day two of the AWS Public Sector Summit. We saw Teresa Carlson yesterday, a lot of keynotes, we saw the CIA. Todd Osbourne is here, he's the Vice President of Alliances of New Relic, a company that's been smokin' hot, six billion dollar market cap, and really is takin' the world by storm. He's joined by Scott Drossos, who's the president of Infiniti, who is a public sector consultancy. Gentleman, welcome to theCUBE, good to see you. >> Thanks, good to be here. >> Thank you. >> So Todd, you heard me, I mean really, everybody's talkin' about New Relic, stocks been smoking, I read an article recently, "it's got to cool off, it's too hot." So why so hot, what's goin' on, why the appeal of New Relic? >> Well as our CEO Lew Cirne has been on a couple of times talking to you about, every business is becoming a software business in the public sector, which we're here representing at the Amazon public sector event. It's the same thing with agencies and all the digital experiences that are happening across all the government and whether it's education, higher ed, healthcare, any of the DOD or other agencies, there's always some sort of digital experience that folks are having with the citizens that all the agencies and organizations are tryin' to support, and New Relic's right there, right there at the forefront of every one of those digital experiences. Everyone's running software that's modern software, or shifting to that with modern software running microservices, running containers, shifting to the cloud, and anyone deploying that type of software needs to have New Relic as part of their engagement to monitor what's happening at the citizen or the customer level, what's going on in the back end, on through the infrastructure. And New Relic, whether it's a large enterprise that we're out there, like Dunkin' Donuts or Dominos, monitoring their applications and their eCommerce sites, or it's an agency in the public sector space, you got to have New Relic as part of those engagements. >> So Scott, when AWS services first came out, 2006 timeframe, we looked at it, we said okay, this is the future, but as much as it potentially simplifies lives, it brings a lot of new complexities. So you know, Stu and I used to talk about, look, the AWS is awesome, we're big fans, but the ecosystem has to grow. Consultancies have to come out of the woodworks, and help customers really, adopt. So that's really exactly what's happened. I presume that's how Infiniti got started, maybe you could tell us a little bit about the company, and what your value is. >> Sure, thanks Dave, so Infiniti is a 15 year old company. We're originally founded in public sector IT consulting, and we realized several years ago that the world was changing and that we needed to make the shift from IT consulting to cloud services. And so we dove in headfirst with AWS, and we really tried to move to the top of the curve very quickly, and so we were a little bit ahead of our market in public sector, being a public sector focused organization, but we felt it was important to get ahead of the market because now the market really is smokin' hot. But we thought it was important that if we're going to move into the cloud, we wanted to move to the top of the curve, and deal with things like DevOps, migrations, even machine learning, predictive analytics, so we kind of pride ourselves on having some of the largest public sector contracts in the US, even though we're, right now, predominantly California based, California focused. >> And what's your head count? >> We're about a hundred people. >> I mean this is the thing, we're seeing this trend toward a lot of, you know, smaller specialists, are really doing super. Why is that, or how are you able to differentiate from these big global SIs that have tens of thousands, hundreds of thousands of employees, vertical expertise, why are you guys winning? >> Well, first of all, I think we're able to be nimble and shift our focus pretty quickly to serve our market, to serve our customers, I think more successfully. But one of the thing's that's changed when the cloud arrived, is the cloud really let smaller organizations like us, act like big organizations, so we didn't need to go deploy millions of dollars of capital to go set up a massive data center, we can build an environment on the fly, as you know, in the cloud, and we can have access to world-class platform tools like New Relic, and we can help a customer, a large customer, perform just as well as if we were a large multi-billion dollar services organization. >> Todd, one of the interesting things to talk to customers about is their journey, and where are they, and the cloud migration and how do they do this, reinvent? A year ago or two I heard there were like seven or nine ARS to get there, anything from the full refactoring and building cool new stuff with server lists and things like that, to just the re-platforming. Lift and shift, is that a good thing, isn't that? Walk us through how New Relic with Infiniti, how are you involved in some of those migrations? There's no typical customer, but give us some examples. >> Yeah absolutely, so Infiniti, just like many of the integrators that we work with are all delivering services generally in a couple different areas. One is typically a cloud adoption, or cloud migration practice. So working with Amazon, how do we get more and more of customer's workloads shifted to the cloud? Usually those projects are also going on with something in the refactoring world or application space. Usually they're also developing or shifting to some sort of DevOps practice, and that's also part of our sweet spot, what's happening in the application there, whether it's on the cloud yet or not, we're going to provide that visibility to that. And then the third piece is, there's usually something else happening with that, as I was mentioning before, the customer experience or the citizen experience, so what's the browser impact, what's the user experience on that, what's the, if it's on a mobile app, what's the user experience on there? So while Infiniti's delivering all those services for the clients, New Relic's part of all those services, so our whole model that we're tryin' to do with all of our partners is embed ourselves into all of those services, such that we can help Infiniti be more successful, deliver those projects on time, and really resolve any issues that may come up during those migration issues. >> Scott, I'd love to hear especially, I know I hear DevOps talked about a lot in New Relic's customers, is it pervasive around the agencies that you work with and please do add some color there too. >> So in the public sector, it's a range of readiness, but we're seeing a real wave building, we believe. We worked with New Relic on a very large DevOps, SysOps, very complex cloud services engagement, largest higher education cloud services engagement in the US, and in that case, just like Todd was referencing, when we implemented the migration of the legacy platform to the cloud, first of all we had to do, make choices around refactory, host, rearchitect and so forth, but then when we're managing that environment, and there's millions of users hitting that environment, we need to be able to make sure that we can monitor the application to make sure the application's performing well, and if there's an issue, we want to see the line of code that's causing the problem as quickly as possible so we can keep the environment up all the time. Even though public sector may not be driven by the same financials as say, commercial, they still expect to be up all the time. They still want to take advantage of the benefits of the cloud and so New Relic allows us to do that, but then, as we're looking at the users interface with the application environment, New Relic's browser and mobile, they let us monitor how that experience is going, and we can proactively get at the performance issues there that the application may not tell us, if there's an issue there. And then, we can do things like test middleware with synthetics and make sure that the whole environment's working, and then obviously on the infrastructure side, it lets us make sure that we're optimizing the environment for our clients. One of the cool thing is, when you in the past, you'd set up an EC2 instance, you may not see that you don't need as much CPU as you're using, and so you can size that appropriately, and allow your environment to still run at a high performance, 100% up time, but give them the cost efficiencies at the same time. So we use New Relic across board to help support the entire environment. >> I wonder if we could talk about the marketplace a little bit, generally and then specifically, the public sector? So Scott, I presume you're obviously public sector focused, but are you exclusive to AWS, no, you probably do some other stuff, is that right, is that fair? >> Well we are both AWS and Azure Gold, in terms of partner, but we do more of our work in AWS for sure. >> Okay, so we'll come back to that. And New Relic, of course you're a software company, so you want everybody to love your software, so if there's a cloud that a customer wants to use, you want your software to be on that cloud, fair enough? >> Sure, and also on PRIM, I mean a lot of our... >> On PRIM too. >> A lot of our applications we monitor are still on PRIM, and there's a tremendous amount of value there regardless of... >> I would just add, Infiniti is a trusted advisor, we like to see ourselves as a trusted advisor, so we do feel like we have to be multi-cloud and have an objective perspective. >> And New Relic is presumably the same way, I mean let the customers decide, so, and it's a hybrid world, folks, despite what Amazon wants, it's a hybrid world, and they even recognize that. My question is, there's a lot of discussion in the industry about Amazon as an infrastructure service provider and their lead or relative lead on the competition. It's our sense that there's still a lead there, what's your sense? >> Well AWS is still the leading cloud services provider in the marketplace. They lead in innovation, they lead in disruption, they lead in market share, they lead in so many metrics, and because they have that lead, and that's where we started, we've benefited from that, and we've invested heavily, and in the same way, we see New Relic, when we made a choice around who we were going to pick as a platform to support our customers, we wanted something that was cloud-born, didn't come out of on-premise and get sort of bootstrapped into the cloud, and we wanted something that was a complete platform. So New Relic was really a clear choice for us. It was not a, we looked at the entire market when we made that choice. >> So the narrative in the market used to be, oh, security in the cloud, now we hear the CIA say hey, security on the worst day in Amazon's cloud is way better than I ever saw with client server. It was a pretty powerful statement, so let's assume security, people are relatively comfortable with security these days, even though I'm sure there's still some issues with regard to corporate edicts, and flexibility, and audits, let's put that aside. SLAs is another big one. People often criticize the public cloud SLAs, and cost, oh it's so expensive, I can do it cheaper on PRIM. Are those myths, are those realities, is it a it depends? What's your sense? >> I mean they're all, they're all factors that all of our customers are looking into. I would say what we're hearing a lot about right now, is how do we help provide more visibility to everything that's happening, so if you've got a developer now that has the ability to write code, put it on any cloud they want, spin up containers, spin down containers, go try out server-less base of architectures, they've got a lot of flexibility to do what they want. Government agencies, as well as customers, one of the things they're looking for is what's actually happening? Who's doing what? The governance piece is a big piece and I think New Relic plays right into that in terms of helping control all that. One of the things that we're, is one of our sweet spots, is as you move to DevOps and a truly microservices architecture, one of the whole values of that is speed, keeping up with how fast the whole market is moving, and customers and agencies, what they want out of that, is to deploy applications where they're releasing multiple times a day. You have to have visibility into everything you're doing across the stack to be successful in that, and that's really New Relic's sweet spot in terms of doing that. So providing that visibility, instrumenting the applications in the infrastructure before, and then helping provide visibility to things like governance, things that other, not necessarily our sweet spot, but other companies in the industry are doing things throughout the DevOps life cycle in the governance realm, things like that. So we're part of that ecosystem that's helping Amazon and the other cloud providers be very successful, helping customers and agencies be very successful deploying modern applications. >> It's all about that visibility. >> Scott, one of the things, when we look at any rollout of new technology or migration, once it's up and running, then what, so wondering how your firm's involved in, you know, is there re-training, is there things go on, once this is in place, now what? >> Well Infiniti, what we found in public sector is that everybody wants to take advantage of the cost efficiencies and the benefits, and most public sector isn't going to reduce cost, they're just going to want to re-use cost more wisely. So some of the confusion around cost savings is that they're getting way more for their dollar in the future state, and the choices you have to make around how fast you want to get to the cloud, and what you want to get out of the cloud when you're there, those all effect the equation in terms of what you're actually outcomes are immediately and in the long term. So we often see that in public sector, some of the legacy applications, they may not naturally or easily move all at once, and so you have to make a choice, are you going to do some refactory and architecting before you get it there, are you going to get in the cloud now, and then do it afterwards. Either way, there's benefits, but you have to make choices about what, how you want to approach it. >> Yeah, when you talk about, after I've rolled this in, I've heard from some customers, they're like, after I've gotten a cloud, I love it, but I had to dedicate an engineer for financial architecting because there's all of these things we need to do. Are we still in that state? And once again, do you help with some of the training as to, okay, or is it plugging them into the Amazon ecosystem and how do they get certified and ready to use all of this. >> So Infiniti works with clients differently, we work with some in a more episodic, lighter capacity, and we work with some in a wholistic capacity where we are that engine for them, where we provide them the complete cloud services team to do everything from migrations, architecture, DevOps, SysOps, SecOps, machine learning and all the way through. And so when we're providing those services, we're doing those kind of things, we're making sure that the next improvement is worked into the architecture. Last year, the customer I was referencing earlier, we did just under a hundred releases, so that's a hundred releases that we're using the New Relic platform and our architectural solution, our solution architects, rather, to make sure that it's faultless, that the process is efficient, it's effective, it's secure, and that we're driving efficiencies wherever possible. So it really depends on what the customer wants. If the customer wants to hone the environment, they may have to go a little slower to account for their learning, their learning curve, and we'll help them, if that's what they want, but if they want to go faster, and they want to take advantage of our expertise, we make that available, and we're happy to do that. >> We had the former CTO of the NSA on yesterday, who now works for Accenture, and we were asking about sort of, federal versus commercial, are we sort of still taking, learning lessons from commercial and bringing it to federal, or is it because federal has so much interesting technology around analytics, does it go the other way, and he said, "it's funny, when you're on the inside, you think all the innovation is goin' on outside, now that I'm on the outside I say wow, there's a lot of interesting stuff going on in federal." We heard Teresa yesterday talk about Aurora, she talked about the VM wear partnership, so things that were announced a while ago and actually being adopted in commercial coming in to federal. So how does it work? Is it more of a two-way than it used to be 20 years ago and I wonder if you could comment? >> Yeah, from Infiniti's perspective, absolutely. We work with clients to understand the problems and where they want to get to, and then we innovate with them. You're pretty dependent on the subject matter expertise of the organization. I think our customers like that, they like that they're part of the solution, but then they need the expertise that we bring to create the next generation solution. We just created something in the higher ed space called, a college called Architecture Builder, and it was after teaming with a specific college, and working in that space for a long time, but we wanted to create a way for colleges to rapidly implement a complete architecture integrated with all the different things, including New Relic, quickly and successfully, and that was done in partnership with them, so we did the work, but we couldn't have done it without them. >> Todd, New Relic obviously, you're a believer, you drink the Koolaid every day. Why New Relic relative to the competition? How do you guys differentiate? Pitch me. >> So it's really all about being successful in that modern software space, again, as I've mentioned, and so New Relic is the only SAS only platform, so we're not going to put anything on PRIM. We've got ourselves one of the biggest and best DevOps team that develops our software, we roll code everyday, and our customers get the benefit of us being a pure SAS platform. Part of that is scalability. What we can do at scale is unbelievable. There was a customer that was just talked about on the news today that I can't mention, but they just went from basically zero to $100 million on an application just in the past 90 days. It's one of our customers and we've scaled, we have no problem scaling with customers that are doing things like that, and again, the full platform value that we have now, looking at everything from the front end on the browser and mobile applications, through the application, which is core to us, it's where we provide that code-level visibility, the ability to trace across all the different microservices that are happening, connected back to that infrastructure. That full platform now provides such tremendous value up and down the stack, but not only to the technology leaders but also to those folks that are business leaders, chief marketing officers, heads of practices at the consultants we work with, all these folks are all getting value out of New Relic. >> What would that customer who should not be named say about the value contribution of New Relic to that scale? >> The value's unbelievable. That's a commercial customer, but their business is taking off like so many of our customer's businesses are at an unbelievable scale. They can't be hamstrung by having to do a server upgrade, or having to go back, working with a release of code from a couple weeks ago, they have to be as fast as possible 'cause their business is moving so fast, their agencies are moving so fast, they need a provider that's going to provide that visibility to that at the speed with which they're moving. >> Awesome so, you got one more? >> No, we've got to run. >> Yeah, we've got to go. So this is the last question, so impressions of AWS Public Sector Summit? I presume you guys, like we did, had to register yesterday. There were some logistic issues, but other than that, maybe you could give us your last word on the summit? >> Well Infiniti is very committed to public sector, so we really enjoy coming to the Public Sector Summit. It's great to connect with our partners, like New Relic and others, and it's great to see the latest innovations coming out from AWS. >> Yeah and I've been to, I don't know, 10 or so summits around the world so far this year. It is unbelievable the excitement and the amount of people that are now excited about what's happening in the clouded option world, and Amazon's piece in that, and what's happening here in D.C. this week is no exception. >> I would second that. It's been a while since I've been at summits. Stu, you go all the time, and they are just exploding and growing, and this is one of the best that's out there. So thanks guys, for comin' on theCUBE, we really appreciate it. >> Thanks very much. >> Thank you for the opportunity. >> You're welcome. Alright, keep it right there everybody, Stu and I will be back with our next guest after this short break. John Furrier's here, you're watchin' theCUBE live, from AWS Public Sector Summit. We'll be right back. (upbeat music)

(fast-paced instrumental music) >> Hello everyone, welcome to the special CUBE conversation, here at theCUBE Studio in Palo Alto. I'm John Furrier, Co-founder of SiliconANGLE Media and host of theCUBE for our special CMO signal series we're launching. Really talkin' to the top thought leaders in marketing, in the industry, really pushing the envelope on a lot of experimentation. And Robson Grieve, Chief Marketing Officer of New Relic, is here. Welcome to this CUBE conversation. >> Thank you, excited to be with you. >> So, New Relic is a very progressive company. You have a founder who's very dynamic, writes code, takes sabbaticals, creates product, he's a musician, is prolific. That kind of sets the tone for your company, and you guys are also state of the art DevOps company. >> Robson: Yes. >> So, pressure's on to be a progressive marketer, you guys are doing that. >> Yeah, I think some of the great things about that DevOps culture are process wise it allows us to experiment with different ways of working. And we've obviously talked a little bit about Agile and the way a different way of thinking about how you actually do the work can change the way you output the kind of things you're willing to make, the way the teams work together. And the degree to which you can integrate marketing and sales, really, around shorter time frames, faster cycle times. And so, we have a great culture around that. We also have a really great culture around experimentation. I think that's one of the biggest things that Lou talks a lot about is, let's try things, let's look for experiments, let's see where we can find something unexpected that could be a big success, and let's not be afraid for something to go wrong. If you can do that, then you have way higher odds of finding the Geo TenX. >> And you guys are also in the analytics, you also look at the signal, so you're very data driven, and I'll give you a prop for that, give you a plug. (Robson laughing) New Relic, a very data driven company. But today we're seeing a Seed Changer, a revolution in the tech industry. Seeing signals like cryptocurrency, blockchain, everyone's goin' crazy for this. They see disruption in that. You've got AI and a bunch of other things, so, and you got the Cloud computing revolution, so all of this is causing a lot of horizontally, scalable change, which is breaking down the silos of existing systems. >> Yeah. >> But, you can't just throw systems away. You have systems in marketing. So, how are you dealing with that dynamic, because we're seeing people going, hey, I just can't throw away my systems, but I got to really be innovative and agile to the real-time nature of the internet now, while having all those analytics available. >> Yeah. >> How do you tackle that, that issue? >> Yeah, there's a couple ways to think about analytics. Number one is, what do you need to know in real-time to make sure things are working and that your systems are up and running and operating effectively? And that runs through everything from upfront in web experiences and trial experiences, that kind of thing. Through to how our leads and customers progressing through a funnel, as they get passed around the various parts of a company. But then the second approach we take to data is, after all that's happened, how can we look backwards on it and what patterns emerge when you look at it over the scale of longer period of time. And so, that's the approach today. You're right, you can't just everything and throw it out and start over again, 'cause some startups stop by with a really cool idea. But, you have to be aggressive about experimentation. I think that's the, back to that big idea that we talked about experimentation. We are trying out a lot of different things all the time. Looking for things that could be really successful. Of course, Intercom is one that we started to experiment with a little bit for in product communications and we've expanded over time as we found it more and more useful. And, so that's not, we haven't taken and just ripped something else out of it, made some giant bet on something brand new. We've tried it, we've gotten to know it, and then we found ways to apply that. We're doing that with a number of different technologies right now. >> Yeah, you're in a very powerful position, you're Chief Marketing Officer, which has to look over a lot of things now, and certainly with IT and Cloud. You're essentially in the middle of the fabric of the organization. Plus, people are knockin' on your door to sell you stuff. >> Yeah. (laughing) >> So, what is-- >> That's happened. (laughing) >> It happens all the time, he's got the big budget. >> What are they saying to you? Who's knockin' on your door, right now? Who's peppering you. Who's tryin' to get on your calendar? Who's bombarding you? Where are you saying, Hey, I'm done with that, or Hey, I'm lookin' for more of that. How do you deal with that tension, 'cause I'm sure it must be heavy. >> Yeah, I think there is definitely a lot of optionality in the market, for sure. I think there's a new wave of martech vendors. Many of whom are sitting right in between sales ops and marketing ops. That's a layer we're really interested in. Systems that can help us better understand the behavior of sale's reps, and how they're using things that we're making, and then systems that you can better understand, indications of prospect intent. >> So, funnel and pipeline, or those kinds of things? >> Yeah, we think about it more from the context of authentic engagement. And so, we don't want to apply too much of a-- >> Structure to it. >> Structure, a sales structure to it. We want to try to follow the customer's intent through the process, 'cause the best prospect is someone who is authentically engaged in trying to find a solution to their problem. And so, if we can avail ourselves to people in a thoughtful, and creative, and authentic way, when they need us, when they're trying to solve that problem, then I think that they can become much more successful prospects. >> I love your angle on agile marketing. I think that's table steaks, not that you got to behave that way, and I'd love to get your thoughts, I'll get your thoughts later on the management style and how you make that happen. But, you mentioned engagement, this is now the new Holy Grail. There's a lot of data behind it, and it could be hidden data, it could be data decentralized all over the place. This is the hottest topic. How do you view engagement as a CMO, and the impact to the organization? What are you lookin' for, what's the key premise for your thesis of getting engagement? >> It's really the number one, two, and three topic we're talking about right now, and we think about it on the content side. How do we get ourselves really producing a constant stream of content that has value to people? That either helps them solve a problem right now, or helps them think about an architectural issue in a different way. We're trying to invest more and more technical resources in people who can produce things that are relevant to all the different kinds of users that we have. DevOps people, SREs, our traditional developer customers. We want to go deep and be super relevant at a content level for them. But then once they start to spend time with us, we want to then have a progressive way to pull them deeper and deeper into our community. And so, the things that we can do, something's in digital for that, but then often there's a pop off line, and we do a lot of workshops, a lot of education. >> Face-to-face? >> Face-to-face, where we're in communities, we look at a map at the start of the year and say, where do we have big user communities, and then we drop events into those places where we take our educators and our product experts and get customers to share with each other. And that becomes a really great platform to put them together and have them help each other, as well as learn more about what our product does. >> So, it sounds like you're blending digital with face-to-face? >> Robson: Yeah, absolutely. >> That's a key part of your strategy? >> Key part is to make sure that we're getting time and attention from the people who are making decisions, and what technologies they're going to buy, but also that we're really investing time in the people who are using it in their everyday lives to do their job better. That's a really-- >> Give some examples of outcomes that you've seen successful from that force. That's a really unique, well unique is pretty obvious if you think about it, but some people think digital is the Holy Grail, let's go digital, let's lower cost. But, face-to-face can be expensive, but you're blending it. What's the formula and what are some of the successes that you've seen as a result. >> Yeah, we tend to try to create events that are good for a very specific audience. So, if you think about a targeting formula that you would use in digital that will make digital really efficient, that same idea works really well for an event. So, if you got a user community that's really good at doing one thing with your product and you feel like if they knew a few more things that they could get better. Then we help them really advance to the next level, and so we run certification programs, where we'll pull together a group of confident users and help them get to the next level. And things like that allow us to make a really targeted event that allows us to reach out to a group and move them to a higher level of competency. To have competency focus is a big deal. Can we help you get better at your job? But then communities, is the other big one. Can we help you connect with people who are doing the same things? Solving the same kinds of problems and are interested in the same topics as you are. >> It sounds like the discovery path of the user, the journey, your potential. >> Yeah, it's important to us for sure. >> And content sounds like it's important too. >> It helps with your engagement. How you dealing with the content? Is that all on your properties? How about off property measurement? How do you get engagement for off property? >> Yeah, we're experimenting a lot in that area, of off property. I think we've had tons of success inside our own website and our blogs, and those kinds of-- >> You guys do pop out a lot of content, so it's content rich. >> Yes, we definitely have a lot, we hopefully, our attitude is, we want to turn our company inside out, so we want to take all of our experts-- >> Explain that, that's important topic, so, you guys are opening up what? >> We have got customer support people, we have technical sales, and technical support engineers, we've got marketing people who are thought leaders in Cloud and other architecture topics. We really want to take all the expertise that they've got and we want to share it with our community. >> John: How do you do that, through forums, through their Twitter handles? >> Through all of the above, really. Through their Twitter handles, through content that they write and produce through videos, through a podcast series that we run. We're really trying to expand as much as possible, but then inside our user help community, anytime somebody solves a problem for one customer, we want to add it to that-- >> Sounds like open-source, software. (laughing) >> From a knowledge perspective, that's really an important idea for us. >> Yeah, that's awesome. You worry about the risk. I like the idea of just opening it up. You're creating building blocks of knowledge, like code. It's almost like an open-source software, but no, it's open knowledge. >> We think if we can help people get really successful at the work they're trying to do, that it's going to do great things for us as a brand. >> What's the rules of the road, because obviously you might have some hay makers out there. Some employee goes rogue, or you guys just trusting everyone, just go out and just do it. >> Well, it's constant effort to distribute publishing rights and allow people to take more and more ownership of it, and to maintain some editorial controls, because I think quality is a big thing. It's probably a bigger concern for us then somebody going rogue. At some level, if that happens to you, you can't stop it. >> So, is this a new initiative or is it progression? >> It's been ongoing for awhile. It's progression of an effort we started probably 18 months ago, and it's a wonderful way for an engineering team, and a product management team, and a marketing team to get together around a really unified mission as well. So our content project is just one of those things that I think really pulls us together inside the company in a really fun way as well. >> It's interesting, you seeing more and more what social peers want to talk to each other and not the marketing guy, and say, Hey, get the Kool-Aid, I like the product, I want to talk to someone to solve my problem. >> Want to have a real conversation about it, and I think that's our job, is to not think of it as marketing, but to think of it as just facilitating a real conversation about how our product works for somebody. >> I'd love to talk about leadership as the Chief Marketer for New Relic in the culture that you're in, which is very cool to be in on the front-end, in the front lines doing cool things. What do you do? How do you manage yourself, how do you manage your time? What do you do, how do you organize the troops, how do you motivate them? What's your management style for this marketing in the modern era? >> I think, number one, we're trying to create an organization that is full of opportunities for people, so it's something that we've done. I've been there for about two and a half years, and we've really looked hard for people who have tons of potential and finding great things to work on. On new projects, and then let them try out ideas that they've got. So, if they can own an idea, give it a shot, and even if it doesn't work, they'll learn a bunch from the process of trying. >> What are the craziest ideas you've heard from some of your staff? (laughing) >> Oh boy, you know a lot of them involve video. There's always a great idea for a video that's risky. And we've made-- >> So the Burger King one with Net Neutrality going around the web is the funniest video I've seen all week. >> Robson: Yeah, yeah. >> Could be risky, could be also a double-edged sword, right? >> Yeah, video is one of those places where you have to check yourself a little bit, 'cause it could be a great idea, and so sometimes you have to actually make it and look at it, and say, would we publish this or not? And, yeah, so that's definitely the place to be. >> So common sense is kind of like your. >> Yeah, you start with common sense, for sure. And, I think we want to be a part of it being culturally responsible in Silicon Valley right now, is really making sure that we're attentive to making sure that we're putting in the right kind of workplace environment for people. And so, our content and the way we go to market has to reflect that as well, so there's a bunch of filters that you put on it, but you have to take risks and try to make things, and if they work great, and if they don't then the cost of that is less than. The cost of failure is so low in some of these things, so you just have to try. >> Well, you know, we're into video here at theCUBE. I have to ask you, do you see video more and more in the marketing mix and if so, how does that compare to old methods? We've seen the media business change and journalism, certainly on the analyst community. Who reads white papers? Maybe the do, maybe they don't. Or, how do they engage? What content formally do you see as state of the art engagement? Is is video, is it a mix, how do you view that? >> It's a mix, really. I think video's really powerful. And it can be great to tree topics and short form in a really powerful way. I think we can stretch it out a little bit in terms of how to and teaching and education also. But, there are times when other things like a white paper are still relevant. >> Yeah, they got to do their homework and get ready for the big test. >> Yes. >> How to install. (laughing) >> Exactly, yeah. >> Okay, big surprises for you in the industry, if you could look back and talk to yourself a few years ago and say, Wow, I didn't know that was going to happen, or I kind of knew this was going to be a trend we would be on. Where is the tailwinds, where's the headwinds in the industry as a marketer to be innovated, to be on the cutting edge, to deliver the value you need to do for your customers and for the company? >> Yeah, I think there's a bunch of great tailwinds organizationally and in the approach to work. And you talked about Agile. I think it's been a great thing to see people jump in and try to work in a different way. That's created tons of scale for a department like ours, where we're tryin' to go to more countries, and more places constantly. Having a better way to work, where we waste less effort, where we find problems and fix things way faster, has given us the chance to build leverage. And I think that's just that integration of engineering, attitudes, with marketing processes has been a, is an awesome thing. Everybody in our marketing department, or at least a lot of people have read the DevOps handbook, and we've got a lot of readers, so the devotes of that thought process that don't suit an engineering jobs. >> DevOps, Ethos, I think is going to be looked at as one of those things, that's a moment in history that has changed so much. I was just at Sundance Film Festival, and DevOps, Ethos is going to filmmaking. >> Robson: Yeah. >> And artistry with a craft and how that waterfall for the Elite Studios is opening up an amateur market in the Indy, so their Agile filmmakers and artists now doing cool stuff. So, it's going to happen. And of course, we love the infrastructures code. We'll talk about that all day long We love DevOps. (Robson laughing) So I got to ask you the marketing question. It will be a theme of my program of the CMO is, if I say marketing is code, infrastructure is code, enabled a lot of automation, some abstracted a way horizontally scaled, and new opportunities, created a lot of leverage, a lot of value, infrastructures code, created the Cloud. Is there a marketing as code Ethos, and what would that look like? If I would say, apply DevOps to marketing. If you could look at that, and you could say, magic wand. Give me some DevOps marketing, marketing as code. What would you have automated in a way that would be available to you? What would the APIs look like? What's your vision for that? >> What about the APIs, that's a good question. >> John: I don't think they exist yet, but we're fantasizing about it. (laughing) >> Yeah, I think the things that tend to slow marketing departments down really are old school, things like approvals. And how hard it is to get humans to agree on things that should be really easy. So, if the first thing you-- >> Provisioning an order. (laughing) >> The first thing you could do is just automate that system of agreeing that something's ready to go and send it out that I think you'd create so much efficiency in side marketing departments all over the world. Now that involves having a really great, and API's a great thought in that, because the expectations have to get matched up of what's being communicated on both sides, so we can have a channel on which to agree on something. That to me is-- >> Analytics are probably huge too. You want to have instant analytics. I don't care which database it came from. >> Yes, exactly. And that's the sense of DevOps and can use. But then you got some feedback on, did it work, was it the right thing to do, should we do more of it, should we fix it in some specific way? Yeah, I think that's-- >> I think that's an interesting angle, and the face-to-face thing that I find really interesting, because what you're doing is creating that face-to-face resource, that value is so intimate, and it's the best engagement data you can get is face-to-face. >> Yeah, I think it also allows us to build relationships to the point where we are getting invited into slack channels to help companies in real-time sometimes. I think there's a real-- >> So humanizing the company and the employees is critical. >> Yeah. >> You can't just be digital. >> Yes, it's a big deal. >> Awesome. Robson, thank so much for coming on theCUBE. The special CMO series. Is there a DevOps, can we automate away, what's going to automate, where's the value going to be in marketing? Super exciting, again, martech. Some are sayin' it's changing rapidly with the Cloud, AI, and all these awesome new technologies. What's going to change, that's what we're going to be exploring here on the CMO CUBE conversation. I'm John Furrier, thanks for watching. (upbeat instrumental music)

(upbeat instrumental music) >> Narrator: Live from Las Vegas, it's the Cube. Covering AWS re:Invent 2017, presented by AWS, Intel, and our ecosystem of partners. >> Hey, welcome back everyone. This is the Cube, live here in Las Vegas for AWS re:Invent 2017. I'm John Furrier, the cohost of the cube. My cohost, Keith Townsend, here for our fifth year in a row, covering the thunderous growth of Amazon Web Services as they continue to not only nail the developers and the start ups, but continue to win the enterprise. Our next guest, Lew Cirne, who's the founder and CEO of publicly held New Relic, a very successful startup, one of the most admired places to work in the Bay area, and in tech. Lew, great to have you on the Cube, welcome. >> Hi. >> John: Hi, first time. >> I know, so great to be here. I can't believe it's the firs time. I've been such a fan for a long time. >> Now you're an alumni, the benefits. >> Here I am. >> All the benefits of being an alumni, all those season tickets to all of our games. I gotta, I want to just share something with the audience out there. You're the only public CEO that I know that's been on the Cube that writes software, has a GitHub account, and manages a publicly held company. So that's a unique thing and I want to just say it's awesome. >> It's a full plate, that's for sure, but I'm the luckiest guy in the world because I've always loved building software since my first computer I got in the Christmas of 82, what's that, 35 years ago now, and, and so, what an exciting time to be someone who's passionate about software and technology. Look what's going on in the cloud, and so I've been fortunate enough to start this company that's participating in this revolution in technology, so it's great. >> You guys are always in the cutting edge. I noticed, you guys get your hands dirty, you get in there, you're coding away, but you guys are very successful in a very important area right now, which is instrumentation of data. >> Lew: Absolutely. >> In applications, so I really want to get your, kind of your thoughts on the landscape. We were talking about on our intro analysis, that we're seeing a renaissance in software development, where with open source growing exponentially, a new software methodology's coming out, where there's just so much going on. Multiple databases within one app, IOT, so a new kind of thinking is evolving. What's your take on that? >> Well I think it's really important to understand why all of this is happening. So why are there 40,000 people here in Las Vegas for re:Invent? Why are people consuming the cloud at just a dizzying pace? It's not just for the sake of cloud computing, it's because there's this business imperative to compete on software, so if you look at where software was 15, 20 years ago, software was a tool to reduce costs and automate things in the back end. Now your software's your business. If you are a large global bank, your app has more to do with your customers' experience and satisfaction than the branch because nobody walks through a branch anymore, so now the best software developing bank is going to be the winner, so if you think about that's what's going on and that's why they're adopting new technologies to move faster, so where do we fit in? If you're going to compete on your software, and by competing you have to build the best stuff, the fastest as possible, so you have to get to market quickly, and that means you've got to change a lot. Anytime you're changing something rapidly, that introduces risk. New Relic de-risks all of that rapid movement by instrumentation, by measuring everything in the software. Those measurements help you move faster with confidence. >> And also I would say that you, not only does that create risks, but new software creates risks, so I'm doing server-less, I want to try the new service because it could A, add value, AKA Lamda or whatever, so a new, maybe time out is needed, so all kinds of new things or elements are going on inside the software stacks. >> Yes, and more complex than ever before, right, so you introduce things like Lambda server-less function computing, call it what you will, and you integrate it with, you know, microservice architecture, and so instead of one monolith, you might have hundreds, or even some of our customers have thousands of independent services, all supposed to be working in flawless concert in order to deliver a great customer experience. How on earth do you make sense of whether that's all working? Well it involves collecting an enormous amount of data about everything that's going on in real time, and then applying intelligence to that data using what we call at New Relic applied intelligence to tell our customers in real time, here's what's working well, and more importantly, here's what's going to be a problem if you don't take immediate action. And that's, you know, that's a hard problem to solve. We think we're the best at doing it. >> And that's critical too, because like you said, if it crashes, or there's some sort of breach hold that comes out there, all the stuff is at risk. >> And like, customers have just incredibly high expectations that only get higher and higher every day. Like, you know, one of our customers is Domino's and it's an amazing thing where you pre-order your pizza and you can see, second by second, how your order is doing, right? They put your pizza in the oven, then they took the pizza out of the oven, and I see that in phone, and that gives, that's that feedback that's valuable to me, right? So long as it's working, right? >> John: I'm hungry now. >> So we, we've ravished this word digital transformation all the time. >> Oh yeah, it's a little overused, but. >> It is a little overused. But melding that physical world with cold. I love it that you're a developer. First off, what's your favorite language? >> Oh geez, it really depends on the project. I'm really getting into, I love React right now on the front end. I'll still do Java when it needs some heavy lifting, Ruby for rapid prototyping. It really depends on the task at hand. >> So the value of reducing friction from a developer seeing a problem, needing to solve that problem, and getting the resources needed to solve a problem, AWS does a wonderful job of saying, you know what, developer, give me your credit card, we'll give you all the tools you need. Where is the first stumbling block because this is new capability, net new over the past few years? Where's the first set of stumbling blocks when developers reduce friction, get to that first level contact with the branch manager of the pizza store, where does it fall apart and New Relic comes in to help? >> Look, how many times have you ever had a developer or a tech or someone that works on my machine, right? >> Exactly, worked on my laptop. I don't know why it didn't deploy well in production, it worked perfectly fine on my laptop. >> I really, I started thinking about and solving this problem 20 years ago now. The notion of less instrument Java code because I was frustrated with the stuff that worked on my laptop. I couldn't understand why it didn't work when a customer used it, and everything prior to the customer using the software is nothing but sunk cost. There is no value in the software you're building until it runs in production. How well it runs in production is what determines the fate of the application. And that's where New Relic comes in, is we feel like alright, let me take you back to the ancient days of like turn of the century, 2000, nothing went to production without QA. Now nothing goes to production without instrumentation. >> Yeah, but now Agile's there, so the old days was a crab. You built a software product, but you didn't know if it was going to work until it went into production with QA. Now you're shipping stuff fast, so it's still. You've got that dev off mindset, but it's in QA. >> One of our customers, Airbnb, deploys more than a thousand times a day. And this is not a small, low load site. I mean like every deploy has to work, otherwise millions of people are impacted and it's the whole business, and it's a big business, so you're talking about a pace of innovation and change that cannot be managed with a traditional QA cycle. I've, of course testing's important, but instrumentation's more important than that. >> Lew, I want to ask you an important question because I asked Andy Jassie this last Monday when I had a one on one with him. A lot of people that are entering ecosystem for Amazon is new, that are new, or considerably, Amazon's the big, they're fearful, it's always going to be that way. He highlighted your company, New Relic, and said they're an amazing part, they do extremely well, even though they introduced Cloud Watch, which because some customers just wanted it, they have monitoring, but you guys are so much better. I said that, but if he implied it, obviously you're doing well. So the successful participation of the ecosystem is there. You can be successful in the Amazon ecosystem. >> Absolutely, it's a great partnership. >> So what's this formula for a new entry coming in or someone who's here that needs to find some white space? How do you read the tea leaves to know where not to play and where to play? >> You know, it just comes down to the fundamental good thought process you use when you're thinking about approaching your customer too. Don't think about what's in it for me, the Amazon partner. What's in it for Amazon? How do you make them more successful? And so when I imagine myself as Andy, who is like, what an incredible job he's done, but what Andy, what's top mind of Andy is how do I get more customers consuming more of Amazon faster, right? All of Amazon, all of Amazon's web services, and so we solve a problem for Andy and his team. We help our customers consume Amazon faster because we give them the confidence to consume more and move faster, and there's data to prove it. When Amazon asks their customers that aren't yet New Relic customers how much they're consuming and how fast, they get a slower rate of adoption than they do for the cohort that uses New Relic, and so it's in our mutual interest to go to market together because we help them consume more, and so I. >> John: Build a good product. >> Build a good product. >> John: Customer value. >> Think about how you help your partner be successful. Talk in that language, don't talk in language. >> Alright, so personal question. So you and I, pretend we're sitting here, having a beer, you're playing the guitar. >> A little light. >> I'm singing some tunes and Keith's our friend. He says I'm in trouble, I'm a CIO. I've got a transformation project. I don't know what to do. Which cloud do I use? How do I become data driven? Guys, help me out. Lew, what do you say? >> I say first of all, you have an instrumentation strategy. Everything, if you're a CIO in a large organization, you don't have one, two, three, or four projects. You have dozens, if not hundreds, sometimes thousands of applications and services that are all running, and you've got, I haven't met a CIO that doesn't say they've got too many monitoring tools. So you need an instrumentation strategy. Nothing should run in production without instrumentation. That's not just the service light stuff that runs on EC2, it's also every click that runs. You know, when Dunkin Donuts, which has been a longtime customer of ours, and they run in the Amazon Cloud, you know when you pre-order that doughnut, we track the tap, how long it takes from the phone all the way through the cloud services, all that's fully instrumented, so if you're a CIO, you say I can't be tactical with instrumentation. If I'm going to move fast and compete at my software, nothing should run in production without education. >> John: That's native. >> That's right. >> Foundational. >> Foundational. It's a core requirement to run in production if you're going to move at any level of speed, so establish that strategy, and then we think, we offer the best instrumentation, certainly the best value, the most ubiquitous, the easiest to use, the most comprehensive, and then we make the most sense of it, but you could pick another, you know you could pick another strategy. Some people do the heavy lifting of manually instrumenting all their code. We just don't think that's a good use of your developer time, so we automatically do that for you, but have a strategy and then execute to it. >> Awesome. Lew, congratulations on a blowout quarter. I won't even get you to comment on it, just say that you guys had a great quarter, stocks at an all time high, all because you guys are doing a great product. Congratulations and great to have you on the Cube. >> We're delighted to be here. I've honestly, I've been a longtime fan. It means a lot that you could have me on, and we really enjoy partnering with Amazon, and what a great show. >> Yeah, super successful ecosystem partner, one of the best, New Relic, based out of San Francisco, here with the founder and CEO, also musician, writes code, gets down and dirty, runs a publicly held company. He's Superman. Lew, thanks for coming on the Cube. More live data and action here on the Cube after this short break, stay with us. (upbeat instrumental music)