Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature Request / Clarification] External read-only telemetry and lifecycle observation over mw::com

Aperta
  • Qualcosa non va?
#817 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
api, backend

Direzione di ricerca

Start by reading score/launch_manager/src/lm_control/, the ILmControl and LmControlService definitions, and requirement comp_req__launch_man__ext_monitor_notify. Determine the intended read-only pull API and cross-process event service, then trace how the daemon exposes lifecycle and supervision state. Done means the architecture and implementation scope for both observer needs are agreed and documented.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Feature Request / Modification Description
Objective & Architectural Clarification

We are exploring the design of an external, read-only telemetry and safety evidence collector (such as a Vehicle Evidence Logger / monitor) that observes the S-CORE Lifecycle and Health Monitoring subsystem.

Under safety guidelines, an external observer must remain strictly read-only (observing runtime state without possessing control privileges). Specifically, the observer requires:

  1. Active Run Target (PULL): Querying the currently active system run target (e.g., Startup, Running, fallback).
  2. Process & Supervision Telemetry (PUSH): Observing real-time process lifecycle states, PIDs, alive indications, and supervision failure events (e.g. deadline violations).
Current Observations in Upstream
  1. Control vs Read-Only Query: score::mw::lifecycle::ControlClient is strictly a control/write interface (ActivateRunTarget()) intended for State Management over shared memory. It lacks query APIs (e.g., get_active_run_target()), and using a control channel for observation would violate read-only safety isolation boundaries.
  2. ILmControl via mw::com: In score/launch_manager/src/lm_control/, there is a defined public interface ILmControl with get_active_run_target() and an mw::com service definition (LmControlService). However, the production launch_manager daemon does not currently host an LmControlSkeleton to offer this service over mw::com at runtime.
  3. Process Supervision Telemetry: Requirement comp_req__launch_man__ext_monitor_notify specifies publishing process monitoring data (state, PID, supervision results, exit codes), but an active cross-process mw::com event service is not currently instantiated in the daemon.
Requested Clarifications / Feature Scope
  1. Is the intended architectural direction for Launch Manager daemon to host LmControlSkeleton and offer ILmControl::get_active_run_target() over mw::com as the standard public pull API for external observers?
  2. How is comp_req__launch_man__ext_monitor_notify intended to be exposed across process boundaries? (e.g., via a MonitorNotify event on LmControlService over mw::com or a dedicated monitoring event service?)
Expected Changes of work products
  • Requirements
  • Architecture
  • Safety Analysis
  • Security Analysis
  • Detailed Design
  • Implementation and Testing
  • all
Impact analysis
  • Functional Impact: Enables external read-only observers and monitoring tools to retrieve active run targets and subscribe to process lifecycle & supervision events via standard mw::com IPC without needing write privileges.
  • Architectural Impact: Launch Manager daemon offers an mw::com service skeleton (LmControlService), bridging ProcessGroupManager runtime states and alive supervision results to external subscribers.
  • Backwards Compatibility: Non-breaking. Systems running without mw::com or without external observers can continue running Launch Manager in legacy/standalone mode.
  • Dependencies: Uses existing S-CORE mw::com middleware and existing score/launch_manager/src/lm_control service definitions.
Safety or Security relevance
  • none
  • Safety relevant
  • Security relevant
Expected required ASIL classification

ASIL_B

Expected Implementation Version (Release)

1.0

Lingua principale
C++
Stelle
6
Fork
35
Merge medio
2g 9h
PR unite (30g)
93

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eclipse-score/lifecycle

Tutte le issue di eclipse-score/lifecycle

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.