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