Currently, when an exception occurs (e.g. network failure) during mirror job, its status is set to ERROR and this is propagated to the quartz scheduler.
It will be nice to be able to trigger an alert in such cases so that an operator can have a look at it.
The API endpoint api/tasks/{id}/ returns a JSON hash with a status such as
Available monitoring such as AWS route 53 support querying an http endpoint (without authentication) and the cheapest option (0$.75 /month) is to rely on the HTTP status code for signaling an issue:
Currently, when an exception occurs (e.g. network failure) during mirror job, its status is set to ERROR and this is propagated to the quartz scheduler.
It will be nice to be able to trigger an alert in such cases so that an operator can have a look at it.
The API endpoint
api/tasks/{id}/returns a JSON hash with a status such asAvailable monitoring such as AWS route 53 support querying an http endpoint (without authentication) and the cheapest option (0$.75 /month) is to rely on the HTTP status code for signaling an issue:
An alternative with an hosted monitoring such as cachet with a custom plugin such as https://github.com/castawaylabs/cachet-monitor#configuration
Exposing an unauthenticated endpoint such as
/healththat returns "DOWN" whenever a job is failed