Podtrace

Podtrace is a lightweight, eBPF-based observability tool for Kubernetes that continuously reports golden signals, detects anomalies, and identifies likely…

  • Development
  • Infrastructure
  • Tools & Utilities
Podtrace is a lightweight, eBPF-based observability tool for Kubernetes that continuously reports golden signals, detects anomalies, and identifies likely root causes across workloads — no code changes, sidecars, or instrumentation required.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

72/100 Good

Maintained
100last commit 15 days ago
Popular
46204 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
94no serious findings, CI, tests, OpenSSF Scorecard 8.4/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
204
Open issues
2
Last commit
2026-11-06
Latest release
v0.15.2
License
Apache-2.0
Activity
declining

Checked 15 days ago - source: GitHub (gma1k/podtrace)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Turn on alerts before running podtrace Set the environment variable (a setting you pass before running it) PODTRACE_ALERTING_ENABLED=true before starting podtrace. Without this, podtrace can run but will stay silent even when it should alert. source
  • Tell podtrace where to send alerts Add the destination you want, such as a webhook (a web address that receives alerts) URL, a Slack webhook URL plus channel, or a Splunk endpoint and token. If these are missing or wrong, alerts have nowhere to go. source
  • Keep alerts useful, not spammy Set PODTRACE_ALERT_MIN_SEVERITY to only alert on warning or critical issues, and use the dedup window (a pause before repeating the same alert) or rate limit (a cap on alert volume) if you want less noise. This keeps your chat or alerting tool from filling up with the same problem. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What host access is required when running Podtrace as a DaemonSet or container?

Podtrace must see the host's cgroup and process filesystems, and for CRI it must also see the container runtime socket. Without these, resolution can fail or events can be filtered out.

Does Podtrace require prior instrumentation or configuration?

No. It is activated on demand and works with no prior configuration or instrumentation.

How do I use declarative tracing in Kubernetes?

Use the Operator docs and choose PodTrace for continuous tracing or the session option. This creates tracing via Kubernetes Custom Resources.

What should I read first when setting up Podtrace?

Start with Installation, the Usage Guide, and Multi-Pod Tracing.

Answers sourced from github.com, github.com, github.com

Community

Collected 48 days ago - public community threads