GS Cleanup: Monitoring |
||||||||||||
Issue descriptionWe have two GCE builders which run the purge_gs.sh script to repeatedly cleanup old GS content. However, we currently have no monitoring of this script, other than to log into the servers by hand. We need something to help record progress, as well as alert on success or failures. The easiest path might be possible to do this via Google Cloud Logging.
,
Mar 29 2016
Paul, any suggestions on how to approach this?
,
Mar 29 2016
,
Mar 30 2016
Well, if you put the Monarch credentials on those machines then it's pretty easy to use Monarch for this task. I'm not sure if you want to wait until the new GCE image is already baked.
,
Apr 4 2016
This two machines aren't using the standard builder image. I just created clean Ubuntu images, installed git, and started the script in question.
,
Apr 4 2016
,
Apr 26 2016
,
May 17 2016
Paul, we can easily add stuff to chromite/bin/purge_gs.sh.... or something. What's the best approach?
,
Jun 20 2017
This is still relevant. The best approach for this is to add the Monarch credentials into the Ubuntu images, then use chromite's ts-mon wrapper.
,
Mar 29 2018
,
Mar 29 2018
Actually, let's hand it over. go/cros-gs-cleanup-design go/cros-purge-servers
,
Apr 9 2018
Mike, can you take a look at this?
,
Apr 9 2018
,
Jul 17
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by dgarr...@chromium.org
, Mar 28 2016