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

Add checks to assess if the server machines are correctly pinging the API #231

Open
AlbertoCasasOrtiz opened this issue Oct 15, 2024 · 1 comment
Assignees
Labels
Caution Be careful merging or implementing this. enhancement New feature or request

Comments

@AlbertoCasasOrtiz
Copy link
Collaborator

We can do this in the dequeue function, save the information about last time a machine pinged the API in a local file (in the API machine, be careful with race conditions), and send an email in case a machine has not been pinging the API for more than a day (discuss period of time).

@AlbertoCasasOrtiz AlbertoCasasOrtiz added enhancement New feature or request Caution Be careful merging or implementing this. labels Oct 15, 2024
@AlbertoCasasOrtiz AlbertoCasasOrtiz self-assigned this Oct 15, 2024
@carmichaelong
Copy link
Contributor

Some other possible ideas:

  • For each IP, provide the latest associated trial "updated at" time. When servers are busy enough, will be easy to see that there is likely an issue that happened a few hours back.
  • For each IP, maybe the last ~5-10 status (error or done) counts to get info on if a machine might be starting to fail. There might be some misleading signals, though, if someone doesn't have the right setup and has a lot of errors for calibration or neutral trials.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Caution Be careful merging or implementing this. enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants