AstraLog-HPC — Mission Control Dashboard

📄 Data Sources — read from C++ pipeline output files (parallel dual-broker ingestion)

Both brokers are ingested concurrently by the C++ adapter — this view mirrors its merged_summary.json Source: results_slurm_g100/ | polled every 5s

HiveMQ #1 No data yet

fb2fb70e5df845aaa8ac44ead8e3c5e1.s1.eu.hivemq.cloud

ingested by C++ MQTTIngestionAdapter (label: hivemq-1)

—

HiveMQ #2 No data yet

03631557be364439a74d8fe1331c24e8.s1.eu.hivemq.cloud

ingested by C++ MQTTIngestionAdapter (label: hivemq-2)

—

Looking for pipeline output files…

—

Pipeline — FR-01…12 · v1.0: 20 rules, 4 types, config-driven

INGEST

MQTT / CSV

▶

VALIDATE

IngestionValidator

▶

RULES

simple · step_diff · stateful · corr

▶

CLASSIFY

AnomalyClassifier

▶

OUTPUT

valid_data.csv · alarms.log

Total Received

—

Validated

—

Anomalies

—

Anomaly Rate

of validated

📈 Telemetry — per subsystem · anomalies marked ●

⚠️ Anomalies by Subsystem

Distribution stacked nominal · anomaly

ABS-001 reference band ± 100 Display only — anomalies are classified by the C++ RuleEngine, not recomputed here

#	Timestamp (UTC)	Subsystem	Sensor	Value	Severity	Rules
Waiting for anomaly events…

#	Timestamp (UTC)	Subsystem	Sensor	Value	Priority	Status
Waiting for telemetry…

#	Timestamp (UTC)	Kind	Detail	Raw payload (as received)
Waiting for corruption_log.json…

🏥 Component Health pass-rate · NFR-16 target ≥ 0.98

Theoretical availability (Ex04 — series + k=2 replication):

A = 0.97 × 0.99 × 0.98 × 0.99 = 0.9315 → k=2 replicas → ≈ 0.988 ✓

📡 Mission Messages — live feed

[system]Dashboard v1.0 ready — reading C++ pipeline output files (sole MQTT consumer is the adapter, GAP-03-2/DD-06); simulation running until results files are found