IT professionals are tasked with keeping networks up and running in order to avoid business-critical interruptions. Obviously the first safeguard to avoiding network nightmares is to install a solution to keep your network healthy and provide insight into the behavior of your systems. If you’ve done this, you’re on the right track.
But using the software doesn’t mean you’re using it at full strength.
Monitor to the Max in Five Steps
If you’re wondering “What else should I be doing to keep my network healthy?”, fortunately there are many ways to maximize your network monitoring solution’s efficiency and streamline its implementation.
In this presentation, Technical Solutions Consultant Kevin Jackson walks you through vital steps to streamline your network monitoring process, including:
- Setting network performance levels
- Performing network device discovery
- Knowing exactly which metrics to monitor
Make sure you’ve left no stone unturned. Dig in and uncover the strength of your software – for a healthier network.
Janine: Hello, everyone, and welcome to today's presentation. My name is Janine Donnelly. I am the Manager of Webinars for IBM Systems Magazine, and I will be the moderator for today's event. Today's webinar "Are You Getting the Most out of Your Network Monitoring Solution?" is sponsored by Intermapper, a division of HelpSystems. Our featured speaker today is Kevin Jackson.
Kevin is a Technical Solutions Consultant for Intermapper. Prior to joining HelpSystems, Kevin was a design engineer and business analyst with Richard Fleischman & Associates for seven years. Kevin has his Bachelor of Science in Computer Science and has a Master's in Technology Management. Today, Kevin will walk you through vital steps you can take to streamline your network monitoring process.
With our introduction complete, Kevin, I will turn the presentation over to you.
Kevin: Thank you, Janine. Much appreciate that wonderful introduction, and welcome. Welcome to today's webinar and thank you for joining. Again, we definitely appreciate your time. So hopefully, doing this presentation I am able to give you some insights into just network monitoring generally, and then give you some feedback and some understanding on how you can effectively make your monitoring situation a little better.
So this is my face. This is what I look like. Again, thank you for joining. So what I want to do first before we get into the presentation, I've added a polling question just to get some feedback from audience and see what some of the pain points you guys are experiencing. So the question that I wanted to pose was, what was the most recent cause of an outage on your network?
And it looks like we're getting some really good feedback. So we'll go through and we'll take a look at some of these options, some of these situations, and some of the causes. And from what I'm looking at based on the polling result, it looks like human error is probably the one largest cause for network outage. And not surprising. It is a big reason for a lot of outages.
So our agenda today, we'll go through, again, understanding what causes network outages. So the polling questions lead into this agenda. We want to see what things cause network outages we can talk about. And then there's a few examples of the financial impact of network outages on business operations.
So there's a few examples of some large brands that you might recognize that have experienced some of these issues in the past few years. We'll also go and take a look at network monitoring in five steps, so I wanted to... I know there's a lot of steps out there in terms of network monitoring in general, but these are five steps that I think that can really help you get a handle on monitoring your environment. And then talk about how network monitoring can improve your network efficiency and performance. Then we'll go online. We'll take a quick look at a live demo of the Intermapper product, and then we'll go to the Q&A session and take some questions.
So again, as an IT professional, our job is to ensure that the technology we're responsible for is working the way we've intended it to. So sometimes network outages are inevitable. But what if we can preempt it? What if we can have a solution that sits in front of a deck and tell us when things are about to happen?
So again, monitoring devices and setting thresholds can help you with the time that you need to mitigate these potential risks. And again, you don't want these potential risks, these small problems to become large business critical issues.
So in terms of just outages in general, understanding what can cause an outage. As we talked about earlier, human error is one of the biggest proponents of causing a network outage that's been recorded. Again, when you start playing around with different things and moving things around, we are imperfect people. We do different things and human error is always a concern. So again, you want to be able to see those changes and see how those changes can have a positive or negative impact on your network.
Environmental factors are right up there, and a lot of times, folks tend to neglect these factors. And keep in mind that if you're not currently monitoring your HVAC, your power, using environmental sensors and things of that nature, you're currently putting yourself at risk. The bottom line is, and a lot of folks neglect this part of their network infrastructure, but keep in mind that if you have environmental issues, if your power goes down, if your HVAC or AC unit breaks down, your devices will be impacted. So again, very important that you consider monitoring all aspects of your wiring closet, your network room, your data center.
Configuration issues. Again, this leads into the human element, the human error. Configuration issues are oftentimes a pretty big proponent of performance problems. Again, not properly configuring your devices, not understanding how those devices are supposed to be configured and behave, not understanding the optimal performance level of those devices are things that I think can provide you issues when you're configuring those devices. So things to be aware of as well.
And then last but not least, lack of visibility. Most people think what you can't see can't hurt you. You got to understand that visibility is very important into understanding what goes on into your network, and it helps you prevent and determine those issues before they cause outages. So what we're providing with the Intermapper solution is all these things: the ability to monitor your devices, the ability to have flexibility in terms of what kind of devices you can monitor and, in terms of configuration, help you validate your configuration and then provide you with a visual representation.
So the next couple of slides I want to go through is some of the larger institutions that we are very familiar with that have, in the past, have had some financial impact based on situations or issues pertaining to their network environment. So the first is Amazon, and we're all very familiar with Amazon. A few years ago, Amazon had a network configuration issue that brought down one of their data stores. So the data for their clients was unavailable.
Now considering the fact that Amazon hosts hundreds of thousands of customers and customers' data, consider the cost associated with an error of that nature. Ten-day credit to all their users that was affected. So again, result, a lot of money lost based on simple configuration issue or the fact that they weren't monitoring that data stored properly.
RIM, Blackberry. Now this is a time when Blackberry was in stiff competition with the other technology like the Android technology, the iPhone technology. So this is a time, a critical time within the Blackberry marketplace, and competition race where they needed to be sound. They needed to provide a reliable and stable product.
Issue: their core switch was basically a hardware failure on their core switch, which affected their Blackberry enterprise server. So again, millions of users running on that server worldwide were affected for at least a day. Meaning, that they had no contingency plan, no backup situation in place to mitigate this risk. Again, result, a lot of money lost and a big damper on their brand in the marketplace.
So instead of being ahead of the game, they took two steps backward in that competition race. Very critical issue. Very critical loss there.
Navitaire is a subsidiary of Virgin Blue. So what they do is they actually do the reservations and booking for the Virgin Blue Airlines. So this is a small company that's looking to make an impact in the marketplace. What they had, their cause, their outage—so their booking systems went down. So again, a company that their sole responsibility is to book flights and reservations for their parent company, Virgin Blue, their booking systems go down, hardware failure on their servers, outage. Big cost here.
So as a company that's looking to grow and get larger and make a name for themselves, what happens is this is a very critical outage that they sustained and it cost them $20 million in compensation to Virgin Blue. So they had to pay Virgin Blue $20 million because of that outage, because they didn't have anything in place to monitor their systems properly and effectively, and they also didn't have a contingency, a backup plan in place as well. Very costly error there.
And last but not least, Bloomberg. We're all familiar with Bloomberg. Global company, large company. So their issue was they had a hardware and software failure in their network. So their terminals, their Bloomberg terminals that they've deployed and sold to their end users, to their end customers, traders, money managers, financial institutions—so they had issues connecting to those terminals.
Again, very big issue, very big situation. So now you're looking at your traders who are responsible for managing millions and millions of dollars. Instead of having that one-click terminal that they can use to make their real-time trades, now they have to get on the phone with their brokers, call in, and wait on the phone or waste that extra ten seconds or 20 seconds that is vital to them making that trade that could be the difference between them making millions of dollars or losing money.
So it might not be a huge impact to the end institution and to Bloomberg, but to the users, it's just giving them that extra work that they don't need and affecting their day-to-day operation. So again, you're looking at 325 subscribers that utilize the Bloomberg terminals at $2,000 a pop or at least $2,000 a pop for one of these terminals. That's a lot of money in revenue that Bloomberg is making.
So to have this type of outage can, again, put a damper on their brand and also have them lose faith and lose money. So again, very important that you have the critical solution in place, a network monitoring solution in place that is working for you, that is providing you with the details and the operation that you require to maintain an efficient and proficient infrastructure.
So network monitoring in five steps. These are my five key steps, I think, that would be very helpful in terms of streamlining your network monitoring process. First and foremost, you want to be able to determine your network performance levels. And what I mean by that is understanding how your devices work, understanding what makes this device perform at an optimal level, even if you have to look and see how the industry views these devices in terms of how they should be configured, how they should be running, how they should be connected. So that's the first and foremost: having that understanding of the performance levels of your devices.
Then having a solution that can help you provide that and perform a network discovery. Oftentimes, we don't necessarily know what devices are running on our infrastructure. There's times where we're suffering performance issues or there's potential bottlenecks. And then we do our due diligence to realize that someone has a hub plugged into a network somewhere that's killing your network and slowing down your performance.
So what you can do is, using the auto-discovery, you can go out there and do a full auto-discovery of all the devices that are running on your network. When new devices are added to your network, you can do that auto-discovery and basically capture those new devices and new information as well. Excuse me. So again, ability to provide that network discovery I think is key to understanding how your performance is going and what devices are running on your infrastructure if you don't have that information up front.
And then very important. You want to determine what information is the most critical to monitor. Listen, we can't monitor everything. There's so many data metrics out there specific to devices. It would be a task to be able to monitor all this information. But what we can do is we can figure out what data is the most critical.
For instance, I have a switch, my core switch. I want to make sure that I monitor the traffic, the bandwidth traffic, the utilization traffic on my core links. So those are information that are critical to my business, that are critical to the performance of my infrastructure. So you have to identify those key metrics, those key information that you want to monitor.
SNMP, Simple Network Management Protocol—very flexible, widely utilized, allows you to do a lot of different things, ways that you can interrogate devices and capture non-standard information. Obviously you want to monitor up-down status and availability of your devices. But you also want to get a little bit more information about your devices. Non-standard information.
For instance, you want to be able to monitor CPU utilizations, storage utilization, alarm points. Again, using SNMP, you can monitor your UPS. You can monitor your HVAC. You can monitor your environmental sensors. So these devices now are being built with SNMP technology so it allows you flexibility in terms of what you can monitor.
And then utilizing the flows technology: understanding how your bandwidth is being utilized at the edge of your network gives you a good understanding of how to properly enforce certain criterion. If you look into monitor inbound, outbound traffic, you are looking to monitor specific applications, you want a product that can tell you how those applications are being used, by whom those applications are being used, how much bandwidth is utilized by your host store or your users.
And then the nice thing about this is you can take that information and then you can do your due diligence, whether you need to provide additional resources, components to augment your situation, or if you need to improve on security.
And then, again, once all these information has been sought out and processed, last but not least, using exception-based alerting and notification. So the bottom line is this: once you have your infrastructure where you need it, now you want to be told when those devices do not perform the way they're supposed to. So you want a software that can alert by exception, lets you know when things are wrong. Not when things are good, because when things are good, you don't need to be told about it, but you want to be told when things are wrong or when things are about to be wrong or about to go in some kind of fault.
So these are the five steps that you can utilize to streamline your network monitoring solution. So you want a solution that can help you utilize these five steps.
So how can network monitoring help you improve network efficiency and performance? So going, piggybacking on the previous slide, one of the things I think, and I mentioned this earlier about visibility, visibility is I think a key component in just giving you the ability to monitor your devices and see how things are happening and be proactive with your monitoring capabilities.
So again, real-time monitoring solutions. So you want to be able to monitor your devices real time. Not five-minute intervals, not 10-minute intervals. Near real-time where you can get an accurate portrayal of how that device is behaving. You can get accurate information, up-to-date information of those devices. So you know real-time how those devices are behaving.
So you want to be able to leverage the right technology. Again, live map of your network, the visibility, the live visualization so you can actually see all your devices at a glance. You can see your devices as they go through different steps and changes. So you have that visual representation.
Auto-discovery. Again, the ability to auto-discovery on your infrastructure so you have a good understanding of all the devices that's running on your infrastructure new, old.
Flow-based technology. As I mentioned previously, you want the ability to manage and be able to monitor your bandwidth and see who's using your bandwidth and how your bandwidth is being utilized. And the nice thing about that as well is you don't necessarily need to utilize it for security measure, but it can be part of a tiered security approach. So again, if you do have some intrusion prevention or intrusion detection solution in place or if you don't have that scenario in place, at least a flow-based technology can give you a little bit of understanding, an insight into how that bandwidth is being used.
And then you can take that information and then do a little bit of more, deeper discovery or a little more due diligence. So you can take it and you can shut down ports or shut down sites or whatever you need to do. But at least you have that information at your fingertips.
Layer 2 mapping. So the ability to see the interconnects of your infrastructure. So this goes with the live mapping, just a different way of showing your infrastructure, so you can see a logical layer 3 diagram. And hopefully you can see a logical layer 3 mapping as well, where you can see the interconnects of your layer to infrastructure if that's what you're running. You can see the switch to switch connections or you can see the endpoints connected to your layer 2 switches. So again, really good information there.
Log data analysis. If you're doing some data analysis, being able to capture logs and use the logs to analyze the data and troubleshoot potential issues. Intermapper has an integration with Splunk. So we do have the ability to ship Splunk, to Splunk our logs. And we also have a mapping integration with Splunk as well. So if you do have Splunk Enterprise scenario situation that you're running, we can have that integration piece that ships our logs to Splunk, and also you can see the maps and all the devices and their behaviors within your Splunk Enterprise situation as well.
So a nice solution there where you can actually do your data analysis. You can do trend analysis using the Splunk server and you can also do your troubleshooting on possible issues.
And as I mentioned earlier, exception-based alerting, we have a number of different mechanisms that allows you to do some alerting and notifying: email notification, text messages, pager notification, sounds, command-line notifications. So a lot of different ways that you can be notified. And also we utilize an API integration piece. So if you have a situation like a pager duty or some kind of web-based notification software that has an API, we can look to integrate that within the product as well. So a lot of options, a lot of features that the InterMapper software can actually provide for you.
And then optimize devices to support those current recommended performance levels. Making sure that your devices are running at optimal level (a) or alleviate a lot of the performance issues. But the same time, give you a good understanding, give you a good foundation in terms of making sure that those devices are performing the way they're supposed to and making your network a little bit more efficient.
So in terms of why we feel Intermapper is the right solution. The one thing about Intermapper is, Intermapper solution is an easy solution to understand, to deploy, to manage. We are multi-platform meaning that we can basically run our application on all the major operating systems out there. So if you're running Windows, Linux, Mac, we can pretty much support our applications on all those operating systems. It's a very easy installation, very easy product to manage. Not a lot of built-in and clunky modules within the product.
The ease of use, the learning curve is very little. So again, we want to provide you with a software that doesn't take you weeks and months to get used to and learn how to deploy. This is something that even a level one technician can take a look at, deploy it, and even understand what's going on. We're able to manage multiple sites, remote sites.
Again, the most important thing is this: as an IT professional, we want to eliminate all the day-to-day and those mundane tasks that takes up so much of your time. And part of watching a network and monitoring a network is time-consuming. So why not have a product that can take the place of that? Why not have a product that can sit there and just tell you when things don't work? So now you can take that time, the time that you would have spent watching this network and worrying about this network to forecast IT budgets, to focus on big picture items.
Managers like it when you come to them and say, "Hey, listen, I have a forecast. I have this budget. Let's look at big picture items. Let's look at new technology. Let's look at ways to improve our infrastructure." That's the fun part of what we do is trying to find the time to be able to go out there and take a look at those types of technology and then bring it to our immediate supervisors so we can actually move forward some of these things.
And again, reduce the cost of network management. So Intermapper, we're not trying to take jobs away, but what we're trying to do is we're trying to reduce some of the costs of network management, costs associated with, again, having a guy sit there watching a network when we can have the software do it for us.
And it's a low cost, high reward. Again, we're competitively priced. So we're priced at a pretty good point where we can provide you with some really good features and functions.
So some of our customers that have utilized the product. Xerox is one of our larger customers that's used the product in the past. Business Only Broadband. So just a few, but we do have thousands of IT professionals out there in the marketplace that's utilizing Intermapper as either their primary network monitoring solution or as an augmented solution to something that they currently are using.
So again, we can either take the place of a solution that you're currently using or we can play nicely with a solution that you are currently using as well. So again, really nice function and features there.
So now what I want to do is I want to take a little time, and I'm going to go online and show you a live installation, live map of the Intermapper software, take you through a few things, a few of the features and function of the product so you have a little bit of understanding of what we can do and what our capabilities are. So give me one second and I'm going to share my screen.
All right. So as you can see, what we have here is just a map of part of our test network in Eden Prairie, Minnesota. And as you can see, so this is just a basic map. We have a few devices on this map. So we have some firewalls, some switches, some servers, routers. But we also have a few remote offices.
So the nice thing about what Intermapper can also do is not just the mapping functionality, but we're able to provide you with an extension to see your remote offices, or if you want to look at, you can do maps by business units. You can do maps by office floors. So if you have infrastructure that's local to these sites, you can create what we call a sub-map.
And if I double click on my Chicago site, I bring up my Chicago sitemap. So the sub-map is an extension of all the devices that's local to that office or that site that you're looking to monitor. So you don't have to have all these devices hidden, loaded on one map. What you can do is you can create an extension to another site.
And the nice thing about what the sub-map function does is if you can see here, my Chicago office is, the icon is blinking red. So the sub-map function will always show you the most severe events that's local to that site. So not only do you get an alert from the device in question and the devices being affected, but you also see visually that there's some issues local to that site. So again, very key visibility and alerting. So those are two components that are provided by this sub-map functionality.
So if we close out of the Chicago office, let's take a look at some of the components that we can see within this map. So if you look at the SonicWALL, you can see that the SonicWALL has a couple of links associated with it. So we're monitoring these links on this particular device. So if I right click on one of the links here, I can bring up my status window, and my status window shows me what link I am monitoring.
So this is a one gig Ethernet link. So what I can do is I can see my utilization traffic, my bandwidth utilization on this particular link. Intermapper tells me how much data is being sent and how much data is being received.
Now I can take this one step further. I can see my information here. What I can also do is I can create what we call a utilization chart. So if I open up my utilization chart, I can bring up this strip chart. And this strip chart basically shows my utilization percentage, my utilization bandwidth on this particular link. So I can keep this chart up and see how the utilization traffic is coming in on that particular link. So if there's any spikes or any anomalies, then I can visually see it on this particular map.
So we can pretty much monitor any one of these data sets, anything that's on the line you can create a strip chart. You can bring up this chart and actually put it on your monitor and on your screen, and actually watch it and see how it trends and see if there's any issues.
So that's one portion. So that's the interface statistics there. We can also look at the device stats. So if we bring up our devices statistic window, here we're monitoring our mail server. So here we can see that we're using a few probes, and the probes we utilize are the backbone of the product. So the probes are the software plugin that allows us to basically interrogate any device using vendor provided MIB information or specific object identifiers. So all these data sets are object identifiers associated with the device that we're monitoring. So we're able to monitor specific device information here. For instance, for this exchange, we're looking at some physical attributes of this exchange server. We're looking at installed memory, disk utilization. We're looking at low percentages, CPU utilization.
So we want to monitor specific information that's important to us on our email server. And again, Intermapper will tell you when there's issues, when there's alarms. So again there's some usage issues here. So we're getting alerts and some notifications saying, "Hey, your device is in some kind of alarm state."
As you can see up in the corner here, we call this our status badges. As you can see here, InterMmpper provides you with, we call it the five states here, five status badges so you can see the down devices, critical devices that are in an alarm state, warning, and good. And then you can click on the icon and it shows you the list of those devices that's in that particular state.
So again, full disclosure. All the information here. And this is a live map. This is a living map. We're pulling every 30 seconds, so we're capturing data every 30 seconds. So this is near real-time information that we're capturing. So you can see a lot of good information here. We have the ability to do some NetFlow balance analyzing as well.
So again, we're capturing flows traffic at one of our routers here. So if I right-click on this device, I can go into my flows window, and this pulls up our NetFlow analyzer product where you can see the information that we're capturing. So again, fully customizable and fully... it's a live interactive graph, so you can drill into the specific host. We show you the top 25 talkers. So you can see how much information, the percentage of bandwidth, has been used. And then you can also interactively drill into the spikes on the graph as well to see who's using the bandwidth and when.
We also show you the top application ports. So again, as I mentioned, you can have a good understanding of what applications are being used. And you could take this information, if you're making recommendations, you can take this information to your managers and say, "Hey, listen, we've done some due diligence and realized that the bandwidth that's been used is justifiable information, justifiable traffic. But we're hitting our performance, we're flatlining on bandwidth, and we need to do some things to improve bandwidth, maybe increase our current bandwidth."
Or if it's not work-related bandwidth, you can take this information and say, "Hey, listen. This is not work information. There's people downloading and streaming. We need to take some steps to throttle the bandwidth a little bit." So then you can take those necessary steps to shut down ports or shut down particular sites.
So again, some really good information here that you can get to make some recommendations on how to improve your current infrastructure. We also show you the top 50 sessions so you can see the client-server relationships. You can see what clients, what they're connected to, what service they're using, what port they're utilizing. Again, what protocol and how much bandwidth is being used and the time in which they're connected to those particular servers.
So a lot of good information there that you can use. We're monitoring network traffic using SNMP. As I mentioned before, we utilize a probing technology to monitor specific information. So the probes are, as I mentioned, the backbone of the product. So we utilize probes to capture the information and interrogate the devices.
So again, chances are, if you are monitoring and working with any device, pretty much all the vendors out there provide you with appropriate MIB information, a MIB library associated with their device. We can capture that information. We can utilize that information, create these probes, and then capture this non-standard information. So a lot of good information there that we can use.
We're monitoring our website. So you can monitor web traffic, web services. As I mentioned earlier, we're monitoring our environmental sensor here. So again, it doesn't have to be standard devices that we're monitoring, but we're monitoring environmental sensors. We can monitor door lock, door sensors, alarms. Anything that's IP-based that has an IP address, Intermapper can put it on your map and monitor that device.
So a lot of flexibility, a lot of range that we can provide for you so you can have that visibility. But not just a visibility, but the functionality as well in terms of having a good understanding of your devices and how your devices are behaving.
So that's a quick demo of the product. So at this time, I'm going to hand this over to our Q&A. We will take some questions and hopefully I can answer your questions for you. So this is the time for us to jump through some of the questions.
Janine: Thanks, Kevin. Just a reminder. If you'd like to ask a question, just put your question in the Q&A panel on the lower right-hand side of your screen and address it to all panelists. Here's one for you. How does mapping work for devices such as firewalls which don't support CDP or other discovery protocols?
Kevin: Good question, Janine. So the way Intermapper works is Intermapper uses SNMP as the main vehicle to do with original or initial discovery. So again, most firewalls are effectively routers, all kinds of devices. They are IP-based and they have the ability to support certain protocols. So although we don't do the initial discovery using a CDP protocol, we're using SNMP, we can get the devices on the map, and then using SNMP we can monitor the traffic, the interface traffic on those devices.
So again, we do have the layer 2 functionality that also utilizes CDP protocol to show the interconnection once the devices are on the map. So we do not use CDP as a way of doing our initial discovery, but we do use SNMP to do discovery, do the monitoring, but we can then use CDP as part of our layer 2 options to show the interconnections and show the layer 2 connectivity to those devices.
Janine: Okay. Is there any impact to network performance generated by devices being probed? That make sense?
Kevin: Good question. Yep. So Intermapper, what we do is... and another reason why we're basically pretty good in the marketplaces. Again, we don't have a lot of built-in modules and clunkiness within a product. What we do is we sit and we collect the information, again, utilizing SNMP. And we all know that SNMP is a very lightweight protocol, and it's very little, minimal, very minuscule impact on the devices that we're polling. We have customers that are monitoring 10,000, 20,000 devices without issues. So our impact is almost not even there. So no issues with impact on your devices.
Janine: Kevin, here's a question that relates to something you said earlier. You said any IP device. Is there a matrix of compatible devices?
Kevin: So Intermapper, we're vendor-agnostic. So it doesn't matter what vendor you're using. There really isn't a matrix of IP devices. It's any device that supports IP connectivity. Any device that's IP-enabled, we can support. So the range and the flexibility in terms of what we can do based on that. We do not install agents, so we are an agentless application. So we don't install agents on target hosts and devices.
As I said before, we just depend on the connectivity between Intermapper and those devices. And again the main vehicle is using SNMP, and also the requirement is that that device has an active...well, it doesn't necessarily have to have an active IP address, but if it's enabled with an IP address, we can see that device, and we can connect to it, and we can put it on the map. Whether it's active or not, we can still display it on a map.
Janine: Great. How is the product licensed? Is it by site, by device?
Kevin: So the product is licensed by IP address. So the nice thing about that as opposed to monitoring a number of centers and licenses and all these sensors, you can effectively have a device that has 40 ports, and instead of paying for monitoring 40 ports, you're paying for one device or one license. So again, we're basically charging you for what you want to monitor. It's based on IP address and devices.
Jeanine: Does Intermapper support virtualization, VMware, Hyper-V, et cetera?
Kevin: Yes, so again, we are virtualization-capable. Meaning that, yes, we can run that application on virtualization, and we can support virtual infrastructure. The nice thing is that VMware, Hyper-V, and Citrix, they all have the supported documentation, the supported MIB information and specific object identifiers associated with their software that allows us to create these probes. So the nice thing about what our product does is the flexibility that we provide in terms of what we can monitor.
As I mentioned earlier, we have customers that's monitoring some really disparate things, not just their infrastructure but they're monitoring door sensors. They're monitoring freezers. So again, there's a nice little range in terms of what we can do, but the virtual environment we can fully support the virtual environment.
Janine: Kevin, can you speak to the reporting capabilities of Intermapper?
Kevin: So Intermapper has its own built-in reports product. So what we can do is we utilize what we call postscript SQL database. So that's installed with the product, and that's the backbone database that's used. We do have the ability to create custom reports. So if you're looking to do SLA reporting or reporting on utilization, response time, any kind of data metrics, we can create custom reports based on the data sets that you're looking to capture.
Janine: Great. Thanks, Kevin. Seeing no more questions, I want to thank everyone for attending today's webinar, and I especially want to thank Kevin for sharing his expertise. Later this week, we will be sending out a link to a recording of today's presentation to everyone on the call as well as to anyone who registered for today's event but could not attend. That concludes our webinar. Thanks again, and have a great day.