chore(rs2000): add journald cap and disk threshold alerts #798

Closed
opened 2026-06-17 21:27:26 +02:00 by codex · 0 comments
Collaborator

Summary

RS2000 now has Docker log rotation and BuildKit GC, but journald and host-level alert thresholds are still policy-only. The closeout observed about 4G in journald and a healthy root filesystem at 58%, but there is no explicit early warning before 75%/85%.

Scope

  • Add an explicit journald size/age policy for RS2000.
  • Add or document root filesystem threshold checks: warn at 75%, urgent/operator attention at 85%.
  • Keep this read-mostly and policy-driven; do not surprise-delete logs.
  • Integrate with the existing disk report timer or an adjacent host-ops timer.

Spec sources (whitelist)

  • runbooks/rs2000-disk-hygiene.md
  • state/reports/rs2000-disk-hygiene-2026-06-17.md
  • state/reports/rs2000-runtime-health-closeout-2026-06-17.md

Do NOT read

  • Application logs beyond aggregate disk usage.
  • Secret-bearing runtime env files.
  • Full repo unless the existing disk report implementation points to a specific file.

Extracted context

Closeout baseline:

/dev/vda3 503G 276G 207G 58% /
/var/log/journal around 4G observed during investigation

Acceptance criteria

  • Journald cap is documented and implemented through a reversible systemd/journald config change.
  • Disk threshold behavior is documented and tested in dry-run/mock form before live rollout.
  • Existing platform-disk-report.timer either includes thresholds or points to the new check.
  • Verification includes journalctl --disk-usage, df -h /, and timer status.

Hard stops

  • Do not run destructive log vacuum as an unreviewed cleanup shortcut.
  • Do not delete application logs or Docker volumes.
  • Do not page/notify external systems until the notification path is explicitly reviewed.

Source

Created from RS2000 runtime health closeout on 2026-06-17.

## Summary RS2000 now has Docker log rotation and BuildKit GC, but journald and host-level alert thresholds are still policy-only. The closeout observed about 4G in journald and a healthy root filesystem at 58%, but there is no explicit early warning before 75%/85%. ## Scope - Add an explicit journald size/age policy for RS2000. - Add or document root filesystem threshold checks: warn at 75%, urgent/operator attention at 85%. - Keep this read-mostly and policy-driven; do not surprise-delete logs. - Integrate with the existing disk report timer or an adjacent host-ops timer. ## Spec sources (whitelist) - `runbooks/rs2000-disk-hygiene.md` - `state/reports/rs2000-disk-hygiene-2026-06-17.md` - `state/reports/rs2000-runtime-health-closeout-2026-06-17.md` ## Do NOT read - Application logs beyond aggregate disk usage. - Secret-bearing runtime env files. - Full repo unless the existing disk report implementation points to a specific file. ## Extracted context Closeout baseline: ```text /dev/vda3 503G 276G 207G 58% / /var/log/journal around 4G observed during investigation ``` ## Acceptance criteria - Journald cap is documented and implemented through a reversible systemd/journald config change. - Disk threshold behavior is documented and tested in dry-run/mock form before live rollout. - Existing `platform-disk-report.timer` either includes thresholds or points to the new check. - Verification includes `journalctl --disk-usage`, `df -h /`, and timer status. ## Hard stops - Do not run destructive log vacuum as an unreviewed cleanup shortcut. - Do not delete application logs or Docker volumes. - Do not page/notify external systems until the notification path is explicitly reviewed. ## Source Created from RS2000 runtime health closeout on 2026-06-17.
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#798
No description provided.