1 個回答
- 最新
- 最多得票
- 最多評論
0
Hi. Assuming you are using the default logging driver, most likely AWS CloudWatch, the capture of the logs from your containers is sent to CW directly, not stored on disks. We run 100s of services and never once have we had a disk capacity error due to logs with AWS Fargate and the CW Log driver (or Fluent-Bit for that matter).
If your application has multiple log streams configured internally and one of these is file, then might be worth to disable it then when running in Fargate, and stick to stdout/stderr
已回答 2 年前
相關內容
- 已提問 1 年前
- AWS 官方已更新 7 個月前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前