失敗したポッドのログ収集の有効化
このページでは、失敗したポッドのログを収集するクラスタエージェント機能を有効にして使用する方法について説明します。この機能は、SaaS コントローラでは自動的に有効になります。このページで説明するように、オンプレミスコントローラを有効にする必要があります。
有効にすると、クラスタエージェントは再起動または失敗したポッドのログを自動的に収集します。ポッド障害ログは、再起動に失敗したコンテナの CrashLoopBackoff バックオフのステータスをキャプチャします。
Minimum Requirements
The Cluster Agent log collection feature requires:
- Cluster Agent >= 20.7
- Controller >= 20.10.0
Controller Settings
The following table lists the log settings that the technical support team can update:
| Setting | Definition | Location | Default |
|---|---|---|---|
|
sim.cluster.logs.bucket.name | The folder name to store the pod logs. |
Controller Administration Console with root user permission (Controller Settings) | kubernetes-log-snippets
|
|
sim.cluster.logs.capture.enabled |
An option to activate or deactivate log capturing. This option is enabled by default. |
Controller Administration Console with root user permission You can configure this setting at both account level (Account Settings) and Controller level (Controller Settings) | true |
|
sim.cluster.logs.expiration.in.days | The number of days after which the logs get cleared from the storage. | Controller Administration Console with root user permission (Controller Settings) | 10
|
|
sim.cluster.logs.root.file.path | The complete root file path to store the logs.Modifying the path results in storing the logs in the new path but the older logs will remain in the previous location. | Controller Administration Console with root user permission (Controller Settings) | /opt/appdynamics
|
sim.cluster.failed.pod.limit
| The number of historical pods beyond this value is purged. | Controller Administration Console with root user permission (Controller Settings) | 1000
|
sim.cluster.logs.s3.enabled
|
An option to save the logs in the S3 bucket. If you specify the value as false, the logs are saved in the Controller filesystem. 注:
| Controller Administration Console with root user permission (Controller Settings) | true
|