Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

Implement Priority Scheduled Telemetry #16

Open
stulewin opened this issue Apr 9, 2023 · 1 comment
Open

Implement Priority Scheduled Telemetry #16

stulewin opened this issue Apr 9, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@stulewin
Copy link
Contributor

stulewin commented Apr 9, 2023

Some telemetry needs to be updated on the period of the main loop (20 msec) but not everything does - and this is also (I believe) a reason for sometimes overrunning the main loop and also perhaps sending too much data to the laptop Dashboard. Something like 20 msec, 500 msec and 1000 msec might be a good baseline for this.

@stulewin
Copy link
Contributor Author

stulewin commented Apr 9, 2023

Pass in an integer priority to the call to log telemetry, and then use that for each supplier to determine what if any gets logged. Could use a falling through switch statement to get it - or perhaps skip the higher priority ones when the lower are being done?

@Java4First Java4First added the enhancement New feature or request label Apr 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants