>> Live from Orlando, Florida, it's theCUBE. Covering .conf18, brought to you by Splunk. >> Welcome back to Orlando everybody, home of Disney World, and this week, home of theCUBE. I'm Dave Vellante and he's Stu Miniman. Steven Hatch is here, he's the manager of Enterprise Logging Services at Cox Automotive. Steven, thanks for coming on theCUBE. >> Thank you. >> So, you've been with Splunk for a while, we're here at conf18. Logging services, enterprise logging services. When you think of Splunk, their roots, Splunk go back to, sort of, log files, analyzing log files, it's in your title. (laughs) You must be pretty intimately tied to, as a practitioner, to this capability, but talk about your role and what you do at Cox. >> Primarily, the role is to be the evangelist, the enabler, and the center of excellence when it comes down to getting those best practices propergated within the enterprise. >> So people come to you for advice, council, you play, sort of, internal consultant. What qualified you to do that? You were a practitioner prior to this, so you got your hands dirty and you kind of now, elevated to-- >> My prior role was a Site Operations, or Site Reliability Engineer, and then Manager. And so, having that background, I've been in IT since '96, so I'm a little old in the game, but basically, having that operational knowledge, and knowing how to think big picture when things are happening or transpiring, or the reverse and go back and find that root cause analysis. >> '96, just a pup, my friend, okay? (both laugh) So, talking to Stu, we were talking off camera, about the number of brands that Cox Automotive has, Cox at Kelley Blue Book and at numerous others, like dozens, each of these is kind of it's own data silo. How do you guys go about using Splunk? Are you able to break down some of those silos? Maybe you could share that with us. >> Yeah, so we have been successful on a lot of the big three really, at Kelley Blue Book, Manheim, as well as Auto Trader, to really break in. A lot of that was because of our, already previous, relationships with team members and leaders. On the other side of the coin is the newly acquired companies that are not in Atlanta, Georgia. That are in places like Groton, Connecticut, South Jordan, Utah, Upstate New York, as well as the Toronto area in Canada. And so, WebEx joined me, email just won't cut it. You actually have to sit down with these people and really showcase your business case, your model, and what you're trying to bring to the table. But of course, the approach is always important. >> And are you using Splunk to do that? As a collaboration tool as well? >> Yes sir, yep. >> Explain that a little bit if you would. >> So, a lot of times, as you mentioned, the silos, as a bigger brand now, it's no longer an excuse for you to only be responsible for your data and not showcase it, or share that data. Because we're thinking about the entire life-cycle of Cox Automotive, and this entity of Cox Automotive, that's important to us now. So for you to hold tight, or to hoard your data, or your metrics and not share them, that's not good business anymore. >> Yeah, so Steven, we talked to a lot of companies that do M&A, and it's usually like, well, this is the products we use, these are the structures that we have. One of the things we hear from Splunk is that you can get to your data, your way. How does the Splunk modeling, and how you look at the data, fit into that M&A? Is that an enabler for you to be able to get that in. >> Yeah, and so, when you can showcase the ability of how the data comes in and, quickly. Key word, right? To showcase how that data can be very valuable to them, especially to their stakeholders, that's when light bolts will go off. And, again, it's the stakeholders, and then champions, that we need to bring to the table to make sure that we can get full adoption. >> Yeah, we've also-- Dave's been to the show a few times, it's my first time, and what I've really heard a bunch of is the people that know how to use Splunk, they're super valuable inside of the company. They get training, people inside the company, they look to get hired, tell us a little about what you've seen, what it means to your role inside the company, and as you network with your peers here. >> It's a lot of exposure. A lot of people are very anxious to get some type of insights into their world, their infrastructure, their applications, their business tools. A lot of times, there are people out there that are very savvy from a business perspective, that have a bunch of KPIs in their head, but no one has actually extracted that information from them, and so, our job is to align with their KPIs. You know, over the last couple of years, that's what we've-- the journey that we've been on, is to now revisit the data that we've just ingested. That's the basic foundation. We want to elevate now and really get more mature, and to align with those business KPIs. >> Meaning they got this tribal knowledge in their head, and you want to codify that so that it can be shared. >> Correct. >> How do you go about doing that? Is it sitting in a whiteboard and understanding that? >> It can be a whiteboard, it can be over a coffee. If I need to get on a plane and go see them in person, and to really just listen and ask the questions when it's time but, again, listen and really understand what's important to them, what is important to their business, to their function, to their silos? Cox Automotive has five, of what we call, pillars, where there's international, finance, marketing, retail, or media, and each one of those owners, over time, wants the specific value. >> So if you go and have a chalkboard session, whiteboard session, with one of these folks, how do you operationalize it? You got to figure out where the data exists, so that you can align with what's in their head? Is that right? And then, how do you do that? How do you scale it? >> Well, so, again, you have to start from the top. If you start from the bottom, you'll be in the weeds until the end of time. So that the more efficient manner is to start from the top and realize those KPIs from those leaders, those stakeholders, and then from there, a tool like ITSI, which is basically built around services, entities, and aligning to their service decomposition model, and that right there allows you to stay consistent and efficient on getting that information. >> So you start top down, but ultimately, people are going to want granularity. So you start-- is it top down, bottom up, type of approach? Where you actually drill, drill, drill, drill, drill, and then get to the point where you can answer all those granule questions? And then, by doing that, if I understand it correctly, it sums to the top line, is that fair? >> Yeah, yeah, there's a point in time where you say, you know what? I could really now enhance or enrichen the data by a dataset that I know where it is. So the keypal will get you to a certain point, and then, to find that happy medium, or that common denominator from the data that you already have on premise, or from your apps, wherever they reside, that's where you can meet the gap. >> Otherwise you're never get it done. You'll end up boiling the ocean. >> That's correct, yes sir. >> All right, so, when we talked to you two years ago, you were using Splunk Cloud, you know? And when we talked to practitioners it's-- the things that they're managing, a lot of times now, most of it's not what they own, and so, how do I get the right information? How do I manage that environment? Talk to us a little bit about what you've seen in the maturation of Splunk and Splunk Cloud, if there's anything in 7.2, or Splunk Next, that's exciting you, to help you do your job even better. >> Oh man, so of course, the keynote today, the DSP, the processing layer that's in front of the Cloud, or in front of the indexes now. Where in real time, I can now route data, specifically from a security standpoint. If there's some type of event, without having to go through all the restarts and configuration management and everything else, I can simply put something in there, right there, and move the data, or mask the data. The ability with the infrastructure app, that's exciting to me, as well as all the feature updates for ITSI, enterprise security, as well as the Cloud itself. >> Can we do a little Splunk 101 for my benefit? So I heard today, from one of the product folks, that it used to be when you added another indexer, you had to add storage and compute simultaneously, whether or not you needed the storage, you had to add it, or vise versa. So an indexer is what, is it, essentially, a Splunk node? >> No, it can be a, basically, a Linux host, that actually has the agent running as an indexer with the attached disk. >> Right, okay, and it used to be you had to buy that in chunks, kind of like HCI, right? And you couldn't scale storage independent of compute? >> That's correct. >> What that meant is you were paying for stuff that you might not need. >> Right. >> So, with 7.2, I guess it is, you can split those and you get more granule, or what does that mean for you? >> Well, being a, now four year customer of Splunk Cloud, and anytime we went to the next version of, or license, the next step up, currently we're on about six terabytes. When we go up to eight, that the entailed more indexes being added to the cluster, which meant more time for the replication of search factors to be met, which can take however long, and then, or if there's any kind of issue with the indexer, where one had to be pulled out and another one introduced. How long does that take? Now, with the decoupling of the compute from the storage, it's minutes, and so it's a fraction of the time. >> And if I understand, I understood it real well when it's an appliance, but it's the same architecture if it's done in the Cloud, is that correct? >> It's, essentially, actually, it's a new architecture in my mind, where now it's able to scale more, and then there's-- I'm not sure how much they talked about it, but there's a potential of the elasticity of it. And so, now, I don't have to be so fixed, I can, on certain times, expand the cluster, you know, for search performance, or bring it back down when it's not needed. >> Some of the promise of Cloud. >> Yes, sir, Splunk Cloud. >> So it's like the Billy Dean, the five tool star. You've got the cost, you've got availability, you got speed, you got flexibility, and you've got business value, ultimately, which is what's driving here. So, I take it, I'm inferring here, you'd expect to use this capability in the near future? >> Very much so. >> Great. What else is on your horizon? What are the cool stuff you're working on? And things you want to share with us? >> Well, in addition to our leveraging Splunk Cloud for four years, next year we plan to move away from our current sim tool, into enterprise security. So it's very exciting to hear that they're continually updating that product, and so our security team has been knocking on my door for the last six months to really get that started. So, once we get there, we'll start the migration efforts and get Splunk Cloud now, enabled with the enterprise security, to really empower our security team, and stay ahead of our threats. >> So, I've been around a long time, and, ever since I can remember being in this business, customers have wanted to consolidate the number of vendors with whom they work. But the allure of best of breed always sucks them in to, oh, lets try this, or you get shadow IT. It sounds like, with Splunk, you're approaching this as a platform that you can use for a variety of different use cases. >> That is correct. >> Now, whether or not you reduce the number of vendors is, maybe a separate conversation, but I guess the question I have is, how are you using Splunk in new ways? It sounds like its permutating a line of business, SecOps, etc, is that an accurate picture? If you could describe it. >> Yeah, so Splunk itself, the core is the platform for so many different other functions within the business. You have security, you have the development group, DevOps, where, from a CICD perspective, now they can measure the metrics or the latency in between, when they create a car, say in rally, all the way to the very end of the line, what are all those metrics that are there, that they can leverage to increase their productivity? Obviously, infrastructure. As we consolidate all of our data centers down, wouldn't it be nice to know if these specific low bouncers or switchers are still having traffic to verse them? And to actually get a depiction of the consolidation effort. From a virtualization standpoint, isn't it powerful to know how many devices E6 hosts are actually fully being utilized, and how many are actually vacant? And how much money can be saved if we were actually to turn down those specifics blades or hosts? Or VMs that aren't being leveraged, but they're sitting there, taking up valuable resources. >> I remember when Splunk, right around the time they went public, I remember two instances, maybe three. There was a MPP database company, there was a large three letter firm, and there was an open-source specialist, and I heard the same thing from each of them, was we have the Splunk killer, this was like, five, six years ago. It seems like this Splunk killer was Splunk. And it really never happened. Why is it? Why is Splunk so effective? You obviously see, you know, you're independent, you want to use the best thing for Cox Automotive. What is it about Splunk that sets them apart, puts them in the lead? >> The scale capabilities, having this type of environment with the conferences and the sales group and the support groups, very intentional about listening. Having workshops where they come on premise to help us out on our use cases, to really educate their users, because the more their users are elevated from a knowledge standpoint, the more they will then exercise the application. If they all stay basic, why would I need another component of Splunk? Why would I need enterprise security? Why would I need to expand my subscription into the Cloud? The more I can exercise it, the more I'll need. >> So this is kind of a give, get. They come in knowing that if they expose you to other best practices, you'll going to be more effective in the use of Splunk and you might apply it in to other parts of your business. >> My appetite will grow and my users appetite will grow. >> And these are freebies that they're doing? Services freebies, or are they paid for services? >> Oh yeah, they have no problem coming in, supplying the necessary ammunition, or food, to entice, to have folks come in, but it's powerful to have all the engineers in there to really show us how things work. 'Cause, again, it's a win, win. >> And you're a football fan, I understand? >> Oh, yes, sir. >> Chiefs are your team, right? >> That's correct. >> Were you a football player? >> For a little while, yes. Now I coach, so that's my-- >> And you coach, what? >> Little girls. >> Kiddie football, huh, awesome. Is that Pop Warner these days, still? >> I guess you call it that. >> Flag football or tackle? >> Tackle football >> Really? >> Yep. >> Eight years old? >> Yes, my son is eight and he's playing full back right now, I'm very excited, happy father. >> Is he a big boy, like his dad? >> He's going to be bigger, I think, than his father, yes, sir. (both laugh) >> That's awesome. Well, listen, thanks very much, Steven, for coming on theCUBE, it's really a pleasure meeting you. >> That's appreciated, thank you very much. All right, keep it right there everybody. Stu and I will be back with our next guest. We're live from Splunk .conf18, you're watching theCUBE.

>> Announcer: Live from Orlando, Florida, it's theCUBE! Covering ServiceNow Knowledge17. Brought to you by ServiceNow. >> We're back in Orlando, everybody. This is theCUBE, the leader in live tech coverage. We go out to the events, we extract the signal from the noise. We're here at Knowledge17. I'm Dave Vellante, with my cohost Jeff Frick. Donna Woodruff is here, she's the service enablement leader at Cox Automotive. Donna, thanks for coming to theCUBE. >> Hi, thank you for having me. >> Good to see you, you're welcome. Tell us a little bit about Cox Automotive, and specifically your role. Are you an IT practitioner by trade, or business process person? Share with us. >> A little bit of everything, actually. First of all, Cox Automotive is a large, privately-held organization that's part of the Cox Enterprises family. We are changing the way the world buys, sells, and owns vehicles. We are made up of five key solution group areas. Everything from inventory solutions, which includes our auto auctions, and everything to get cars from dealerships to our auctions and back out again for their inventory. We have financial services, which provides floor planning to our dealerships so they can buy cars from our auctions. We have media services, which are all about how do you connect the cars that you're selling to retail customers, so autotrader.com, Kelley Blue Book are some notable brands as part of our organization. We develop software around analytics, and an ERP system for dealerships, to help them move their inventory and do their floor planning, so they can maximize sales in their dealerships. And then of course we have international. We are a global company. We have over 34,000 team members that we support. We're a very heterogeneous organization, and that can drive complexity into the organization. My role is, I am the service enablement leader. I am based out of technology, but I look at my role as much broader than that. It's about solving problems for our business and being able to deliver services internally and externally, and help the organization run more efficient and effectively. >> So you've seen, you know, the narrative in IT, and ServiceNow's described that very well over the years, IT getting beat up, and you only call IT when there's a problem, and obviously the platform and the adoption of that have changed a lot of organizations, presumably you experience something similar. So, take us back to the beginning days, the early days of what it was like, the before and after ServiceNow. What led you to that decision? What were some of the drivers, how'd you get there? >> Absolutely. Well, Kelley Blue Book was an acquisition for Autotrader group of companies about four or five years ago, and they had implemented ServiceNow as a help desk ticketing system. When we acquired them, we saw some great wins with the platform that we thought, hey, this really should be our help desk ticketing system. And so it brought under cross that small group of companies, but it was always viewed as a help desk ticketing system. Over time, just like many other platforms, it starts to get highly customized. Fast-forward to a couple of years ago, we had a need. I was supporting HR and communications from a technology liaison perspective. The problem that they were trying to solve was that they have two employee service centers, one on the East Coast, one on the West Coast, that were staffed by analysts, and they primarily helped our auto auction personnel deal with their benefits and questions around just HR. All the way down to time sheet corrections and things like that. They came to me with this problem, and they said, "You know, we've been using Remedy to some extent." We were in a transitional time in the organization where we were collapsing our help desk tools onto ServiceNow, and they said, "We need some help, here." "We just want to do a few requests." Well, we identified early on as that liaison that I really think that this ticketing platform can do what you need it do. Myself along with a business analyst and an intern sat down with the business, we understood the requirements, and that was the launch of our HR portal. While we were in there-- >> Just you, an analyst, and an intern. >> That's correct. That's correct. And we weren't developers. It was all about configuration. But we understood the tool, we understand that this is really no different than any other business process, and we set out to deliver the first service catalog around HR services. Since then, we haven't looked back. We learned a lot about the platform. We diagrammed out what was wrong with how the service desk had been highly customized, we sat down with our VP and we just showed him the diagram and said, "We think that this platform can do a lot more." He listened to us, and he turned to us, and he said, "Well, do you guys want the platform?" And I turned to my team, and I said, "Do you guys want it?" We took it on, and since then, in the last 18 months, we have expanded the platform very broadly. We've implemented performance analytics to improve our help desk services. Beyond the HR portal, we are now implementing governance risk compliance, a vulnerability management. We're now doing PPM as well. We are re-looking at our CMDB because we want to do more with automation. We've done some orchestration with storage agility and how we can get those engineers more productive by doing zero-touch ticket requests from our developers to expand file shares and to sunset file shares, or to request new file shares with other applications. >> So what'd you do with all the custom mods, when you talked about the Kelley Blue Book coming over. Did you sort of scrub the hose and start over, or-- >> Well, you know what, we took it back to out of the box, and it wasn't difficult to do. We just rationalized the things that were duplicated across requests and incident, we pulled it back to out of the box, we took an agile approach. My team now is very agile. We do weekly releases on the platform. By bringing it back to out of the box, it allows us to upgrade to the latest major feature releases within a two-week period. Because of that, we're able to adopt and consume the new product enhancements that ServiceNow has to offer very, very quickly. >> So, obviously you had success, or you wouldn't have been able to expand the footprint so radically. How are you measuring success, how did you go from a little bitty thing to a very large thing? >> I think it's about visibility. Visibility and strong leadership support, and showing how we're getting better incrementally over time. I think one of the strategic things that we've done, probably in the last six months, is implement performance analytics, which that started to show the behaviors of how people were working within the platform, how they were addressing incidents, how they were responding to our mean time to response, to our mean time to closure of a ticket, the aging of these tickets. When we first implemented performance analytics, we found a lot of anomalies in the platform. We found orphaned assignment groups, which to the behavior of the organization, they weren't necessarily working the system the way they should be. >> Jeff: Orphaned assignment groups. >> Orphaned assignment groups. Tickets were going in and they were backing up, and nobody was working them. So, allowed us to change the behavior of the organization, to drive consistency in how they were using this, which then made the metrics more meaningful. Now people are running their areas of operation from the platform. >> So the next thing I got to ask you, we talked about it in the open, is behavior. Tech's hard, but it's not that hard compared to people and process. How did you get people at that moment of truth, when I need something, to not send an email like I'm used to, and to actually execute my work through this tool? >> Well, one thing we did that was very unique, and we've continued to do that is as we roll out major feature functionality, we actually create commercials about ServiceNow, about the platform. Internally, we call it Service Station. Everything is associated with a vehicle. We've promoted our brand around the platform as well, and our brand is about doing things more simply, getting things routed to the right people, that's why it's better than email, and demonstrating the power of what it will do to you, and getting those answers more quickly instead of going to your favorite IT person or your favorite HR person. How this platform is helping you get to your answers more quickly, as well as all the self-service capabilities and the knowledge articles around, hey, fix it yourself. You don't have to talk to somebody on the phone. But we still give that personalized touch if they really need help and they want to talk to an individual. >> So really, a lot more carrots than sticks. >> Lot more carrots than sticks, absolutely. It's if you can solve your problem faster, why not? 'Cause at the end of the day, that's ultimately what you want to do. Solve your problem, and get on to the rest of your day. >> How long does it take for a typical employee to go, "Ah, this is fantastic!", and to really shift their behavior and buy in and start selling it, as your advocate? >> I think we're doing a better job now, introducing it to our new hires as soon as they get engaged in the organization, about this is your platform to go to when and if you need help. And here's how easy it is to find the things that you need. It's something that just happens over time, and I think if you address some of those small wins, you create advocates in the organization, and when they have a good experience, they tell others. So some of it's word-of-mouth, some of it is internal promotion. A big part of it is leveraging the platform to get the work done and having a great user experience along the way. >> Donna, you mentioned Service Catalog and CMDB, these are consistently two components that allow customers like you to get more leverage out of the ServiceNow platform. So, specifically as it relates to CMDB, what are you doing there? Do you have a single CMDB across the organization? Is that something you're considering? >> That's probably one of our next big transformational areas. We do have a CMDB within the platform that's been used primarily around the linkages for incident, problem, and change management. But we know that we need to do more with it, and like I said before, we've grown through acquisition, so there's a number of other CMDBs. And we are in the process of bringing that all together onto the ServiceNow platform. Because we're seeing the power of everything else that that connects to. And that's also going to be a key on how we promote more orchestration, more automation, more about the health of our services. >> So, ServiceNow's obviously promoting you guys throughout this event, showcasing some of the things that you've been doing. What've you been talking to other customers about? What are you most proud of? >> Honestly, I'm really proud of my team (laughs), because we are responding to the needs of the organization, and the fact that you can add value through what you do on a day-to-day basis is great. I think one of the most unique things that, in terms of the application, is we actually built an application for our safety auctions. So, as you can imagine, we have a hundred auctions. There's a lot of people working in the auctions. We have everything that a dealership would have, and we have lanes of vehicles running through to be auctioned off with our dealerships. So we have service areas, we have vehicles and people moving about the auction. So safety is a very critical thing for our organization. About a year ago, the safety director came and said, "You know, we have this problem. "We are doing these auctions' safety checklist "around compliance, how can we make "our auctions a safer place?" "You know, we don't have a lot of money, "but we think there's a better way to do it." And they explained the process where they had six area safety managers that were distributed across these hundred auctions, and trying to get the safety message out there through making sure people were wearing their goggles, or that they had all the appropriate OSHA standards in place. So after having a lot of conversations around this, again, we found ServiceNow would be a great solution. We did work with a partner to help us build it, but we took a very manual process and we automated it on the platform. Now we've moved the safety business process to the auctions themselves, where they own it. The general manager's involved, the shop leads are involved in it. And what it's done, it's been a catalyst to reducing our workers' comp claims. We've seen a two basis point improvement over the number of workers' comp claims, which is cost-avoidance, you know. When your average worker comp claim can be around $10,000, that's a significant saving. With a very, very small investment, we saw a 3,000% ROI on this initiative alone. We're bringing visibility to the process, using the platform and the reporting capabilities. It's gotten the general managers and the shop leads engaged and having the conversation about safety. >> This is great, 'cause you got the platform piece of it, and went from basic application delivery to seeing that it is just a workflow tool. >> Donna: Exactly. >> And the benefit of the automation, and now applying it to, I don't think they announced a auto auction safety module this morning. >> No. (laughing) >> Not yet, but we are doing a session... (Donna laughs) >> It's pretty impactful that you were able to see that, execute it with a really small investment, like you said, your initial one with you, an analyst and an intern, and now, really grow and expand the footprint within the organization. >> Yeah, it's really just about business processes in general. You've got everything you need to collect some attributes, or some information, you need to route it or get approvals around it, and then you can measure it. And you can see what's going on with that business process, and then you focus on, how do we improve the business process? The tool helps enable that and facilitate that. >> And how has the conversation around IT value changed, since you started this journey, right? >> Yeah. >> It used to be very cost-focused, I'm sure. Has it evolved to more of a, you mentioned ROI? >> It is, look at it, it's still cost-focused. It's still about savings, but it's also about how do we get things done in an organization more efficiently, with less people pushing paper, and actually focused on solving problems. And being able to measure how we get better in the activities that we're supporting. And then the dollars will follow. >> Dave: Is there a recognition in the business units, that things are changing? >> You know, there really is. One of the areas that we're starting to see real recognition is we're now dipping our toe into customer service management. We brought two platforms together with one of our business units that we acquired in the last year. They were doing some things on Zendesk, they were doing some things on another tool, and they were the same team. So, we've taken that experience, we've brought those agents onto the platform. We didn't change the experience for the customer just yet, because we wanted our agents to be very successful and help them work differently than through email. We pull those channels onto the platform, and now they have a dashboard of these issues in supporting our lenders, who are our customers. Next is really around the portal, in changing the experience for those end customers. Moving it out of the reply to all with email and making it more measurable. We've gotten halfway there, and we see a big growth area there for us, and making a better experience around our customers' support. >> And are you sunsetting some of these other systems as you bring stuff in? >> We absolutely are. I mean, our goal is to eliminate all other ticketing-type systems. In fact, all of the people that are on those ticketing systems, like, "When can we get on the platform?" "We want to be there now." "Help us get there." But bringing things together is going to help us across all of our functional areas, in supporting our customers and our team members much more effectively. It really is becoming our system of action, where you go to get things done. >> Donna, what, from your perspective, is on ServiceNow's to-do list? >> ServiceNow's to-do list. You know, and I've been pretty vocal with ServiceNow, it's like, make it easier for us to use and consume the other capabilities of the platform much more quickly. Allow us to use the great capabilities with some of our external collaborators a little bit more effectively. And I think that's where it is. I think ServiceNow does a fantastic job of bringing more capabilities and maturing all of their service areas. I like the fact that they have two major feature releases a year, and we consume them as quickly as they can send them out, probably faster than some other customers do. And continue to listen to your customers. Just, listen to what our problems are, and our needs are, and continue to answer them. They're doing a good job of that. >> Well, Donna, I have to say thanks for all the great products you guys build. The Kelley Blue Book, we've used it for years-- >> Oh, wonderful! >> And Autotrader, it's a great way to shop for vehicles. So thanks for that! >> You're welcome! >> Dave: Thanks for coming on theCUBE. >> Thank you so much. >> Thanks for sharing your story. >> Keep it right there, everybody. Jeff and I will be back with our next guest. This is theCUBE, we're live from Knowledge17. We'll be right back. (energetic music)