Although no monitoring architecture is perfect, most monitoring issues can be traced back to avoidable gaps. Join Monalytic Vice President of Technology Scott Pross to learn how to find these problematic blind spots and mitigate “unknown” gaps before they impact valuable uptime, so teams can become proactive in resolving issues before disruptions happen.
Corey Baumgartner
On behalf of SolarWinds and Carahsoft, we would like to welcome you to today's podcast, Gaps Exist in Your Monitoring Infrastructure—Know Your Weaknesses, where Scott Pross, Vice President of Technology at Monalytic, we'll discuss what to focus on to prevent monitoring gaps in the future.
Scott Pross
Good afternoon, everybody. My name is Scott Pross. I'm a vice president of technology from Monalytic. I've been doing SolarWinds for about 16 years. And today we're gonna be discussing gap that exists in your monitoring infrastructure, know your weaknesses. So, this is something that's super important. We're going to go into some details about how do we do this? How do we identify them? What do we do when we do find them, and you know, even political hurdles that we have to work through in order to get around these. So, without too much fanfare, let's go ahead and get started. So just a little bit about myself. As I mentioned, I've been doing SolarWinds for about 16 years, I learned SolarWinds, when I had to build up a NOC from the ground up for a billion-dollar company, we have a 99.99% customer facing SLA that gave me four minutes and 37 seconds of downtime a month for 33,000 devices. So, you might imagine get pretty good with it. And a lot of those tips and tricks on those struggles that I learned when I was running that have really helped me in my professional career with Monalytic and SolarWinds. It's really been able to show me where, you know, my weaknesses were as a NOC engineer, and a NOC manager. And you know how I can turn those in those gaps that I hired him not only my knowledge, but also my marine environment into something now that was resolved. And not only works for me, but now actually works in my customers as well. So, as we go through today, just know that, you know, many of these tips and tricks are things that are just happened to me in the real world. And it's how we got around a lot of these problems that we saw, as we were seeing them at different points. So, let's define what it is we're talking about here. What actually is a monitoring? Yep. So, monitoring gap is a known or unknown unknown, it's important to know that there's two kinds of monitoring gaps here, area in your monitoring infrastructure, that doesn't allow you to know the status changes or failures in your infrastructure. So that can be not, don't just think about devices here, when we're thinking about this. Think of interfaces, volumes, think of application, think of network bandwidth, all of those little things. Now, we all know, we can't cover everything, we were very much aware that, you know, we're already drinking from the firehose, when it comes to monitoring that already exists for each and every one of us the amount of information that solar wind is taking it. And then we have to consume as a NOC engineer, or an infrastructure engineer, or as directors that are that are responsible for the environment is huge. So, the question is, how do we put that leave all that information out. So, we don't have any gaps in our monitoring, not only the information that we're bringing in, but the but also understand what information that we're not seeing? What are we not aware of? So, the second part, you know, is a gap can cause an engineering monitoring team to miss a failure and not identify the cause of the failure. You know, both of those are significant. And they're actually separate, even though people think they're the same. The first one is, you missed the failure. Okay. And now a customer, for example, where a user is calling you up to say, I can't do XYZ, that always dies. You know, whenever you call Comcast, let's say, because your internet goes down, you as a customer always get a better feeling. It's not a great feeling. But it's a better feeling. When you call Comcast, to tell them that your internet's not working, and they go, we know about it. You know, there's nothing worse than having a customer tell you that you have a problem that you didn't know about. So same thing there, you know, it actually makes the customer Okay, they're on a good look, they're still having an outage, they're still having a problem, but at least it makes them feel better, that they're aware that, you know, the company is aware of it, the IT team is aware of the issue and that they're working on it. So, you know, identifying it is part of that that process, okay? The second piece of that, though, is not identifying the cause of the failure. Sometimes these things go away, or we do something like reboot a server, that would fix the problem. But we don't know what the actual cause of that problem was because we weren't monitoring enough where the right places. I don't shouldn't actually see it now. budgeting, you know, I want to make sure that I'm monitoring very specific areas that I know are important to me, then monitoring everything, and not know what I don't know. So super important to when you're thinking about this stuff to understand that you can have a failure, but still not even after the failure happens, you will not understand what caused the failure, you may know what fix the failure, but you may not know what caused it. And that is due to a gap in monitoring. So, two separate ideas, both are extremely important to understand that you need to have both, you need to be able to see when a failure happens. But you also have to understand what caused that failure. So, we're going to talk a little bit more about that as well. And if you don't know where your monitoring gap exists, you won't know the risk to the, to the business into the customers. This is extremely important, especially you know, it's less important for the everyday IT person, the eye, every eye, IT person is just really worrying about keeping everything up and running. But your executive to your senior leadership team, the thing that keeps them up at night are what are the risks to my business? What are the risks of my business work through with to my customers right now, you know, they're not worried about their IT environment, because they trust you guys? They trust all of us, you know, to do our job every day. But they are worried of what are my risks. And to be honest, most of them, they do they know that you're monitoring the environment, they may not be actually aware of how you're doing it. But they're aware that it's an important part of the system of the network. And that it's something that's super important for them to mitigate their risk as a business owner. So when you're thinking about this, whether you're a DoD or you're in the Fed, or you're in education, know that even though your senior management who are non-technical people, you know, they care about this, because they understand that this is about the major risks to their business, if their users can't do things, if their customers can't do things, you know, in DoD are fed up or other agencies that are relying on your information, they can't access it for what they need to do. You know, that's a huge problem. So, you have to be aware of your gaps in monitoring to keep your customers or your other sister agencies, you know, have that availability for the data they need to do their job. So, all of that is part of what we're going to really be discussing quite a bit today. So how do you get rid of gaps? Well, the truth is, you don't. And that's an honest look, and understanding my monitoring, you don't actually ever get rid of gaps, you mitigate your gaps, you can make them smaller, you can become aware of them, you can remediate that. But if you think you're going to put a monitoring system in many and get rid of all of your gaps. That's not reasonable. And it's something I always have a talk with those business executives about that our job is to mitigate the monitoring gaps and failures in our environment, we don't eliminate, if we could eliminate, we would mean high availability, if we could eliminate, we wouldn't meet disaster recovery. So those things are mitigation factors, they're not there to eliminate a failure. They just mitigate them again. So, when you mitigate them, you're going to mitigate them as much as you can. Now, we're going to talk about these three in depth. But the three pieces to getting rid of your gaps are identifying the gap. Okay? Being able to say, hey, wait a minute, I actually am missing something in my monitoring infrastructure that I can't see. Then you need to evaluate it. What is it that I need to do to it's important, it's something I have to watch, do people care about this? You know that kind of stuff. But we're going to talk a little bit more in depth about that. And then finally, remediation, and narrow mediation. That's a slippery slope. Because, you know, a lot of times we're talking budget, we're talking definitely resources and time that many of us don't already have available because we're all already all pre stretched, prepared, to be honest. So, we're talking all of those different things. And we want to be able to make sure that you know, when we remediate them that we do a good job of remediating but there's other steps remediating the doesn't always mean you're getting rid of the gap. Again, the real goal here is to mitigate. If you can remediate, that's great, but we may have to fall back on mitigating them. So, identifying modern gaps, we're going to talk about this. So, the first thing I always tell people is when they say, how do we do? How do we identify our monitoring gaps? The first thing is break them up by the business services. And this is really difficult for IT teams and agencies. And the reason is because we know about databases, and we know about Active Directory, and we know about, you know, our Linux systems and our network switches and our configurations. But we don't always know what business service or what agency service are they associated with, you know, when I have something plugged into ERPs, you know, five, I may know that it's a server plug in, but do I know what that server is actually doing? You know, I might even know that the DB server, I may be very much aware that this is a database server that's running a very important database. And I might even know that it's a large database. But do I know what that database is actually fulfilling for my end user. So, when we break it up by business service, it's going to start to really help out. So, when I think business terms, I mean, let's say that this particular database, that's part of your web portal, and your web portal that your users logged into, accesses this database to pull up information about your customers’ accounts. By knowing that and identifying what you're watching on that database and what you're not watching on a database. By identifying a business service, you're now going to be able to understand more cohesively, you know, is this something important that I need to watch? You know, is this something that doesn't have redundancy, for example, is that a single point of failure, maybe not a cluster database, you know, so you want to be aware of, if you start off with a business services, and the great thing is, you know, all of your agency that all of your Fiammetta, they love to talk about their business services, you know, what are they responsible for? What part of the business or agency are you actually responsible for, they'll talk about that all day long? And once you break up all those pieces that make up their business, and their job responsibility, now you go to the backend, you say, Okay, let's now break that down and say, Okay, let's translate this into engineering, where he mentioned that he's responsible for the web portal, he's talking about this server, he's talking about this application, he's talking about this database, he's talking about this, the network piece of the title, talking about this network segment, the subnet, even now you have an understanding of not only that, the importance of that business service, but what it actually represents, you know, on an eye on the it level, and now you're going to be able to go back if you need to, to your manager and say, Okay, this is important. You've told me all about this, this wonderful web portal that our agency relies on, these are the pieces that are relied on, and I can't see x y&z and they can help you just how to determine whether or not is this a big risk. So, we're gonna get to that in the evaluation. So, I put something, again, that you're very interesting here to hear about is, you know, identify it by the business service. And not only that, now you're bringing non-IT people into this, into this, they're getting buy in from them, when you get buy in from them from when, for identifying it, it's gonna further give you buy in, when you're evaluating it. And more important, when you need the budget to remediate it. You know, if you start them from the beginning of the process, they're not surprise when you come to them at the end and say, I need a budget for this, because now they understood the entire process that you brought them through. So, if you're working, and you have NPM, and you have NTA, and all the other SolarWinds node modules, but you're not wanting NCM, we are backing up your configs. And you're identifying the big changes and those kinds of things. You're bringing them in at the beginning and say, okay, this is the information, and we don't stay. And then when you sit down with them, you say, Listen, when we need to push out new context to all of these devices, I can't do it because I don't have an easy way of doing it. It's going to take us, you know, two months to do that. Is that a reasonable amount of time? Or do we need a tool that's going to allow us to do that quickly. So, it's, again, it's mitigating and remediating the problem, but because you brought them in from the beginning, they're on board to the entire process. And generally, it's easier to get sign off and you're not surprising them, you know, they can start including that in their budgets, which were all of us here. Do you come back to them with a non-budgeted line item? And everybody freaks out? Why didn't I know about this, you start to include them in the conversation early, at a very different conversation, because now they're adding it into their budget, and they can plan for it as well. So, the second idea is, review what areas of the network are not covered by Orion and other souls. And they, okay, again, don't take this as a negative for you and your team is, okay, they have things that you can't see. And by the way, a lot of times when you're getting information along other agencies, it's a black box, you know, you don't know what that Box does, or what's coming in on that pipe, all you know, is that it comes in on that pipe, and you're able to access it. So, you have to accept that we're not going to have a tool for everything, you know, like, you want to be able to review what isn't covered and put that list together. You know, and, you know, again, this isn't a strike against you with a team, when you're adding things there, you want to be realistic with it, and you want to let your manager know, these are the things that I cannot see right now. These are the things that keep me up at night. And then when you translate them into business services, they're going to be the things that keep your senior management up at night. So, because they don't understand it, well, you know, when you say I can't see interface, 14, they don't really care about that. But when you tell them that, I can't see interface 14, which is responsible for our customers, web portal, that our agency utilizes and our customers to log into, that tends to mean something to them. Because they may be like, well, we have been our customers, and agency and we'll get to that every single day. And you know, like Yeah, and I don't know what's going on with it. So again, translating between this is the it gap into this is the business service gap that I'm seeing. And then finally, we view your previous outages to determine what was missed. This is actually usually pretty simple. When you have an outage, you're gonna go you're gonna say, okay, what were our outages? And what was this something that I could have seen? You know, and I tell people, this is going to be part of your postmortem. So, when you have, you know, instead while you're going through this process, feel free when you're doing that reason for outage, or the postmortem to say, okay, what did we see? Or more importantly, what didn't we see? What did Orion Miss? What did my other tools miss, because let's be honest, we're not all just using SolarWinds. And that's okay. There are other great tools out there as well. But I need to make sure that we are at least getting a complete picture of the network. And when we do that, you know, we want to make sure that if SolarWinds isn't covering it, at least it's covered somewhere else. You know, so make sure you're getting that complete picture from your previous outages. But a great way to do that. If you're new, that's okay. Chances are, somebody has documented your previous outages. Somebody has put something together, or just talk to the engineers, because let's be honest, everybody loves a good war story. You know, you used to say, hey, remember back last summer, when the old database went down? By talked it up? I know what happened? What did it do? You know, what were the problems? That kind of epilation. So, again, really useful. So that's identifying. Let's take a look at the next one. Evaluating. As I said, many things come into play when you're evaluating the gaps. This is a huge piece of this isn't really super important to bring in your senior management, you want them to help you evaluate it. Because really, at the end of the day, they are going to make the decision on is this a problem for my business? Or not? Do I need to see this information or not? Usually, they're going to trust their engineers to do that. But it helps give ownership over to them if you start let them know, guys, I need to have understand how my bandwidth is being utilized, and TA and following my net flows and being able to see what my users are doing and how data is coming across my network and who's talking to who is important being you can check out and tell them and explain to them why. Now they have ownership in this. So, there's a bandwidth utilization problem. You know, they're going to take ownership and take responsibility when you came to them. And you told him that I'm not telling you that you're covering yourself in any way. But what I am saying is you're bringing that into the conversation and letting them be part of the solution. Now, as we all know, doesn't mean there's gonna be money here, but there might be other. I've already talked about this on the next page on remediation to other ideas that we can do, to be able to get the information we need. till the budget becomes available. So, evaluating is really important for that. So, is the bridge for monitoring gap acceptable? And the answer here is going to be yes, sometimes, sometimes we are going to accept that a modern gap exists, and it is acceptable, the cost might be an issue, the importance of the device or the application that's wrong, might be an issue. But look, if you have an application that's used by a dozen people, you know, once a year, you may not be monitoring it as much, you know, you might not want to want to spend your money there. And that's understandable. So, definitely, you know, looking at the risk of it, is it, you're gonna have a risk, but is it acceptable to you? You know, what, at what point do you say, wait a minute, this is too painful. It's either going to be from a financial cost, or resource cost of time, or a customer stack cost. And when I say customers, I'm not just talking about having an outside customer, I'm talking about our users, because our users, our customers, many times is their budget to address the monitoring gap. You know, he talked money, but let's be honest, it's an it's a reality for all of us. We only have a certain amount of money. And we don't know how do we remediate without money, but it's actually going to be something that we're going to go into discuss. And I have made some crazy, throwing together solutions to remediate a problem, and I'm sure all of us have. So, to be able to now remediate but at least monitor a problem, because I didn't have money to do it the right way. And duck would talk about that story, you know, in a few minutes, you know, does the money exist? And, you know, is that how we want to spend our money. So, again, great discussion to have with your, with your business and your agency leaders, they'll be very, very happy that they're, that you're having this proactive discussion. And then are there resources and time to resolve watering gaps. So sometimes we have all the money we need, but we don't have the time, we don't have the personnel. And we see this a lot, actually, with Monalytic people will call us and say, hey, you know, we could do the work. We know, SolarWinds, we know how to how to do it. But I just don't have the manpower. I don't you know, my team is straight out right now. And can you come in and do this for us? Absolutely, we kept more than happy to, they're not calling us in for any other reasons. But if you don't have the resources to actually build this out, and the time to build it out, it's probably not going to happen. So again, this is what you're waiting, okay, time and resources against, you know, the importance and priority of filling in that monitoring gap, you have to have both of those things, and they've got to one's gonna outweigh other the other every time and then somebody's got to make a decision on which way you're going to move. But this is a reason why professional services exist, to be honest, in not only in solar wind everywhere, like we all, we're all smart, we can all do our jobs, you know, we're all really good at what we do for the most part. You know, at the same time, sometimes we just don't have the time, we just have other projects and other things that are priorities. So, we're gonna bring in professional services, they're gonna give us those best practices, they're gonna put it in, and I don't have to spend months learning best practices, and then doing it myself, when I can hire somebody to do it quicker. So, it's just evaluating are the resources available? If they're not, do we need professional services to come in to assist us with this? And, you know, if I can do it myself, and I have time? You know, that's great. We'll put that into the evaluation as well. So, this is the big one. This is a big discussion, remediating the gaps, and everybody wants to know, how do we remediate these gaps, you know, and when you talk about remediation, we're going to talk about mitigating them as well. But you really want to think about, okay, what does remediation mean? Does it mean being able to see every detail? What level of insight do I need? Do I just need up down? Because up down sometimes is enough for certain things? Or do I need to be able to see every granular thing that this is doing now, sometimes, these monitoring gaps are going to be dictated to you either remediation is going to be dictated to you by compliance, whether you're an educational facility, where you're a DoD facility, they're going to tell you that this is what you have to monitor. And maybe you got to know, you know, and they say, hey, you should have to collect the logs. You don't have to actually utilize them, but it might be helpful to actually utilize those logs and pull that information you're cooking in anyway. So, utilize them for your actual, you know, remaining problems that come Mr. At this point, you're really at a point where you're going to accept the risk of the gap or you're going to remediate the problem. And this is a said, if you brought your senior management through this discussion, there's no surprises here. Okay, that's the great thing, if you haven't joined, and step two, there's probably no surprise, if you haven't joined here, they're going to say to you, why is this the first-time hearing about it, it can't be that big of a problem. Nobody's ever mentioned it to me before, you're gonna hear that a lot. Why? You know, this is the first time I'm hearing anything about this new product or this new tool that you need. Whereas if you started from the beginning, they've been hearing about it probably for a couple of months, they've experienced a little bit of pain, probably with it as well, they they've gone through the evaluation process with you. And now they're ready to actually have a conversation about okay, what is remediation? You know, how do we do that, because now, you're, you're completely outside of their experience level, when you talk to your executives or your command and all this. Now, it's like, I need to trust my engineers to tell me what this means. Because, yeah, I can help identify a little bit based on business service. And I gotta say, Yeah, I can actually help them evaluate whether or not this is important, that I'm good at, again, based on business services, they have no idea how to remediate that gap. They don't understand what tools are needed; they don't understand if we already have the only tool that's needed. They don't understand the cost of those tools. You This is where your expertise actually becomes more important. Because now, they are fully relying on you and your team to determine what this remediation strategy is going to look like. And this is what they pay for they pay, they pay us to make these decisions, you know, whether it's a DoD agency, Educational Agency, or you're a contractor for you know, a federal customer, this is what they want that consultative piece. That's why they want you there. So, you know, really great place for us to be kind of my credit monitoring tools provide the necessary monitoring. Well, that's the first place you want to look, sometimes we have monitoring gaps, just because we haven't set up our monitoring tools correctly. Let's be honest, when I look at NCM, SolarWinds, I always look at that, you know, 90% of my customers are using it to backup their environment, they all do that. And I always say if you're only using NCM, to backup your devices, that's kind of like owning a Lamborghini and using it to drive across the street to your neighbor's house. Yeah, you'll get there, and you'll get your own style, you'll look good doing it. But that's not really what it's used for. If you're missing out on the compliance piece. And on the change management piece, and being able to the real time change detection, if you're not using those features, events, the end, you're using a very small piece of it. So, when you've identified your gaps, go back through your tools, even if you feel like you know that tool Well, keep in mind, all of these tools, especially SolarWinds, are getting updated constantly, with the latest and greatest features and new things that are coming out and new ideas that people have had. And take a look at it. The other thing I'm going to tell you to do is look at black typing where you're trying to monitor with, go to the flat black product for you don't say, hey, you know, I'm trying to monitor this, can this module do it? You know, utilize that, because it's a great tool to have. But, you know, don't overlook the fact that this may not have a budgetary requirement as much as it has a time, or a resource requirement tied to it. Do we need to purchase additional modules? Sometimes the answer is just gonna be yes. Okay. There are times when you're going to have to purchase an additional module, that if you want to be able to see how your systems are using the bandwidth, you're going to just need to purchase it and really make it happen so that you can see what's going on now that said, and I told you earlier, I have seen things and one of the great things about SolarWinds is how customizable it is. You can do anything with it doesn't mean you should, but you can. I actually had a customer who had only purchased NCM already NPM. And it was a standalone app, but they were insisting on getting IP SLA information from their devices into NPM. Yeah, is that possible? Absolutely. You can go and you can build custom polls and pull out those i o ID and pull that information and put them into charts and reports and dashboards. Should you, do it? Probably not a cost him a ton of money just to pay me to configure that As I make that happen, it didn't look nearly as good as, as what you know, the solar winds into the MQM module would do. And, you know, it was good to consider, you know, when you do it with the MQM, it's consistent. If you can, if you add something, if you're easy to add, you create the right in there. So, all of those things, you know, it's just a question of, just because you can doesn't mean you should, you know, in this case, so, most of the time, you can find a workaround, if you have somewhat of the right kind of module to pull that information in. But be aware of these can be time killers, they can be absolutely a real difficult time to maintain, and pass on. And, you know, we don't like to think about, well, what about when I lead is somebody else going to take care of this, you know, we don't want to make things even worse for people. The goal is to keep you the company in a good place. And the best way of doing that is utilizing the right tool to fill these gaps. So, a lot of times you do, but if you if you have questions about which module, we'll do it, because you, you know, your gap is, but you're not sure which module will fall under that. This is where so it shines, because it's got so many modules to choose from, you know, there's just so many different modules that we can sit down with you, your accountant on, you can pull in there, the engineers and say this is what we see from other agencies. This is what we see from other institutions, from other federal agencies. And this is what they're doing. And this is what we've done in the past, we all have that experience. So, a great way of doing things. When moving. Okay, let's also talk about moving to the hybrid calzone model. So, this is opera, you know, and for those of you that don't know, so it is moving to what they call HCl, this hybrid cloud observability. And what this is, in nutshell, in is a bundle of modules, where you're basically going to right now, paper on a permanent basis, and you're going to get these bundles, okay? And the great thing about this is, if you don't want one of the, the real positives of this model, is even our cart can be easier, where you can grab scrap, NPM and NPM. You know, you're gonna have Monterey gaps, now you're gonna get all the information based on your node count. And it's a simplified licensing model. Now, that your way of doing it, you know, down the road, when, so when you start doing more and more AI ops, they're going to be able to see more of your network, they're going to be able to see more things inside of NPM, NPM and V and QM, because now you moved on to this observability model. And because of that, AI ops will come in and start helping you with remediations. As far as, okay, I'm seeing this over here in in Blue Bay, I'm seeing this over here in Group B, I'm seeing this over here in Group C, how are these all related and running solo and help you make that determination. So having that moving to that ACO model is actually very helpful. From our side, because it's a new, it's a new licensing model. It's no longer a perpetual license. So, it's subscription based. And as you grow, it can grow as well. And, more importantly, as you're moving to that, as you're moving your network to that, you know, particular model. Now you just fill in your gaps. And now it's just a question of you having the time to actually do that. But now, you know, you're going to have the tools to do it. Because the tools are bundled together. So, something you definitely want to take a look at. If you have a lot of gaps in your monitoring. This is where you want to head if you're if you're hearing, you know this discussion going, oh, this is totally me, I've got to do something about this. This is a great place to start. It's almost letting you say, okay, I'm going to go out, I'm going to do this on a per node basis, I'm going to get everything I need. And then I can slowly work through my gaps one by one, I'll set a priority for that, and go through each one and fill them in. So, talk to your, your account manager, if you need to have more discussions with the engineering team over at SolarWinds. We're all moving in this direction. It's a great place for us to go we're really excited about it. The last one is super important. And it's one that we don't like to do. We want to document any known gaps. So, all the current GDP members are aware of the known risk, you know, this is painful to do. It's because it's almost like you're accepting defeat. But you're not. What you're doing. Is your basically waiting history, your writing. This is what we did. This is what we saw. This is why we take action, right or wrong and This is where we're where you are right now. And what this is going to do is this is going to allow, you know, either current team members, as you move up through promotions and you become less available, you know, if you were, maybe you were a junior, and you know, when you started and you've just become a director, you know, you don't need them coming to you and saying, you know, we can't see this lie, if you really documented modern gaps document, which by the way, I have placed, and it was readily available to the entire operations team, I want everybody to recognize these gaps. And I didn't hide it, I put it out there because I wanted to be able to, to utilize it to say, okay, to my business executives, this is what keeps me up at night, my monitoring gaps as a mock manager, these are what this is what concerns me that I won't hit my 99.99% Customer SLA, and I won't make my bonus, this isn't a document. So, when they ask for my Christmas list, it's going to be something over that document that will clear out one of those gaps that he that keeps me up at night. So, you know, and I joke around the day that I got v man in my infrastructure, I was absolutely thrilled, because it filled in a huge gap for me, you know, that allowed me to see so much more of what was going on, you know, in my infrastructure. So it was like Christmas, because it was such a powerful tool. But it gave me so much information as well, as well as being able to forecast what I was going to need in the future. So don't be afraid to document these things as well. All right. Well, I do want to thank everybody for hopping on this was a great topic. It's something that we don't talk about enough, we've got to talk about it even more so because we have to be able to identify them. If you guys have questions about what modules can help with your gaps, you have spent some time you know, identifying, reach out to SolarWinds reach out to your account managers, we're gonna be able to hear you every step of the way. So let us know we can do we're more than willing to help you guys out. But I really appreciate everybody's time today. If you do have any other questions, reach out and go back in now let's see we can identify, evaluate and remediate some of those gaps.
Corey Baumgartner
Thanks for listening. If you'd like more information on how Carahsoft or SolarWinds can assist your organization, please visit www.carahsoft.com or email us at SWMarketing@carahsoft.com. Thanks again for listening and have a great day.