Skip to content

Increase in PutLogEvents for cloud watch due to batch job #5368

@lacoak21

Description

@lacoak21

I am trying to disable cloud watch logging because we had a multifold increase in Cloud Watch PutLogEvents. We didn't change anything for our cextflow pipelines and configuration so we are still unclear what happened. It was confirmed that the increase came from nextflow tower resources. In the meantime I would like to switch from forwarding logs to CloudWatch to
"logConfiguration": {
"logDriver": "json-file",
"options": {},
"secretOptions": []
},

It seems like there is no easy way to do this since next flow automatically creates the job definitions.

I could manually update the job definitions through the AWS-cli and then use process.container = 'job-definition://your-job-definition-name' for each one but we have many and that would be a tedious solution.

Do you have any suggestions?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions