forked from docs/doc-exports
Wei, Hongmin
1c932a8714
Reviewed-by: Rumpler, Mihály <mihaly.rumpler@t-systems.com> Co-authored-by: Wei, Hongmin <weihongmin1@huawei.com> Co-committed-by: Wei, Hongmin <weihongmin1@huawei.com>
35 lines
8.7 KiB
HTML
35 lines
8.7 KiB
HTML
<a name="rms_08_0100"></a><a name="rms_08_0100"></a>
|
|
|
|
<h1 class="topictitle1">Resource Recorder</h1>
|
|
<div id="body0000001072055984"><div class="section" id="rms_08_0100__section39667213499"><h4 class="sectiontitle">Are Resource Snapshots and Resource Change Notifications Stored into the Same OBS Bucket?</h4><p id="rms_08_0100__p330319360490">Yes, they are stored into the same OBS bucket.</p>
|
|
<p id="rms_08_0100__p1130353604917">If you specified an OBS bucket and an SMN topic when you configured the resource recorder, resource snapshots and resource change notifications are periodically stored in the OBS bucket.</p>
|
|
</div>
|
|
<div class="section" id="rms_08_0100__section97752046184912"><h4 class="sectiontitle">How Often Are Resource Snapshots and Resource Change Notifications Stored, Respectively?</h4><p id="rms_08_0100__p27314108504">After you enable the resource recorder and specify an SMN topic and an OBS bucket, Config will store your resource snapshots to the OBS bucket every 24 hours and your resource change notifications every 6 hours.</p>
|
|
</div>
|
|
<div class="section" id="rms_08_0100__section8379155274918"><h4 class="sectiontitle">Do I Need to Configure Both Topic and Resource Dump When I Enable and Configure the Resource Recorder?</h4><p id="rms_08_0100__p3431905019">No. However, you need to configure either <strong id="rms_08_0100__b31908702041541">Topic</strong> or <strong id="rms_08_0100__b17052149241541">Resource Dump</strong>. To enable the resource recorder, you must configure either an SMN topic or an OBS bucket.</p>
|
|
</div>
|
|
<div class="section" id="rms_08_0100__section1349953185017"><h4 class="sectiontitle">Why Are There No Notifications of Resource Changes Even When the Resource Recorder Has Been Enabled?</h4><p id="rms_08_0100__p16111161284">The possible causes are as follows:</p>
|
|
<ul id="rms_08_0100__ul44261140601"><li id="rms_08_0100__li842615401206">You didn't specify an SMN topic when you configured the resource recorder. To receive resource change notifications, modify the resource recorder to configure an SMN topic.</li><li id="rms_08_0100__li182627142286">You did not <a href="https://docs.otc.t-systems.com/simple-message-notification/umn/subscription_management/adding_a_subscription.html" target="_blank" rel="noopener noreferrer">add subscriptions</a> or <a href="https://docs.otc.t-systems.com/simple-message-notification/umn/subscription_management/requesting_subscription_confirmation.html" target="_blank" rel="noopener noreferrer">request subscription confirmations</a> for the specified SMN topic. </li><li id="rms_08_0100__li18710185293216">Resource changes were not reported to Config.</li><li id="rms_08_0100__li20559844325">There was a delay in synchronizing or sending the notification.</li></ul>
|
|
</div>
|
|
<div class="section" id="rms_08_0100__section15641074526"><h4 class="sectiontitle">Why Are Resource Change Notifications Not Stored into the Configured OBS Bucket?</h4><p id="rms_08_0100__p515311324214">To store resource change notifications, you need to configure both an SMN topic and an OBS bucket.</p>
|
|
<p id="rms_08_0100__p8060118">To make an SMN topic effective, you not only need to create a topic, but add subscription endpoints and request subscription confirmation.</p>
|
|
</div>
|
|
<div class="section" id="rms_08_0100__section28980415516"><h4 class="sectiontitle">Why Do I Receive a Notification When I Did Nothing with a Resource?</h4><p id="rms_08_0100__p15577141745117">If you have specified an effective SMN topic when you enabled the resource recorder, Config will send notifications of resource changes that are resulted from both user operations and non-user operations. For more details, see <a href="rms_04_0300.html">Notifications</a>. You are advised to use HTTPS or FunctionGraph functions instead of SMS messages or emails to receive notifications from Config.</p>
|
|
</div>
|
|
<div class="section" id="rms_08_0100__section1077795954511"><a name="rms_08_0100__section1077795954511"></a><a name="section1077795954511"></a><h4 class="sectiontitle">How Can I Obtain Resource Attributes Reported to Config?</h4><p id="rms_08_0100__p1154964785316">You can obtain resource attributes reported to Config in either of the following ways:</p>
|
|
<ul id="rms_08_0100__ul1655419476534"><li id="rms_08_0100__li95531447205318">Go to Config console and open the <strong id="rms_08_0100__b17465191953714">Query Editor</strong>. Resource attributes that are reported to Config are displayed on the left side of the <strong id="rms_08_0100__b20526154420381">Query Editor</strong>. The following procedure shows how to open the <strong id="rms_08_0100__b19338433163916">Query Editor</strong>.<ol id="rms_08_0100__ol763992315814"><li id="rms_08_0100__li146391323185811">Log in to the management console.</li><li id="rms_08_0100__li356185855416">Click <span><img id="rms_08_0100__rms_03_0102_rms_03_0102_rms_03_0101_rms_11_3000_rms_03_0102_rms_03_0101_image4857236125711" src="en-us_image_0000001978727588.png"></span> in the upper left corner of the page. In the service list that is displayed, under <strong id="rms_08_0100__b1242865465313">Management & Deployment</strong>, select <strong id="rms_08_0100__b16429145414532">Config</strong>.</li><li id="rms_08_0100__li1277115512">In the navigation pane on the left, choose <strong id="rms_08_0100__b16601141914556">Advanced Queries</strong>.</li><li id="rms_08_0100__li10989173618119">On the <strong id="rms_08_0100__b3899133164218">Default Queries</strong> tab, click <strong id="rms_08_0100__b1623953213428">Query</strong> in the <strong id="rms_08_0100__b583874434215">Operation</strong> column of any rows.<div class="fignone" id="rms_08_0100__fig1574711541020"><span class="figcap"><b>Figure 1 </b>Using a query</span><br><span><img id="rms_08_0100__image67488159109" src="en-us_image_0000002001635001.png"></span></div>
|
|
</li><li id="rms_08_0100__li169512341141">View resource attributes on the left side of the <strong id="rms_08_0100__b1783424711444">Query Editor</strong>. You can also enter a resource type to search for resource attributes.<div class="fignone" id="rms_08_0100__fig538612491597"><span class="figcap"><b>Figure 2 </b>Viewing resource attributes</span><br><span><img id="rms_08_0100__image203872491191" src="en-us_image_0000001964993150.png"></span></div>
|
|
</li></ol>
|
|
</li><li id="rms_08_0100__li15553104705316">Alternatively, you can call the the querying schema API (GET /v1/resource-manager/domains/{domain_id}/schemas) to obtain resource attributes. In the response, the <strong id="rms_08_0100__b7823729185016">type</strong> field indicates the resource type, and the <strong id="rms_08_0100__b38231729185011">schema</strong> field indicates resource attributes that are reported to Config. For more details, see <em id="rms_08_0100__i28231529125017">Config API Reference</em>.</li></ul>
|
|
</div>
|
|
<div class="section" id="rms_08_0100__section1356812297234"><a name="rms_08_0100__section1356812297234"></a><a name="section1356812297234"></a><h4 class="sectiontitle">Why Is an Error Reported When Data Is Dumped to the OBS Bucket After the Resource Recorder Is Enabled?</h4><div class="p" id="rms_08_0100__p1573316404147">If the message "Failed to write the ConfigWritabilityCheckFile file to the OBS bucket because the OBS bucket or the IAM agency is invalid" is displayed, the possible reasons are as follows:<ol id="rms_08_0100__ol1774482510141"><li id="rms_08_0100__li1674422520146">The IAM agency assigned to the resource recorder does not contain the permission, <strong id="rms_08_0100__b374811102812">obs:object:PutObject</strong>.</li><li id="rms_08_0100__li157441125111420">If an OBS bucket from the current account was used, the reason may be that the bucket policy explicitly denies the <strong id="rms_08_0100__b9468183143013">PutObject</strong> action from the IAM agency. If an OBS bucket from another account was used, the reason may be that the bucket policy does not explicitly allow the <strong id="rms_08_0100__b57021738103418">PutObject</strong> action from the IAM agency. For more details, see <a href="rms_04_0200.html#rms_04_0200__section95911732882">Cross-Account Authorization</a>. For permission judgement logic of budget policies, see <a href="https://docs.otc.t-systems.com/object-storage-service/umn/obs_console_operation_guide/permissions_control/bucket_policy_parameters/effect.html" target="_blank" rel="noopener noreferrer">Effect</a>.</li><li id="rms_08_0100__li1744132517141">You used an encrypted OBS bucket, but the agency assigned to the resource recorder did not contain related KMS permissions. For more details, see <a href="rms_04_0200.html#rms_04_0200__section1414618337911">Storing Resource Change Notifications and Resource Snapshots to an Encrypted OBS Bucket</a>.</li></ol>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rms_08_0000.html">FAQs</a></div>
|
|
</div>
|
|
</div>
|
|
|