<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reference on Tetragon - eBPF-based Security Observability and Runtime Enforcement</title>
    <link>/docs/reference/</link>
    <description>Recent content in Reference on Tetragon - eBPF-based Security Observability and Runtime Enforcement</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="/docs/reference/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Daemon Configuration</title>
      <link>/docs/reference/daemon-configuration/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/reference/daemon-configuration/</guid>
      <description>Tetragon default controlling settings are set during compilation, so configuration is only needed when it is necessary to deviate from those defaults. This document lists those controlling settings and how they can be set as a CLI arguments or as configuration options from YAML files.&#xA;Options The following table list all Tetragon daemon available options and is automatically generated using the tetragon binary --generate-docs flag. The same information can also be retrieved using --help.</description>
    </item>
    <item>
      <title>Helm chart</title>
      <link>/docs/reference/helm-chart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/reference/helm-chart/</guid>
      <description>The Tetragon Helm chart source is available under github.io/cilium/tetragon/install/kubernetes/tetragon and is distributed from the Cilium helm charts repository helm.cilium.io.&#xA;To deploy Tetragon using this Helm chart you can run the following commands:&#xA;helm repo add cilium https://helm.cilium.io helm repo update helm install tetragon cilium/tetragon -n kube-system To use the values available, with helm install or helm upgrade, use --set key=value.&#xA;Values Key Type Default Description affinity object {} crds.installMethod string &amp;quot;operator&amp;quot; Method for installing CRDs.</description>
    </item>
    <item>
      <title>gRPC API</title>
      <link>/docs/reference/grpc-api/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/reference/grpc-api/</guid>
      <description>The Tetragon API is an independant Go module that can be found in the Tetragon repository under api. The version 1 of this API is defined in github.com/cilium/tetragon/api/v1/tetragon.&#xA;tetragon/bpf.proto BpfCmd Name Number Description BPF_MAP_CREATE 0 Create a map and return a file descriptor that refers to the map. BPF_MAP_LOOKUP_ELEM 1 Look up an element with a given key in the map referred to by the file descriptor map_fd. BPF_MAP_UPDATE_ELEM 2 Create or update an element (key/value pair) in a specified map.</description>
    </item>
    <item>
      <title>Metrics</title>
      <link>/docs/reference/metrics/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/reference/metrics/</guid>
      <description>Tetragon Health Metrics tetragon_bpf_error_metrics_total The total and type of errors encountered exposed via the BPF error metrics API. Internal use only.&#xA;label values error 22 error_name EINVAL file_name bpf_d_path.h helper_func FnProbeRead line_number 166 tetragon_bpf_missed_events_total Number of Tetragon perf events that are failed to be sent from the kernel.&#xA;label values error E2BIG, EAGAIN, EBUSY, EINVAL, ENOENT, ENOSPC, unknown msg_op 13, 14, 15, 16, 23, 24, 25, 26, 27, 28, 5, 7 tetragon_build_info Build information about tetragon</description>
    </item>
    <item>
      <title>Tracing Policy</title>
      <link>/docs/reference/tracing-policy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/reference/tracing-policy/</guid>
      <description>A TracingPolicy is a user-configurable Kubernetes custom resource (CR) that defines how Tetragon observes events in both the kernel and userspace using eBPF. It supports a variety of hook points including kprobes, uprobes, tracepoints, LSM hooks, and USDTs, giving users fine-grained control over what to trace and what actions to take. Policies consist of hook points, selectors for in-kernel filtering, and optional actions that can be executed when a match occurs.</description>
    </item>
  </channel>
</rss>
