parca
pixie
Our great sponsors
| parca | pixie | |
|---|---|---|
| 18 | 19 | |
| 3,833 | 5,273 | |
| 3.2% | 1.9% | |
| 9.9 | 9.4 | |
| 4 days ago | 4 days ago | |
| TypeScript | C++ | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
parca
- Seeing what a Go process does (like `set -x`)
- Julia 1.9 Highlights
-
Track Code Efficiency during Development
Continuous profiling tools such as parca may be worth looking into for your use case.
-
Hi everyone, How could you find the lines executed for a particular method call in any language (java, go..) using eBPF?
They were bought by Elastic, maybe they'll open source it. There's also https://github.com/parca-dev/parca
-
How do you monitor your Go apps?
an alternative option to pyroscope to do continuos profiling in production could be parca.dev check and here
- Go garbage collector doesn't release memory
-
How to observe an http web application in real time with pprof?
+1 to Parca.dev https://github.com/parca-dev/parca as continuos profiling tool in production
-
Continuous Profiling in Kubernetes Using Pyroscope
Parca collects, stores and makes profiles available to be queried over time. It is open source and can be deployed on production environments as Parca focuses on sampling profiling two main types of profiles: tracing and sampling.
-
Launch HN: ContainIQ (YC S21) – Kubernetes Native Monitoring with eBPF
Polar signals develops Parca [0] which is another eBPF observability tool, and Isovalent develops Cilium [1] which is built on eBPF as well. Genuinely curious if there are differences, or if eBPF only allows for specific observability functionality and each tool has it all.
[0]: https://github.com/parca-dev/parca
[1]: https://github.com/cilium/cilium
- Parca: Continuous profiling for analysis of CPU and memory usage over time
pixie
- Grafana Beyla: OSS eBPF auto-instrumentation for application observability
-
Show HN: Alaz: Open-Source, Self-Hosted, eBPF-Based K8s Monitoring
I am really curious, why build another project that has similar features as another open source software pixie - https://px.dev/.
-
Open source alternatives to Grafana
Kibana is a good alternative if you can allow storing all your data in Elasticsearch, or you can use all-in-one monitoring tools like pixie https://github.com/pixie-io/pixie
-
Lens Dashboard for monitoring multiple AKS/EKS/... clusters
Plenty of paid monitoring solutions out there. Instana is pretty slick. NewRelic has a new open source tool, https://github.com/pixie-io/pixie
-
Too many cook in the kitchen? I find everyone just wanna create their own Kubernetes plugin solution.
Cilium multi-cluster mesh is a bit different, compared to service meshes, and it's L4, so should be fine with eBPF / XDP based routing. From observability standpoint I'd go for pixie - it should work just fine with both linkerd and istio, instead of Hubble, and Cilium's Tetragon was missing policies about 3-4 months ago (needs doublec-hecking if they had introduced any).
- Improving Observability of Go Services
-
Launch HN: Odigos (YC W23) – Instant distributed tracing for Kubernetes clusters
Congratulations on the launch, and thank you for choosing an awesome license!
For an unrelated reason, today I was reminded about Pixie (https://news.ycombinator.com/item?id=25375170 and https://news.ycombinator.com/item?id=31687978 and https://github.com/pixie-io/pixie#readme ), which says is also an ebpf kubernetes observability tool, also Apache licensed.
I suspect the difference may be your aspirations to move out of just kubernetes, but I wondered if that's the biggest difference between your project and theirs? Or maybe the C++ versus golang?
- Linux /proc/pid/stat parsing bugs
- Go based eBPF projects
-
Does mTLS add request latency due to ssl termination? Any best practices for performance?
eBPF solutions look cool though. I heard of https://px.dev/ which sounds similar to ciliums eBPF mesh recently.
What are some alternatives?
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code [Moved to: https://github.com/grafana/pyroscope]
cilium - eBPF-based Networking, Security, and Observability
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code
tracer - 🧶 Dead simple, lightweight tracing.
pprof - pprof is a tool for visualization and analysis of profiling data
statsviz - 🚀 Visualise your Go program runtime metrics in real time in the browser
profefe - Continuous profiling for long-term postmortem analysis
kubestriker - A Blazing fast Security Auditing tool for Kubernetes
grafana-operator - An operator for Grafana that installs and manages Grafana instances, Dashboards and Datasources through Kubernetes/OpenShift CRs
enhancements - Enhancements tracking repo for Kubernetes
roumon - Universal goroutine monitor using pprof and termui
sysbindings - sysctl/sysfs settings on a fly for Kubernetes Cluster. No restarts are required for clusters and nodes.