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