kx events
Shows Kubernetes events recorded against the exact object each index names — unlike kx logs, this doesn’t reach into the pods a Deployment or StatefulSet owns.
--since bounds how far back the listing looks, in the same vocabulary kx diag reads — s, m, h or d: 90s, 30m, 12h, 7d. Without it every event the cluster still holds is listed — on a default cluster roughly the last hour, since that is how long the API server keeps an event before dropping it. Set events_max_age in config.toml to choose a window once rather than per run.
Usage
kx events [OPTIONS] <index>...Arguments
| Argument | Description |
|---|---|
<index>... | Row number from the current listing, or @name for a mark; kx state or kx mark shows them |
Options
| Option | Description |
|---|---|
--since string | Only events newer than this; s, m, h or d: 90s, 30m, 12h, 7d. Defaults to events_max_age, which is unset: every event the cluster still holds is listed |
Global options
| Option | Description |
|---|---|
--no-color | Disable styled output |
-h, --help | Show this message and exit |
Examples
kx events 1
kx events 1 2
kx events 1 --since 30m
kx events 1..3
kx events 3..