Add AWS Batch job ID to task view
acknowledged
A
Advisory Spoonbill
The NF execution log outputs the AWS Batch job ID for each task. I would like to see that Batch job ID in the Task view. Bonus points for a direct link to the Batch console for the job.
This is for debugging purposes (easy access to CloudWatch log stream) and also be able to start a session to the EC2 instance, or leverage ECS Exec command to send commands to the running container task.
C
Charcoal Mandrill
Honestly, I think this is one of the most sorely needed features in the Platform UI. And I would take it a step further, and recommend that the Task View in a Platform Run should also include references to the EC2 that the Job ran on, the CloudWatch log stream, the ECS entry, etc.. Bonus points if you can just give me a click-able link directly in the Task view to take me to these entries in AWS. All of these are critical for debugging and being forced to jump between
multiple
webpages both in Seqera Platform and in AWS Console is one of the most tedious and difficult parts of debugging failed runs in Platform using AWS Batch.
Rob Newman
Charcoal Mandrill: As noted to Advisory Spoonbill below, the ID is already available in the
native_id
field in the task table. Can you please confirm too?We are looking at the feasibility of adding external links to the various resources in the cloud provider via the Task Detail View modal to help users more quickly troubleshoot/debug failed runs in the Platform.
Rob Newman
acknowledged
Rob Newman
Advisory Spoonbill: The Batch job ID should already be listed in the Task table as the
native_id
field. Can you please confirm that field is visible to you?A
Advisory Spoonbill
Rob Newman Customer ask, I will ask them to confirm
Y
Yellow sunshine Firefly
Rob Newman it would still be nice to have it listed as having it specified when in the task view.