本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。

# 信任的修復程式中的修復日誌
<a name="tr-logging"></a>

Trusted Remediator 會以 JSON 格式建立日誌，並將其上傳至 Amazon Simple Storage Service。日誌檔案會上傳至 AMS 建立且名為 的 S3 儲存貯體`ams-trusted-remediator-{your-account-id}-logs`。AMS 會在委派管理員帳戶中建立 S3 儲存貯體。您可以將日誌檔案匯入 QuickSight，以產生自訂的修補報告。

## 修復項目日誌
<a name="tr-logging-rem-item"></a>

建立修復 OpsItem `Remediation item log`時，信任的修復程式會建立 。此日誌包含手動修復 OpsItem 和自動修復 OpsItem。您可以使用 `Remediation item log`來追蹤所有修補的概觀。

**Compute Optimizer 建議的修復項目日誌位置**

`s3://ams-trusted-remediator-delegated-administrator-account-id-logs/compute_optimizer_remediation_items/remediation creation time in yyyy-mm-dd format/10 digits epoch time or unix timestamp-Trusted Advisor check ID- Resource ID.json`

** Trusted Advisor 檢查的修復項目日誌位置**

`s3://ams-trusted-remediator-delegated-administrator-account-id-logs/remediation_items/remediation creation time in yyyy-mm-dd format/10 digits epoch time or unix timestamp-Trusted Advisor check ID- Resource ID.json`

**修復項目日誌範例檔案 URL**

`s3:///ams-trusted-remediator-111122223333-logs/remediation_items/2023-02-06/1675660464-DAvU99Dc4C-vol-00bd8965660b4c16d.json`

**Compute Optimizer Remediation 項目日誌格式**

```
{
  "AccountID": "Account_ID",
  "ComputeOptimizerCheckID": "Compute Optimizer check ID",
  "ComputeOptimizerCheckName": "Compute Optimizer check name",
  "ResourceID": "Resource ID",
  "RemediationTime": Remediation creation time,
  "ExecutionMode": "Automated or Manual",
  "OpsItemID": "OpsItem ID"
}
```

**Trusted Advisor 修復項目日誌格式**

```
{
   "TrustedAdvisorCheckID": Trusted Advisor check ID,
   "TrustedAdvisorCheckName": Trusted Advisor check name,
   "TrustedAdvisorCheckResultTime": 10 digits epoch time or unix timestamp,
   "ResourceID": Resource ID,
   "RemediationTime": Remediation creation time,
   "ExecutionMode": Automated or Manual,
   "OpsItemID": OpsItem ID
}
```

**Compute Optimizer Remediation 項目日誌格式範例內容**

```
{
  "AccountID": "123456789012",
  "ComputeOptimizerCheckID": "compute-optimizer-ebs",
  "ComputeOptimizerCheckName": "EBS volumes",
  "ResourceID": "vol-1235589366f77aca7",
  "RemediationTime": 1755044783,
  "ExecutionMode": "Manual",
  "OpsItemID": "oi-b8888b38fe78"
}
```

**Trusted Advisor 修復項目日誌格式範例內容**

```
{
    "TrustedAdvisorCheckID": "DAvU99Dc4C", 
    "TrustedAdvisorCheckName": "Underutilized Amazon EBS Volumes",
    "TrustedAdvisorCheckResultTime": 1675614749,
    "ResourceID": "vol-00bd8965660b4c16d",
    "RemediationTime": 1675660464,
    "OpsItemID": "oi-cca5df7af718"
}
```

## 自動化修復執行日誌、Compute Optimizer 和 Trusted Advisor
<a name="tr-logging-rem-exe"></a>

當自動化 SSM 文件執行完成`Automated remediation execution log`時，信任的修復程式會建立 。此日誌僅包含自動修復 OpsItem 的 SSM 執行詳細資訊。您可以使用此日誌檔案來追蹤自動化修復。

**Compute Optimizer 自動化修復日誌位置**

`s3://ams-trusted-remediator-delegated-administrator-account-id-logs//remediation_executions/remediation creation time in yyyy-mm-dd format/10 digits epoch time or unix timestamp-Compute Optimizer recommendation ID.json`

**Trusted Advisor 自動化修復日誌位置**

`s3://ams-trusted-remediator-delegated-administrator-account-id-logs//remediation_executions/remediation creation time in yyyy-mm-dd format/10 digits epoch time or unix timestamp-Trusted Advisor check ID-Resource ID.json`

**Compute Optimizer 自動化修復日誌位置範例**

`s3://ams-trusted-remediator-111122223333-logs/remediation_executions/2025-06-26/1750908858-123456789012-compute-optimizer-ec2-i-1235173471d2cd789.json`

**Trusted Advisor 自動化修復日誌位置範例**

`s3://ams-trusted-remediator-111122223333-logs/remediation_executions/2023-02-06/1675660573-DAvU99Dc4C-vol-00bd8965660b4c16d.json`

**自動化修復日誌格式範例內容**

```
{
    "OpsItemID": "oi-767c77e05301",
    "SSMExecutionID": "93d091b2-778a-4cbc-b672-006954d76b86",
    "SSMExecutionStatus": "Success"}
```