 From San Francisco, it's theCUBE. Covering Sumo Logic Illuminate 2018. Now, here's Jeff Frick. Hey, welcome back, everybody. Jeff Frick here with theCUBE. We're at Sumo Logic Illuminate at the Hire Regency San Francisco Airport down in Berlin Game. And we like to talk to people that run these companies, but we really like to talk to customers. That's our favorite part of our day. And we're excited to have a customer of Sumo Logic who's come on to tell us part of his story. It's Eric Rocknoby. He's a senior manager, platform engineering at USA Networks. Great to see you. Good to see you? Yeah, so first off, just impressions of the event. I think it's only the second year they did it. They had the Silent Disco certifications going on this morning. I didn't participate in the Silent Disco. You did not do the Silent Disco? I will, because I'll be talking tomorrow. And so I'm very curious to see how this can work out. It's pretty cool, actually. Everybody in the same room, except they can't hear it. So it's very much like this Silent Disco if you've ever done one of those. But in your talk tomorrow, it's all about migration. That's kind of what you're here for. You've done some big, big migration. So talk a little bit about some of the thought processes that started this migration process. There's always a lot of talk of lift and shift and can you migrate and should you migrate? And then some of the things that happen as you went through that process. Sure, so we migrated from Splunk Cloud to Sumo Logic. And at the same time, we're migrating workloads from AWS to Google. We're now about 60% in Google. And also, we've really been stepping up our containerization and use of Kubernetes. Actually, the 2016 elections was our very first time we used Kubernetes in production, figured go big or go home. Good timing. Yeah. And it was an amazing success. I think we did 160 plus deployments that night, which we'd never be able to do just on a VM-based workload. So we've been migrating a lot of our workloads to Kubernetes and it actually really dovetailed nicely with Sumo Logic because they had great support for that. So migrating is never easy. So what were some of the motivations that were causing you guys to look at and ultimately making some of these migrations? Just the typical technology on speed of market, being able to serve our internal customers quickly. The platform we were on was a lot of opening tickets and asking for maintenance windows for plugins or change and things like that. And we really needed something that was SAS from the beginning and be able to integrate rapidly. Right. So how difficult was the process? How long did it take? Big team, small team? So my team is about eight folks, but one of the things I'll talk about in my talk tomorrow is find your key stakeholder. And for us that was security and engineering. And we involved them early in the vetting process for Sumo Logic, really had them step up their requirements and help drive the process. And they also helped wrangle a lot of the rest of the enterprise, which we may not have had input or say over, but security has their hands in a lot of places. So that was a key win for us. As far as how long it took us, it were agile team, new two-week sprints. I think we probably got it done within a quarter, which felt pretty good. And it was, when we actually ended up cutting over as a non-event. Really? Yeah. Were you all keyed up for the event and then the event didn't happen? Yeah, it was like, okay, we're as a fire and it's like, no big whoop, right, right. So we're here at Sumo Logic Illuminate. So what were some of the specific attributes of Sumo Logic that helped you with this process? Yeah, so we're a chef shop and for our VM-based workloads and configuration management. And then we're also big into Kubernetes. And they have a couple of key integrations there. They have a great chef cookbook for deploying their collector and configuring sources and everything. And we leverage that heavily and then customize it for, it's open source. So you take it and then you make it your own. Right, right. And so we customize it for our own needs. And then that was for the VM workloads and then the Kubernetes, there's a FluentD Sumo Logic collector. It has excellent integration with Kubernetes and we did some customization there so it would match our taxonomy of our source categories and everything just to make things easier to search and index. But it's really about delivering for internal customers and making it seamless and easy. Like, they don't have to think about it. They're containers log and this thing just picks them up and ships them and they know where to find them. That's cool. And there's a lot of dev ops is now moving into dev sec ops, right? We hear it more and more every place we go. And we also hear about security. It needs to be baked in all along the path. And as you said, your security team was one of your primary stakeholders and supporters of the effort. So I wonder if you can speak a little bit deeper into how the role of security and the where security plays has changed from the old walled garden days to really integrating it into everything that you do up and down the application side. So, I mean, they have a ton of tools of their own that they need to aggregate data all in one place. So that's one key takeaway. But they also, actually just a couple of weeks after we went live, we had a DDoS attack on one of our properties. So we have over 100 papers across the country, digital properties and print. And we have some mitigation at our CDN fastly, but really investigating the source and getting it locked down and everything SumoLogic played a key role in that kind of rapid response. You know, and other things like GitHub, like seeing, like they've got alerts to go off as somebody adds somebody to the org and they don't have two factor authentication on and that's all coming through Sumo. So, they're really leveraging it proactively to enforce policy and also for investigation and things like that. So you had more migrations on the horizon since it was so easy this last time. You had the non-event on the cutover day. I don't know. I think maybe we'll stick with our tool set and build on what we got. All right here. Well, I don't know. You got to do it again. I mean, if you're so successful, you got to do it a few more times. We'll see, you never know who might get swapped out next year. All right, Eric. Well, thanks for taking a few minutes and sharing your story and good luck on your presentation tomorrow. Appreciate it. All right, he's Eric. I'm Jeff. You're watching theCUBE where it's SumoLogic Illuminate. Thanks for watching.