clockworklabs / clockworklabs/SpacetimeDB
maincloud dashboard longtime metrics
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the maincloud dashboard metric-loading path and reviewing how existing metrics are retained and read from the clog. Inspect the proposed st_metrics event-table approach and how it could provide historical data. Done means a specified period such as the last month can show useful time steps, including CCU and corresponding energy-cost data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100