[session 1] docs: four operational traps (journal amounts, core.version pin, log levels, OOM ordering) #45
Reference in New Issue
Block a user
Delete Branch "docs/four-operational-traps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #44
Session: 1
Four traps that had each already bitten, two of them twice, none written down where the next person would look. Surfaced by auditing sessions 1-3 merged PRs against Guide coverage.
Verified against source, not from the audit summaries:
JournalParser.java:38-54- mask covers leading digits; DISPENSED matched separately and wins; whitelist excludes BALANCE/ATM OWNER FEE/SUBTRACThiveops-agent/pom.xml:44-hiveops.agent.core.versionis a separate property from<version>compose/aria.yml:14-16- carries an inline comment confirming root-logger override, measured on hiveiq-journalcompose/journal.yml(+500 x11),infrastructure.yml(-900),agent-proxy.yml(-900)Deliberate choices: the journal section flags an unresolved question (whether pre-fix rows are 0 or absent) rather than guessing, since it affects figures quoted to customers. The devops.prod section gives a grep for live heap values instead of copying numbers that would drift.
Left as Refs rather than Closes so the issue stays open until the rendered pages are eyeballed.