Add asset host logs ingest and UI
This commit is contained in:
7
bible-local/decisions/2026-03-15-asset-log-ingest.md
Normal file
7
bible-local/decisions/2026-03-15-asset-log-ingest.md
Normal file
@@ -0,0 +1,7 @@
|
||||
# 2026-03-15 - Asset Log Ingest Is Separate From History
|
||||
|
||||
- Date: `2026-03-15`
|
||||
- Decision: Host/BMC/Redfish event logs are accepted as a separate ingest payload (`event_logs`) and stored in a dedicated asset log read model with dedup/upsert semantics. They are not written to history events, snapshots, or timeline cards.
|
||||
- Context: Operational logs may contain useful diagnostics, but their semantics, duplication patterns, and lifecycle differ from canonical asset/component state mutations. Mixing them into history/timeline would pollute domain events and break history-first invariants.
|
||||
- Consequences: Hardware ingest contract must define `event_logs` as an optional raw/normalized log section. Persistence must use a separate table family (not `timeline_events`). UI must expose a dedicated asset log section/page with source/severity/date filters. Future derivations from logs into domain signals must be explicit secondary rules, not implicit by ingest.
|
||||
- Supersedes: No prior explicit decision.
|
||||
Reference in New Issue
Block a user