To contend with their escalating, intensifying demands, today’s operations teams must constantly be on the quest to boost efficiency. In my prior post, I offered a high-level introduction to DX Unified Infrastructure Management (DX UIM) Monitoring Configuration Service (MCS), outlining how its key features can significantly streamline administration in large-scale enterprise environments. In this follow up post, I’ll provide more details for teams looking to start working with MCS.

In a previous blog post, we dove into the wayback machine and looked at Simple Network Management Protocol (SNMP) Traps – a technology that allows devices (including network devices) to send alerts when specific thresholds have been reached. In this post, we are going to be a bit more forward looking and discuss some technologies that will, in theory, replace SNMP. It is important to keep in mind that the demise of SNMP has been predicted for years (actually decades).

We all know that cloud and SaaS adoption continues to grow rapidly, often outpacing budgets. In fact, spending on IaaS and SaaS exceeded budgets in more than 40% of organizations in 2021. As a result, network traffic is now spending much more time on the internet than in our own data centers. The internet has become the new enterprise network.

When considering application source code, the way you maintain consistency throughout environments is mostly straightforward. You write application code, commit it to source control, and then build, test and deploy via a CI/CD pipeline. Since the application is defined by the source code living in source control, the build will be identical in all environments to which it’s deployed. But what about the infrastructure on which an application runs?

For many companies, the beginning of October is also the beginning of the fourth and final quarter of the fiscal year. In IT, it’s a time to prepare for the new year by defining our priorities and setting our budget. COVID-19 threw a wrench into all of our 2020 plans last year and a lot has changed since then. But one thing that hasn’t changed is the need for a network monitoring system in your software stack.

For just about any organization, there’s a balance that has to be struck between absolute security and absolute convenience. Seemingly, every new innovation that increases convenience also introduces new risks. On the other hand, every safeguard instituted can also create complexity, delays, or in some other way diminish the user experience. Either way, businesses are exposed, whether to the catastrophic consequences of breaches, or of an erosion of user productivity and customer retention.

Cilium is a Container Network Interface (CNI) for securing and load-balancing network traffic in your Kubernetes environment. As a CNI provider, Cilium extends the orchestrator’s existing network capabilities by giving teams more control over how they build their applications and monitor traffic. For example, vanilla Kubernetes installations typically rely on traditional firewalls and Linux-based network utilities like iptables to filter pod-to-pod traffic by an IP address or port.

In Part 1, we looked at some key metrics for monitoring the health and performance of your Cilium-managed Kubernetes clusters and network. In this post, we’ll look at how Hubble enables you to visualize network traffic via a CLI and user interface. But first, we’ll briefly look at Hubble’s underlying infrastructure and how it provides visibility into your environment.

There are a variety of different connectivity models available to enterprises as they embark further on their cloud journey. In this blog, we take a look at which model could suit your business best...