Skip to content

kafka_dae_diagnostics: runstate readback #71

@Tom-Willemsen

Description

@Tom-Willemsen

Proposed logic:

  • If latest runInfo msg is a run stop
    • SETUP
  • If latest runInfo msg is a run start
    • If we have received 'recent' frames on _event topic for this run:
      • If percentage of vetoed frames in buffer of last N frames >=50%
        • If 'most' of the recent vetoed frames are from runcontrol vetoes:
          • WAITING
        • Otherwise
          • VETOING
      • If percentage of vetoed frames in buffer of last N frames < 50%
        • RUNNING
    • If we have not received 'recent' frames on _event topic for this run:
      • PROCESSING?

Pause/resume logic will also need adding after #39 - not yet clear how kdaectrl will notify consumers that a run is paused.

One option would be to make it a "paused veto" (hard veto which prevents events being emitted, but configured from software like runcontrol), which we could then treat in the same way as runcontrol from a consumer perspective.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status
In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions