Kentik Blog: Network Observability

In part 1 of this blog series, Kentik director of technical product management Greg Villain discusses what matters with network interconnection and their cost considerations. Greg examines the different types of interconnections, necessary operational measures, and applicable elements of network observability.

Integrated application and network observability enables network, SREs, and developer teams to deliver reliable services with great user experience.

Cloud solutions architect Ted Turner describes how Kentik Synthetics easily uncovers network-related latencies that often cascade into cloud application performance problems — DevOps teams take note.

What is the difference between monitoring and observability? There’s a big difference! While monitoring can give you information, observability is what you need to answer questions and solve problems. In addition, we touch on some of the specifics of network observability.

In order to answer any question, network observability requires a broad range of telemetry data. It takes a capable platform to make the data useful. In this blog, the fourth in the network observability series, Avi Freedman describes requirements for the data platform.

In part 3 of the network observability series, Kentik CEO Avi Freedman discusses the different categories telemetry data. Avi shows how a complete network observability solution can answer an exponentially broader range of questions.

https://www.kentik.com/go/assessment-network-readiness/Port mirroring is one key tool in the network observability toolbelt. Find out how it can help your team in this quick guide.

The basics of network troubleshooting have not changed much over the years. When you’re network troubleshooting, a lot can be required to solve the problem. You could be solving many different issues across several different systems on your complex, hybrid network infrastructure. A network observability solution can help speed up and simplify the process.

In part 2 of the network observability series, we tackle the first key to the input needed for network observability — from what networks and network elements we gather telemetry data.

The goal of network observability is to answer any question about your network infrastructure and to have support from your observability stack to get those answers quickly, flexibly, proactively, and interactively. In this post, Kentik CEO Avi Freedman gives his thoughts on the past, present, and future of network observability.

Cloud Solution Architect Ted Turner describes a process of migrating all of applications to the cloud, and gives key takeaways as to how building your observability platform to understand both the application state as well as underlying infrastructure is key to maintaining uptime for customers.