feat(go): expose retained incident views
This commit is contained in:
parent
eff31b3a82
commit
6355fb403d
6 changed files with 166 additions and 7 deletions
|
|
@ -160,6 +160,17 @@ fails nonzero rather than forwarding corrupted evidence. It does not load the
|
|||
agent configuration, so retained evidence remains available while a broken
|
||||
configuration prevents the service from starting.
|
||||
|
||||
Inspect the isolated incident index without starting the agent:
|
||||
|
||||
```bash
|
||||
enodia-sentinel-go --incidents-list --state-dir /tmp/enodia-go-state
|
||||
enodia-sentinel-go --incident-show inc-20260722-101112-abcd --state-dir /tmp/enodia-go-state
|
||||
```
|
||||
|
||||
`--incident-show` returns `enodia.incident.view.v1` with the durable incident,
|
||||
available snapshot reports, and a time-ordered timeline. These read-only
|
||||
commands never modify or consult the Python daemon state.
|
||||
|
||||
`--fixture`, `--host`, `--timestamp`, `--proc-root`, and `--suid-root` exist for
|
||||
deterministic parity/testing. Fixture mode never activates the live baseline
|
||||
manager. Production work should continue to use the default live `/proc`,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue