>> from Burlingame, California It's the Cube covering Suma logic Illuminate 2019. Brought to You by Sumer Logic. >> Hey, welcome back, everybody. Jeffrey here with the Cube worth, assume a logic illuminate 2019 of it. It's at the Hyatt Regency San Francisco airport. About 809 100 people are second year. It's a 30 year of the event, excited to be here and watch it grow. We've seen a bunch of these things grow from little to bigger over a number of years, and it's always funded kind of beer for the zenith. We're excited to do it by our next guest. She's an analyst. It's Nancy Goering, senior analyst for 4 51 research. Nancy, great to see you. >> Thank you for having me. >> Absolutely so first off, Just kind of impressions of the event here. >> Yeah, good stuff. You know, like he's definitely trying to, you know, get on top of some of the big trends. You know, The big news here was their new Cooper nineties monitoring, also obviously kind of staying on the the leading edge of the cloud. Native Technologies. >> It's it's amazing how fast it's growing, you know, doing some research for this. Then I found some of your stuff out on the Internet and just one quote. I think it's from years ago, but just for people to kind of understand the scale, I think, he said, Google was launching four billion containers a week. Twitter had 12,000. Service is uber 4000. Micro service is Yelp and Justin 25 million data points per minute. I think this is like a two or three year old presentation. I mean, the scale in which the data is moving is astronomical. >> Yeah, well, I mean, if you think of Google launching four billion containers every week, they're collecting a number of different data points about a container spinning up about the operation of that container while it's alive about the container spinning down. So it's not even just four billion pieces of data. It's, you know, multiply that by 10 20 or many more. So, yeah, So the volume of operations dated that people are faced with is just, you know, out of this world, and some of that is beginning to get abstracted away, terms of what you need to look at. So, you know, Kubernetes is an orchestration engine so that's helping move things around. You still need to collect that data to inform automation tools, right? So even if you was, even if humans aren't really looking at it, it's being used to drive automation, right? It still has to be collected, >> right, And they're still configurations and settings and and dials. And it seems like a lot of the breaches that we hear about today are people just miss configuring something on us. It's human error. And so how do we kind of square the circle? Because the date is only growing. The quantity sources, the complexity, Yeah, the lack of structure. And that's before we had a I ot And now we got edge devices and they're all reporting in from from home. Yeah, crazy problem. It's >> really, I think, driving a lot of the investments in the focus and more sophisticated analytics, right? So that's why you're hearing a lot more about machine learning. And a I in this space is because humans can't just look at that huge volume >> of data and >> figure out what it means. So the development of machine learning tools, for instance, is gonna pull out a piece of data that's important. Here is the anomaly. This is the thing you should be paying attention to. Andi, obviously getting increasingly sophisticated, right? In terms of correlating data from different parts of your infrastructure in order to yet make sense of it, >> right? And then, Oh, by the way, they're all made up of micro service is a literal interconnected in AP eyes. The third party providers. Yeah. I mean, the complexity is ridicu >> and then, you know, and I've been actually thinking and talking a lot recently about organizational issues within companies that exacerbate some of these challenges. So you mentioned Micro Service is so ah, lot of times, you know, you've got Dev ops groups and an individual Dev Ops group is responsible for a or multiple. Micro service is right. They're all running, sort of autonomous. They're doing their own thing, right? So they could move quickly. But is there anybody overseeing the application that's made up of maybe 1000 Micro Service's? And in some cases, the answer is no. And so it may look like all the Micro Service's are operating well, but the user experience actually is not good, and no one really notices until the user starts complaining. So it's like things start. You know, you have to think about organizational things. Who's responsible for that, right? You know, if you're on a Dev ops team and your job has been to support the certain service's and not the whole, like who's responsible for the whole application and that's it's a challenge, it's something. Actually, in our surveys, we're hearing from people that they're looking for people that skill set, someone who understands how to look at Micro Service's as they work together to deliver a service, right? It's it's a It's a pain point. Shouldn't >> the project the product manager for that application would hopefully have some instances abilities to kind of what they're trying to optimize for? >> In some cases, they're not technical enough, right? A product manager doesn't necessarily have the depth to know that, or they're not used to using the types of tools that the Dev Ops team or the operations team would use to track the performance of an application. So sometimes it's just a matter of having the right tooling in front of them, >> and then even the performance I was like What do you optimizing four you optimized for security up the mind thing for speed are optimizing for yeah, you can optimize for everything if you got a stack rank order at some point in time. So that would also then drive in a different prioritization or the way that you look at those doctorsservices performance. Yeah, interesting. It's another big topic that comes up often is the vision of a single pane of glass in You know, I can't help but think is in my work day. You know how often I'm tabbing between, you know, sales force and email and slack and asana and, um, a couple of browsers air open. I mean, it's it's it's bananas, you know, it's no longer just that that email is the only thing that's open on my desk all day and only imagine the Dev Ops world. No, we saw just crazy complexity around again, managing all the micro service's of the AP eyes. So what's kind of the story? What are you seeing in kind of the development of that? And there's so many vendors now, and so many service is yeah, it's not just we're just gonna put in HB open view, and that's the standard, and that's what we're all right on. >> So if you're looking at it from the lens of of monitoring or observe ability or performance. Traditionally, you had different tools that looked at, say, different layers of a service, so you had a tool that was looking at infrastructure. Was your infrastructure monitoring tool. You had an application performance monitoring tool. You might have a network performance monitoring tool. You might have point tools that are looking just at the data base layer. But as things get more complicated, Azadliq ations are getting much more complex. Looking at that data in a silo tool tends to obscure the bigger picture. You don't understand when you're looking at the's separate tools how some piece of infrastructure might be impacting the application, for instance. And so the idea is to bring all of that operations data about the performance of an application in tow. One spot where you can run again, these more sophisticated analytics so that you can understand the relationship between the different layers of the application stack also horizontally, right? So how micro service's that are dependent on each other? How one micro service might be impacting the performance of another. So that's conceptually the idea behind having a single pane of glass. Now the execution can happen in a bunch of different ways, so you can have one vendor. There are vendors that are growing horizontally, so they're collecting data across the stack. And there's other vendors that are positioning themselves as that sort of central data repositories, so they may not directly collect all of that data. But they might in just some data that another monitoring vendor has collected. So there's an end. You know, there's there's always going to be good arguments for best of breed tools, right? So, you know, in most cases, businesses are not going to settle on just one monitoring tool that does it all. But that's conceptually the reason, right, and you want to bring all of this data together. However you get it, however, it's being collected so that you can analyze it and understand that big picture performance of a complicated application, >> right? But then, even then, as you said, you don't even want, you're not really monitoring the application performance per se. You're just waiting for the you're waiting for some of those needles to fall out of the haystack because you just you just can't get that much stuff. And you know, it's where do you focus your priority? You know what's most critical? What needs attention now. And if without a machine to help kind of point you in the right direction, you're gonna have a hard time finding that needle. >> And there's a lot of different approaches that are beginning to develop. So one is this idea of SL owes or service level objectives. And so, for instance, a really common service level objective that teams are looking at is Leighton. See, So this Leighton see of the service should never drop under whatever ah 100 milliseconds. And and if it does, I want to be alerted. And also if it drops below that objective for a certain amount of time, that can actually help you as a team. Allocate, resource is so if you're not living up to that service level objective, maybe you should shift some people's time toe working on improving the application instead of developing a new feature, right? So it can really help you prioritize your time because you know what? There was a time when people in operations teams or Dev. Ops teams had a really hard time, and they still d'oh figuring out which problems are important because you've always people always have a lot of performance problems going on. So which do you focus your time on? And it's been pretty opaque. It's hard to see. Is this performance impacting the bottom line of my business? Is this impacting? You know, my customers? Are we losing business over this? Like that's That's a really common question that people I can't answer, right? So there you people are beginning to develop these approaches to try to figure out how to prioritize work on performance problems. It's >> interesting because the other one that and some of you mentioned before is kind of this post incident review instead of a post boredom. And, you know, you talked about culture and words matter, and I think that's a really interesting take because it's it's it implies we're gonna learn, and we're gonna go forward. It's dead. Um, yeah, you know, we're gonna yell at each other and someone's gonna get blamed. That's exactly it. And we're going to move on. So, you know, how is that kind of evolved in. And how does that really help organizations do a better job? >> There's, I mean, there's there's much more of a focus on setting aside time to do that kind of analysis, right? So look at how we're performing as a team. Look at how we responded to an incident so that you can find ways that you can do better next time and some of that Israel tactical right? It's tweaking alerts. Did we not get an alert? You know, did we not even know this problem was happening? So maybe you build new alerts or sport get rid of a bunch of alerts that did nothing. You know, there's there's a lot you can learn on again to To your point, I think part of the reason people have started calling in a post Incident review instead of a postmortem is because yet you don't want that to be a session where people are feeling like Blaine. You know, this is my fault. I screwed up. I spent way too long on this, so I >> had to >> set things out properly. It's it's meant to be productive. Let's find the weak points and fill them right. Fill those gaps. >> It's funny you had another. There's another thing I found where you were talking about not not necessarily the Post Borden, but you know, people, people being much more proactive, much more, you know, thoughtful as to how they are going to take care of these things. And it is really more of a social cultural change unnecessarily. The technical piece that culture pieces. So so >> it is and especially, you know, right now there's a lot of focus on on tooling and that can cause some, you know, interesting issues. So, you know, especially in an organization that has really adopted Dev ops practices like the idea of a Dev Ops team is that it's very autonomous. They do what they do, what they need to do right to move fast and to get the job done. And that often includes choosing your own tools, but that that has created a number of problems, especially in monitoring. So if you have 100 Dev ops teams and they all have chosen their own, monitoring tools like this is not efficient, so it's not. It's not a good idea because those tools aren't talking to each other, even though they're micro service's that are dependent on each other. It's inefficient. From a business perspective. You've got all these relationships with vendors, and in some cases, with a single vendor, you might have 50 instances of the same monitoring tool that you know you have 50 accounts with them, like that's just totally inefficient. And then you've got people on a Dev ops, an individual, all the all the individual Dev ops teams have a person who's supposed to be the resident expert in these tools, like maybe you should share that knowledge across. But my point is, you get into the situation where you have hundreds of monitoring tools, sometimes 40 50 monitoring tools. You realize that's a problem. How do you address that problem? Because you're gonna have to go out and tell people you can't use this tool that you love. That helps you do your job that you chose. And so again, this whole cultural question comes out like, How do you manage that transition in a way that's gonna be productive? >> Thea other one that you brought up that was interesting is where the the sport team basically tells the business team you only have X number of incidents. We're gonna give you a budget. Yeah, exceed the budget. We're not going to help you. It's a really different way to think about prioritization. I >> don't necessarily think that's a great approach, but I mean, there was somebody who did that, but I think it's kind of it's kind of >> an interesting thing. And you talked about it in that. I think it was one of your presentations or speeches where, you know, it makes you kind of rethink. You know, why do we have so many incidents? Yeah, and there shouldn't be that many incidents, and maybe some of the responsibility should be shifted to think about why in the how and is more of a systemic problem than a feature problem or a bug, right? It's a broken code. So again, I think there's so many kind of cultural opportunities to rethink this. In a world of continuous development, continuous publishing and continuous pushing out of new code. Yeah, yeah, sure. All right. Nancy will. Thanks for taking a few minutes, and it's really great to talk to you. Thanks >> for having me. >> Alright. She's Nancy. I'm Jeff. You're watching the Cube where it's Uma Logic illuminate 2019. Thanks for watching. We'll see next time

>> from Burlingame, California It's the Cube covering Suma logic Illuminate 2019. Brought to You by Sumer Logic >> Hey, welcome back, everybody. Jeffrey here with the Cube were at the higher Regency San Francisco Airport at Suma Logic, Illuminate, 2019 were here last year for our first time. It's a 30 year the show. It's probably 809 100 people around. 1000 packed house just had the finish. The keynote. And we're really excited to have our first guest of the day. Who's been here since the very beginning is Bruno Critic, the founding VP of product and strategy for Suma Logic, you know, great to see you. Likewise. Thank you. So I did a little homework and you're actually on the cube aws reinvent, I think 2013. Wow. How far has the cloud journey progressed? Since efforts? I think it was our first year at reinvented as well. >> That's the second year agreement, >> right? So what? What an adventure. You guys made a good bet six years ago. Seems to be paying off pretty well. >> It really has been re kind of slipped out that the cloud is gonna be a real thing. Put all of our bats into it and have been executing ever since. And I think we were right. They think it is no longer a question. Is this cloud thing gonna be re alarm enterprise gonna adopt it? It's just how quickly and how much. >> Right? Right. But we've seen kind of this continual evolution, right? Was this jump into public cloud? Everybody jumped in with both feet, and now they're pulling back a little bit. But now really seen this growth of the hybrid cloud Big announcement here with Antos and Google Cloud Platform and in containers. And, you know, the rise of doctor and the rise of kubernetes. So I don't know, a CZ. You look a kind of the evolution. A lot of positive things kind of being added to the ecosystem that have helped you guys in your core mission. >> That's right. Look, you know, five years ago, which is such a short time, But yet instead of the speed of the technology adoption and change, you know it's in It's in millennia. What's happened over the last few years is technology stocks have changed dramatically. We've gone from okay, we can host some v ems in the cloud and put some databases in the cloud. So we're now building micro service's architecture, leveraging new technologies like Kubernetes like Serverless Technologies and all the stuff And, you know, some one of the fastest growing technologies that's being adopted by some village custom base, actually the fastest kubernetes and also the fastest customer segment growing customer segments. ImmuLogic is multi clog customers, basically that sort of desire by enterprise to build choice into their offerings. Being able to have leverage over the providers is really coming to fruition right now, >> right? But the multi cloud almost it makes a lot of sense, right, because we're over and over. You want to put your workload in the environment that supposed appropriate for the workload. It kind of. It kind of flipped the bid. It was no longer. Here's your infrastructure. What kind of APs can you build on it? Now here's my app. Where should it run that maybe on Prem it may be in a public cloud. It may be in a data center, so it's kind of logical that we've come into this this hybrid cloud world that said, Now you've got a whole another layer of complexity that that's been added on. And that's really been a big part of the rise of kubernetes. >> That's right. And so, as you're adopting service's that are not equal, right, you have to create a layer that insulate you from those. Service is if you look a tw r continues intelligence report that we just announced today. You will also see that how customers and enterprise are adopting cloud service is is they're essentially adopting the basic and core compute storage network, and database service is there's a long, long tail of service that are very infrequently adopted. And that is because enterprise they're looking for a way to not get to lock Tintin into anyone. Service provider kubernetes Give them Give them that layer of insulation with in thoughts and other technologies like that, you are now able to seamlessly manage all those workloads rather there on your on premise in AWS in G C. P. In azure or anywhere else, >> right? So there's so much we can unpack. You're one of the things I want to touch on which you talked about six years ago, but it's even more thing appropriate. Today is kind of this scale this exponential growth of data on this exponential scale of complexity. And we, as people, has been written about by a lot of smart people, and I, we have a real hard time. Is humans with exponential growth. Everything's linear. Tow us. So as you look at this exponential growth and now we're trying to get insights. Now we've got a I ot and this machine a machine data, which is a whole another multiple orders of magnitude. You can't work in that world with a single painted glass with somebody looking at a dashboard that's trying to find a yellow light that's earned it. I'm going to go read. You don't have analytics. Your hose. >> That's right. This is no longer world of Ding dong lights, right? You can just like to say, Okay, red, green, yellow. The as sort of companies go digital right? Which is driving this growth in data, you know? Ultimately, that data is governed by Moore's law. Moore's law says machines are gonna be able to do twice as much every 18 to 24 months. Well, that guess what? They're gonna tell you what they're doing twice as much. Every 18 to 24 months, and that is an exponential growth rate, right? The challenge that is, budgets don't grow at that rate, either, right? So budgets are not exponentially growing. So how do you cope with the onslaught of this data? And if you're running a digital service, right, if you're serving your customers digital generating revenue through digital means, which is just about every industry. At this point in time, you must get that data because if you don't get the data, you can't run your business. This data is useful not just in operations and security. It's useful for general business abuse, useful in marketing and product management in sales and their complexity. And the analytics required to actually make sense of that data and serve it to the right constituency in the business is really hard. And that has been whatever we have been trying to solve, including this economics of machine. Dad and me talked about it today. Keynote. We're trying t bend the cost curve >> Moore's law >> yet delivered analytics that the enterprise can leverage to really not just operate an application but run their business >> right. So let's talk about this concept of observe ability. You've written box about it. When you talk to people about observe ability, what should they be thinking about? How are you defining it? Why is it important? >> It's great question, So observe ability right now is being defined as a technique right. The simplest way to think about it is people think, observe a witty I need to have these three data sets and I have observed ability. And then you have to ask yourself a question. First of all, what is Observe ability and why does it matter? I think there's a a big misconception in the market how people adopt this is that they think, observe abilities the end. But it isn't observe. Ability is the means of achieving a goal. And what we like to talk about is what is the goal? Observe, observe ability right now. Observe abilities talked about strictly in the devil up space, right? Basically, how am I going to get obs Erv City into an application? And it's maybe runtime how it's running, whether it's up and performance. The challenge with that is that is a pigeon pigeon hole view off, observe ability, observe ability. If you think about it, we talk about objectives during observe ability. Operability tau sa two ns Sorry could be up time in performance. Well, guess what a different group like security observe. Ability is not getting breached. Understanding your compliance posture. Making sure that you are compliant with with regular to re rules and things like that observe ability to a business person to a product manager who's who owns a P N. L. On some product is how are my users using this product powers my application being adopted where users having trouble. What are they and where's the user experience? Poor right? So all of this data is multifaceted and multi useful as multi uses and observing Tow us. Is his objectives driven? If you don't know what your object it is, observe. Ability is just a tool. >> I love that, you know, because it falls under this thing We talked about off the two, which is, you know, there's data, right, and then there's information in the data and then, but it is a useful information because it has to be applied to something that's right in and of itself. It has no value, and what you're talking about really is getting the right data to the right person at the right time, which kind of stumbled into another area, which is how do you drive innovation in an organization? In one of the simple concepts is democratization. Get more people more than data more than tools to manipulate the data. Then piano manager is gonna make a different decision based on different visibility than Security Person or the Dev Ops person. So how is how is that evolving? Where do you see it going? Where was it in the past? And you know, I think he made it interesting or remain made. Interesting thing in the keynote where you guys let your software be available to everyone. And there was a lot of people talking about giving Maur. People Maur access to the tools and more of the data so that they can start to drive this innovation >> abuse of an example of one of the one of the sort of aspects of when we talk about continued continues intelligence. What do we mean? So this concept of agile development didn't evolve because people somehow thought, Hey, why don't we just try to push court production all the time? Break stuff all the time. What's the What's the reason why that came about? It did not come about because somehow somebody decided so better. Software development model It's because cos try to innovate faster, so they they wanted Toa accelerate. How they deliver digital product and service is to their customers. And what's facilitates that delivery cycle is the feedback loop. They get out of their data. They push code early. They observed the data. They understand what it's telling them about how their customers are using their products, and service is what products are working with or not. And they're quickly baking that feedback back into their development cycles into the business business cycles. To make better Prada effectively, it evolved as a as a tool to differentiate and out innovate the competition. And that's to a large degree one of the ways that you deliver the right inside to the right group to improve your business right. And so this is applicable across all use cases in order pot. All departments are on the company, but that's just one example of how you think of this continuous innovation, continuous data from to use analytics and don't >> spend two years doing an M r d and another two years doing a P R d and then another to your shift >> When you when you actually ship it. Half of the assumptions that you made two years ago already all the main along, right? So now you've gotta go. You've wasted half of your development time, and you've only released half of the value that you could have other, >> right? Right. And your assumptions are not gonna be correct, right? You just don't know until you get that >> you think over time, like two years of kubernetes with a single digits percentage adoption technology and soon was customer base. Now it's 1/3 right? Right? Which means no things have changed. If I had made an assumption as of two years ago on communities, I would have no way wouldn't have done this announcement, >> right? Right. >> But we did it in an interactive mode and re benefit from that continuous information continues intelligence that we do in our own >> right, right? We fed Joe and the boys on lots of times so that it's a pretty interesting how fast that came and how it really kind of over took. Doctor has informed they contain it. Even the doctor, according to reporters. Still getting a Tana Tana traction >> and it's >> working in conjunction with communities. Communities allows you to manage those containers right, And Dr Containers are always part of the ecosystem. And so it's, you know, you know, it's like the management layer and the actual container layer, >> right? So as you look forward to give you the last word, you know, as we're really kind of getting into the SIA Teague World and five G's coming just around around the corner, which is gonna have a giant impact on an industrial I ity and this machine a machine communications, what are some of your priorities? What are you looking, you know, kind of a little bit down the road and keeping an eye on >> interesting question. You know, we used to think about I ot as is the new domain. We should think about I or tea. And maybe we need to build a solution for right. It turns out our biggest customers, customers and the way that I have personally reframed my thinking about Iris is the following Computational capacity is ubiquitous. Now, what used to be a modern application 345 years ago was something that your access to your laptop or three or mobile app, and maybe you're a smart watch Now the computation that you interface with runs in your doorbell, you know, in a light switch in your light bulbs and how's it runs everywhere runs in your shoe because when you're around, it talks to your phone to tell you how many steps you've taken, all the stuff right? Essentially, enterprises building application to serve their customers are simply pushing computation farther and farther into our being, like everywhere. There's now I, P Networks, CP use memory and all of those distributed computers are now running the applications that are serving us in our lives, right? And to me, that's what I ot is. It's just an extension off what the digital service is our and we interface with does, and it so happens that when you push computation farther and farther into our lives, you get more and more computers participating. You get more data, and many of our largest customers are essentially ingesting their full stack of iron devices to serve their customers >> right crazy future and you know, it just kind of this continual Adam ization to of computer store and memory. Well, Bruno, hopefully it will not be six years before we see you again. Congrats on the conference. And thanks for taking a few minutes. Absolutely. All right. He's Bruno. I'm Jeff. You're watching the Cube where? It's suma logic illuminate at the Hyatt Regency seven square port. Thanks for watching. We'll see you next time.

>> from Burlingame, California It's the Cube covering Suma logic Illuminate 2019. Brought to you by Sumer Logic >> Hey, welcome back already, Jeffrey Here with the Cube Worth Suma >> logic illuminated the higher Regency San Francisco airport. About 800 people, 900 people packed house in the keynote earlier this afternoon. Really interesting space, and we're excited to have our next guest >> kind of on the cutting edge >> of the I o T space on the consumer side. And he's Robert Parker, the CTO of Sand Samsung. Smart things, Robert. Great to see you. >> Great to be here. >> Absolutely so before we get into >> the kind of the depth of the conversation, a little bit of a background on smart things. I was doing some research getting ready for this and the fact that it started as a kickstarter a long time ago, not that long ago, and now is part of Samsung, a global electronics giants. What a fun adventure. >> Absolutely. I think it's been one of these things where it's great to be something where it's community driven to begin with, so kick start. It was a big part of our launch, and we were one of the biggest kicks are launches at the time. Uh, really powered by our community around the website and early users. We got a lot of interest in I O. T. And then moved on to the next stage of the vision, which is sort of encompassing all devices. And so that meant we have more than 2000 different Samsung devices on the platform now, which really allow devices to talk to each other in ways that are really exciting. And that breath has been really great thing to be part of >> right. It's really funny. We went to the Samsung Developer conference a couple of years ago. It was funny to see the the living room guys fighting with the kitchen guys, you know, What was >> the centers that the TV or is it >> the fridge aerator? Or is it the washing machine for that bit? And Samsung's got really got a foot in all those places? >> Absolutely. This is one of the things that the smart thing platform is really enabled Samsung to transition across is then it's no longer a conversation with the washing machine person or the dryer. All the devices are part of the smart things. Cloud. Martin Claude is a one way that you could talk to Samsung Devices, and it's an open ecosystem. So it's not just Samsung. Devices were equally comfortable with manufacturers. Any manufacturer bringing those devices because home is a multi vendor environment you are not. We're gonna have all of your home from anyone, vendor, right? And that's been one of the exciting parts of visions that's been part The open ecosystem is something that's been part of smart things. Story forever to really immortalize that in a platform for Samsung has been great transit, >> right? So we're here. It's Uma Logic, eliminate and preparing for this. I saw an interview with you. You made a really interesting comment. >> You said that we are a pervasive >> user of suma logic, and he said 90% of the team are using similar logic. It's fascinating to me because I think a lot of companies air chasing innovation. I think one of the ways to get innovation is you enable more people to have more access to more data and the tools to actually operate that data so that they can do their jobs and find cool ways to make improvements that aren't necessarily coming from the top down. It sounds like you guys have addressed that philosophy wholeheartedly, >> so we absolutely have addressed it wholeheartedly. I think there's a lot of luck involved, and I want to sort of describe it Is that one of the things that worked well for us is people were excited to use sumo more and more. They're more excited to see what they could do with the tool, what insights they could get. And so you see your neighbor looking at it and they look a dashboard and they say, Can I do a little bit of that? And so much So you know, in the last year we've seen ah lot of unplanned value come out. So 1/3 of the value we gotta assume of, um, um in the past year was unplanned. These things people didn't process, they didn't know they would improve. That really just came from this groundswell from what I would call the community. And I think that's where you get that. That unlocks a lot of the potential because you really can't do things from sort of the planned high level. You really need. People actively engaged right and doing stuff you wouldn't expect. >> That's great. So I >> want to talk about >> a little bit about security. Security is a big topic here. It's topic everywhere we go on and now, with connected devices and connected keys and connect doorbells, it seems like, Oh, here we go again And there's this constant talk that security's got to be baked in throughout the entire process. How are you guys dealing with security? Obviously got to be right at the top of mind in terms of priorities. While you're still connecting the sprinklers in the thermostat and everything else. Security >> and privacy are both critical link in privacy, even though you didn't ask about it. Because as you think about devices like cameras and things like this, privacy is top of mind. Also, in terms of regulation like GDP, are so because of that, we're really looking at both cases that the challenge for both security and privacy is it really cuts through your whole organization and every process, and by the way, every process that every partner, if the organization has because we can have something that could be exploited from sort of a an attack through a customer service representative. That could be a person in the customer service organization. It could be how some of social engineered that. And so what we've really needed is this kind of continuous intelligence that can span all of these processes because in something I security, you're as good as your weakest process. And that doesn't mean that we don't focus on all things that you talked about. Were industry leading from device perspective tohave hardware baked in keys and, you know, do things the manufacturing process that lead to something that could be as secure as anything. But that's really that the secret of using a lot of the continuous intelligence tools like sumo is that all of these could bees aren't enough. You have to bring it together by having the intelligence that spans those processes to make sure that all of them are elevated. Because at the end of the day, a security attack is gonna attack your weakest thing, not your strongest right. >> So one of the other >> topics here that talked about is this exponential growth of data, and you guys were part of the problem because now we got sensors and light switches and all these other things that are kicking off data that before we weren't monitoring. And so from from an execution point of view at the company, when you've got so much data that you need to turn into information and then actionable insight, you said Sumo's got some unique characteristics that allow you guys to get more leverage of that platform. I wonder if you could dig into that little bit more >> and I'd like to reframe the data discussion a little bit. A lot of people look at it. It's a problem. I want to really talk about the opportunity side. So part of that goes to our story where we started off at KICKSTARTER with a few 1000 users, we have over 50 million active users now. >> 50 million >> 50 million. Our Android application, the Google Play store, had been downloaded around 200 million times, so it gives you some idea of that size and scope. So the data is an opportunity. There's an opportunity to build a customer base, too, excite people and to manage the processes that do that. And you know what's great now is that the availability of this data means that you can do it in more ways than you ever could before. The problem is, you need a tool that brings us together. To be able to do that in doing that well is difficult, difficult both on the teams and difficult because the size, scope and complexity of the systems because of the data that you mentioned. But the >> reason you want to >> do it is so that you can cross the chasm in terms of this opportunity, and more and more companies are enough. You have this opportunity on the front of them. One of the things that's been really exciting, but the cloud is a sort of democratized the entry point. But that wasn't good enough just because you could get in the game with three people. It's like making a you can make us application in Mobile Applications store, either on Google's on Apple's really easily that gets you in there. What you really need to do is manage the intelligence that goes from that, and for us, it's been really exciting to be able to take our decisions and make them data driven, and we can do that by this explosion of data because it is their >> right in the date is good. And I think we see, you know, kind of date of it as an asset. It hasn't really hit balance sheets officially yet, but I think you see it in the valuations of of companies like Google and Facebook and Amazon, right, who obviously have these crazy giant multiples of the revenue one because they're growing but too because they have so much data. So the markets kind of valuing that data without explicitly calling it out as a line on the balance sheet. That said, not all data has the same value, not all day. Not all data needs to be treated the same and so really opens up an opportunity. How do you tear it so you don't want to get? You know, it's been a ton of money on a piece of data and a big fat stream that somebody leaves open and accidentally suddenly have a big building that maybe wasn't the most valuable. So >> it actually double down on what you said because for a typical company, one of things has also been true. Of the mega scale companies that you pointed out with is there's a lot of uniformity in their data coming the cost of the Amazon. They have customer orders, and they've got orders at this massive scale. A typical company doesn't look like that. They have their data spread is more fragmented, smaller scale on so >> because they want to make different decisions. And this is the >> same thing that has already happened in the storage area. People are really comfortable with storage that they're gonna have in either just disaster recovery or long term storage. And they want a very low cost footprint around that they've got their hot data and they're much more willing, tohave that data managed differently and at a higher cost rate because it's it's much more valuable. We're looking for tools that span that not just in storage, but in the ingestion in the management in the querying of that data. Because, like you said for most businesses, a lot of data's infrequently looked at or looked at in response to a situation, so I'll never know which 10% of the data will be looked at. It will be based on Oh, I got audited or, you know, some other business event that happened on, so this is one of the key things that business is struggling with. One of them is that they they want to adopt these practices to become modern or boring, modernized. But the 2nd 1 is to really be able to tear the data because they couldn't treat all the data's if it's hot data, just like they already figured that out for storage, >> right? It's pretty interesting. It's been going on for storage forever. We really saw it, I think, with the rise of Flash, which was super high quality but super expensive in the early days that's coming down and then at the other. And we have the end of the glacier storage in the cold, cold, cold store. Just put it away by what your last thought's that last. Answer, Robert. As you look forward, I can't believe you're already in middle of September of 2019. It's fascinating to me that time flies so fast. But as >> you look >> forward, what are some of your priorities over the next year or so? How are you guys kind of moving the ball down the field? >> So we're one of the things that we're looking at? Was the data problem that you were talking about, if really looking at are infrequent data and be able to manage that effectively both from the types of insights that we can get from that. So a lot of this starts to be better usage of machine learning pattern recognition a eye on so that we can, you know, the ideal situation for us and not type of data is it got touched once it got looked at once, and then we could understand how to action it later that deferred action. And then how do you know trigger that deferred action as well as the tearing that we sort of talked about that all day? It is not created, equal, created equally, and so both those things are happening just to put some numbers on this. And why is that? We have 150 terabytes or so of data that is somewhat interesting to our business generated on a daily basis. 150. Terrible, terrible. That's interesting. And then on that's out of that, I'd say 10 terabytes is kind of really actionable. It's that gives you an idea. The other part is how that's growing. Where a year ago, we would have been at maybe 60 terabytes of what I would have called this interesting data and maybe five terabytes of, of of, you know, immediately actionable. And And so that's where you know this is following that where that's exponentially growing and it's a big number. So that's what we really think about. >> So you scared those curves. Curves get state, we look. It >> is a huge opportunity. What will happen is either people will create value out of that for customers, in which case, actually the opportunity, because is that such a scale? It will be great for everyone or number two, you know, it just becomes noise, right? And so it isn't really something that scared of, because worst case is it became noise to you. We really want to be one of those people were getting value out of it and see sort of the business growth and the consumer value growth. Out of that, I I'm pretty optimistic that we'll be able to do it because we really if I look back 34 years, we've just been able to figure out a way, and I think it will continue to do that >> All right. Well, Robert, thanks for taking a few minutes of your time and ensuring the story. It's a great story. Thank you. Appreciate being here. All right. >> He's Robert. I'm Jeff. You're watching the Q word. Suma logic illuminate 2019. >> Thanks for watching. We'll see you next time.

>> from Burlingame, California It's the Cube covering Suma logic Illuminate 2019. Brought to You by Sumer Logic >> Hey, welcome back, everybody. Jefe Rick here with the cue, We're at the higher Regency San Francisco airport. Here. It's Suma logic. Illuminate 2019. It's our second year here, the third year of the show. I think it's about 1000 people that Kino was packed. A lot of great energy, a lot of good community as we see a lot of these smaller show, especially when they're getting started. It's all about community is a lot of sharing of information. It's a really cool time in the life of these companies. Worksite have our next guest slightly irreverent cool culture will dig into it a little bit with Justin bike. Oh, he is the co founder of Expelled Justin Creek to see >> likewise. Thanks for Thanks for having me. >> Absolutely. So give us the give us a rundown expel what you guys all about. >> So in a nutshell, were a 24 73 65 transparent, manage security provider. What that really means is on a 24 hours a day, seven days a week basis. We're looking for you know, signs. They're bad guys inside your environment. If they're there, we're gonna tell you they're they're gonna tell you what they're up to and help you get >> rid of them. Now, the transparent word comes up time and time again, Looking at some of your guys materials that transparent in terms of we can see inside the black box and how you're operating is that transparent. Like we're just going to tell you and show you what transparency is Obviously a really important piece of your messaging. >> Yeah, kind of all of the above. We try to take it to heart and try to really mean it. I think the easiest way to think about it is we want our customers to feel like we're just another part of their team. Right. And the easiest way for us to do that is to let them be a part of what we do on a day in and day out basis. That means if they want a ride shotgun with us when we're working an incident, they can They can watch everything that we do. Watch the investigation unfold in real time if they want to get in there and work with us. They certainly have the ability to do that. And then, you know, we take transparency pretty far. We put our real actual prices on our website, which is not something you see a lot of security companies do. So we just try to be as up front as we can be in the way that we approach dealing with our customers and working with him over time. >> Right? So we we cover our say, we've been covering our safe forever. It's it's 40,000 people at Mosconi. Few is more vendors than you can count, all talking about security. So, you know, you're in the year in the business and then remain in his keynote, put up a security section, had a whole bunch of companies. How did people sort this? I always think of the poor CEO on the other side is being told, you know, you got a big security in every place. You've gotta have a B A B Y o d was using their own iPhones and now we got I t With all these connected devices, the threat surfaces expanding geometrically. How should people think about security? How do you guys play in this kind of morass of complexity. >> You know, it's an interesting question how people deal with it. I think that's why you're starting to see a lot of these really strong in a lot of cases, sort of regional and local see. So groups start to form right because they want to get together and actually talk about a. I'm dealing with this challenge. What do you do and how are you handling this problem? And the only way to do that is to learn from appears, right. Everybody's in this fight together. As for how we fit in, one of the things that we try to do is help customers who have made a lot of investments in a lot of different security technology make sense of it. All right, so you've got 56789 10 20 pieces of security technology. They're deployed there, all blinking red lights of like, Hey, this might be a threat. This might be an intruder inside your infrastructure, and you've got a handful of people that work Monday through Friday, 8 to 5 ish. Somebody's gotta look at that all day long, and that's what we're there for. So our job is to make space for our customers, to do the things they actually love about security instead of just sitting there trying to keep up with a constant, you know, basically overflow of alert. >> Right? And you guys are socking the service. Is that Is that a hard sell? Is that easy sell to people? Understand? They need kind of the augmentation. How does that how does that go over with the customer? It has >> been, I think it's over the years it's become, I think, an easier thing for people to wrap their head around. Because at the end of the day, everybody is infrastructure to grow and write. Their footprint of what they need to protect is growing. They can't. Still, nobody can hire enough people that they need. That's a pervasive problem. It's a top five c. So problem has been for you will never go for a long time. So you've got all this security technology. You get the whole network instrument and then suddenly the business moves to the cloud. You have two instrument that too, and you have to do it using the team that you've gotten. That's not enough people And so what choice do you really have? You need somebody to come in and help provide that 24 7 coverage. There's certain things that your security at the institute, that on Lee be done from inside the business. Right things. They remove your program forward, let your team focus on that and all the stuff around monitoring technology to look for signs. They're bad guys in the environment. Let a provider like expel, help you out, >> right? So let me get your take on kind of the explosion of data. But both the quantity of the date as well as the sources of the data, as well as the structure of the date or the lack of structure in a lot of this data, it's growing exponentially right in people. And we all have our time kind of wrapping our heads around exponential growth, one of the kind of the fundamental problems that we have from your point of view, as you see this and you see your customer struggling with it and interests. Other kind of dichotomy is, Is it? Is it is it Is it asset? Of course, there's a lot of good stuff in there hopefully, But it's also liability because it's expensive. It's expensive. The hold. It's expensive to move. It's expensive to store. How do you help people deal with Keep it secure in this explosion of data environment that we are. >> You know, if there were a silver bullet, answer that question, we'd probably be the only security company in existence. >> They would be on a boat >> in >> the Caribbean or >> something like that, you know, being able to apply the technology that we're, you know, that we can bring to bear, which helps our analysts take all of these different disparate data sources. So we can take your I d. S. We can take your e t r. We can take your cloud control platform, your cloud control plane like an aws cloudwatch cloudtrail all that sort of stuff, bring it in one place, makes sense of it, put it together in a way that contextualized is it against what we know about your business. That's ah, whole lot of the battle right there is just being able to help somebody sort of understand what's going on. What does it mean to my business? What do I do about it? What do I do next on? If you can free up that chunk of time, you let the customer focus on those sort of more tactful things that they need to do inside their business, which is, you know, what's the next big evolution of security inside? You know our company, >> right? The word assume a logic fit in for you guys were here, obviously at the sumo logic event. And you know, the scale of the complexity of this stuff is getting beyond the ability of a human keep track of quite frankly. So there's got to be some automation. There's got to be tools. Even though you guys were transparent, there's just there's just some things I can't look into. How are using similar logic? How's it helping you do your business? You >> know, our partnership with Suma Logic came about actually from our 1st 2 customers who are actually symbolize your customers. And so they're sending all of their infrastructure data. They're sending all their security data and assume a logic, and they came to us and they said all that it is there. If you want to monitor our infrastructure, start there right on our ability because it lives in the cloud. There's no sort of management for the customer to do our villages plug right into that and immediately, like within an hour, to start getting security value out of what the customer has inside Suma Logic is, it's pretty substantial to be able to just start immediately telling him, giving him visibility into what's going on. So that's kind of how the relationship came about and how we worked with him today is we find that again. A lot of our customers have just a ton of data, security or otherwise that they need to store. They need to do it in a place that's going to scale with, um, so your traditional on Crim. You know, it's like a more old school Sim. We just gotta keep buying drives and buying drives and buying more and more places to store things. It's a tough life, right? So Cloud hosted platform, like Suma Logic lets you continue to scale, lets you quickly and easily search that they didn't do it in a reasonably cost effective way. It's a great way for us to work with customers. You don't have any visibility today. We know the folks over assume a logic really well, it's super easy to get up and running and get it up really quickly. It's easy for us to plug into. We can get you visibility in your environment really, really fast. If you don't have any today, >> so is that enabled you to bring a different scale of data to bear on your analytics is too. We know there's bad guys in there. You know how fast you can find him and shut him down to take action? >> I think so. Because of the way the technology with Suma logic scales that lets customers send more data, then they may have otherwise ordinarily sent toe like a more traditional Sam or something like that on what that does is that gives us more data to look at when we have more today to look at. We have more visibility and what's going on the customer environment. We can start delivering more value to them. Tell you hey, did you know this is going on over here something you weren't previously looking at because it scales reasonably well. That's something that we can start doing for >> her just because you have a good kind of macro point of view on multiple customers and the market. I just love to get your take on now. We used to hear all the time that, you know, the time between the breach and the knowledge of a breach was like 260 days. Whatever. And we keep hearing whatever show you out. It's coming down. It's coming down, coming down, but at the same time, pretty much every day. You know, you hear about a new breech and it's it's it's, I think everybody is going to be breached, it seems like, and it's really more of a function of How fast can you find out? You know, how quickly can you can you cut down on the damage and take the action? And I wonder if you could share your thoughts of kind of, You know, I still think some people think there's a moat strategy that you can just keep people out, and it's just it's just not, >> you know, somebody who is an attacker that's determined enough there. Well, fuck. You know, they've got enough funding. We're gonna get in and think about it like your house, right? Like, but all the doors. Put all the locks on his many doors. You want as many bars on as many windows as you want. If somebody wants it badly enough and they have enough time, they have enough planning. They have enough money, they're getting in your house, right? And so what you want to do? You want to know when they get in there so that you can react pretty quickly and so sure that like you dwell time of how long before, you know, from the time the intruder got in the environment till the time they were actually discovered. You obviously don't want that to be hundreds and hundreds of days, So it is important to figure out when they're they're what have they accessed when they're in there? So you understand what risk your date is that? Where are they In your environment? And that's the kind of thing you want to make sure that you have instrumentation to be able to see quick, because you can't. There is no silver bullet. You can't just keep the attackers out. You can't say I've prevent all these prevention mechanisms in. Nobody's gonna get in, so I don't need to worry about trying to find them once they're inside. It's just not the case. It's not really. >> And have you guys built a technological answer to social manipulation for penetration? I mean, my favorite examples are the, you know, somebody calling. You know I can't get into the company softball game. Can you please click on this or another one? I heard a Vegas. A Vegas casino was breached via that. The bomb it, er in the fish tank in the lobby. That was that was a connected thermometer so the fish wouldn't die. I mean, are we are you thinking about, you know, kind of social engineering is still a really effective way to get into these places and tools to break those kind of that access. >> Yes. Oh, social engineering. Absolutely. If you look across our customer base, the incidents and our customers deal with the number one by a long shot vector for how these companies are actually getting compromised in the first place. It's fishing, right? It's ominous. Intuit e mail. And I'm gonna convince you to click on this link, or I'm gonna convince you to open this file or I'm gonna convince you to give me a password or something like that, because at the end of the day, some of these things are pretty good and it's hard to spot a fake. It's just really difficult spot a fake if it's well tailored. A lot of the security companies and I'll give credit to a lot of the infrastructure. Providers like Google have done a really good job at trying to flash warning signs. You've never received an E mail like this from this person before. You've never received an e mail from this person with an attachment. You've never received an e mail from this person with, you know, from this domain or anything like that. They're starting to get more and more sophisticated around some of those mechanisms. But at the end of the day, social engineering fishing, that is the number one vector. It's a really hard problems. All then the security industry hasn't solved yet. >> Yeah, All right, well, let's get his job security for you. Well, Justin, thanks for taking a few minutes and really enjoyed the conversation. Thanks for having me. Alright. He's Justin. I'm Jeff. You're watching the Cube. Were Touma logic illuminate in San Francisco Hyatt Regency? Thanks for watching