it would be nice to have long time metrics of the module like the ccu curve over the last month and the corresponding energy cost data. currently it is near impossible to tell what happened to the module if we don't have it actively running while something bad happens and even for the few metrics that are loading a bit of the past, it isn't showing enough of the past to tell what happened a day later.
again this would be a lot easier if the metrics would be stored in a st_metrics (event) table and read from the clog for the dashboard to get the data for a specified time (like the last month in x steps per hour accumulated and/or not)
Requested by @xDovos via the SpacetimeDB site.
it would be nice to have long time metrics of the module like the ccu curve over the last month and the corresponding energy cost data. currently it is near impossible to tell what happened to the module if we don't have it actively running while something bad happens and even for the few metrics that are loading a bit of the past, it isn't showing enough of the past to tell what happened a day later.
again this would be a lot easier if the metrics would be stored in a st_metrics (event) table and read from the clog for the dashboard to get the data for a specified time (like the last month in x steps per hour accumulated and/or not)
Requested by @xDovos via the SpacetimeDB site.