Fiber optic cables carrying massive amounts of information on pulsating beams of light are a critical part of the physical infrastructure supporting our digital society. By their nature, these cables are highly exposed, spanning huge distances in territories beyond the control of a network operator whether underground, under water or on aerial cables, and popping up in equipment huts.

During the Data World event, Erwin Halmans, Project Manager of Data-Driven Network Operations & Assurance at T-Mobile Netherlands, Shounit Lax-Swisa, CEO of Company Booster, and Anodot Chief Data Scientist and Co-Founder Ira Cohen got together to discuss the future of network monitoring.

Just imagine the current situation continues well into the foreseeable future—let’s merge reality with a little fiction. The apocalypse is over, but life has changed permanently. This means we’re going to wear masks in public transport, shops, and restaurants and follow sports events on television instead of in the stadium. But hey, beer is much cheaper at home anyway. Office jobs are outsourced, but not into countries with cheap labor—they’re outsourced to our own homes.

Network performance monitoring has become a standard practice for modern businesses. With the shift towards large cloud-based applications, and hosted services, businesses rely on optimal network performance to sustain some of their key applications. Because of that, tools like network performance monitoring software have piqued the interest of users even outside of the IT team.

Today we are introducing the Agent Modes to help our users to configure the client / server relation between monitoring agents. This article describes the differences between the old settings and the new one. The documentation on Agent Modes is available at Agent Modes. This article refers to old settings that are no longer available in the App and it should be read only by users used to these old settings.

Today, network automation has shifted from nice-to-have to must-have. Automating key NOC processes (ranging from simple to complex) offers a wide range of benefits. But don't take my word for it — the ROI numbers speak for themselves.

Today, AWS has announced AWS Network Firewall: a new managed service that makes it easy to deploy essential network protections for Amazon Virtual Private Clouds (VPCs). As a launch partner, Splunk has worked closely with AWS to provide customers an integration to AWS Network Firewall. In today’s blog, co-authored by my esteemed colleague Anush Jayaraman, we’ll first detail the data flow architecture and your options to ingest the AWS Network Firewall data.

AWS Network Firewall is a firewall for Amazon Virtual Private Cloud (VPC) with pluggable support for third-party intrusion detection systems like Snort and Suricata. Customers use AWS Network Firewall to guard against unwanted traffic to and from their VPCs.

Log Sampling is a powerful feature introduced in HAProxy 2.0 that lets you define a percentage of your logs to create a representative view of your data allowing you to minimize your costs. Log files are the key to observability. They can provide helpful information that can be used for debugging as well as analytics that can be used to understand how users interact with an application.

In the inaugural Network Vendor Diversity report, Auvik discovered high diversity in the network devices IT teams and MSPs were managing. In 2019, the data showed complexity continuing to rise as all categories became increasingly fragmented. In the 2020 edition, we look at the same four categories of managed network devices—access points, switches, routers, and firewalls—deployed across a sample of 30,000 networks, and compared the data to both 2018 and 2019.