Raise visibility of tests of occurrence downloads

16277
Reporter: trobertson
Assignee: cvizitiu
Type: Task
Summary: Raise visibility of tests of occurrence downloads
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2014-08-30 10:11:21.102
Updated: 2015-03-02 15:30:39.19
Resolved: 2015-03-02 15:30:39.168
        
Description: Small occurrence downloads were failing, and I noticed this by chance today, and fixed them.  We need to implement something that raises the visibility of this kind of issue in our system - someone should have been alerted at critical priority of this before I stumbled on the issue.  In this case it was a bad configuration, so either a) someone changed table names and dropped the original table, or b) it was deployed incorrectly at the beginning.  Either of these should have alerted immediately following the event.

Please propose something for post scrum one day.]]>
    

Author: cvizitiu@gbif.org
Created: 2014-09-15 16:55:08.302
Updated: 2014-09-15 16:55:08.302
        
Nagios check in place to verify

1. The existence of an answer email for an API call
2. The existence of "Your download (\d\d\d\d\d\d\d-\d\d\d\d\d\d\d\d\d\d\d\d\d\d\d) is ready at the following address" type of string

Currently working on the ability to also remove the files and the DB records so that checking interval can be lowered to 10 minutes without producing useless download files.