>>From around the globe. It's the cube presenting, accelerating automation with dev net brought to you by Cisco and welcome back to the cubes coverage. Just to keep virtuals coverage of dev net create virtual. We're not face to face the cubes been there with dev net and dev net create. Since the beginning, dev net create was really a part of the dev net community. Looking out at the external market outside of Cisco, which essentially is the cloud native world, which is going mainstream. We've got a great guest here. Who's who's been the company's been on the cube. Many times. We've been talking to them recently acquired by Cisco thousand eyes. We have Joe Vaccaro, his beast vice president of product, Joe, welcome to the cube. Thanks for coming on. Great. And thanks for having me. You have the keys to the kingdom. You are the vice president of product, which means you get to look inside and you get to look outside, figure it all out, uh, make everything run on thousand eyes. >>You guys have been finding common language across multiple layers of network intelligence, external services. This is the heart of what we're seeing in innovation with multi-cloud microservices, cloud native. This is really a hot area it's converged in multiple theaters and technology super important. So I want to get into that with you. But first thousand eyes was recently acquired by Cisco, um, big acquisition, uh, super important, the new CEO of Cisco, very clear API, everything we're seeing that come out. That's a big theme at dev net create the ecosystem of Cisco is going outside their own, you know, their, their walls outside of the Cisco network operators, network engineers. We're talking to developers talking programmability. This is the big theme. What's it like at Cisco? Tell us, honestly, the COVID hits. You get acquired by Cisco. Tell us what's happening. >>Yeah, surely been an exciting six months, 4,000 eyes on the entire team and our customers as we all kind of shifted to the new normal of working from home. And I think, you know, that change alone really kind of amplified. Even some of the fundamental beliefs that we have as a company that you know, cloud is becoming the new data center or customers that Indra internet has become the new network and the new enterprise network backbone. And that SAS has really become the new application stack. And as you think about these last six months, those fundamental truths have never been more evident as we rely upon the cloud to be able to, to work as we rely upon our own home networks and the internet in order to be productive. And as we access more sized applications on a daily basis. And as you think about those fundamental truths, what's common across all of them is that you rely upon them now more than ever, not only to run your business, but to enable your employees to be productive, but you don't own them. And if you don't own them, then you lack the ability in a traditional way to be able to understand that digital experience. And I think that's ultimately what, what thousand eyes is trying to solve for. And I think it's really being amplified in really these last six months. >>Talk about the COVID dynamic because I think it highlighted and certainly accelerated digital transformation, but specifically exposes opportunities, challenges, weaknesses, I've talked to many CXOs CSOs. Uh, sec security is huge. Um, the home of the conference and book talk track we'll get to in a second, but it exposes what's worth doubling down on what to abandoned from a project standpoint, as people start to look at their priorities, they're going, Hey, we got to have a connected experience. We got to have security. People are working at home. No one has VPNs at home VPNs or passe. Maybe it's SD when maybe it's something else they're on a backbone. They're connecting to the internet, a lot of different diversity in connections. At the same time, you got a ton of modern apps running off for these networks. This is a huge issue. COVID is exposed this at scale. What's your view on this? And what does thousand nights thinking about this? >>You know, if you think about the kind of legacy application delivery, it went from largely users in an office connected over, say a dedicated corporate network, largely to traditional say internal hosted applications. And that was a early, simple, uh, connectivity bath. And as you mentioned, we've seen amplifications in terms of the diversity from the users. So users are not in the office. Now they're connected in distributed disparate locations that are dynamically changing. And you think that how they're getting to that application, they're going across a really complex service chain of different network services that are working together across as public internet backbone. We'll totally to land them on an application. And then those applications themselves are becoming now, as you mentioned, distributed largely based upon a microservices architecture and increasing barrel independence upon third party sample size applications to fulfill say key functions of that application. >>Those three things together ultimately are creating that level of complex service chain. It really makes it difficult to understand the digital experience and ultimately the it organization it's really chartered with not just delivering the infrastructure, but delivering the right experience. And yet then have a way to be able to see, to gain that visibility, that experience, you know, to measure it and understand, and to provide that intelligence and then ultimately to act on it and be able to ensure that your employees, as well as your customers are getting the right overall, um, approach to being able to leverage those assets. >>It's funny, you know, as you're getting to some of these high-scale environments, a lot of these concepts are converging. You know, we had terms like automation self-healing networks. Um, you mentioned microservices earlier, you mentioned data out of the clouds, the new data center, uh, or when's the new land. However, we're going to look at it. It's a whole different architecture. So I want to get your thoughts on, on the automation piece of networking and internet outages, for instance, um, because when you, you know, there's so many outages going up and down, it is like, uh, catching, looking for a needle in a haystack, right. So, um, we've had this conversation with you guys on cube before. How does automation occur when you guys look at those kinds of things what's important to look at? Can you comment on and react to, you know, the internet outages and how you find resolve those? >>Yeah. It's um, it was really great. And as you mentioned, automation really in a place that a key, when you think about the, just a broad problem that it is trying to drive and, you know, from our lens, we look at it in really three ways. Your first off is you have to be able to gain the level of visibility from where it matters and be able to, to test and be able to provide that level of active measurements across the, the type of ways you want to be able to inspect the network. But then also from the right vantage points, you want to inspect it. But what we talked about right aside, you know, data, um, alone, doesn't solve that problem. As you mentioned, that needle in the haystack, you know, data just provides the raw metrics that are screaming across the screen, and you have to then enable that data to provide meeting. >>You need to enable that data to become intelligent. And that intelligence comes through the automation of being able to process that data very quickly. They'll allow you to be able to see the unseen, allow you to be able to quickly understand the issues that are happening across this digital supply chain to identify issues that are even happening outside of your own control across the public internet. And then the last step of automation really comes in the form of the action, right? How do you enable that intelligence to be put, to use? How do you enable that intelligence to then drive across the rest of your it workflow as well as be able to be used as a signaling engine, to be able to then make the fundamental changes back to the network fabric, whether that is a dressing you're modifying your BGB pairing, that we see happen within our customers using thousand eyes data, be able to route around major internet outages that we've seen over the past six months, or to be able to then use that data, to be able to optimize the ultimate experience that they're delivering to both our customers, as well as our employees, >>Classic policy based activities take into a whole nother level. I got to get your thoughts on the employees working at home. Okay. Because, um, you know, most it people like, Oh yeah, we're going to forecast in cases of disruption or a hurricane or a flood or arcane Sandy, but now with COVID, everyone's working at home. So who would have forecasted a hundred percent, um, you know, work from home, which puts a lot of pressure on him, everything. So I got to ask you, now that employees are working at home, how do you tie network visibility to the actual user experience? >>Yeah, that's a great question. As you know, we saw it within our own customer base, you know, when COVID head and we saw this rise of work from home, it teams were really scrambling and said, okay, I have to light up this, say VPN infrastructure, or I need to now be able to support my users in a work from home situation where I don't control the corporate network. In essence, now you have naturally thousands. Every employee is acting across their own corporate network and people were then using thousand eyes in different ways to be able to monitor their CTP and infrastructure across, uh, back into the corporate network, as well as in using our thousand eyes endpoint point agents that runs on a local, a user's laptop or machine in their home to help you to be able to gain that visibility down to that last mile of connectivity. >>Because when a user calls up support and says, I'm having trouble say accessing my application, whether that's Salesforce or something else, what ultimately might be causing that issue might not necessarily be a Salesforce issue, right? It could be the device in the device performance in terms of CPU, memory utilization. It could be the wifi and the signal quality within your wifi network. It could be your access point. It could be your raw, local home router. It can be your local ISP. It could be the path that you're taking ultimately to your corporate network or that application. There's so many places that could go wrong that are now difficult to be able to see, unless you have the ability to see comprehensively from the user to the application, and to be able to understand that full end to end path, >>You know, it teams have also been disrupted. They've been on offsite prop off property as well, but you got the cloud. How is your technology help the it teams? Can you give some examples there? Um, >>Yeah, a great way is, you know, how people use thousand eyes as part of that data sharing ecosystem. Again, that notion of how do you go from visibility to intelligence to action and where in the past you might be able as an it administrator to walk over to their network team and say, Hey, can you take a look at what I'm seeing now? That's no longer available. So how do you be able to work efficiently as the Nike organization? You know, we think a thousand eyes and how our customers are using us a thousand times becomes a common operating language and allows them to be able to analyze across from the application down into the underlying infrastructure, through those different layers of the network what's happening. And where do you need to focus your attention? And then furthermore, within thousand eyes in terms of a need, enabling that data sharing ecosystem, leveraging our Sherlyn capability really gives them the ability to say, you know, what, here's what I'm seeing and be able to send that to anybody within the it organization. But it goes even further and many times in recent times, as well as over the course of people using thousand eyes, they take those share links and actually send them to their external providers because they're not just looking to resolve issues within their own it organization. They're having worked collaboratively with the different ESPs that they're pairing with, with their cloud providers that they're appearing, uh, they're leveraging, or the SAS applications that are part of that core dependency of how they deliver their experience. >>I've got to ask you the question we think about levels of visibility and making the lives easier for it. Teams. Um, you see a lot of benefits with thousand eyes. You pointed out a few of them. It's got to ask you the question. So if I'm an it person I'm in the trenches, are you guys have, uh, an aspirin or a vitamin or both? Can you give an example because it does a lot of pain point out there. So yeah. Give me a, a cup, a couple Advils and aspirins, but also you're an enabler. The new things are evolving. You pointed out some use case. Talk about the difference between where you're helping people pain points and also enabling them be successful for it teams. >>Yeah, that's a great analogy. You're thinking it, like you said, it definitely sits on both sides of that spectrum, you know, thousand eyes is the trusted tool, the source of truth for it. Organizations when issues are happening as their alarm bells are ringing, as they are generating the, um, the different, uh, on call, uh, to be able to jump into a worm situation thousand eyes is that trusted source of truth. Allow them to focus, to be able to resolve the issue in the heat of the moment. But that was a nice also when we think about baselining, your experience, what's important is not understanding that experience at that moment in time, but also how that's deviated over time. And so by leveraging thousand eyes on a continuous basis, it gives you the ability to see the history of that experience, to understand how your network is changing is as you mentioned, networks are constantly evolving, right? >>The internet itself is constantly changing. It's an organic system, and you need to be able to understand not only what are the metrics that are moving out of your bounds, but then what is potentially the cause of that as a network has evolved. And then furthermore, you can be begin to use that, as you mentioned, in terms of your vitamin type event analogy, you'll be able to understand the health of your system over time on a baseline basis so that you can begin to, uh, be able to ensure its success in a great way to really kind of bring that to light as people using say, thousand eyes, as part of saying se land base for allow where you're looking to say benchmark and gain confidence as you look to scale out and either, you know, benchmarking different ESPs within that, I feel like connectivity for as you look to ensure a level of success with a single branch to give you that competence, to then scale out to the rest of your organization. >>That's great insights. The classic financial model ROI got baseline and upside, right? You got handle the baseline as you pointed out, and the upside music experience connectivity, you know, application performance, which drives revenue, et cetera. So great point. Great insight, Joe. Thank you so much for that insight. It's got a final question for you. I want to just riff a little bit with you on the industry. A lot of us have been having debates about automation. I mean, who doesn't, who doesn't love automation, automation's awesome, right? Automate things. But as the trend starts going on, as everything is a service or X, a S as it's called, certainly Cisco's going down that road. Talk about your view about the difference between automation and everything is a service because at the end of the day, everything will be a service, but without automation, you really can't have services, right? So, you know, automation, automation, automation, great, great drum to bang all day long, but then also you got the same business side saying as a service, as a service, pushing that into the products, it means not trivial. Talk about, talk about how you look at automation and everything as a, and the relationship and interplay between those two concepts. >>Yeah. Ultimately I think about in terms of what is the problem that the business is trying to solve in ultimately, what is the value that they're trying to face? And in many ways, right, they're being exploded with increase of data that needs, they need to be able to not only process and gather, but then be able to then make use of, and then from that, as we mentioned, once you've processed that data and you'd say, gather the insights from it. You need to be able to then act on that data. And automation plays a key role of allowing you to be able to then put that through your workflow. Because again, as that, it experience becomes even more complex as more and more services get put into that digital supply chain. As you adopt say increased complexity within your infrastructure, by moving to a multicloud architecture where you look to increase the number of say, network services that you're leveraging across that digital experience. >>Ultimately you need the level of automation. You'd be able to see outside of your own vantage point. You need to be able to look at the problem from as broad of a, a broad of a way as possible. And, you know, data and automation allows you to be able to do what is fundamentally difficult to do from a very narrow point of view, in terms of the visibility you gather intelligence you generate, and then ultimately, how do you act on that data as quick as possible to be able to provide the value of what you're looking, salt >>Feature it's under the hood, the feature of everything, because the service is automation, data, machine learning, all the goodness and the software. I mean, that's really kind of what we're talking about here. Isn't it a final question for you as we wrap up, uh, dev net create really, again, is going beyond Cisco's dev net community going into the industry ecosystem where developers are there. Um, these are folks that want infrastructure as code. They want network as code. So network programmability, huge topic. We've been having that conversation, uh, with Cisco and others throughout the industry for the past three years. What's your message to developers out there that are watching this who say, Hey, I just want to develop code. Like I want, you know, you guys got that. That was nice. Thanks so much. You know, you take care of that. I just want to write code. What's your message to those folks out there who want to tap some of these new services, these new automation, these new capabilities, what's your message. >>And ultimately, I think, you know, when you look at thousand eyes, um, you know, from a product perspective, we, you know, we try to build our product in an API first model to allow you to be able to then shift left of how you think about that overall experience. And from a developer standpoint, you know, what I'd say is, is that while you're developing in your silo, you're going to be part of a larger ultimate system. In your experience you deliver within your application is now going to be dependent upon not only the infrastructure it's running upon, but the network it's connected to. And then ultimately the user in the sense of that user and by leveraging a thousand eyes, being able to then integrate thousand 18 to how you think closely on that experience, that's going to help ensure that ultimately the application experience that the developers looking to deliver meets that objective. And I think what I would say is, you know, while you need to focus on your, uh, your role as a developer, having the understanding of how you fit into the larger ecosystem and what the reality of how your users will access that application is critical. >>Awesome, Joe, thank you so much. Again, trust is everything letting people understand that what's going on underneath is going to be viable and capable. You guys got a great product and congratulations on the acquisition that Cisco made of your company. And we've been following you guys for a long time and a great technology chops, great market traction, congratulations to everyone, 1,009. Thanks for coming on sharing. I appreciate it. Thanks for having me. Do you have a car, a vice president of product here with thousand eyes. Now, part of Cisco I'm John farrier, host of the cube cube virtual for dev net. Create virtual. Thanks for watching.