Lossy TimeSeries DataBase
Go to file
Peter J. Holzer c5b8476a42 Rename reporting/recording scripts
I think record_* is less ambiguous than report_*.
A close second would be collect_*, but record seems to me to be a bit
closer to what the scripts are doing.
2023-01-03 18:33:58 +01:00
clients Rename reporting/recording scripts 2023-01-03 18:33:58 +01:00
doc Think about scheduling measurements and processing them 2022-11-27 10:19:37 +01:00
templates Display min, max and last value in description 2022-12-31 17:55:25 +01:00
app.py Add dashboard with gauges 2022-12-27 10:29:49 +01:00
dashboard.py Use special linear scale for time values 2023-01-01 01:06:24 +01:00
ltsdb-json Maintain a single lossy timeseries (PoC) 2022-08-20 17:39:12 +02:00
ltsdb_json.py Avoid division by 0 2022-12-30 21:31:50 +01:00
ltsdb_test Implement json prototype of LTsDb 2022-08-21 11:58:31 +02:00
predict_disk_full Use a lossy timeseries to predict when a filesystem will be full (PoC) 2022-08-20 17:40:16 +02:00
predict_disk_full_home_bytes Use a lossy timeseries to predict when a filesystem will be full (PoC) 2022-08-20 17:40:16 +02:00
predict_disk_full_var_bytes Use a lossy timeseries to predict when a filesystem will be full (PoC) 2022-08-20 17:40:16 +02:00
process_queue Add logging to process_queue 2022-12-27 11:44:03 +01:00
record_df Record disk usage in LTsDb 2022-08-21 12:00:07 +02:00
record_dus Be quiet(er) 2022-08-21 13:15:01 +02:00
requirements.txt Add gunicorn to requirements 2022-09-03 22:57:32 +02:00