TSDB to Store Historical Data

[quinkirsten]

Problem

Users' historical data is currently not saved anywhere - all pod, node, and cluster-level data is received though a fetch request on page load. This means users cannot go back in time to see how performance has changed. It also means there is no data, and therefore no purpose associated with their personal account other than their username and password.

Solution

Creating a database to store not just user info, but historical Kubernetes data associated with each user. This could include CPU/Memory usage and latency data, pod logs (going back farther than they do currently), pod restarts over time, etc. A time-series database like InfluxDB might be necessary for this because of the vast quantity of data and the need to look up past data by timestamp.

Additional information

No response

👨‍👧‍👦 Contributing

• 🙋‍♂️ Yes, I'd love to make a PR to implement this feature!