Tetragon

Tetragon is an eBPF-based security observability and runtime enforcement tool from the Cilium project that detects and responds to security events such as…

  • Infrastructure
  • Security
  • Tools & Utilities
Tetragon is an eBPF-based security observability and runtime enforcement tool from the Cilium project that detects and responds to security events such as process execution, system calls, and network and file activity in containerised and Kubernetes workloads.

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.

77/100 Good

Maintained
100last commit 23 days ago
Popular
745,131 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
88no serious findings, 2 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
5,131
Open issues
301
Last commit
2026-10-29
Latest release
v1.7.1
License
Apache-2.0
Activity
steady

Checked 23 days ago - source: GitHub (cilium/tetragon)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Start a test app first Download the sample docker-compose file from the docs, then run `docker compose up -d` to start a small demo workload. This gives Tetragon something to watch, so you can confirm it is running before connecting it to your real containers. source

Fetched 46 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I confirm a Docker-based Tetragon test setup is working before pointing it at real containers?

Start the sample docker-compose workload from the getting-started guide. This gives Tetragon something to observe and lets you verify it is running before connecting it to real containers.

Can Tetragon apply security detection per Kubernetes workload?

In Kubernetes, Tetragon understands identities such as namespaces and pods. That allows security event detection to be configured in relation to individual workloads.

Which process events does Tetragon produce by default?

It generates process_exec and process_exit by default. Generic tracing can also produce process_kprobe, process_tracepoint, and process_uprobe events for advanced use cases.

Can Tetragon send its observability data to external monitoring systems?

A community thread says Tetragon can integrate with monitoring backends. It can also connect that data to CNI-level network policies.

Where is the recommended place to ask Tetragon setup questions?

Use the Tetragon Slack channel and community call. It is intended as a first stop for asking questions and sharing experiences with developers, maintainers, and users.

Answers sourced from github.com, github.com, www.reddit.com

Community

Collected 48 days ago - public community threads