cilium/tetragon

eBPF-based Security Observability and Runtime Enforcement

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 13th, 2026
Created on March 23rd, 2022
Open Issues & Pull Requests: 284 (+0)
GitHub issues: Enabled
Number of forks: 610
Total Stargazers: 5,020 (+0)
Total Subscribers: 60 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 25.6 hours
Mean response time: 75.1 days
90th percentile: 263.6 days
Tracked items: 395

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 81% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/bug" is answered fastest, typically in about 20 hours, while "area/metrics" waits about 4 weeks. 56% of tracked open issues have had no activity in three months. 68% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 132
New in 7 days: 8
Closed in 7 days: 6
Avg open age: 510 days
Stale 30+ days: 104
Stale 90+ days: 92

Recent activity

Opened in 7 days: 7
Closed in 7 days: 6
Comments in 7 days: 8
Events in 7 days: 25

Top labels

  • area/ci (48)
  • good first issue (41)
  • automated-issue (37)
  • kind/bug (37)
  • area/documentation (31)
  • kind/ci-flake (26)
  • area/metrics (14)
  • kind/enhancement (10)

Detailed Description

Tetragon is an eBPF-based security observability and runtime enforcement tool that operates at the kernel level to detect and respond to security-significant events in real time.

Tetragon addresses the challenge of gaining deep visibility into system behavior by leveraging eBPF to hook into critical kernel execution points. It generates events for process lifecycle changes, system call activity, and I/O operations including network and file access. When deployed in Kubernetes, the tool is Kubernetes-aware, understanding pod identities and namespaces so that security policies can be scoped to individual workloads. Events are enriched with both Linux and Kubernetes metadata, enabling context-aware security decisions.

Tetragon suits organizations that need runtime security monitoring and enforcement without the overhead of traditional kernel module approaches. It works well for teams already operating Kubernetes clusters who want to observe process execution, detect suspicious system calls, monitor file and network access, and track credential usage. The tool supports both Kubernetes and standalone Linux deployments. It provides built-in sensors for common observability needs like process lifecycle tracking, and offers a TracingPolicy mechanism for custom kernel-level tracing through kprobes, tracepoints, and uprobes when standard sensors are insufficient.

The project maintains active community engagement through a dedicated Slack channel and regular community calls. Development activity shows consistent attention to both core functionality and user-facing tooling, with documentation covering getting started guides, use cases, and contribution processes. The maintainers emphasize code quality through a developer certificate of origin requirement for contributions.