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.
In the configuration audit service, each resource entity has its own compliance timeline records. When a resource is evaluated by rules, a compliance assessment record is generated, and continuous compliance assessment forms a resource compliance timeline.
Point of compliance time line
- Start point: the time when the resource is evaluated by the rule for the first time. The time when the resource is evaluated by the rule may be the scheduled cycle evaluation, manual evaluation, or real-time configuration change trigger evaluation.
- Node: each rule assessment will form a node on the compliance time line, and each assessment may involve one or more rules.
- Breakpoint: Different from resource configuration timeline (View the resource configuration timeline), rule assessment is triggered based on real-time configuration changes. Since there is no continuity, there is no breakpoint.
Content of the compliant timeline
- The compliance timeline belongs to a specific resource entity and is a set of historical compliance assessment records.
- On the left side of the compliance timeline, in addition to the time, each node also clearly shows the triggering mechanism of the compliance assessment. This also shows the reason why resources are assessed, the options include manual execution, periodical execution, and change triggering.
- On the left side of the compliance timeline, each node also marks the evaluation result "compliance" or "non-compliance ". This allows you to quickly find the nodes that need attention.
- The details of each node include basic resource information and the list of associated rules (rules and evaluation results). If an evaluation is triggered by a real-time change, the details of this change will also be displayed, so that you can locate the "non-compliance" specific configuration as soon as possible.
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.