1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 8 mois
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a un an