Operations | Monitoring | ITSM | DevOps | Cloud

Network operations teams face many challenges in ensuring optimal network performance and availability in today's complex and dynamic environments. These teams need to monitor and manage multiple devices, technologies, and vendors, while contending with huge amounts of data and significant complexity. How can your teams get a clear and accurate picture of your network performance and health?

Out of the gate, NMS collects an impressive array of metrics and telemetry. But there will always be bits that need to be added. This brings me to the topic of today’s blog post: How to configure NMS to collect a custom SNMP metric.

A network key performance indicator (KPI) is a measurement and a benchmark to achieve optimal network performance goals. To support these goals, measuring actual performance against the KPI goals helps the network team make decisions to improve and sustain network performance and service levels and meet the KPI objective.

As networks of educational institutions continue to get more complex, so does the demand for robust network monitoring and security measures. Without a secure and optimized network, student records become vulnerable to hacking, bandwidth congestion disrupts essential services, and online assignments remain unfinished. When lesson plans heavily rely on video-conferencing for seamless education delivery, the margin for errors or outages is slim.

Network protocols are necessary for data transmission and networking over different devices. One of the most common protocols is the TCP/IP framework, which builds connections through our internet. In fact, if you check email, watch Netflix, or stream music from Spotify, you’re relying on TCP/IP in the background. In this article, you’ll learn about the TCP/IP protocol layers and how they function.

While many wifi access points and SD-WAN controllers have a rich data set available via their APIs, most do not support exporting this data via SNMP or streaming telemetry. In this post, Justin Ryburn walks you through configuring Telegraf to feed API JSON data into Kentik NMS.

HAProxy Kubernetes Ingress Controller 1.11 is now available. For our enterprise customers, HAProxy Enterprise Kubernetes Ingress Controller 1.11 is coming soon and will incorporate the same features. In this release, we enhanced security through the adoption of rootless containers, graduated our custom resource definitions to v1, made them easier to manage, and introduced support for the QUIC protocol.