Releases: naztronaut/RaspberryPi-Website-Uptime-Monitor
Releases · naztronaut/RaspberryPi-Website-Uptime-Monitor
Beta Release version 0.3.0-b01
- Added support for Apache. Flask app can now be fronted by an Apache web server that doesn't need to be turned on every time.
- Uses standalone WSGI implementation
- Apache2 and libapache2-mod-wsgi-py3 dependencies added
- Added
util
directory which containsactivate_this.py
anduptime.wsgi
which are needed for Apache integration. - Fixed bug that required all queries to be committed in the reporting methods
- Added table of contents to readme
- Minor typo fixes
- Other minor bug fixes
Beta Release version 0.2.5-b02
Second build to fix a couple of issues:
- The email script was sending blank emails if the downtime counts was not divisible by 3. The script is meant to send emails only after each 3 failed checks (45 minutes by default). But it was sending one every 15 minutes, two blanks and one with actual data. This has been fixed.
- Added a screenshots folder for documentation purposes. Accidentally checked it in earlier. Added it to .gitignore
- Updated readme to point to the newly created release
- Typos
These following were posted in the last build, they remain the same:
- Updated README with more documentation steps
- Added the following
GET
web services into the Flask App- Get Cron - get a list of all cron jobs
- Get Notifications - get a list of every time the app tried to notify you via email, whether it was successful or not
- Added the following
PUT
web services into the Flask App- Override Green - override the on/off status of the green LED as defined by cron jobs
- Check Frequency - modify how often sites are checked
- Update Cron - modify all cron jobs based on their comment (unique identifier)
- Moved GPIO Pin settings into the configuration file for easier editing
- Fixed bug to allow saving notifications to database to keep track of successful and failed email notifications
- Typos
- Other bug fixes
Beta Release version 0.2.5-b01
- Updated README with more documentation steps
- Added the following
GET
web services into the Flask App- Get Cron - get a list of all cron jobs
- Get Notifications - get a list of every time the app tried to notify you via email, whether it was successful or not
- Added the following
PUT
web services into the Flask App- Override Green - override the on/off status of the green LED as defined by cron jobs
- Check Frequency - modify how often sites are checked
- Update Cron - modify all cron jobs based on their comment (unique identifier)
- Moved GPIO Pin settings into the configuration file for easier editing
- Fixed bug to allow saving notifications to database to keep track of successful and failed email notifications
- Typos
- Other bug fixes
Beta Release version 0.2.3-b01
Beta release of version 0.2.3. Application is ready to work in headless mode. These fixes were made:
- Email notification triggers are now stored in the
notifications
table as 'success' or 'fail' - Flask App offers these 4 GET services:
- Get Current Status - gets the status of all sites in the currentStatus table - this table includes any websites that were previous monitored. Those sites will appear as 'down'
- Get Activity - gets all status updates for sites at all times whenever the sites are checked
- Get Outages - gets all data in the
outages
table that which records when websites were down - Get Downtime Counts - gets data from the downtimeCounts table which keeps track of websites that report offline in multiple checks
- All end points also take the following two URL parameters along with their default values if not defined:
- page (default: 1)
- limit (default: 25)
- Example: {{addr}}/getActivity?page=2&limit=100 (this will output records 101 to 200 on page 2)
Alpha 0.2.3
Features:
- Adjustable cronjobs that will check your sites with an HTTP GET
- Stores all data in a MySQL database so that it's easy to report on
- Emails outage notifications using Gmail if a site fails to respond 3 times
- Preliminary Web Service endpoints created with Flask to be consumed by a frontend app at a later time