The section your link pointed to isn't on tetragon's page any more, so we've brought you to the top.
Tetragon is an eBPFeBPFA Linux technology for running verified programs inside the kernel without changing its source. Tools use it to observe processes, enforce rules and process network traffic.-based security observability and runtime enforcement tool for Kubernetes and cloud-native environments.
Tetragon is an open-source runtime security agent, licensed Apache 2.0, that uses eBPF to observe process execution, system calls, and network and file activity in real time and can enforce policy on what it sees rather than just log it. It runs as a sensor deployed on Linux hosts or as a component alongside Cilium in Kubernetes, where it understands namespaces, pods, and workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials., making it a fit for platform and security teams responsible for cluster runtime defense rather than static scanning. Policies are written as TracingPolicy CRDsCRDsA Kubernetes extension that adds a new object type to the cluster, so a tool's configuration is stored, validated and versioned by Kubernetes itself rather than in a file beside it. covering kprobes, uprobes, tracepoints, and USDTUSDTUserspace Statically Defined Tracing probes, a mechanism originating in Solaris and adopted by Linux, that lets a program embed named hook points so debuggers and tracers can attach at runtime with near-zero overhead when idle. probes, with recent work adding fentry sensors and in-kernel CELCELCommon Expression Language, an open-source expression language maintained by Google, used to embed lightweight, safe policy evaluation logic into tools without running a full scripting engine. expression evaluation to cut userspace overhead. Started in 2022, it has drawn 210 contributors and over 2,000 commits in the past year, with its latest release 114 days ago.
Tetragon is an eBPF-based security observability and runtime enforcement tool for Kubernetes and cloud-native environments.
Which processes on this host executed which binaries, and by whom were they spawned?
records every exec and exit as a kernel-observed event enriched with process lineage, so a full parent-to-child chain is available without relying on host logs
Which pod or namespace did a given system call or file access actually come from?
tags each kprobe, tracepoint, and network/file event with the Kubernetes identity of the workload that triggered it, so activity maps directly to a pod rather than a bare PID
Can a suspicious action be stopped instead of just recorded?
a TracingPolicy attached to the matching kprobe or uprobe can carry an enforcement action, letting the sensor block or override the call in-kernel at the moment it happens rather than only emitting an event
Which ancestor process is really responsible for a chain of unwanted activity?
a selector can match on the binaries of parent processes, so alerts can be scoped to activity descending from a specific ancestor rather than every process that shares a name
49 capabilities
across 2 capability groups
· 2 backed by code, an API document or a real run
Built from tetragon's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
tetragon covers 2 of the 11 endpoint investigation and controls capabilities we track.
What tetragon offers you
Command-line interface5
gRPC API support1
Show
No capabilities match.
+Process telemetry15 featuresEndpoint investigation and controlssince 2022▸
+Process lifecycle monitoringshippedObserve process execution and exit events via Tetragon's process_exec and process_exit JSON events.17 releases · 3 other sources · first seen Mar 2023▸
Shared capability: Process telemetry
Also counts toward: Command-line interface
release
17 total
Uses tracefs instead of debugfs for BPF program attachment.
v1.7.0 · Apr 2026
· source
· release history
Allows tracing policies to load even when kptr_restrict is set to 2.
v1.6.1 · Mar 2026
· source
· release history
Switches from debugfs to tracefs for BPF tracing attachment.
v1.6.1 · Mar 2026
· source
· release history
Adds pod.uid field to the Kubernetes Pod API, surfacing pod UIDs in events.
v1.6.0 · Oct 2025
· source
· release history
Adds Kubernetes node labels to Tetragon events for richer event context.
v1.5.0 · Jul 2025
· source
· release history
Adds .process.pod.container.privileged field to PodInfo in events, surfacing container privilege status.
v1.5.0 · Jul 2025
· source
· release history
docs
Process execution Monitor process lifecycle with process_exec and process_exit This first use case is monitoring process execution, which can be observed with the Tetragon process_exec and process_exit JSON events.
docs update · Oct 2026
· source
example
Filter uprobe events by argument value — useful when you only want events for a specific argument passed to a user-space function.$ spec: uprobes: - path: /usr/bin/myapp symbol: myFunction args: - index: 0 type: int selectors: - matchArgs: - index: 0 operator: Equal values: - "42"
v1.6.1 · Mar 2026
· source
Filter event payload to include only specific fields, reducing bandwidth or storage cost.$ tetragon get-events --fields process.pid,process.name
v0.9.0 · Apr 2023
· source
+Process ancestry trackingshippedTrack and correlate parent-child process relationships in tracing policies via the FollowChildren attribute.6 releases · first seen Sep 2024▸
Shared capability: Process telemetry
Also counts toward: Command-line interface
release
Adds a separate configuration option for enabling ancestors in ProcessLoader events.
v1.7.0 · Apr 2026
· source
· release history
Adds --enable-ancestors flag to consolidate ancestor-tracking configuration across all event types.
v1.5.0 · Jul 2025
· source
· release history
Adds CEL filter support to the tetra CLI for client-side event filtering.
v1.4.0 · Mar 2025
· source
· release history
Adds ancestor process information to process events, giving full lineage context for every observed action.
v1.4.0 · Mar 2025
· source
· release history
Adds map_errors_update_total and map_errors_delete_total metrics replacing the former tetragon_map_errors_total.
v1.4.0 · Mar 2025
· source
· release history
Adds FollowChildren attribute to MatchBinaries selector in tracing policies, enabling matching on child processes.
v1.2.0 · Sep 2024
· source
· release history
+Parent argument pattern matchingshippedMatch tracing events based on regular expressions applied to parent process arguments.3 releases · first seen Nov 2024▸
Shared capability: Process telemetry
release
matchArgs/matchBinaries Postfix and NotPostfix values longer than 87 characters are now rejected on kernels without large BPF program support.
v1.8.0 · Oct 2026
· source
· release history
New retprobes events cache size configuration option.
v1.7.0 · Apr 2026
· source
· release history
New parent_arguments_regex filter type lets policies match events by parent process argument patterns using regular expressions.
v1.2.1 · Nov 2024
· source
· release history
+Container-specific event filteringshippedFilter exported events based on whether a process belongs to the container's init tree, enhancing containment scope control.2 releases · first seen Dec 2024▸
Shared capability: Process telemetry
release
Applies redaction filters to all environment variables in events, broadening the reach of existing redaction configuration.
v1.7.1 · Aug 2026
· source
· release history
Introduces the in_init_tree flag on process events indicating whether a process spawned from its container's init process tree.
v1.3.0 · Dec 2024
· source
· release history
+Environment variable supportshippedRetrieve and filter environment variables within kprobe and uprobe events, including application of redaction filters to all environment variables.2 releases · first seen Apr 2026▸
Shared capability: Process telemetry
release
Applies redaction filters to all environment variables in events, broadening the reach of existing redaction configuration.
v1.7.1 · Aug 2026
· source
· release history
Adds support for retrieving environment variables in kprobe/uprobe events.
v1.7.0 · Apr 2026
· source
· release history
+Username enrichmentshippedResolve process UIDs to login names in process_exec events using a local cache.2 releases · first seen Jun 2024▸
Shared capability: Process telemetry
release
Adds username enrichment to process_exec events, resolving UIDs to login names via /proc and a local cache.
v1.2.0 · Sep 2024
· source
· release history
Adds uid username resolution support (backported from v1.1) to improve identity context in traces
v1.1.2 · Jun 2024
· source
· release history
+Process capability tracingshippedTrace kernel capability checks performed by the process.2 releases · first seen Oct 2022▸
Shared capability: Process telemetry
release
Export filters support a new filter type for process capabilities via the capabilities export filter
v1.1.0 · Apr 2024
· source
· release history
tracing: trace capability checks performed by the kernel on X access
v0.8.3 · Oct 2022
· source
· release history
+Ancestry binary filteringshippedFilter tracing events based on the binaries of ancestor processes using a new matchParentBinaries selector.1 release · first seen Apr 2026▸
Shared capability: Process telemetry
release
New matchParentBinaries selector for filtering events based on ancestor process binaries.
v1.7.0 · Apr 2026
· source
· release history
+Kubernetes node label enrichmentshippedAdds Kubernetes node labels to Tetragon events to provide richer context for observed processes and network activity.1 release · first seen Jul 2025▸
Shared capability: Process telemetry
release
Adds Kubernetes node labels to Tetragon events for richer event context.
v1.5.0 · Jul 2025
· source
· release history
+Windows process lifecycle monitoringshippedMonitors process create and exit events on Windows hosts, extending Tetragon's core visibility capabilities to the Windows platform.1 release · first seen Jul 2025▸
Shared capability: Process telemetry
release
Adds Windows support for process create and exit events, enabling Tetragon to monitor process lifecycle on Windows hosts.
v1.5.0 · Jul 2025
· source
· release history
+32-bit ARM syscall tracingshippedTrace syscalls on 32-bit ARM (aarch32) architectures.1 release · first seen Dec 2024▸
Shared capability: Process telemetry
release
Adds support for tracing 32-bit ARM (aarch32) syscalls.
v1.3.0 · Dec 2024
· source
· release history
+Container-specific export filteringshippedFilter exported events by container ID or init process status using dedicated export filters.1 release · first seen Dec 2024▸
Shared capability: Process telemetry
release
Introduces a container_id export filter and an in_init_tree export filter.
v1.3.0 · Dec 2024
· source
· release history
+Nested cgroup pod associationshippedCorrectly associate pod information with processes even when nested cgroups are utilized.1 release · first seen Dec 2024▸
Shared capability: Process telemetry
release
Adds support for associating pod information when nested cgroups are used.
v1.3.0 · Dec 2024
· source
· release history
+Cgroup event rate limitingshippedLimit the number of events generated per cgroup to control telemetry volume.1 release · first seen Sep 2024▸
Shared capability: Process telemetry
release
Adds cgroup rate support for limiting events per cgroup.
v1.2.0 · Sep 2024
· source
· release history
+Process killer detectionshippedDetect and trace the specific process responsible for terminating another process using a dedicated killer sensor.1 release · first seen Nov 2023▸
Shared capability: Process telemetry
release
Adds a new killer sensor for process lifecycle detection
v1.0.0 · Nov 2023
· source
· release history
+File integrity monitoring1 featureEndpoint investigation and controlssince 2024▸
+IMA file integrity visibilityshippedCapture Integrity Measurement Architecture (IMA) hash information within LSM events to verify file integrity.1 release · first seen Dec 2024▸
Shared capability: File integrity monitoring
release
Adds IMA hash information to LSM events for file integrity visibility.
v1.3.0 · Dec 2024
· source
· release history
+Other / not yet classified33 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+Tracing policy managementshippedInstall, persist, and restore tracing policies via the gRPC API so that desired state survives agent restarts.7 releases · 2 other sources · first seen Oct 2022▸
Also counts toward: gRPC API support
release
7 total
Add support for stateful tracing policies, gRPC-based persistent policies, JSON schema and CEL validation for tracing policies without Kubernetes support, an eBPF-based glob library for tracing policy matching, and domain-sharded tracing policy management.
v1.8.0 · Oct 2026
· source
· release history
Adds an alpha feature to generate kernel stack traces for kprobe events
v1.0.0 · Nov 2023
· source
· release history
Implements DeleteTracingPolicy functionality to remove tracing policies dynamically
v0.11.0 · Sep 2023
· source
· release history
Supports LT and GT operators in matchReturnArgs within TracingPolicy
v0.10.0 · Jul 2023
· source
· release history
Adds Signal and NoPost actions to TracingPolicy for event control
v0.10.0 · Jul 2023
· source
· release history
Allows optional labels on arguments in TracingPolicy for better context in events
v0.10.0 · Jul 2023
· source
· release history
docs
Persistent gRPC policies Persist and restore tracing policies installed through gRPC
docs update · Jul 2026
· source
Persistent gRPC policies Persist and restore tracing policies installed through gRPC Tetragon can persist tracing policies installed through the gRPC API and restore their desired state after the agent restarts.
docs update · Jul 2026
· source
+Uprobe and USDT extensionshippedExtend uprobe and USDT capabilities with return probes, pointer dereference, user string preloading, register-based data retrieval, and ARM64-specific support.8 releases · 1 other source · first seen Apr 2026▸
release
8 total
Add support for multiple preloaded string-resolved arguments in BPF sensors.
v1.8.0 · Oct 2026
· source
· release history
(improved) Add argNew{Symbol,Addr,Offset} support to the uprobe override action and support for multiple sopath actions in uprobes.
v1.8.0 · Oct 2026
· source
· release history
Add the uprobe Set action with u64 argValue support, and symbolized user-space stack traces to ProcessUprobe events for uprobe Post actions that enable userStackTrace.
v1.8.0 · Oct 2026
· source
· release history
Adds current_task resolve support for uprobes.
v1.7.0 · Apr 2026
· source
· release history
Supports preloading user strings in uprobe/usdt probes.
v1.7.0 · Apr 2026
· source
· release history
Adds resolve: support for uprobes, enabling pointer dereference in userspace probe arguments.
v1.7.0 · Apr 2026
· source
· release history
docs
matchCmdArgs : filter on process command-line arguments. Command-line arguments filter Command-line argument filters can be specified under the matchCmdArgs Unlike , which filters on arguments passed to the hook, matchCmdArgs filters on the arguments passed to the current process when it was executed.
docs update · Sep 2026
· source
+Uprobe argument filteringshippedsuggestedFilter uprobe events by specific argument values or types using selectors like matchArgs, CEL expressions, or integer/bitwise operations.7 releases · 1 other source · first seen Mar 2026▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
7 total
(improved) Add support for CEL expressions in argRegs register overrides, bit-shifting operators (lsh, rsh), 16-bit and 8-bit signed and unsigned integers, and multiplication and division operators to CEL expressions.
v1.8.0 · Oct 2026
· source
· release history
Adds btfType and btfTypeModule support in tracing policies, enabling more precise BTF-based type resolution for kernel arguments.
v1.7.1 · Aug 2026
· source
· release history
Adds int argument type support for tracepoints in TracingPolicy, expanding the set of kernel tracepoint arguments that can be traced and filtered.
v1.7.1 · Aug 2026
· source
· release history
Scopes uprobe and USDT events through policy filters, bringing them in line with kprobe/tracepoint filtering capabilities.
v1.7.1 · Aug 2026
· source
· release history
Supports argument matching selectors (matchArgs, etc.) in uprobe policies.
v1.7.0 · Apr 2026
· source
· release history
Supports matchArgs filtering in uprobe-based tracing policies.
v1.6.1 · Mar 2026
· source
· release history
docs
matchCmdArgs : filter on process command-line arguments. Command-line arguments filter Command-line argument filters can be specified under the matchCmdArgs Unlike , which filters on arguments passed to the hook, matchCmdArgs filters on the arguments passed to the current process when it was executed.
docs update · Sep 2026
· source
+CEL-based argument filteringshippedsuggestedFilter kernel events by specifying Common Expression Language (CEL) expressions that are evaluated in-kernel against syscall or function arguments.5 releases · 2 other sources · first seen Sep 2022▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Add bitwise operators (and, or, xor, not) for CEL expressions.
v1.8.0 · Oct 2026
· source
· release history
Add new tracing policy selectors: matchCmdArgs to filter tracing events by individual command-line arguments of the invoking process, matchWorkloads, nodeSelector, and MatchCEL to allow mixing arguments and data in CEL expressions.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
v1.8.0 · Oct 2026
· source
· release history
Adds sock and skb selectors to matchArgs for deeper packet-level filtering
v0.10.0 · Jul 2023
· source
· release history
Adds arguments_regex filter capability to TracingPolicy selectors for matching exec arguments against a regex pattern
v0.8.1 · Sep 2022
· source
· release history
Adds pod_label_filter capability to TracingPolicy selectors for matching events against pod labels
v0.8.1 · Sep 2022
· source
· release history
docs
), subtraction ( ), multiplication ( * ), and division ( uint64 Last modified September 9, 2026: docs: add div and mul cel operations (df028d34b)
docs update · Oct 2026
· source
CelExpr CelExpr argument filter CelExpr argument filter allows specifying filtering expressions in CEL that are evaluated in-kernel.
docs update · Jul 2026
· source
+Uprobe sensor memory tuningshippedsuggestedConfigure the maximum number of entries for heap maps used by uprobe and USDT sensors to control memory usage.5 releases · 2 other sources · first seen Oct 2022▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Add btfType and btfTypeModule argument types, support for the fd type to retrieve file*, the --sleepable-preload-size option to configure the sleepable preload size, a read-only, frozen configuration map, the --execve-map-no-prealloc option to control execve map memory allocation, and BPF area-specific…
v1.8.0 · Oct 2026
· source
· release history
Adds support to dump the processLRU cache for operational introspection.
v1.2.1 · Nov 2024
· source
· release history
--rb-size and --rb-size-total CLI flags to configure BPF perf ring buffer size.
v0.9.0 · Apr 2023
· source
· release history
Adds --rb-size and --rb-size-total CLI options to the Tetragon agent for configuring perf ring buffer sizes
v0.8.4 · Mar 2023
· source
· release history
uprobe-heap-size : set the process call heap map size uprobe-heap-size This option sets the maximum number of entries for following heap maps: process_call_heap ratelimit_heap string_postfix_maps_heap string_prefix_maps_heap string_maps_heap buffer_heap_map used by uprobe and usdt sensors.
docs update · Oct 2026
· source
example
Tune ring buffer capacity to prevent event drops during high-throughput tracing.$ tetragon --rb-size=131072 --rb-size-total=524288
v0.9.0 · Apr 2023
· source
+Policy testingverifiedAuthor and run Tetragon policy tests to validate tracing policy behaviour before deployment.1 release · 3 other sources · first seen Mar 2025▸
release
Supports running multiple Tetragon operator replicas simultaneously via tetragonOperator.replicas and tetragonOperator.failoverLease.enabled.
v1.4.0 · Mar 2025
· source
· release history
Run two Tetragon operator replicas with leader-election failover to reduce downtime during upgrades.$ helm upgrade tetragon cilium/tetragon --set tetragonOperator.replicas=2 --set tetragonOperator.failoverLease.enabled=true
v1.4.0 · Mar 2025
· source
+Process cache tuning and introspectionshippedTune event cache retry behavior and dump the process LRU cache for diagnostics.3 releases · 1 other source · first seen Nov 2024▸
Also counts toward: Command-line interface
release
Adds tetra probe config command to check kernel configuration compatibility.
v1.6.0 · Oct 2025
· source
· release history
Event cache retry count and delay intervals are now tunable, giving operators control over cache behavior under load.
v1.2.1 · Nov 2024
· source
· release history
Adds support to dump the processLRU cache for operational introspection.
v1.2.1 · Nov 2024
· source
· release history
example
Check whether the running kernel supports the eBPF features Tetragon requires before deploying policies.$ tetra probe config
v1.6.0 · Oct 2025
· source
+Target binary digest verificationshippedsuggestedScope uprobe policies to a specific binary version by verifying the binary's SHA-256 digest before attaching, preventing accidental attachment to unintended versions.1 release · 2 other sources · first seen Dec 2024▸
Suggested capability: Security baseline enforcement. This is our guess, not confirmed.
release
Enables matchBinary names to use process arguments as match criteria.
v1.3.0 · Dec 2024
· source
· release history
docs
ignore digestVerificationFailure When the above policy is added, Tetragon calculates the sha256 hash of and compares it against all configured binary digests.
docs update · Aug 2026
· source
Target Binary Digest Verification In some cases, a uprobe policy is only intended to apply to a specific version of a binary, and could have adverse effect if attached to a different version of the binary.
docs update · Jul 2026
· source
+Agent server introspectionverifiedRetrieve runtime information and state from the Tetragon server via the CLI.1 release · 2 other sources · first seen Apr 2023▸
Also counts toward: Command-line interface
release
Add pprof HTTP support for runtime profiling via standard pprof endpoints.
v0.9.0 · Apr 2023
· source
· release history
command line
info — Retrieve information from the server
v1.7.0 · Apr 2026
· command-line history
example
Access runtime profiling data without requiring a separate port mapping for standard debug tools.$ curl http://localhost:6060/debug/pprof/heap > profile.out
v0.9.0 · Apr 2023
· source
+LSM-based enforcement and tracingshippedsuggestedEnable policy enforcement and event generation using Linux Security Module (LSM) hooks.2 releases · 1 other source · first seen Sep 2024▸
Suggested capability: Security baseline enforcement. This is our guess, not confirmed.
release
Adds tetragon_enforcer_missed_notifications_total metric for the enforcer.
v1.3.0 · Dec 2024
· source
· release history
Adds LSM (Linux Security Module) sensor for LSM-based policy enforcement and event generation.
v1.2.0 · Sep 2024
· source
· release history
docs
eBPF-based Kubernetes-aware security observability and runtime enforcement tool that detects process, syscall, and I/O events.
+Per-policy action metricsshippedExposes counters for each action defined in a TracingPolicy, allowing users to track how many times specific actions have fired.2 releases · first seen Oct 2025▸
release
Metrics labels are changed: opcode now carries the numeric ops.OpCode, opstr is the new label for its readable name, and event_type replaces prior EventType labeling; dashboards or alerts keyed on the old label names will break.
v1.8.0 · Oct 2026
· source
· release history
Adds per-policy action counters to TracingPolicy, exposing how many times each action has fired.
v1.6.0 · Oct 2025
· source
· release history
+User space caller filteringshippedsuggestedFilter tracing events based on the user-space callstack of the hooked function using the matchUserCallers selector.1 release · 1 other source · first seen Sep 2026▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Add caller function filtering to uprobe selectors in tracing policies.
v1.8.0 · Oct 2026
· source
· release history
docs
matchUserCallers : filter on the user space callstack of the hooked function. matchUserCallers matchUserCallers selector allows filtering based on the user space callstack of the hooked function.
docs update · Sep 2026
· source
+Tracepoint selector filteringshippedFilter and constrain tracepoint events in tracing policies by argument type and BTF type identity.2 releases · first seen Aug 2026▸
release
Adds int argument support for tracepoints in TracingPolicy selectors
v1.7.1 · Aug 2026
· source
· release history
Adds btfType and btfTypeModule fields to TracingPolicy to constrain tracepoints by BTF type identity
v1.7.1 · Aug 2026
· source
· release history
+Tracing policy enforcement modeshippedsuggestedAllows tracing policies to operate in monitoring mode where they observe events without taking enforcement actions.2 releases · first seen Mar 2025▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Adds monitor-only mode for uprobes and stats.
v1.7.0 · Apr 2026
· source
· release history
Adds a monitoring mode for tracing policies, allowing policies to observe without enforcing.
v1.4.0 · Mar 2025
· source
· release history
+CEL event export filtersshippedFilter exported events using Common Expression Language (CEL) expressions, including IP and CIDR helpers.2 releases · first seen Dec 2024▸
Also counts toward: Command-line interface
release
Adds CEL filter support to the tetra CLI for client-side event filtering.
v1.4.0 · Mar 2025
· source
· release history
Adds a Common Expression Language (CEL) filter for event export, including IP and CIDR helper functions.
v1.3.0 · Dec 2024
· source
· release history
+Event drop monitoringshippedMonitor and expose metrics for dropped or lost telemetry events to assess the reliability of the tracing system.2 releases · first seen Dec 2023▸
release
Adds tetragon_pod label to metrics via ServiceMonitor and supports extra labels on ServiceMonitors.
v1.2.0 · Sep 2024
· source
· release history
Adds a new missed_events metric (per-event) to expose dropped or lost telemetry data.
v1.0.1 · Dec 2023
· source
· release history
+Kubernetes liveness probe configurationshippedCustomize liveness probe behavior for Kubernetes deployments via Helm chart values.1 release · 1 other source · first seen Jun 2024▸
release
Adds tetragon.livenessProbe to Helm values to customize the liveness probe configuration
v1.1.2 · Jun 2024
· source
· release history
example
Restore the pre-v1.1.2 liveness check using the tetra status command via the new Helm value$ tetragon: livenessProbe: timeoutSeconds: 60 exec: command: - tetra - status - --server-address - "54321" - --retries
v1.1.2 · Jun 2024
· source
+Execve map memory allocation controlshippedAllows the execve map to skip pre-allocation of memory at startup, reducing idle memory usage on nodes with many short-lived processes.1 other source · first seen Oct 2026▸
example
Prevent execve map from pre-allocating memory at startup to reduce idle memory usage on nodes with many short-lived processes.$ tetragon --execve-map-no-prealloc
v1.8.0 · Oct 2026
· source
+Tracing policy deprecation enforcementshippedDeprecated tracing policy actions and fields are removed and rejected at load time, requiring policies to be updated before upgrade.1 release · first seen Oct 2026▸
release
Deprecated actions have been removed; policies referencing them will be rejected on upgrade.
v1.8.0 · Oct 2026
· source
· release history
+Fentry sensor supportshippedAttach to kernel function entry points using the fentry BPF program type.1 release · first seen Apr 2026▸
release
New fentry sensor for attaching to kernel function entry points via fentry BPF programs.
v1.7.0 · Apr 2026
· source
· release history
+BPF program introspectionshippedEnables kprobes to use the `bpf_prog` argument type, allowing users to inspect BPF programs directly via tracing policies.1 release · first seen Oct 2025▸
release
Adds bpf_prog argument type support for kprobes, enabling introspection of BPF programs.
v1.6.0 · Oct 2025
· source
· release history
+BPF ring buffer transportshippedsuggestedUses the BPF ring buffer as the default event transport on kernels v5.11 and later to improve telemetry performance.1 release · first seen Oct 2025▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Supports BPF ring buffer as the default event transport on kernels v5.11 and later for improved performance.
v1.6.0 · Oct 2025
· source
· release history
+Non-Kubernetes metadata enrichmentshippedEnables Kubernetes control plane metadata enrichment for Tetragon deployments running on non-Kubernetes (standalone) hosts.1 release · first seen Oct 2025▸
release
Enables k8s control plane metadata enrichment for non-Kubernetes (standalone) deployments.
v1.6.0 · Oct 2025
· source
· release history
+USDT tracing capabilityshippedsuggestedSupports User Statically Defined Tracing (USDT) sensors with action support, argument parsing, and resolution in tracing policies.1 release · first seen Oct 2025▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Adds USDT (User Statically Defined Tracing) sensor with action support, set action, sibling argument parsing, and resolve support in USDT tracing policies.
v1.6.0 · Oct 2025
· source
· release history
+Raw tracepoint collectionshippedsuggestedAdds support for raw tracepoints in tracing policies to allow lower-overhead kernel event collection.1 release · first seen Jul 2025▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Adds raw tracepoint support in tracing policies for lower-overhead kernel event collection.
v1.5.0 · Jul 2025
· source
· release history
+Cgroup tracker policy filteringshippedsuggestedApply tracing policies and filters specifically to the cgroup tracker component.1 release · first seen Dec 2024▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Adds policy filter support for the cgroup tracker (cgtracker).
v1.3.0 · Dec 2024
· source
· release history
+Syscall mask supportshippedsuggestedApply masks to syscall64 tracing policies to enable or disable specific system calls.1 release · first seen Dec 2024▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Adds all operator support (including Mask) for the syscall64 tracing policy type.
v1.3.0 · Dec 2024
· source
· release history
+Dynamic log level adjustmentshippedChange the agent's logging verbosity at runtime via the CLI.1 release · first seen Sep 2024▸
release
Adds dynamic log level change option via the tetra CLI.
v1.2.0 · Sep 2024
· source
· release history
+Enforced single instance per nodeshippedPrevent multiple Tetragon instances from running on the same node to avoid conflicts.1 release · first seen Sep 2024▸
release
Enforces single Tetragon instance per node.
v1.2.0 · Sep 2024
· source
· release history
+Kernel ring buffer error metricsshippedExpose metrics for kernel ring buffer errors and Go scheduler latencies.1 release · first seen Sep 2024▸
release
Exposes kernel ring buffer errors and Go scheduler latencies in metrics.
v1.2.0 · Sep 2024
· source
· release history
+Node Resource Interface (NRI) hooksshippedSupport runtime hooks via the NRI interface for container runtime integration.1 release · first seen Sep 2024▸
release
Adds NRI (Node Resource Interface) support for runtime hooks via tetragon.rthooks.
v1.2.0 · Sep 2024
· source
· release history
+Kernel stack trace generationshippedsuggestedGenerate kernel stack traces for kprobe events to provide deeper visibility into the execution path causing a traced event.1 release · first seen Nov 2023▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Adds an alpha feature to generate kernel stack traces for kprobe events
v1.0.0 · Nov 2023
· source
· release history
+Network socket trackingshippedsuggestedTrack network socket activity and correlate it with process execution events to provide context for network connections.1 release · first seen Jul 2023▸
Suggested capability: Process telemetry. This is our guess, not confirmed.
release
Enables socket tracking to correlate process activity with network connections
v0.10.0 · Jul 2023
· source
· release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for tetragon, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail tetragon puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Cilium's home page and 40 more pages as they looked each month from September 2021 to October 2026: 50 renders, 1 change of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
Show
42 entries
No entries match these filters.
October 20263
September 20266
August 20264
July 20269
April 20261
March 20261
October 20251
July 20251
March 20251
December 20241
November 20241
September 20241
June 20241
April 20241
December 20231
November 20231
September 20231
July 20231
April 20231
March 20231
October 20221
September 20222
May 20221
Project health
Issue, contributor and maintainer activity in cilium/tetragon, 2023-10 – 2026-09,
as of 2026-09-25. Twelve-month figures first; the trend lines run
the whole window.
Contributors78+8 vs prior 12 months
Maintainers9+6 joined · −5 left, last 12 months
Bus factor4committers behind half the commits
Community-filed78%of issues opened, last 12 months
Median time to close16 daysfirst maintainer reply 2.9 days
Open backlog130of 825 issues ever filed
Issues opened / month5 · 2communitymaintainers
Open backlog130
Contributors / month23
Commits / month158
Stars5,009
Issue themes, last 12 months
bugs 1%
questions 2%
docs 4%
other 93%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.
None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.