Audit log coverage
The operations that yoink records in the audit log and the operations that it does not record.
Recorded
yoink records each yoink up run. A rollback deploys through up, so yoink records it as an up run.
RunStarted/RunFinished: one pair for each run.LockAcquired/LockReleased: one pair for each host. The time between the two events is the hold time of the lock.ContainerCreated: one for each completed swap of a service on a host.DeployFailedwithlog_tailwhen a healthcheck never passes.HookStarted/HookFinished: one pair for each hook run, in the operator log. A failed hook has noHookFinished.WebhookFired: one for each webhook call.- Progress events, for example
PullStarted,NetworkReady, andHealthcheckHealthy. These events give more detail for triage.
Not recorded
yoink pruneandyoink secrets rotate. These commands write no events.- Read commands:
status,history,doctor,diff,tui,audit log,secrets show,secrets env. A run ofaudit logdoes not appear in its own output. - Operator identity other than
$USER@$HOSTNAME. No central identity provider exists. The field is for information only. - Secret values. Event payloads contain names, never values.
See also
- Audit event schema: the fields of each event variant, and the storage paths.
- Read the audit log: the commands that read and filter the log.
- Security: the security model that the audit log is a part of.