Hi, we run private workers in AWS (using a fork of your ec2-workerpool module). I'm noticing a pretty sizable (relatively speaking) cost when it comes to CloudWatch metrics. Specifically, the MetricMonitorUsage usage type.
The majority of that cost is coming from custom metrics; the only ones we have are in the DefaultWorkerPool namespace. I traced it back to metrics being pushed by your worker pool AMI: https://github.com/spacelift-io/spacelift-worker-image/blob/7f085d534c355229d8145ffc17a76e7e8804be4d/aws/configs/amazon-cloudwatch-agent.json
Is there any way to turn off those metrics without building our own AMIs? I don't want to disable the CloudWatch agent entirely, just the custom metrics in that config file.
Please authenticate to join the conversation.
🔭 Discovery
💡 Feature Requests
Workers
4 months ago
Get notified by email when there are changes.
🔭 Discovery
💡 Feature Requests
Workers
4 months ago
Get notified by email when there are changes.