Skip to content

JUNO Monitoring Agent — Planned

Status: planned / not yet implemented

Objective

A JUNO-side integration should provide the same normalized observability available from HCMR without coupling JUNO production to the central monitor.

The preferred future repository is:

medmfc-monitoring-agent-juno

Expected responsibilities

  • observe JUNO production/upload state;
  • report cycle start, file readiness, upload, DNT and response state;
  • provide periodic heartbeat;
  • report takeover/fallback activation;
  • expose enough evidence to detect overlapping HCMR/JUNO ownership;
  • remain non-blocking if the monitoring endpoint is unavailable.

Target relationship

flowchart LR
    JP[JUNO Production] --> JA[JUNO Agent]
    JA -->|HTTPS telemetry| MON[Central Monitoring]
    HA[HCMR Agent] -->|HTTPS telemetry| MON
    MON --> CYCLE[Cycle / Ownership State]
    CYCLE --> UI[Dashboard]

Important design requirement

The current legacy mechanism is asymmetric: JUNO can inspect copernicus01 progress, while Neptune does not reliably receive an authoritative successful JUNO takeover signal.

The future JUNO integration should therefore not merely reproduce the legacy progress-file mechanism. It should report normalized cycle ownership and activity to the common coordinator/monitoring service.

Security

Secrets must remain in protected node-local configuration. No JUNO credentials should be committed to Git or copied into the documentation repository.