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

Abierto
  • ¿Algo no está bien?
#817 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp
Área
api, backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
C++
Estrellas
6
Forks
37
Merge medio
2 d 9 h
PR fusionados (30 d)
109

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eclipse-score/lifecycle

Todos los issues de eclipse-score/lifecycle

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.