Skip to content

Telemetry deferrals from 107: per-region statistics, failure kinds, latency #61

Description

@IanMayo

Recorded in specs/107-operator-view/spec.md ("Deliberately not in this feature"):

  • Per-region residual statistics (scope.level: 'region'): the master carries the shape; the scenario-level scope serves the demo. Build when a consumer wants regional skill.
  • run_failed / publication_refused telemetry kinds: no failure path produces them — the runner throws on a store refusal, which is a defect signal, not telemetry. Wire them when a genuine failure path exists (V3's real offload transfer is the obvious producer).
  • End-to-end latency in simulation time: throughput per sim-second landed; the latency display waits for a consumer that reads it.

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