Prints each project event as one line (one JSON object per line with –json): its sequence, type and time. Start from –since, the sequence of the last event you already have (default 0, everything); the command reconnects by itself from the last event it printed, so nothing is skipped or repeated. It stops after –limit events. Needs the read scope.
Usage
overlane events watch [--since SEQUENCE] [--limit N]Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--since |
string | no | Sequence number of the last event already received (default 0) | |
--limit |
string | no | Stop after N events (default: keep following) |
Examples
overlane events watch
overlane events watch --since 120 --limit 20 --jsonBehavior
- Effect:
read(changes nothing). - Needs credentials: yes. Uses the network: yes.
- Supports
--dry-run: no. Accepts--force: no. - Machine-readable description:
overlane schema events watch.
Result
With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.
{
"type": "object",
"properties": {
"received": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"cursor": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
}
},
"required": [
"received",
"cursor"
],
"additionalProperties": false
}See exit codes for the status the process returns.