parca
opentelemetry-go-instrumentation
Our great sponsors
| parca | opentelemetry-go-instrumentation | |
|---|---|---|
| 18 | 9 | |
| 3,833 | 282 | |
| 3.2% | 1.1% | |
| 9.9 | 1.7 | |
| 6 days ago | 9 months 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
opentelemetry-go-instrumentation
-
Launch HN: Odigos (YC W23) – Instant distributed tracing for Kubernetes clusters
The BPF instrumentation is quite cool! I wonder if uprobes have a performance impact. Does it roughly compare to a single syscall?
https://github.com/keyval-dev/opentelemetry-go-instrumentati...
-
How do you monitor your Go apps?
OpenTelemetry for distributed tracing. There is also a project that uses eBPF for automatic instrumentation (https://github.com/keyval-dev/opentelemetry-go-instrumentation).
- Using eBPF for the auto-instrumentation of Go
- Automatic instrumentation for Go applications
- Show HN: Automatic Instrumentation for Go Applications
- Automatic instrumentation for Go applications using eBPF
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]
grafana-operator - An operator for Grafana that installs and manages Grafana instances, Dashboards and Datasources through Kubernetes/OpenShift CRs
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code
hubble-otel - Hubble adaptor for OpenTelemetry
pixie - Instant Kubernetes-Native Application Observability
opentelemetry-go-instrumentati
pprof - pprof is a tool for visualization and analysis of profiling data
odigos - Distributed tracing without code changes. 🚀 Instantly monitor any application using OpenTelemetry and eBPF
profefe - Continuous profiling for long-term postmortem analysis
opentelemetry-go - OpenTelemetry Go API and SDK
prometheus - The Prometheus monitoring system and time series database.