Fix onboard WebKit preview and archive board telemetry locally
This commit is contained in:
DCCONSTRUCTIONS
@@ -0,0 +1,100 @@
|
||||
# Node local viewer and onboard system monitoring
|
||||
|
||||
## Approved operator job and placement
|
||||
|
||||
Owner request: investigate the black onboard window after local K1 START, and
|
||||
add «Мониторинг системы БК» to the selected apparatus in Fleet. The selected
|
||||
board owns measurements and history; UI navigation, capture and network outages
|
||||
must not control collection. This is a detail view in the existing Fleet
|
||||
workspace, not the compute-worker contour or a new primary navigation root.
|
||||
An independent System workspace would lose the selected apparatus context; a
|
||||
modal would constrain history inspection. The owner explicitly selected the
|
||||
apparatus-detail entry. Novelty class A: domain content in admitted composition.
|
||||
|
||||
Reuse SettingsCard, ApplicationPanel, Button, Select, StatusBadge, ResourceRow,
|
||||
Icon(activity/refresh/chevron-left), and the existing TelemetrySeries domain
|
||||
renderer. Domain cards contain current metrics; selected series shows source
|
||||
time, min/max/mean and gaps. No missing generic visual primitive is required.
|
||||
States: collecting, historical/offline, waiting for first sample, unavailable
|
||||
metric, storage failure, replication backlog, loading/query failure, empty range.
|
||||
No acquisition, provisioning, shell or host-reconfiguration action belongs here.
|
||||
|
||||
## Reproduced diagnosis
|
||||
|
||||
R17 installed WebKitGTK 2.52.6 on Ubuntu. Public standalone Rerun 0.36.3 starts
|
||||
and stays responsive using WebGL2. WebGPU is unavailable. RTCPeerConnection is
|
||||
undefined, and constructing it raises ReferenceError. The shared preview effect
|
||||
constructs that API synchronously after viewer readiness, outside its catch.
|
||||
Node had no React error boundary. The historical window and WebKit processes
|
||||
remained alive with an empty accessible document; Node/K1 services did not restart.
|
||||
App cgroup memory peak was about 811 MiB and OOM counters were all zero. Ten-minute
|
||||
sysstat samples cannot rule out brief peaks but do not support memory exhaustion.
|
||||
The camera consumer lease subsequently expired from queue age; that is a delivery
|
||||
symptom, not proof of GPU/RAM exhaustion.
|
||||
|
||||
Enabling WebKit's WebRTC setting alone and supplying missing GStreamer modules
|
||||
in an isolated diagnostic environment did not expose the API. No global graphics
|
||||
workaround or new browser engine is admitted on this evidence. The local carrier
|
||||
uses authenticated loopback HTTP and the same plugin-owned bounded RRD/fMP4
|
||||
delivery, acknowledgements, recording cursor and release logic. Remote paired
|
||||
WebRTC remains unchanged. There is no second capture implementation.
|
||||
|
||||
## Telemetry architecture and limits
|
||||
|
||||
An independent native collector samples Linux counters every second and commits
|
||||
to a dedicated local PostgreSQL/TimescaleDB database. It uses only an OS-protected
|
||||
Unix socket, with no database TCP listener or embedded credential. Acquisition
|
||||
does not depend on that service. CPU/RAM/swap/pressure, per-interface bytes and
|
||||
errors, per-disk I/O, filesystem capacity, temperatures, observable GPU counters,
|
||||
USB topology/link speed and service cgroup usage/OOM counters are separate series.
|
||||
Unsupported counters remain null with a reason; USB negotiated speed is never
|
||||
presented as measured traffic. No USB payload, process arguments or environment
|
||||
variables are collected. UI exceptions carry only category and asset positions.
|
||||
|
||||
Raw retention target: seven days, with a two-GiB database target and two-GiB free
|
||||
disk reserve. Capacity is checked once per minute; writes pause at the target
|
||||
and oldest completed hourly chunks are removed. This is not a strict filesystem
|
||||
quota: a minute of writes, WAL and temporary files may exceed the database target. Retention and capacity loss are visible, never disguised as zeros.
|
||||
Bounded batches replicate over the existing paired mTLS connection. Core commits
|
||||
idempotently before acknowledging; disconnects leave local collection running.
|
||||
Latest status and historical delivery cursors are distinct so a fresh snapshot
|
||||
cannot skip unreplicated history. Historical timestamps and boot identity survive
|
||||
reconnection. Core's local archive is queryable while the board is offline.
|
||||
|
||||
Acceptance must separate fixture checks, real host collection, local viewer
|
||||
compatibility and owner hardware scans. A healthy repeated laboratory scan does
|
||||
not establish critical-scenario qualification of the K1 Bridge contour.
|
||||
|
||||
|
||||
## Implementation acceptance before installation
|
||||
|
||||
A bounded native WebKitGTK probe on the owner Ubuntu loads the unmodified
|
||||
production hook through a minified Vite bundle. Its source is synthetic RRD
|
||||
(100 points) and a synthetic H.264/fMP4 camera; it cannot submit device commands.
|
||||
The 2026-09-07 22:28 UTC probe reports the error boundary present with the shell
|
||||
alive, then `hasScene=true`, `presented=true`, `cameraPresented=true`. Video time
|
||||
advances to 2.9 s. After the fixture ends, freshness expires while the scene
|
||||
remains. This establishes compatibility for these fixtures, not live K1 load.
|
||||
Local transport uses completed bounded reads, a stable viewer cursor and native
|
||||
EventTarget dispatch. Remote transport keeps WebRTC with guarded construction.
|
||||
|
||||
Native PostgreSQL 16.15 / TimescaleDB 2.29.2 was exercised using privately
|
||||
extracted signed packages and a temporary socket-only cluster. Three real host
|
||||
samples with 184 discovered metrics were committed and replayed in order. The
|
||||
temporary cluster was stopped and removed. Installed-service acceptance is a
|
||||
separate gate.
|
||||
|
||||
Core keeps seven-day raw data plus minute min/max/sum/count rollups. Long ranges
|
||||
use complete minute buckets, preserving extrema; the selected end is rounded
|
||||
to the last complete minute. Missing intervals break the plot. Replica writes
|
||||
run outside the control heartbeat; only a durable committed cursor is ACKed.
|
||||
The archive is a best-effort diagnostic record at one-second sampling resolution;
|
||||
unobserved subsecond peaks and unsupported hardware counters remain unproved.
|
||||
|
||||
Packages: Node 0.8.15 and K1 0.1.14, with exact signed Timescale OSS/loader
|
||||
2.29.2~ubuntu24.04-1615. The dedicated `16/ndc-monitor` PostgreSQL cluster has no
|
||||
TCP listener. Its service memory cap is 384 MiB, collector cap 128 MiB; CPU caps
|
||||
are 25% and 15% of one core respectively. An initial PostgreSQL install suppresses
|
||||
automatic creation of an unrelated default cluster through a temporary supported
|
||||
postgresql-common configuration drop-in, removed on installer exit. Acquisition
|
||||
is protected by the existing package preinst guard and is not a test action.
|
||||
Reference in New Issue
Block a user