List view
3. Web frontend - chart and statistics of uptime based on a user selected filter - sign up ability for email alerts
No due date- No due date
### Planned Features: - Web Frontend - Database Storage ### Milestones: 1. Store Data in Database Basically, we need to store a list of dictionaries once every minute. Simplest way I know to do this would be to have a table of curl requests: | datetime | json.stringify(curl(endpoint)) | | ---------------------- | ----------------------------- | | 2023-02-12T04:03:12 | "[{...}, {...}, {...}, ...]" | | 2023-02-12T04:03:13 | "[{...}, {...}, {...}, ...]" | | 2023-02-12T04:03:14 | "[{...}, {...}, {...}, ...]" | But clearly this isn't ideal. Each curl request is about 500KB of data. This table would grow to be ~200GB/year. A system like this also wouldn't let us index data quickly. I've never used a database before so I don't know how to do this properly. Each request can occupy a table, but I don't want to generate a new table once a minute either.
No due date