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

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

(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)