Commit | Line | Data |
---|---|---|
51100f8e SK |
1 | TODO |
2 | ---- | |
3 | - track energy usage rate | |
4 | - formalize message format and protocol | |
5 | - tests (design is starting to take shape, so it is time) | |
6 | - show how many Debian package updates are available | |
7 | - show how many Debian package security-updates are available | |
8 | - monitor disk usage rate of change and alert if suspiciously fast | |
9 | - bring back CPU usage monitor | |
10 | - actual METAR parser, to replace the flaky `metar` program | |
11 | - status bar templating language | |
12 | - retry/cache for sensors fetching flaky remote resources (such as weather) | |
13 | - throttling of broken sensors (constantly returns errors) | |
14 | - alert specification language | |
15 | - trigger threshold | |
16 | - above/bellow/equal to threshold value | |
17 | - priority | |
18 | - snooze time (if already alerted, when to re-alert?) | |
19 | - text: subject/body | |
20 | - monitor processes | |
21 | - totals (grand and per state) | |
22 | - zombies | |
23 | - threads | |
24 | - CPU hogs | |
25 | - memory hogs | |
26 | - memory leaks (if some process consistently grows) | |
27 | - is select process up? | |
28 | - log resource usage of select processes | |
29 | - monitor arbitrary HTTP endpoint availability | |
30 | - is status within expected range? | |
31 | - response time | |
32 | - is responce time within acceptable range? | |
33 | - report detailed status upon request (to a terminal) | |
34 | - use color to indicate age of data | |
35 | - monitor logins | |
36 | - totals (per time period) | |
37 | - failures | |
38 | - successes | |
39 | - most recent | |
40 | - success | |
41 | - failure | |
42 | - monitor battery time remaining | |
43 | - monitor accuracy (is percentage change rate on track to meet estimate?) | |
44 | - adjust estimate based on observed inaccuracies in past estimates (Kalman?) |