Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Stall Detection #2712

Open
NickCraver opened this issue May 7, 2024 · 0 comments
Open

Feature: Stall Detection #2712

NickCraver opened this issue May 7, 2024 · 0 comments

Comments

@NickCraver
Copy link
Collaborator

Talking on the weekly sync, basic idea is we have a timer that fires say once per second. We only need 1 entire process (static, not per-multiplexer).

Overall setup:

  • 1 static timer
  • Timer fires once per second, recording 3 values:
    • Timespan since the last timer fire ("is this a stall?")
    • Timestamp of the current run (for the next cycle)
    • Stall data - (string describing the stall, or clearing it if there's no stall)
  • Exception messages include this new stall data if present

Question:

  • What is a stall? (e.g. how long?) - 1 sec timer took 2+ to fire?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant