rungar events
Show what the daemon has done: runners created, adopted, connected, starting jobs, removed and lost, and why, with how long each step took, providers a scale set found full or failing to create its runner, and scale sets paused, resumed, and given another min_runners by their schedule. The daemon keeps them in its events file, so they explain what happened while nobody was looking, and outlive a restart. Like the journal, it writes what is kept and exits; --follow keeps writing new events as they happen. With --json it writes one JSON object a line, for scripts.
Usage
$ rungar events [flags]
Flags
| Flag | Description |
|---|---|
-f, --follow | Keep writing new events as they happen. |
--json | Write JSON, one event a line. |
--provider string | Only the events on this provider: of its runners, and of it. |
--runner string | Only this runner’s events. |
--scale-set string | Only this scale set’s events. |
--since string | Only the events since a time, or for a duration: 2026-09-28, 10:30, 1h. |
-n, --tail int32 | Only the last this many events (default all kept). |
Global flags
| Flag | Description |
|---|---|
--socket string | The daemon’s socket (default $RUNGAR_SOCKET, or /run/rungar/rungar.sock). |