Infrastructure monitoring relies on four core methods—capturing, scanning, probing, and logging—each serving a distinct role in maintaining visibility across a network environment. Together, these approaches form the foundation of a comprehensive monitoring strategy.
Infrastructure Monitoring Methods
I've broken down monitoring into four different categories: we can capture, we can scan, we can probe, or we can log.
Capturing is the idea that we're taking a little more of a passive approach. What I mean by that is we have information that's flowing back and forth across our network, we have packets that are flowing back and forth across our network. The idea behind capturing is we're going to capture some of that data, some of that information that's flowing, and then we're going to analyze that data, we're going to analyze those packets.
Scanning is a little more of an active approach, and we may scan certain things. For instance, we may scan IP ranges. So if I'm on this laptop right here, I can scan the IP range and I can find different devices that are on this network right here. Or within each of these devices, maybe I do a port scan and I can scan ports on here. And so I can discover what is on my network by doing these scans.
Polling takes a little more in depth. For instance, let's say this is a server right here. Well, the server has CPU and it's running at a percent usage, so maybe it's running at 80% usage. And then there's RAM on this, and there's some sort of how much RAM is being utilized. So polling is the idea that I'm going to go and ask for some of this information, or be able to get some of this information: what is the CPU, what is the RAM, what's the temperature of this machine. Polling is maybe getting some sort of value out of something, like what is the CPU usage.
Logging is the idea that we are logging certain events that are happening. For instance, let's say this user logs into the system. Now what has been created is an event log of that event right there, and so now we have a record of it. So logging is the idea that we're creating records based off of some sort of event.
For a lot of what we do, we can think of them as sensors. For instance, I've got a web server right here, and maybe I'm going to create a sensor that's going to be for the CPU, and then one for the RAM, and maybe one for some of the storage devices, maybe one for the networking on here. So we're going to create a sensor for each one of these that we're going to sense. We even maybe create a sensor for pinging this device to make sure that it's still up. Or maybe, since it's a web server, we're going to create an HTTP sensor that will sense if HTTP is up and running or not.
Ultimately, between all of these we can create a really robust monitoring system that's monitoring what's happening within our infrastructure.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →