Google Cloud Batch - logging & monitoring options #6860
Unanswered
puerta-amarilla
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Google Cloud Batch supports enableing logs and installing Ops Agent:
https://docs.cloud.google.com/batch/docs/create-run-job-ops-agent#ops-agent-requirements
"logsPolicy": {
"destination": "CLOUD_LOGGING"
}
Nextflow seems to enable this by default. All messages written to stdout and stderr are captured. Even the central logging "nextflow.log" can be redirected. However, I can't find a way to redirect the tasks logs from each working directory to Cloud_Logging? The reason to want to use Cloud Logging instead of the default scratch space of cloud storage is two fold:
It's unpreticable when oogs in storage bucket will show up. It seems after the tasks are done, not during running.
Be able to have a single place to see all logs offers the convenience.
set process.debug to true might be possible but it could print too many messages.
For monitoring:
Sometimes it's also useful to see Ops Agent based metrics
"allocationPolicy": {
"instances": [
{
"installOpsAgent": true
}
]
},
However, I can't find a way to enable it through Nextflow. Any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions