Skip to content

Engine-side telemetry for service twins (workflow grouping) #36

Description

@andre-merzky

Service-mode twins get task-level telemetry for free from the endpoint's rhapsody plugin, and the xGFabric report set renders from it unmodified. Two things only the engine side can provide:

  1. asyncflow.workflow_id stamping — the standalone demos wrap runs in workflow_scope(); the service engine runs none, so per-workflow gantt grouping degenerates.
  2. flow.start_telemetry(...) equivalents (resource polls at the engine host, checkpoint path control).

Proposal: an optional per-engine config knob in the session config (e.g. "telemetry": {"checkpoint_path": ...}) that _build_engine honors, plus an opt-in workflow scope per twin. Surfaced converting the xGFabric twin to service mode (radical-cybertools/xGFabric PR "Service twin: telemetry reports").

🤖 Generated with Claude Code

https://claude.ai/code/session_016Npyz3Hbnwos12ESsdJ2YU

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions