-
Notifications
You must be signed in to change notification settings - Fork 0
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
Improve Activity History #188
Labels
Milestone
Comments
dostuffthatmatters
added a commit
that referenced
this issue
Oct 24, 2023
Add new activity history component
dostuffthatmatters
added a commit
that referenced
this issue
Oct 24, 2023
Replace current activity logs with new ones
dostuffthatmatters
added a commit
that referenced
this issue
Oct 24, 2023
Simplify activity history dumping logic
dostuffthatmatters
added a commit
that referenced
this issue
Oct 24, 2023
Add all activity properties to interface
dostuffthatmatters
added a commit
that referenced
this issue
Oct 24, 2023
Add graceful teardown hook to write out activity logs
dostuffthatmatters
added a commit
that referenced
this issue
Oct 24, 2023
Move graceful teardown hook out of loop also listen to signal when closing the terminal
dostuffthatmatters
added a commit
that referenced
this issue
Oct 25, 2023
Move activity history code from utils to interfaces and types
dostuffthatmatters
added a commit
that referenced
this issue
Oct 26, 2023
Move activity history code from utils to interfaces and types
dostuffthatmatters
added a commit
that referenced
this issue
Oct 26, 2023
Move activity history code from utils to interfaces and types
dostuffthatmatters
added a commit
that referenced
this issue
Oct 27, 2023
Render new activity history in UI
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, the logic of rendering the activity history is quite complicated and error-prone. Instead of logging the times of starting/stopping certain events (errors, etc.), we should log a datapoint about the current state every minute. I am doing this now, because I heavily simplified the frontend code for 4.1.0 anyways.
Math when storing one of these datapoints per minute:
Writing the data every 5 minutes is enough because on a 24 hour plot, we are barely able to see anything more recent than 5 minutes ago. Nevertheless, we still plot a cell for every minute.
Notice that we have no field
core_is_running
because that is implied when records are present. Also, we have the new fieldsis_uploading
,camtracker_startups
,opus_startups
andcli_calls
:)The text was updated successfully, but these errors were encountered: