You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I'm not 100% sure, I think the autoscaler (this repo) is responsible.
Context
When this autoscaler is used in the Lambda created by your Terraform module. I haven't tested this outside of a Lambda.
Problem
So, the Lambda itself is configured to dump its logs in to the /aws/lambda/spacelift-workers-ec2-autoscaler group:
However, three additional groups are also created, which contain identical logs (though split across those three files instead of being combined like the Lambda's log group)
Worse yet, they don’t have any log retention settings configured, and get recreated every time the autoscaler runs.
Can you confirm if the autoscaler itself is sending logs to Cloudwatch (in addition to the Lambda sending all its output to its own)?
The text was updated successfully, but these errors were encountered:
While I'm not 100% sure, I think the autoscaler (this repo) is responsible.
Context
When this autoscaler is used in the Lambda created by your Terraform module. I haven't tested this outside of a Lambda.
Problem
So, the Lambda itself is configured to dump its logs in to the
/aws/lambda/spacelift-workers-ec2-autoscaler
group:However, three additional groups are also created, which contain identical logs (though split across those three files instead of being combined like the Lambda's log group)
Worse yet, they don’t have any log retention settings configured, and get recreated every time the autoscaler runs.
Can you confirm if the autoscaler itself is sending logs to Cloudwatch (in addition to the Lambda sending all its output to its own)?
The text was updated successfully, but these errors were encountered: