NautheraAuditPartitionsNotMaintained
Docs version v1 (main)Nauthera is pre-1.0, in a design-partner program
Audit log partitions for the coming months are missing.
Meaning
nauthera_ has been above 0 for an hour:
partitions the maintenance keeps ready ahead of the writes are missing. With
audit. the maintenance CronJob (appendOnlyAudit) has
not run lately or is failing; with internal, the server's own pass, every
audit. (6h), cannot create them. Nothing fails until a month
without a partition begins.
Impact
Nobody is affected yet. If nothing is done before the first missing month starts (UTC), NautheraAuditPartitionMissing follows, with its risk of an outage at the next restart under external maintenance.
Diagnosis
- How many:
nauthera_.audit_ partitions_ missing{job="<name>"} - External:
kubectl -n <ns> get cronjob <name>-maintain -o wide(is it suspended? when did it last succeed?),kubectl -n <ns> get jobs, and the failing run's log. The server logsaudit log partitions for the coming months are missing; .at each check, with the. . missingpartition names. - Internal:
kubectl -n <ns> logs <pod> | jq 'select(.. The failure is also recorded as a failedmsg|startswith("could not create audit log partitions"))' system..audit. partition_ created
Mitigation
- External: run it now,
kubectl -n <ns> create job --from=cronjob/, and fix whatever stops the scheduled runs (a suspended CronJob, a failing image pull, an expired owner credential,<name>-maintain <name>-maintain-manual activeDeadlineSecondstoo short for an index build). - Internal: fix what the log names, usually privileges or a lock timeout; the next pass or a pod restart creates the partitions.
Escalation
No page. Escalate to the identity platform owner if the cause is not fixed within a few
days, and well before the month boundary. Open an issue if maintain succeeds but the
server still reports partitions missing, with the maintenance log and the partition list.
Alert runbooks · Generated from internal/ and operator/ in nauthera-server.