Skip to main content

New Year's Resolution: Five Network Monitoring Tips for 2016

Dirk Paessler

New Year's resolutions aren't always the easiest to keep, but for IT workers, we have a few suggestions that will work wonders in 2016. Network and systems administrators do important work that keep businesses operating, yet are often overworked and overlooked. But this year, if they resolve to monitor their networks, they'll improve performance, productivity and perhaps even work a little less. Here are five easy ways IT can solve common problems with network monitoring in 2016:

1. Get A Handle On Your Growing Infrastructure

SMB and small enterprise IT is not any less complex than enterprise IT, it's just smaller in scale. The addition of cloud services, virtual machines, mobility, and even in some cases the Internet of Things has created a sprawling infrastructure that needs to be managed. Network monitoring, including features like mapping and auto-discovery, give administrators the power to stay on top of their growing infrastructure.

2. Eliminate Split Shifts and Overnights

Employees need 24/7 access to files and business applications – and they need it regardless of whether or not IT can staff it. But, nothing weakens the morale of an IT department more than split or overnight shifts. Network monitoring software acts as an extra set of eyes, ones that can monitor key infrastructure all day and alert IT when there are problems, giving admins peace of mind when they aren't at the office.

3. Set Up Separate WiFi

Much thinking has gone into how best to address BYOD. While issues of security and access are more complex, one issue should be a no-brainer – set up a separate WiFi network for employees' mobile devices. App updates, syncing and streaming video can all sop bandwidth, but rather than play cop with your coworkers, it's much easier to set up a separate network and monitor it.

4. Keep Track of Your Certificates

Some cyberattacks are sophisticated and many of the smartest companies in the world are struggling to find ways to solve that problem. But, many more are not, and instead rely on simple exploits, things like either flawed or expired SSL certificates. Network monitoring allows you to track SSL certificates and notify expiration, which takes much of the security risk off the table.

5. Control Costs

As technology has changed so has the nature of spending, especially on cloud. Load testing, computer power, cloud storage and other services all involve paying for scale, but when it comes to a lot of the services, those dollars can add up if you forget to turn them off. Using networking monitoring to track cloud usage can be a major cost saver.

We can't speak for all New Year's resolutions, but if IT can stick with network monitoring, they'll have at least one thing to celebrate at the end of 2016.

Dirk Paessler is CEO and Founder of Paessler AG.

Hot Topics

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

New Year's Resolution: Five Network Monitoring Tips for 2016

Dirk Paessler

New Year's resolutions aren't always the easiest to keep, but for IT workers, we have a few suggestions that will work wonders in 2016. Network and systems administrators do important work that keep businesses operating, yet are often overworked and overlooked. But this year, if they resolve to monitor their networks, they'll improve performance, productivity and perhaps even work a little less. Here are five easy ways IT can solve common problems with network monitoring in 2016:

1. Get A Handle On Your Growing Infrastructure

SMB and small enterprise IT is not any less complex than enterprise IT, it's just smaller in scale. The addition of cloud services, virtual machines, mobility, and even in some cases the Internet of Things has created a sprawling infrastructure that needs to be managed. Network monitoring, including features like mapping and auto-discovery, give administrators the power to stay on top of their growing infrastructure.

2. Eliminate Split Shifts and Overnights

Employees need 24/7 access to files and business applications – and they need it regardless of whether or not IT can staff it. But, nothing weakens the morale of an IT department more than split or overnight shifts. Network monitoring software acts as an extra set of eyes, ones that can monitor key infrastructure all day and alert IT when there are problems, giving admins peace of mind when they aren't at the office.

3. Set Up Separate WiFi

Much thinking has gone into how best to address BYOD. While issues of security and access are more complex, one issue should be a no-brainer – set up a separate WiFi network for employees' mobile devices. App updates, syncing and streaming video can all sop bandwidth, but rather than play cop with your coworkers, it's much easier to set up a separate network and monitor it.

4. Keep Track of Your Certificates

Some cyberattacks are sophisticated and many of the smartest companies in the world are struggling to find ways to solve that problem. But, many more are not, and instead rely on simple exploits, things like either flawed or expired SSL certificates. Network monitoring allows you to track SSL certificates and notify expiration, which takes much of the security risk off the table.

5. Control Costs

As technology has changed so has the nature of spending, especially on cloud. Load testing, computer power, cloud storage and other services all involve paying for scale, but when it comes to a lot of the services, those dollars can add up if you forget to turn them off. Using networking monitoring to track cloud usage can be a major cost saver.

We can't speak for all New Year's resolutions, but if IT can stick with network monitoring, they'll have at least one thing to celebrate at the end of 2016.

Dirk Paessler is CEO and Founder of Paessler AG.

Hot Topics

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...