4.4 KiB
06 — Parsers
Parsers live in a separate module
All archive/vendor-format parsing and the Redfish raw-payload replay/analysis engine
live in git.mchus.pro/reanimator/parser/v31 (a plain Go module dependency, see
ADL-2026-10-08). logpile does not implement or register parsers itself anymore.
The dependency is pinned to the published v31.0.0 (ADL-084), without a local
parser replacement. This includes Lenovo XCC mini-log and full FFDC .tzz
archives, binary component journals, Linux service journals and structured
component activity with historical identities and firmware. Existing PAX tar.gz,
nvidia-smi inventory and Inspur audit support are retained. Reopen stored
archives to apply the updated parsing behavior.
The module supplies supported file extensions and registered parser versions
to /api/file-types and /api/parsers; upload and batch conversion use those
capabilities directly. Lenovo diagnostic/configuration evidence remains in
raw_payloads.lenovo_xcc; structured component activities remain on the shared
AnalysisResult.events model. Historical components do not become current
hardware inventory.
The vendor coverage matrix, detection rules, per-vendor data-quality notes, and the
VendorParser contract are documented in that repository's own bible-local/
(06-parsers.md equivalent, decisions log) — read it there, not here, when working on
parsing/interpretation behavior. This file only covers the boundary: what logpile owns,
what it hands to the module, and what comes back.
What logpile still owns
- Live BMC/Redfish collection (
internal/collector/redfish.go): crawling, HTTP session handling, prefetch/recovery, telemetry — everything that talks to a real BMC. - Acquisition-time tuning (
internal/collector/redfishprofile/):CollectSignals,MatchProfiles,BuildAcquisitionPlan,ResolveAcquisitionPlandecide worker counts, which paths to prefetch, and retry/post-probe policy during the crawl. This package also still carriesApplyAnalysisProfiles/PostAnalyzeand their supporting types, which are now unreachable in logpile (that half of the package is exercised only inside the parser module's own copy) — left in place rather than split out, since the package'sProfileinterface bundles both concerns and splitting it would just duplicate work already done once on extraction. - The web server, DB layer, exporter, and UI/visualization.
- A small local dedup/scoring helper set in
internal/collector/redfish_dedup.go(dedupeRedfishPaths,redfishHostSystemScore,lastRedfishPathSegment) — generic utilities the live crawler needs directly; also present inside the parser module's own copy of the same logic, intentionally duplicated rather than shared, since the module does not expose internal packages.
What the module owns and how logpile calls it
Two entry points on git.mchus.pro/reanimator/parser/v31's Service:
Service.AnalyzeArchivePayload(filename string, payload []byte) (*models.AnalysisResult, string, error)— uploaded archive parsing. Used byinternal/server/handlers.go(upload flow) andcmd/logpile-cpu-audit.Service.AnalyzeRedfishRawPayloads(rawPayloads map[string]any, meta RedfishSourceMetadata) (*models.AnalysisResult, string, error)— the single call at the end ofRedfishConnector.Collect()(internal/collector/redfish.go): the crawl builds a rawrawPayloadstree (redfish_tree,redfish_profiles,redfish_telemetry,redfish_fetch_errors,redfish_log_entries,redfish_debug_payloads), then hands it to the module for the actual doc-to-model interpretation. This same call point also serves raw Redfish-tree archive imports (live_redfishsource inhandlers.go), so live collection and offline raw-tree import share one analyzer, one interpretation.
Top-level helpers also used directly: ListParsersInfo(), IsSupportedArchiveFilename(),
SupportedArchiveExtensions(), ParseInDefaultArchiveLocation(), PrivacyScanEnabled(),
and the pciids package (git.mchus.pro/reanimator/parser/v31/pciids) for PCI
vendor/device name lookups in both the live collector and the exporter.
models package
git.mchus.pro/reanimator/parser/v31/models is used directly everywhere in logpile;
there is no local internal/models anymore (fully repointed, 2026-10-08). The module's
models package is kept strictly additive against what logpile used to define, so this
needed no adapter.