As it stands right now metrics are directly submitted to the database - With DEMU submitting 6 sensor's measurements off one node every second we generate ~60 bytes/second/sensor. Over the course of one day (86400 seconds) we generate 31104000 bytes of data (86400 * 60 * 6). That is 31.104 Megabytes / day from one node with six sensors.

We need to be able to rollup data older than a few hours or at intervals (60min, 24hrs, Week, Month, Year)

Thinking it might be a good idea to modify the database and add a field to each entry to indicate if its raw, or rolled and if rolled to what extent

We need unit tests for all the things.

registrar - add/ probe/ remove/ fetc
metric streaming - add/ delete streams & essentially implement the system_tests/stream_test but at compile time

Update crate and monolith so node registration and deletion / modification is done through a specific endpoint like

/registrar/add/<id>/<encoded_node>
/registrar/delete/<id>

Update crate and then also add a delete node in crate.

• Also : Update crate to offer functionality to register/de-register streams