Create design-update.md #40
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oesteban
reviewed
Feb 11, 2022
Co-authored-by: Oscar Esteban <[email protected]>
oesteban
reviewed
Feb 14, 2022
|
|
||
|
|
||
| ## Message packets | ||
|
|
There was a problem hiding this comment.
Suggested change
| - Try TCP/Restful first, resort to UDP if communication fails |
| - ETA (progress bar or such, using previously acquired stats from other users) | ||
|
|
||
| ## Wishlist | ||
| - use a more generic logging tool as the backend (like prometheus) |
There was a problem hiding this comment.
Suggested change
| - use a more generic logging tool as the backend (like prometheus) | |
| - identification logic to establish user/session constructs that allow: 1) defining a "unique users" concept; 2) defining "exit points" where sessions are aggregated (i.e., 90% of the processes ended on this particular error). | |
| - use a more generic logging tool as the backend (like prometheus) |
| - Relevant options | ||
| - "Session" information | ||
| - "User" information | ||
| - (possibly) Elapsed time |
There was a problem hiding this comment.
Suggested change
| - (possibly) Elapsed time | |
| - (possibly) Input dataset hash - so that we could identify open data executions (if the dataset is run unaltered). | |
| - (possibly) Elapsed time |
mgxd
reviewed
Mar 9, 2022
| i would like to avoid. | ||
| - make querying, accessing, and doing analytic plots | ||
| - spin up your own backend on heroku/some such | ||
|
|
There was a problem hiding this comment.
Suggested change
| - revisit backend DB choice (mongo/sqlite/redis) |
| (even though not advertised). if messages become arbitrary, we may need | ||
| registration/auth tokens. brings up a whole different level of complexity that | ||
| i would like to avoid. | ||
| - make querying, accessing, and doing analytic plots |
There was a problem hiding this comment.
+1 to making the data acquired more usable, just need to be mindful of large server load increase
|
Here's an ongoing draft: https://github.com/mgxd/fastapi-telemetry A few design notes on the backend:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Design doc for next version of the etelemetry service