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.
In Part 2 of this series, we showed how Hubble, Cilium’s observability platform, enables you to view network-level details about service dependencies and traffic flows. Cilium also integrates with various standalone monitoring tools, so you can track the other key metrics discussed in Part 1. But since the platform is an integral part of your infrastructure, you need the ability to easily correlate Cilium network and resource metrics with data from your Kubernetes resources.
An Active Directory (AD) environment has things like forests, trees, domains, organization units, and objects. After growing acquainted with these concepts, the next step on this learning journey is to understand AD sites.
Learning Apache Kafka doesn’t have to be difficult. Read on to get a friendly explanation of the Apache Kafka fundamentals.
For Summer 2022, Logz.io is thrilled to have earned six G2 Research Badges for our Cloud SIEM offering. These honors highlighted the ease of setup, ease of use, and high performance that we provide our customers through Cloud SIEM. G2 Research is a tech marketplace where people can discover, review, and manage the software they need to reach their potential.
SIGNL4 supports the remote execution of automated tasks or workflows in IT or IoT systems using Remote Actions. These remote actions offer a wide range of applications. You can execute remote actions in response to an alert to trigger some kind of remediation action. But there are many more possible use cases. This article provides some examples and ideas about what is possible.
