hubble VS coroot

Since we installed Hubble on the cluster, Let’s check its cool UI and see how the traffic flows between the pods. To do so, let’s run:

This doesn’t just provide improved operational visibility - it’s incredibly beneficial to network security engineers. For instance, if Cilium is unable to communicate with core components such as ‘Hubble,’ this will show-up in the connectivity test.

It may be we could further optimize in some way, but in our testing we didn't find the streaming or EBPF based tables to work all that well for our purposes in osquery. This tool seems more promising for logging this sort of activity: https://github.com/cilium/hubble. We're focused on K8s visibility but this could replace all of our Linux Auditing level logging if it works well.

Cilium team also offers Hubble (yes, the name is the same as the famous far space crawling telescope's one, but for clouds), which is a fully distributed networking and security observability platform for cloud native workloads. Hubble is open source software and built on top of Cilium and eBPF to enable deep visibility into the communication and behavior of services as well as the networking infrastructure in a completely transparent manner.

However, if you look at projects like Cilium Hubble and Istio Galley, you can see that you not only get all the instrumentation to manage this stuff out of the box, but you also get observability into the health of your pods and fine-grained visibility that you won’t get with traditional tools.

CNI plugins like Cilium

I'm Peter Zaitsev, co-founder at Coroot. I come from the database world where observability, or monitoring, was crucial for keeping databases running smoothly. But as technology evolves, so do the challenges we face.

Today, many applications are built using microservices architecture, making it harder to pinpoint issues. Developers now have more ownership over the entire environment, but they lack the expertise to navigate intricate infrastructure details. And with the complexity of modern observability systems, crucial components often go unmonitored, leaving blind spots.

That's where Coroot comes in!

We're excited to announce the release of Coroot 1.0 – a simplified observability platform designed to provide actionable insights for modern environments. With Coroot you get:

- Comprehensive Visibility: Coroot covers your entire environment, ensuring no information gaps. Whether you're on Kubernetes, traditional VMs, or cloud services, Coroot has you covered.

- Simple Deployment: We've made deploying Coroot a breeze. Leveraging modern Linux features like eBPF and Netlink, setup requires zero configuration. Coroot also identifies and configures additional components for you.

- Actionable Insights: Coroot prioritizes the most important information, helping you resolve issues up to 80% faster than with legacy solutions.

And the best part? Coroot has open-source version. If you prefer a hosted solution, there is Coroot Cloud, which comes with a free trial and transparent affordable pricing.

While Coroot is already an awesome open-source observability platform, we're not stopping there. We have ambitious plans to automate issue resolution and minimize human intervention.

Got ideas? Let us know on GitHub - https://github.com/coroot/coroot

See detailed overview of Coroot Features - https://coroot.com/overview

Take a look at https://github.com/coroot/coroot (Apache 2.0). It offers plenty of ready-to-use dashboards and inspections

I think ClickHouse is becoming a default storage for observability nowdays: https://clickhouse.com/use-cases/logging-and-metrics

And there are quite a few solutions on top of it.

A couple of examples that seem to be interesting (however I didn't use them in real life):

https://coroot.com/

Landing page: https://coroot.com