C
Charcoal Mandrill
Its possible for a mis-configured bioinformatics tool inside a Nextflow pipeline to output exorbitant amounts of stderr messages and incur massive AWS CloudWatch fees. Its not clear if this is reflected in the current Seqera Platform pipeline Run cost estimates. If not, it should be included. Right now you can map these costs as such;
  • Based on Seqera documentation
  • The AWS Batch Job includes the ARN for the CloudWatch log stream for each job
  • Note that this log stream will be included in the AWS CloudWatch log group
    aws/batch/jobs
    by default
  • It should be possible to calculate the size of the CloudWatch log stream
  • The size of the log stream should correspond to the costs incurred by logging of each Nextflow task
Thanks!