Skip to content
This repository has been archived by the owner on Jul 19, 2019. It is now read-only.

Monitoring Backups to S3 #22

Open
murphyj21 opened this issue Oct 3, 2018 · 2 comments
Open

Monitoring Backups to S3 #22

murphyj21 opened this issue Oct 3, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@murphyj21
Copy link
Contributor

Problem Description:

If AWS S3 experiences issues when writing backups, cronjobs pile up and crash the instance. To remedy this a timeout was added to the cronjob. However, if the cronjob times out backups are not written to S3.

Fix recommendation:

Create a lambda function to poll S3 and generate an alert if backups are not written at the required interval.

@murphyj21 murphyj21 added the enhancement New feature or request label Oct 3, 2018
@ferricoxide
Copy link
Member

This stopped being a problem for a few months, but has recently returned. Probably requires wholly rearchitecting the backups ...and possibly the storage used for ${JENKINS_HOME} (to allow for filesystem snapshotting to create a "static" backup-set to copy from).

@ferricoxide
Copy link
Member

Added an enhancement issue (#47) to describe a better backup system. While a monitoring lambda function would be useful, in general, the problem likely is best solved by a less-simplistic backup method.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants