An official English-language version of the documentation is not available. For your convenience only, we have introduced the use of machine-translation software capable of producing rough translations in various languages, including English.This machine-translated version of the documentation was produced using only machine-translation software and without any human intervention. We are making continuous efforts to improve the machine-translation software. HOWEVER, MACHINE TRANSLATIONS MAY CONTAIN ERRORS. ANY RELIANCE BY YOU UPON THIS MACHINE TRANSLATION IS SOLELY AT YOUR OWN RISK, AND ALIBABA CLOUD SHALL NOT BE LIABLE TO YOU OR ANY OTHER PARTIES FOR ANY ADVERSE CONSEQUENCES (DIRECT, INDIRECT, CONSEQUENTIAL OR OTHERWISE) ARISING FROM OR IN CONNECTION WITH THE DOCUMENTATION OR ANY TRANSLATIONS THEREOF.

To request a human-translated version of this article or to comment on the quality of machine translation, please use the "More suggestions" text area in the feedback form below to submit feedback.

Configuration audit records each configuration change details of the resources under monitoring, and organizes the results. That is, records of the evolution of resource configurations over time.

Configure a time line

  • Start point: for the resources that are stored when you activate the configuration audit service, the starting point of the configuration timeline is the service activation time. For resources created after you activate the configuration audit service, the starting point of the configuration timeline is the resource creation time.
  • Node: configuration audit refreshes the resource configuration snapshot every 10 minutes. If the snapshot is different from the one created 10 minutes ago, a configuration change record is displayed, which is a node on the configuration time line.
  • Breakpoint: If you remove a resource type from the monitoring range, the monitoring of the related entity resources stops and the configuration timeline is not updated until you move the resource type back to the monitoring range, restart monitoring and tracking. The change history during monitoring stop cannot be traced.

Configure the content of the timeline

The configuration timeline belongs to a specific resource entity and is a set of historical resource configuration records.

  • First, you can see the current configuration snapshot of the resource. Each node is a historical configuration snapshot.
  • Each node includes the configuration details of the current change result, including the comparison details with the last change result.

[Note] configuration audit organizes resource changes every 10 minutes. If a resource configuration change occurs during the 10-minute window and is quickly restored before the change, the change cannot be perceived, therefore, the corresponding operation events cannot be displayed.

You can check the preceding information online or download it to your OSS bucket through APIs to facilitate offline integrated analysis. The OpenAPI and snapshot download capabilities are undergoing rapid iteration, so stay tuned.