Since load balancers are active devices that can be included in the design of a WAN, the question arises: Should we adapt our monitoring scheme to include something that could be called Load Balancer Monitoring? To answer this question we can assume that WAN monitoring is based on the following fact: the behaviour of communication links directly affects the performance of applications and therefore the entire platform.

To fully understand what NetFlow is and why it’s used for network monitoring, we first need to know what a flow is. When computers need to talk to one another they establish communication channels, commonly referred to as connections. (Technically speaking, these communication channels can only be called connections when the TCP protocol is involved.) A flow refers to any connection or connection-like communication channel.

Although since 1985 the federal government of the United States of America provided the radio bands (frequencies) to be used for our daily use, it was not until 1999 when the brand Wi-Fi® was registered, which means wireless fidelity and in that same year was founded the WECA (Wireless Ethernet Compatibility Alliance).

Let’s say one of your techs is configuring a client’s firewall and makes a mistake that results in the firewall (and the rest of the network) no longer being accessible. What are your options for fixing the issue?

Deploying an application on Kubernetes can require a number of related deployment artifacts or spec files: Deployment, Service, PVCs, ConfigMaps, Service Account — to name just a few. Managing all of these resources and relating them to deployed apps can be challenging, especially when it comes to tracking changes and updates to the deployed application (actual state) and its original source (authorized or desired state).

Suricata is an open source threat detection system. Initially released by the Open Information Security Foundation (OISF) in 2010, Suricata can act both as an intrusion detection system (IDS), and intrusion prevention system (IPS), or be used for network security monitoring.

Since all technology traffic analysers have evolved, and in order to answer the question of what the next step in this evolution is many experts suggest that the deep packet inspection is the point to which all will evolve. However, deep packet inspection is not a new concept; ISPs have been using it, not without controversy, for some years. Then why is it referred to as the next step?

Ok, so you own a company, now what? All right, then one of the million things to keep in mind, in addition to the plant that you are going to buy for your office, is learning how to monitor networks. Think that if your computerized network stops working properly (for any reason) and the data that normally flows through it does not, the company is not functional anymore, during the whole time the disaster lasts.

In a world where consumer-level computing technology has been largely dominated by Windows, many users remain unaware of the need for administrators to configure and maintain network hardware and environments based on the Linux operating system. But Linux in its various distributions and the Unix operating system from which they derive have for decades provided the backbone for the core systems that make consumer-level computing and indeed many aspects of daily life possible.

The secret to exceptional network management is periodically identifying and diagnosing network problems. Putting your experts at the network operations center (NOC) all day watching for a device to go down isn’t the best use of your workforce’s time. There has to be a smarter way to view potential network pitfalls without being glued to the chair in your NOC.