compare
Parca vs Zabbix
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Parca | Zabbix |
|---|---|---|
| Language | TypeScript | Go Template |
| Licence | Apache-2.0 | AGPL-3.0 |
| Stars | 5k | 6.4k |
| Latest | v0.29.1 | 7.4.15 |
| Last push | 2026-09-29 | 2026-10-06 |
| Release cadence | about 26 days between releases | too few releases |
| Active contributors | 6 commit authors on the default branch in the last 90 days | 42+ commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Datadog. Alternatives to Datadog →
PartialParcaContinuous profiling only, with an eBPF agent that needs no code changes.
PartialZabbixInfrastructure and network monitoring with agents, templates and alerting; no APM.
Parca
- v0.29.12026-09-28Fix relable configs validation scheme not being set.
- v0.29.02026-09-23ui: Fix the mis-highlighting in flamegraphs
- v0.28.02026-05-07Add support for OpenTelemetry eBPF Profiler profile type
- v0.27.12026-03-20.github: Fix authentication for release container pushing
- v0.27.02026-03-20Update otlp support
Zabbix
This repository publishes tags, not GitHub releases.
Parca
✓ signed The latest release, v0.29.1, carries a signature GitHub verified.
Loading the security report
Zabbix
unsigned The latest release, 7.4.15, carries no signature GitHub could verify.
Loading the security report