go-instrument
pixie
| go-instrument | pixie | |
|---|---|---|
| 2 | 19 | |
| 210 | 5,523 | |
| - | 0.9% | |
| 7.5 | 9.2 | |
| 14 days ago | 20 days ago | |
| Go | C++ | |
| MIT License | 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.
go-instrument
- Tool for Automatic Instrumentation of OpenTelemetry Traces
-
Anyone is running automatic instrumentation in production?
UPD: I developed one :) https://github.com/nikolaydubina/go-instrument
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?
go-commentage - How far Go comments drifting behind?
cilium - eBPF-based Networking, Security, and Observability
tracer - 🧶 Dead simple, lightweight tracing.
parca - Continuous profiling for analysis of CPU and memory usage, down to the line number and throughout time. Saving infrastructure cost, improving performance, and increasing reliability.
otelsql - OpenTelemetry instrumentation for database/sql
otelinji - OpenTelemetry auto-instrumentation tool for Golang. It automatically injects OpenTelemetry blocks.
statsviz - 🚀 Visualise your Go program runtime metrics in real time in the browser
otelchi - OpenTelemetry instrumentation for go-chi/chi
enhancements - Enhancements tracking repo for Kubernetes
kubestriker - A Blazing fast Security Auditing tool for Kubernetes