One question about containiq though which I could not figure out with the skimming of the link. How it compares to (istio + prometheus + grafana)?
The amount of 1/2 broken prometheus/grafana setups we see is crazy.
From a feature perspective there is some overlap (ex pod/node CPU and memory). But we have features that you can't get from the solutions you mentioned (ex service latency, latency by URL path (coming soon!). And have a lot more in the roadmap too. :)
We are also housing and managing the data for our users.
If you are out there to replace existing monitoring stack like ELK, Prometheus-grafana, victoria metrics, i think it will be an uphill battle proving your value because there is high switching cost.
Also, In most of the organisations, core resources that people care about are well monitored. Just my 2 cents.
[1] https://grafana.com/grafana/plugins/grafana-kubernetes-app/
The initial version of ContainIQ is in a similar space to what pixie has built, but our eventual vision has a few differentiators. I believe Pixie was built using BCC (an assumption based on the 2GB requirement and their BPF trace tooling) which requires llvm and the kernel headers to be installed on every node. This ends up requiring a lot of ephemeral storage. Since Kubernetes is most commonly used for stateless applications this ends up being a problem, because the default node storage allocatable is relatively low. We’re in the process of migrating out from BCC to libbpf which should alleviate a lot of the issues associated with the larger storage/memory footprint of BCC. We also have a few unique features in the pipeline that I believe are unique to our product (EX: P95, P99 http latency by microservice endpoint).
I’m on GKE. How does this compare against Cilium and the new Dataplane V2? https://cloud.google.com/blog/products/containers-kubernetes...
Sounds like you have more work curating dashboards at the least. And maybe this bolts on to the standard kube-proxy dataplane so folks don’t need to change that?
Exactly we bolt on to the standard kube-proxy setup. We put a lot of effort into ensuring that everything works right out the box.
- ContainIQ just works. Comes pre-configured and you don't need a degree from DD University to know how to use it.
- We are only focused on K8s.
- We have differentiated features, easier setup and we take less time to maintain (ex our latency features like service latency and latency by URL path don't need to be instrumented on each application)
- transparent pricing. We are a flat rate of $250 per month up to 50 / nodes. You don't have to worry about insane bill spikes.