Skip to content

docs: inputs: ebpf: document tcp trace type #2549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eschabell merged 1 commit into from
Apr 20, 2026
+18 −2
Merged

docs: inputs: ebpf: document tcp trace type #2549

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 18 additions & 2 deletions pipeline/inputs/ebpf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The plugin supports the following configuration parameters:
|:----|:------------|:--------|
| `poll_ms` | Set the polling interval in milliseconds for collecting events from the ring buffer. | `1000` |
| `ringbuf_map_name` | Set the name of the eBPF ring buffer map to read events from. | `events` |
| `trace` | Set the eBPF trace to enable (for example, `trace_bind`, `trace_malloc`, `trace_signal`, `trace_vfs`). This parameter can be set multiple times to enable multiple traces. | _none_ |
| `trace` | Set the eBPF trace to enable (for example, `trace_bind`, `trace_malloc`, `trace_signal`, `trace_tcp`, `trace_vfs`). This parameter can be set multiple times to enable multiple traces. | _none_ |

## System dependencies

Expand Down Expand Up @@ -130,7 +130,7 @@ All traces include the following fields:

| Field | Description |
|:------|:------------|
| `event_type` | Type of event (`signal`, `malloc`, `bind`, or `vfs`). |
| `event_type` | Type of event (`signal`, `malloc`, `bind`, `tcp`, or `vfs`). |
| `pid` | Process ID that generated the event. |
| `tid` | Thread ID that generated the event. |
| `comm` | Command name (process name) that generated the event. |
Expand Down Expand Up @@ -166,6 +166,22 @@ The `trace_bind` trace includes these additional fields:
| `bound_dev_if` | Network device interface the socket is bound to. |
| `error_raw` | Error code for the bind operation (`0` indicates success). |

### TCP trace fields

The `trace_tcp` trace captures TCP connection lifecycle events and includes these additional fields:

| Field | Description |
|:------|:------------|
| `event_type` | TCP event subtype (`listen`, `accept`, or `connect`). |
| `fd` | File descriptor for the socket. |
| `backlog` | Listen backlog size (for `listen` events). |
| `new_fd` | New file descriptor returned by the kernel (for `accept` events). |
| `peer_port` | Remote peer port number (for `accept` events). |
| `peer_addr` | Remote peer IP address (for `accept` events). |
| `remote_port` | Remote port number (for `connect` events). |
| `remote_addr` | Remote IP address (for `connect` events). |
| `error_raw` | Error code for the operation (`0` indicates success). |

### `VFS` trace fields

The `trace_vfs` trace includes these additional fields:
Expand Down
Loading