Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#817 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
cpp
領域
api, backend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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

主要言語
C++
スター
6
フォーク
35
平均マージ
2日 7時間
マージ済み PR（30日）
97

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

eclipse-score/lifecycle のほかの issue

eclipse-score/lifecycle の issue をすべて見る

似ている issue

C++ の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。