Analysis of Monitoring Scripts #30
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
add a script to collect all target files
a unique way of naming files so it is clear which one belongs to which process
-- grabbing the last 5 "/"-dilemeted fields seems unique enough + creating
/full_pathto include full paths if needediterate through the bucket dir to grab the files
-- downloading folders locally is inefficient. Each folder is +100GB.
-- instead I am only grabbing the files I want after generating their paths through
gsutil ls gs://BUCKET/.../**/monitoring.log-- copying files over takes about 15 min
automatically copy
pull_monitor_logs.shscript to/sharedadd
summary.logexample cmd:
bash /shared/pull_monitor_logs.sh --gs-path griffith-lab-test-layth/cromwell-executions/immuno --wf-id b6ef294d-080b-41cb-924e-ea53f6c54a2a