-
Notifications
You must be signed in to change notification settings - Fork 23
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
Telemetry Database Handler Requirements #201
Comments
|
"define new telemetry items" means I want to store a new telemetry item. Basically, I'm integrating a payload, and I want to start storing the internal temperature of that payload. We need a way to put it in the right place and be handled properly. basically, just bulk telemetry |
Receive IP Messages - From where and about what? Telemetry categorization - Could the subsystem include the level of importance as a field in the telemetry message it sends? Unless you mean "for this subsystem, only store telemetry messages that are informational level or higher" |
IP - Basically GraphQL requests for telemetry and new telemetry items to log. So from everywhere. No, because you can have subsystem items that are more/less important, and you want to log everything on the spacecraft. Importance is only used to figure out what we want to downlink. |
Additional potential work item: periodically do SQLite integrity check or quick check to check for database corruption |
Yes to both of those! |
Must autoboot.... |
What does a telemetry DB handler need to do?
The text was updated successfully, but these errors were encountered: