Difference between revisions of "Floodzilla Features"
Jump to navigation
Jump to search
(Created page with "== Floodzilla Features == This is a list of all pages related to features for the Floodzilla Gage Network. * LogBook === Future Feature Ideas === ==== Site Alerts ====...") |
|||
| Line 27: | Line 27: | ||
* Should we record the temperature readings that sensors are sending? | * Should we record the temperature readings that sensors are sending? | ||
* We could chart battery level to get a better idea of how to represent battery percentages, and to better predict battery life. | * We could chart battery level to get a better idea of how to represent battery percentages, and to better predict battery life. | ||
| + | |||
| + | __NOTOC__ | ||
Revision as of 21:32, 20 March 2020
Floodzilla Features
This is a list of all pages related to features for the Floodzilla Gage Network.
Future Feature Ideas
Site Alerts
There are certain types of errors or misconfigurations that aren't important enough to send email about, but are still worth surfacing. Examples might be:
- a Senix receiver has two different sample intervals set (usually we want them to be the same)
- a Senix transmitter is connected to a different receiver than it usually is (if we ever have receivers with overlapping ranges)
- we suddenly see a lot of similar-looking 404 requests
It might be nice to have a way for the server processes to put up alerts that are visible to admins to notify them about this kind of issue.
Gage/Receiver reliability tracking
We know how often a given gage should be reporting data, so we could do some work to report on what percentage of data points are missing for a given gage. We can also correlate that info across receivers to find out if a given receiver is possibly less reliable than others.
Miscellaneous
Small bits of work we could consider doing:
- Since the server no longer generates 404s, the client could detect malformed request URLs and report them. This still wouldn't catch external sites trying random URLs from an automated tool; we could possibly find a server-side way to log URLs that don't match expected patterns on our end, maybe?
- Should we record the temperature readings that sensors are sending?
- We could chart battery level to get a better idea of how to represent battery percentages, and to better predict battery life.