From 00:00:00 on December 20, 2020, ActionTrail changes some write event logs to read event logs. This change optimizes the classification of event logs to improve the efficiency when you query event logs in the ActionTrail console and helps locate important event logs. This change may affect the event logs delivered by the trails of some users.
Description
The following table describes write event logs that are changed to read event logs.
| Service name | Service code | API version | Name of the event log | Reason for change |
|---|---|---|---|---|
| Content Moderation | Green | 2018-05-09 | TextScan | These event logs record operations that scan and evaluate content material. These frequently performed operations do not affect cloud service configurations or the normal running of applications. Therefore, the event logs that record these operations are changed to read event logs. |
| ImageSyncScan | ||||
| ImageAsyncScan | ||||
| VideoAsyncScanResults | ||||
| VoiceAsyncScanResults | ||||
| VoiceAsyncScan | ||||
| 2017-01-12 | TextScan | |||
| ImageSyncScan | ||||
| ImageAsyncScan | ||||
| ImageAsyncScanResults | ||||
| 2016-12-16 | ImageDetection | |||
| ImageResults | ||||
| 2017-08-25 | ImageSyncScan | |||
| Key Management Service (KMS) | Kms | 2016-01-20 | Decrypt | These event logs record operations that generate data keys or use keys to encrypt and decrypt data on the client side. These operations do not affect the key configurations. Event logs that record these frequently performed operations may affect the analysis of important write event logs. Therefore, the event logs that record these operations are changed to read event logs. |
| Encrypt | ||||
| GenerateDataKey | ||||
| Security Token Service (STS) | Sts | 2015-04-01 | AssumeRole | When a RAM role is used to perform management operations, event logs are generated. These event logs record the operation that the RAM role is assumed. The operation does not affect the configurations of the RAM role. Therefore, the event logs are changed to read event logs. |
Impacts
After the change takes effect, take note of the following impacts:
- When you query all event logs, the preceding event logs are marked as read event logs. This improves efficiency of analyzing write event logs and helps locate the operations that affect the cloud-based IT systems. ActionTrail retains all types of event logs.
- When you query historical event logs on the Query Event Details and Event Summary Query pages of the ActionTrail console, and set the read and write type to write event logs, the preceding event logs do not appear.
- When you create a trail in the ActionTrail console and set Event Type to Write, the preceding event logs are not delivered to a Logstore you specify. If you want to deliver the preceding event logs to an Object Storage Service (OSS) bucket or Log Service Logstore, set Event Type to Read or All.