forked from docs/doc-exports
CTS UMN 20230718 version.
Reviewed-by: Mützel, Andrea <andrea.muetzel@t-systems.com> Co-authored-by: Liu, Siying <liusiying@noreply.gitea.eco.tsi-dev.otc-service.com> Co-committed-by: Liu, Siying <liusiying@noreply.gitea.eco.tsi-dev.otc-service.com>
This commit is contained in:
parent
0b03009fd1
commit
df92dd687a
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
37
docs/cts/umn/cts_01_00011.html
Normal file
37
docs/cts/umn/cts_01_00011.html
Normal file
@ -0,0 +1,37 @@
|
|||||||
|
<a name="cts_01_00011"></a><a name="cts_01_00011"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Configuring Key Event Notifications</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_01_00011__en-us_topic_0179639609_section227013810565"><h4 class="sectiontitle">Scenarios</h4><div class="p" id="cts_01_00011__en-us_topic_0179639609_p10532203716237">You can use this function for:<ul id="cts_01_00011__en-us_topic_0179639609_ul134761051152412"><li id="cts_01_00011__en-us_topic_0179639609_li11476145172419">Real-time detection of high-risk operations (such as VM restart and security configuration changes), cost-sensitive operations (such as creating and deleting expensive resources), and service-sensitive operations (such as network configuration changes).</li><li id="cts_01_00011__en-us_topic_0179639609_li114761251192411">Detection of operations such as login of users with admin-level permissions or operations performed by users who do not have the required permissions.</li><li id="cts_01_00011__en-us_topic_0179639609_li10476165182416">Connection with your own audit system: You can synchronize all audit logs to your audit system in real time to analyze the API calling success rate, unauthorized operations, security, and costs.</li></ul>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_00011__en-us_topic_0179639609_section166121016175719"><h4 class="sectiontitle">Prerequisites</h4><ul id="cts_01_00011__en-us_topic_0179639609_ul180315494816"><li id="cts_01_00011__en-us_topic_0179639609_en-us_topic_0179639609_li17631852165614">SMN sends key event notifications to subscribers. Before setting notifications, you need to know how to create topics and add subscriptions on the SMN console.</li><li id="cts_01_00011__en-us_topic_0179639609_li293723811443">You can create up to 100 key event notifications on CTS:<ul id="cts_01_00011__en-us_topic_0179639609_ul1627918415445"><li id="cts_01_00011__en-us_topic_0179639609_li14302184324420">Specify key operations, users, and topics to customize notifications.</li><li id="cts_01_00011__en-us_topic_0179639609_en-us_topic_0179639609_li376315523566">Complete key event notifications can be sent to notification topics.</li><li id="cts_01_00011__en-us_topic_0179639609_li13350352194417">Typical key event notifications can be sent to specified users and notification topics.</li></ul>
|
||||||
|
</li></ul>
|
||||||
|
<ul id="cts_01_00011__en-us_topic_0179639609_ul20763052155613"><li id="cts_01_00011__en-us_topic_0179639609_li449074665114">If CTS and Cloud Eye use the same message topic, they can receive messages from the same terminal but with different content.</li><li id="cts_01_00011__en-us_topic_0179639609_li19385577408">You can configure one key event notification for operations initiated by a maximum of 50 users in 10 user groups. For each key event notification, you can add users from different user groups, but cannot select multiple user groups at once.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_00011__en-us_topic_0179639609_section50451709105654"><h4 class="sectiontitle">Creating a Key Event Notification</h4><ol id="cts_01_00011__en-us_topic_0179639609_ol5786112111231"><li id="cts_01_00011__en-us_topic_0179639609_li5098804111231">Log in to the management console.</li><li id="cts_01_00011__en-us_topic_0179639609_li6039246711240">Click <span><img id="cts_01_00011__en-us_topic_0179639609_image16807172915217" src="en-us_image_0000001186930850.png"></span> in the upper left corner and choose <strong id="cts_01_00011__en-us_topic_0179639609_b1912015357487">Management & Deployment</strong> > <strong id="cts_01_00011__en-us_topic_0179639609_b080812291824">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_01_00011__en-us_topic_0179639609_li8120135513217">In the navigation pane on the left, choose <strong id="cts_01_00011__en-us_topic_0179639609_b26590559184937">Key Event Notifications</strong>.<p id="cts_01_00011__en-us_topic_0179639609_p47256182184937">The <strong id="cts_01_00011__en-us_topic_0179639609_b84235270616453">Key Event Notifications</strong> page is displayed.</p>
|
||||||
|
</li><li id="cts_01_00011__en-us_topic_0179639609_li423764012244">Click <strong id="cts_01_00011__en-us_topic_0179639609_b842352706162340">Create Key Event Notification</strong>. On the displayed page, specify required parameters.</li><li id="cts_01_00011__en-us_topic_0179639609_li16908374285">Enter a key event notification name.<p id="cts_01_00011__en-us_topic_0179639609_p471524722814"><a name="cts_01_00011__en-us_topic_0179639609_li16908374285"></a><a name="en-us_topic_0179639609_li16908374285"></a><strong id="cts_01_00011__en-us_topic_0179639609_b84235270616337">Notification Name</strong>: Identifies key event notifications. This parameter is mandatory. The name can contain up to 64 characters. Only letters, digits, and underscores (_) are allowed.</p>
|
||||||
|
</li><li id="cts_01_00011__en-us_topic_0179639609_li39811928192214">Configure key operations.<ul id="cts_01_00011__en-us_topic_0179639609_ul1038384713513"><li id="cts_01_00011__en-us_topic_0179639609_li14383164719513"><strong id="cts_01_00011__en-us_topic_0179639609_b69849561928">Operation Type</strong>: Select <strong id="cts_01_00011__en-us_topic_0179639609_b13991356821">All</strong> or <strong id="cts_01_00011__en-us_topic_0179639609_b1199216565215">Custom</strong>.<ul id="cts_01_00011__en-us_topic_0179639609_ul28485134112442"><li id="cts_01_00011__en-us_topic_0179639609_li13163617112451"><strong id="cts_01_00011__en-us_topic_0179639609_b764155112165">All</strong>: This option is suitable if you have connected CTS to your own audit system.When <strong id="cts_01_00011__en-us_topic_0179639609_b13282102441711">All</strong> is chosen, you cannot deselect operations because all operations on all cloud services that have connected with CTS will trigger notifications.You are advised to use an SMN topic for which HTTPS is selected.</li><li id="cts_01_00011__en-us_topic_0179639609_li2294112317272"><strong id="cts_01_00011__en-us_topic_0179639609_b591211326182">Custom</strong>: This option is suitable for enterprises that require detection of high-risk, cost-sensitive, service-sensitive, and unauthorized operations. You can connect CTS to your own audit system for log analysis.<p id="cts_01_00011__en-us_topic_0179639609_p11901129171716">Select the operations that will trigger notifications. Up to 1000 operations of 100 services can be added for each notification. For details, see <a href="cts_03_0300.html">Supported Services and Operations</a>.</p>
|
||||||
|
</li></ul>
|
||||||
|
</li></ul>
|
||||||
|
</li><li id="cts_01_00011__en-us_topic_0179639609_li4336918449">Configure users.<p id="cts_01_00011__en-us_topic_0179639609_p4885125616538"><a name="cts_01_00011__en-us_topic_0179639609_li4336918449"></a><a name="en-us_topic_0179639609_li4336918449"></a>SMN messages will be sent to subscribers when the specified users perform key operations.</p>
|
||||||
|
<ul id="cts_01_00011__en-us_topic_0179639609_ul1217943143717"><li id="cts_01_00011__en-us_topic_0179639609_li16179431153720">If you select <strong id="cts_01_00011__en-us_topic_0179639609_b14308849183911">All users</strong>, SMN will notify subscribers of key operations initiated by all users.</li><li id="cts_01_00011__en-us_topic_0179639609_li717973114377">If you select <strong id="cts_01_00011__en-us_topic_0179639609_b87931504197">Specified users</strong>, SMN will notify subscribers of key operations initiated by your specified users. </li></ul>
|
||||||
|
</li><li id="cts_01_00011__en-us_topic_0179639609_li201879183492">Configure an SMN topic.<ul id="cts_01_00011__en-us_topic_0179639609_ul12619275533"><li id="cts_01_00011__en-us_topic_0179639609_li176191775318">If you select <strong id="cts_01_00011__en-us_topic_0179639609_b1779419531044">Yes</strong> for <strong id="cts_01_00011__en-us_topic_0179639609_b1779514531418">Send Notification</strong>, you can select an existing topic or click <strong id="cts_01_00011__en-us_topic_0179639609_b17795653646">Topic</strong> to create one on the SMN console.</li><li id="cts_01_00011__en-us_topic_0179639609_li761947185316">If you do not want to send notifications, no further action is required.</li></ul>
|
||||||
|
</li><li id="cts_01_00011__en-us_topic_0179639609_li131251298488">Click <strong id="cts_01_00011__en-us_topic_0179639609_b93191941165513">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_00011__en-us_topic_0179639609_section9309139191514"><h4 class="sectiontitle">View Key Event Notification</h4><ol id="cts_01_00011__en-us_topic_0179639609_ol1948141013179"><li id="cts_01_00011__en-us_topic_0179639609_li92002013191717">Log in to the management console.</li><li id="cts_01_00011__en-us_topic_0179639609_li14200181320171">Click <span><img id="cts_01_00011__en-us_topic_0179639609_image666214442816" src="en-us_image_0000001417288029.png"></span> in the upper left corner and choose <strong id="cts_01_00011__en-us_topic_0179639609_b156131224185312">Management & Deployment</strong> > <strong id="cts_01_00011__en-us_topic_0179639609_b166214414283">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_01_00011__en-us_topic_0179639609_li2200141318176">In the navigation pane on the left, choose <strong id="cts_01_00011__en-us_topic_0179639609_b1793614225224">Key Event Notifications</strong>. The <strong id="cts_01_00011__en-us_topic_0179639609_b19422022162218">Key Event Notifications</strong> page is displayed. </li><li id="cts_01_00011__en-us_topic_0179639609_li155511916151718">Click <strong id="cts_01_00011__en-us_topic_0179639609_b198432182239">View</strong> in the <strong id="cts_01_00011__en-us_topic_0179639609_b14538173012238">Operation</strong> column. The <strong id="cts_01_00011__en-us_topic_0179639609_b1171618915234">View Key Event Notifications</strong> page is displayed.</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_00011__en-us_topic_0179639609_section17271412161"><h4 class="sectiontitle">Enable Key Event Notification</h4><ol id="cts_01_00011__en-us_topic_0179639609_ol14992141751713"><li id="cts_01_00011__en-us_topic_0179639609_li10992817171711">Log in to the management console.</li><li id="cts_01_00011__en-us_topic_0179639609_li2992101717174">Click <span><img id="cts_01_00011__en-us_topic_0179639609_image999214175177" src="en-us_image_0000001366607830.png"></span> in the upper left corner and choose <strong id="cts_01_00011__en-us_topic_0179639609_b71813338537">Management & Deployment</strong> > <strong id="cts_01_00011__en-us_topic_0179639609_b513474411232">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_01_00011__en-us_topic_0179639609_li189920179176">In the navigation pane on the left, choose <strong id="cts_01_00011__en-us_topic_0179639609_b1810175417232">Key Event Notifications</strong>. The <strong id="cts_01_00011__en-us_topic_0179639609_b1217155402318">Key Event Notifications</strong> page is displayed. </li><li id="cts_01_00011__en-us_topic_0179639609_li95141154174915">Click <strong id="cts_01_00011__en-us_topic_0179639609_b61091050115316">Start</strong> in the <strong id="cts_01_00011__en-us_topic_0179639609_b19281245154612">Operation</strong> column. The <strong id="cts_01_00011__en-us_topic_0179639609_b19281345134610">Enabling Key Event Notifications</strong> page is displayed.<div class="note" id="cts_01_00011__en-us_topic_0179639609_note7955144813412"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cts_01_00011__en-us_topic_0179639609_p1595519482343">CTS can trigger key event notifications only after SMN is configured.</p>
|
||||||
|
</div></div>
|
||||||
|
</li><li id="cts_01_00011__en-us_topic_0179639609_li953318441204">Click <strong id="cts_01_00011__en-us_topic_0179639609_b1121217235255">Yes</strong> to enable the key event notification function.</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_00011__en-us_topic_0179639609_section189971828161617"><h4 class="sectiontitle">Modifying a Key Event Notification</h4><ol id="cts_01_00011__en-us_topic_0179639609_ol14976191915173"><li id="cts_01_00011__en-us_topic_0179639609_li1797615192170">Log in to the management console.</li><li id="cts_01_00011__en-us_topic_0179639609_li897613197172">Click <span><img id="cts_01_00011__en-us_topic_0179639609_image897661915179" src="en-us_image_0000001366287882.png"></span> in the upper left corner and choose <strong id="cts_01_00011__en-us_topic_0179639609_b4102821543">Management & Deployment</strong> > <strong id="cts_01_00011__en-us_topic_0179639609_b31829168264">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_01_00011__en-us_topic_0179639609_li19976101912172">In the navigation pane on the left, choose <strong id="cts_01_00011__en-us_topic_0179639609_b193018346207">Key Event Notifications</strong>. The <strong id="cts_01_00011__en-us_topic_0179639609_b11305344208">Key Event Notifications</strong> page is displayed. </li><li id="cts_01_00011__en-us_topic_0179639609_li143381842192119">Click <strong id="cts_01_00011__en-us_topic_0179639609_b368795064317">More</strong> > <strong id="cts_01_00011__en-us_topic_0179639609_b17321253174312">Modify</strong> in the <strong id="cts_01_00011__en-us_topic_0179639609_b3411144482612">Operation</strong> column. The <strong id="cts_01_00011__en-us_topic_0179639609_b1949385562618">Key Event Notifications</strong> page is displayed.</li><li id="cts_01_00011__en-us_topic_0179639609_li16322175802216">Then, click <strong id="cts_01_00011__en-us_topic_0179639609_b12428883270">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_00011__en-us_topic_0179639609_section15225143861612"><h4 class="sectiontitle">Deleting a Key Event Notification</h4><ol id="cts_01_00011__en-us_topic_0179639609_ol616002312178"><li id="cts_01_00011__en-us_topic_0179639609_li15160182331719">Log in to the management console.</li><li id="cts_01_00011__en-us_topic_0179639609_li81609233172">Click <span><img id="cts_01_00011__en-us_topic_0179639609_image19160132301715" src="en-us_image_0000001417089185.png"></span> in the upper left corner and choose <strong id="cts_01_00011__en-us_topic_0179639609_b79658913544">Management & Deployment</strong> > <strong id="cts_01_00011__en-us_topic_0179639609_b1670733011278">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_01_00011__en-us_topic_0179639609_li3160122315172">In the navigation pane on the left, choose <strong id="cts_01_00011__en-us_topic_0179639609_b398643616274">Key Event Notifications</strong>. The <strong id="cts_01_00011__en-us_topic_0179639609_b1998643602711">Key Event Notifications</strong> page is displayed. </li><li id="cts_01_00011__en-us_topic_0179639609_li17857123517233">Choose <strong id="cts_01_00011__en-us_topic_0179639609_b19499115894316">More</strong> > <strong id="cts_01_00011__en-us_topic_0179639609_b13747140154417">Delete</strong> in the <strong id="cts_01_00011__en-us_topic_0179639609_b15100195132717">Operation</strong> column. The <strong id="cts_01_00011__en-us_topic_0179639609_b1851008284">Delete Key Event Notifications</strong> page is displayed.</li><li id="cts_01_00011__en-us_topic_0179639609_li168571535192314">Click <strong id="cts_01_00011__en-us_topic_0179639609_b1369383519322">Yes</strong> to delete the key event notification function.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030581457.html">Getting Started</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
26
docs/cts/umn/cts_01_0003.html
Normal file
26
docs/cts/umn/cts_01_0003.html
Normal file
@ -0,0 +1,26 @@
|
|||||||
|
<a name="cts_01_0003"></a><a name="cts_01_0003"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">How CTS Functions</h1>
|
||||||
|
<div id="body8662426"><p id="cts_01_0003__en-us_topic_0179741689_p58710469155545">CTS connects to other cloud services on the cloud platform, records operations on cloud resources and the results, and stores these records in the form of trace files to OBS buckets in real time.</p>
|
||||||
|
<p id="cts_01_0003__en-us_topic_0179741689_p23523863155811">You can use CTS to create trackers to record trace files. If trace transfer has been configured, trace files will be stored in the OBS bucket that you have specified.</p>
|
||||||
|
<p id="cts_01_0003__en-us_topic_0179741689_p52755425183850">You can perform the following operations on a trace file:</p>
|
||||||
|
<ul id="cts_01_0003__en-us_topic_0179741689_ul14822373174923"><li id="cts_01_0003__en-us_topic_0179741689_li14442340174923">Trace file creation and storage<ul id="cts_01_0003__en-us_topic_0179741689_ul3821386210501"><li id="cts_01_0003__en-us_topic_0179741689_li838043810501">When you add, delete, or modify resources on services interconnected with CTS, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), and Image Management Service (IMS), the target services will record the operations and their results automatically and deliver them in the form of trace files to CTS for archiving.</li><li id="cts_01_0003__en-us_topic_0179741689_li1767361290">Operation records of the last seven days are displayed on the CTS console. If trace transfer has been enabled, operation records are periodically delivered to the OBS bucket that you have specified for long-term storage.</li></ul>
|
||||||
|
</li></ul>
|
||||||
|
<ul id="cts_01_0003__en-us_topic_0179741689_ul26561971174932"><li id="cts_01_0003__en-us_topic_0179741689_li9689073174932">Trace file query<ul id="cts_01_0003__en-us_topic_0179741689_ul47412741105037"><li id="cts_01_0003__en-us_topic_0179741689_li24061488105037">You can query operation records of the last seven days on the <strong id="cts_01_0003__en-us_topic_0179741689_b9605949181112">Trace List</strong> page by filter or time.</li><li id="cts_01_0003__en-us_topic_0179741689_li34778036105041">To query operation records earlier than seven days, you can download the trace files stored in OBS buckets if trace transfer has been configured.</li><li id="cts_01_0003__en-us_topic_0179741689_li43310262154949">You can enable, disable, configure, or delete a tracker on the <strong id="cts_01_0003__en-us_topic_0179741689_b84235270610169">Tracker List</strong> page.</li></ul>
|
||||||
|
<p id="cts_01_0003__en-us_topic_0179741689_p4283783154958">For example, if you create an image using IMS, the service will report the creation operation to CTS. Then, CTS will deliver the trace to an OBS bucket for storage if trace transfer has been configured. You can view trace files in the trace list. <a href="#cts_01_0003__en-us_topic_0179741689_fig160773715544">Figure 1</a> shows the working principle of CTS.</p>
|
||||||
|
</li></ul>
|
||||||
|
<div class="fignone" id="cts_01_0003__en-us_topic_0179741689_fig160773715544"><a name="cts_01_0003__en-us_topic_0179741689_fig160773715544"></a><a name="en-us_topic_0179741689_fig160773715544"></a><span class="figcap"><b>Figure 1 </b>How CTS functions</span><br><span><img id="cts_01_0003__en-us_topic_0179741689_image1960813795412" src="en-us_image_0000001231522936.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030579718.html">Service Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
||||||
26
docs/cts/umn/cts_01_0004.html
Normal file
26
docs/cts/umn/cts_01_0004.html
Normal file
@ -0,0 +1,26 @@
|
|||||||
|
<a name="cts_01_0004"></a><a name="cts_01_0004"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Application Scenarios</h1>
|
||||||
|
<div id="body8662426"><p id="cts_01_0004__en-us_topic_0179741535_p58012339141056">CTS can be used in the following four scenarios.</p>
|
||||||
|
<div class="section" id="cts_01_0004__en-us_topic_0179741535_section65243784104210"><h4 class="sectiontitle">Compliance Auditing</h4><p id="cts_01_0004__en-us_topic_0179741535_p5013900611126">CTS helps you obtain certifications for auditing in industry standards, such as PCI DSS and ISO 27001, for your service systems.</p>
|
||||||
|
<p id="cts_01_0004__en-us_topic_0179741535_p4859787111126">If you want to migrate your services to the cloud, you will need to ensure the compliance of your own service systems, and the cloud vendor you choose will need to ensure the compliance of your service systems and resources.</p>
|
||||||
|
<p id="cts_01_0004__en-us_topic_0179741535_p3472766011126">CTS plays an important role in compliance. The service records operations of almost all services and resources, and carries out security measures such as encryption, disaster recovery, and anti-tampering to ensure the integrity of traces during their transmission and storage. In addition, you can use CTS to design and implement solutions that help you obtain compliance certifications for your service systems.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_0004__en-us_topic_0179741535_section42199805104240"><h4 class="sectiontitle">Key Event Notifications</h4><p id="cts_01_0004__en-us_topic_0179741535_p1848111983212">CTS works with FunctionGraph to send notifications to natural persons or service APIs when any key operation is performed. The following are real application examples:</p>
|
||||||
|
<ul id="cts_01_0004__en-us_topic_0179741535_ul6004692104033"><li id="cts_01_0004__en-us_topic_0179741535_li3883927104033">You can configure HTTP or HTTPS notifications targeted at your independent systems and synchronize traces received by CTS to your own audit systems for auditing.</li><li id="cts_01_0004__en-us_topic_0179741535_li34955345104033">You can select a certain type of log as a trigger (such as file upload) in FunctionGraph to trigger the preset workflow (for example, convert the file format), simplifying service deployment and O&M and avoiding problems and risks.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_0004__en-us_topic_0179741535_section2133755910435"><h4 class="sectiontitle">Data Mining</h4><p id="cts_01_0004__en-us_topic_0179741535_p22854168104121">CTS mines data in traces to facilitate service health analysis, risk analysis, resource tracking, and cost analysis. You can also obtain the data from CTS and explore the data value yourself.</p>
|
||||||
|
<p id="cts_01_0004__en-us_topic_0179741535_p4360927104121">A trace contains up to fields, recording when an operation was performed by a specific user on a specific resource and the IP address from which the operation was performed.</p>
|
||||||
|
<p id="cts_01_0004__en-us_topic_0179741535_p39248344104121">By configuring HTTP or HTTPS notifications, you can synchronize traces to your own system for analysis. In addition, CTS is connected to Cloud Eye and Log Tank Service (LTS) to help you monitor high-risk operations, detect unauthorized operations, and analyze resource usage.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_01_0004__en-us_topic_0179741535_section298272104332"><h4 class="sectiontitle">Fault Locating and Analysis</h4><p id="cts_01_0004__en-us_topic_0179741535_p37930674104150">You can configure filters to pinpoint the faulty operation and its details when a fault occurs, reducing the time and manpower required for detecting, locating, and fixing faults.</p>
|
||||||
|
<p id="cts_01_0004__en-us_topic_0179741535_p5831752104150">CTS provides the following search dimensions: trace type, trace source, resource type, filter, operator and trace status. Each trace contains the request and response of an operation. Querying traces is one of the most efficient methods for locating a fault.</p>
|
||||||
|
<p id="cts_01_0004__en-us_topic_0179741535_p52485768104150">If a problem occurs on the cloud, you can configure filters to search for all suspicious operations in a specified time period. You can then synchronize the relevant traces to O&M and customer service personnel who will handle the problem.</p>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030579718.html">Service Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
13
docs/cts/umn/cts_01_0005.html
Normal file
13
docs/cts/umn/cts_01_0005.html
Normal file
@ -0,0 +1,13 @@
|
|||||||
|
<a name="cts_01_0005"></a><a name="cts_01_0005"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Billing</h1>
|
||||||
|
<div id="body8662426"><p id="cts_01_0005__en-us_topic_0179741550_p1275320177515">You can use the basic functions of CTS for free, including enabling a tracker, tracking traces, as well as storing and querying traces of the last seven days. In addition, CTS works with other services to provide you with value-added functions such as trace file transfer and encryption.</p>
|
||||||
|
<p id="cts_01_0005__en-us_topic_0179741550_p6058545111289">Value-added functions:</p>
|
||||||
|
<ul id="cts_01_0005__en-us_topic_0179741550_ul65242556114212"><li id="cts_01_0005__en-us_topic_0179741550_li50312100114212">Trace transfer: OBS is required. Trace files configured for the management tracker are permanently stored.</li><li id="cts_01_0005__en-us_topic_0179741550_li35251733123211">Trace analysis: This function is provided by CTS and is free to use. However, it depends on log storage of Log Tank Service (LTS), which may generate fees.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030579718.html">Service Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
206
docs/cts/umn/cts_01_0006.html
Normal file
206
docs/cts/umn/cts_01_0006.html
Normal file
File diff suppressed because it is too large
Load Diff
21
docs/cts/umn/cts_02_0001.html
Normal file
21
docs/cts/umn/cts_02_0001.html
Normal file
@ -0,0 +1,21 @@
|
|||||||
|
<a name="cts_02_0001"></a><a name="cts_02_0001"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Enabling CTS</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_02_0001__en-us_topic_0179639580_section60206522184734"><h4 class="sectiontitle">Scenarios</h4><p id="cts_02_0001__en-us_topic_0179639580_p17783542182613">You need to enable Cloud Trace Service (CTS) before using it. A management tracker named <strong id="cts_02_0001__en-us_topic_0179639580_b574464415415">system</strong> is automatically created when CTS is enabled. All traces recorded by CTS are associated with the tracker.</p>
|
||||||
|
<p id="cts_02_0001__en-us_topic_0179639580_p678344213266">Trace files must be stored in an Object Storage Service (OBS) bucket. Ensure that you have enabled OBS and have full permissions for the OBS bucket you are going to use. By default, only the owner of OBS buckets can access the buckets and all objects contained in the buckets, but the owner can grant access permissions to other services and users by configuring access policies.</p>
|
||||||
|
<p id="cts_02_0001__en-us_topic_0179639580_p3806222294436">This section describes how to enable CTS.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_02_0001__en-us_topic_0179639580_section043432413438"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_02_0001__en-us_topic_0179639580_p10571132278">You have enabled OBS.</p>
|
||||||
|
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_02_0001__en-us_topic_0179639580_section789915422345"><h4 class="sectiontitle">Procedure</h4><ol id="cts_02_0001__en-us_topic_0179639580_ol510016169458"><li id="cts_02_0001__en-us_topic_0179639580_li530093789458">Log in to the management console.</li><li id="cts_02_0001__en-us_topic_0179639580_li597456569458">Click <span><img id="cts_02_0001__en-us_topic_0179639580_image1667711455215" src="en-us_image_0000001232728809.png"></span> in the upper left corner and choose <strong id="cts_02_0001__en-us_topic_0179639580_b14678741529">Management & Deployment</strong> > <strong id="cts_02_0001__en-us_topic_0179639580_b367818417520">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_02_0001__en-us_topic_0179639580_li410790839458">Choose <strong id="cts_02_0001__en-us_topic_0179639580_b174320328119">Tracker List</strong> in the navigation pane on the left.</li><li id="cts_02_0001__en-us_topic_0179639580_li225657719458">Click <strong id="cts_02_0001__en-us_topic_0179639580_b175694439183">Enable CTS</strong>.</li><li id="cts_02_0001__en-us_topic_0179639580_li34415716101720">In the displayed dialog box, click <strong id="cts_02_0001__en-us_topic_0179639580_b942254864218">Enable</strong>. A tracker is automatically created.</li></ol>
|
||||||
|
<p id="cts_02_0001__en-us_topic_0179639580_p16947979171336">You can view the tracker information on the <strong id="cts_02_0001__en-us_topic_0179639580_b1876943015191">Tracker List</strong> page.</p>
|
||||||
|
<p id="cts_02_0001__en-us_topic_0179639580_p65113063183035">The tracker records operations on cloud resources performed by the tenant who creates the tracker. For details about the cloud services supported by CTS, see section "Supported Services and Operations" in the <em id="cts_02_0001__en-us_topic_0179639580_i1821219516342">User Guide</em>.</p>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030581457.html">Getting Started</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
36
docs/cts/umn/cts_02_0003.html
Normal file
36
docs/cts/umn/cts_02_0003.html
Normal file
@ -0,0 +1,36 @@
|
|||||||
|
<a name="cts_02_0003"></a><a name="cts_02_0003"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Querying Archived Traces</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_02_0003__en-us_topic_0179639508_section1534311495828"><h4 class="sectiontitle">Scenarios</h4><p id="cts_02_0003__en-us_topic_0179639508_p1901988917341">CTS periodically sends trace files to OBS buckets. A trace file is a collection of traces. CTS generates trace files based on services and transfer cycle, and adjusts the number of traces contained in each trace file as needed.</p>
|
||||||
|
<p id="cts_02_0003__en-us_topic_0179639508_p2525842395828">This section describes how to obtain historical operation records from trace files downloaded from the OBS bucket.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_02_0003__en-us_topic_0179639508_section18621912172323"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_02_0003__en-us_topic_0179639508_p19610739172324">You have configured a tracker. For details, see <a href="cts_03_0002.html">Configuring a Tracker</a>.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_02_0003__en-us_topic_0179639508_section4763421295828"><h4 class="sectiontitle">Procedure</h4><ol id="cts_02_0003__en-us_topic_0179639508_ol2707562395828"><li id="cts_02_0003__en-us_topic_0179639508_li618917495828">Log in to the management console.</li><li id="cts_02_0003__en-us_topic_0179639508_li5346313795828">Click <span><img id="cts_02_0003__en-us_topic_0179639508_image1045015451188" src="en-us_image_0000001232728979.png"></span> in the upper left corner and choose <strong id="cts_02_0003__en-us_topic_0179639508_b1743814131578">Management & Deployment</strong> > <strong id="cts_02_0003__en-us_topic_0179639508_b144506459814">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_02_0003__en-us_topic_0179639508_li3441308995828">Choose <strong id="cts_02_0003__en-us_topic_0179639508_b1186114313014">Tracker List</strong> in the navigation pane on the left.</li><li id="cts_02_0003__en-us_topic_0179639508_li1617149695828">Click a bucket in the <strong id="cts_02_0003__en-us_topic_0179639508_b1785205217818">OBS Bucket</strong> column.<div class="fignone" id="cts_02_0003__en-us_topic_0179639508_fig971717479509"><span class="figcap"><b>Figure 1 </b>Selecting an OBS bucket</span><br><span><img id="cts_02_0003__en-us_topic_0179639508_image9718204715502" src="en-us_image_0000001467612717.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li><li id="cts_02_0003__en-us_topic_0179639508_li5554945111133">In the OBS bucket, select the trace to be viewed based on the trace file storage path, and download the file to the default download path of the browser. If you need to save the event file to a custom path, click <strong id="cts_02_0003__en-us_topic_0179639508_b91151243155415">Download As</strong> on the right.<ul id="cts_02_0003__en-us_topic_0179639508_ul148190001162"><li id="cts_02_0003__en-us_topic_0179639508_li279919171162">The trace file storage path is as follows:<p id="cts_02_0003__en-us_topic_0179639508_p47428456155727"><a name="cts_02_0003__en-us_topic_0179639508_li279919171162"></a><a name="en-us_topic_0179639508_li279919171162"></a><strong id="cts_02_0003__en-us_topic_0179639508_b1121122891210"><em id="cts_02_0003__en-us_topic_0179639508_i1039932631211">OBS bucket name > CloudTraces > Region > Year > Month > Day > Tracker name > Service directory</em></strong></p>
|
||||||
|
<p id="cts_02_0003__en-us_topic_0179639508_p4663776495828">An example is <strong id="cts_02_0003__en-us_topic_0179639508_b126921336121310"><em id="cts_02_0003__en-us_topic_0179639508_i18364736121319">User-defined name > CloudTraces > region > 2016 > 5 > 19 > system > ECS</em></strong>.</p>
|
||||||
|
</li></ul>
|
||||||
|
<ul id="cts_02_0003__en-us_topic_0179639508_ul342885641165"><li id="cts_02_0003__en-us_topic_0179639508_li529846131165">The trace file naming format is as follows:<p id="cts_02_0003__en-us_topic_0179639508_p1621688895828"><a name="cts_02_0003__en-us_topic_0179639508_li529846131165"></a><a name="en-us_topic_0179639508_li529846131165"></a><strong id="cts_02_0003__en-us_topic_0179639508_b3493124141517"><em id="cts_02_0003__en-us_topic_0179639508_i12115114113152">Trace file prefix_CloudTrace_Region/Region-project_Time when the trace file was uploaded to OBS: Year-Month-DayTHour-Minute-SecondZ_Random characters.json.gz</em></strong></p>
|
||||||
|
<p id="cts_02_0003__en-us_topic_0179639508_p577818395828">An example is <em id="cts_02_0003__en-us_topic_0179639508_i449391271613"><strong id="cts_02_0003__en-us_topic_0179639508_b9493612131610">File Prefix</strong></em><strong id="cts_02_0003__en-us_topic_0179639508_b849381216160">_CloudTrace_region-project_2016-05-30T16-20-56Z_21d36ced8c8af71e.json.gz</strong>.</p>
|
||||||
|
</li></ul>
|
||||||
|
<div class="note" id="cts_02_0003__en-us_topic_0179639508_note4679381511655"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cts_02_0003__en-us_topic_0179639508_p564014491176">The OBS bucket name and trace file prefix are user-defined, and other parameters are automatically generated.</p>
|
||||||
|
</div></div>
|
||||||
|
<p id="cts_02_0003__en-us_topic_0179639508_p1590129142913">For details about key fields in the CTS trace structure, see <a href="cts_03_0010.html">Trace Structure</a> and <a href="cts_03_0011.html">Example Traces</a>.</p>
|
||||||
|
<div class="fignone" id="cts_02_0003__en-us_topic_0179639508_fig67924624816"><span class="figcap"><b>Figure 2 </b>Viewing trace file content</span><br><span><img id="cts_02_0003__en-us_topic_0179639508_image579194654810" src="en-us_image_0000001410476944.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li><li id="cts_02_0003__en-us_topic_0179639508_li60299728173928">Decompress the downloaded package to obtain a JSON file with the same name as the package. Open the JSON file using a text file editor to view traces.<div class="fignone" id="cts_02_0003__en-us_topic_0179639508_fig17496885104024"><span class="figcap"><b>Figure 3 </b>JSON file</span><br><span><img id="cts_02_0003__en-us_topic_0179639508_image7961553104024" src="en-us_image_0296237505.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030581457.html">Getting Started</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
||||||
33
docs/cts/umn/cts_02_0005.html
Normal file
33
docs/cts/umn/cts_02_0005.html
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
<a name="cts_02_0005"></a><a name="cts_02_0005"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Querying Real-Time Traces</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_p333055219577">After CTS is enabled, the tracker starts recording operations on cloud resources. CTS stores operation records for the last seven days.</p>
|
||||||
|
<p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_p3008599195238">This section describes how to query operation records of the last seven days on the CTS console.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_section6300091795238"><h4 class="sectiontitle">Procedure</h4><ol id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_ol3001478295238"><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_li3954991595238">Log in to the management console.</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_li3694304795238">Click <span><img id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_image1338112524417" src="en-us_image_0000001187249376.png"></span> in the upper left corner and choose <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b1790833133719">Management & Deployment</strong> > <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b934662524415">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_li4560416895238">In the navigation pane on the left, choose <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b42162954165740">Trace List</strong>.</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_li13293145514314">Set filters to search for your desired traces, as shown in <a href="#cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_f402e07400398464a97ed73852447a5de">Figure 1</a>. The following filters are available:<div class="fignone" id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_f402e07400398464a97ed73852447a5de"><a name="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_f402e07400398464a97ed73852447a5de"></a><a name="en-us_topic_0000001285438117_en-us_topic_0179639644_f402e07400398464a97ed73852447a5de"></a><span class="figcap"><b>Figure 1 </b>Filters</span><br><span><img id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_i9dd056eb8e3648e697edd19dff8ef9fa" src="en-us_image_0295789897.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
<div class="p" id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_ade2312c3996b48b3acb7dceec5f0838f"><ul class="subitemlist" id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_u06be46012c3c4188b825e2dd7369090f"><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_lc8d4f52d6cde4269b952549a9a943d7b"><strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b528314916259">Trace Source</strong>, <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b228913922511">Resource Type</strong>, and <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b17289159172511">Search By</strong><p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_en-us_topic_0030598499_p191056131255">Select a filter from the drop-down list.</p>
|
||||||
|
<p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_ab5acbaebe8f240c2a36e34644e2d6027">If you select <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b2067310533216">Resource ID</strong> for <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b56732531325">Search By</strong>, specify a resource ID.</p>
|
||||||
|
</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_l765f93c9085644a4ad1cc9ade0ae751d"><strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b98151395276">Operator</strong>: Select a user.</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_l327190a2a0b74af8a2de339832630494"><strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b6981161112286">Trace Status</strong>: Select <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b1298716111281">All trace statuses</strong>, <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b7987181115281">Normal</strong>, <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b2988181112810">Warning</strong>, or <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b99881511132820">Incident</strong>.</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_l010c900905114ec895708573dde4a714">Time range: You can query traces generated during any time range in the last few days.</li></ul>
|
||||||
|
</div>
|
||||||
|
</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_li16224135215470">Click <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b17617115510179">Export</strong> on the right to export all traces in the query result as a CSV file. The file can contain up to 5000 records.</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_li944262995238">Click <span><img id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_image1224105211452" src="en-us_image_0179639581.jpg" title="Click to enlarge" class="imgResize"></span> on the left of a trace to expand its details.<p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_p1770896102611"></p>
|
||||||
|
<p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_p1325965010460"><span><img id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_image202591150134611" src="en-us_image_0000001460694917.png" title="Click to enlarge" class="imgResize"></span></p>
|
||||||
|
<p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_p5348416194010"></p>
|
||||||
|
</li><li id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_li344192371514">Click <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b15749435122">View Trace</strong> in the <strong id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_b210414043517">Operation</strong> column. The trace details are displayed.<p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_p1214616272506"><span><img id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_image1714662755019" src="en-us_image_0000001410575694.png" title="Click to enlarge" class="imgResize"></span></p>
|
||||||
|
<p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_p19963139165010"><span><img id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_image20963499507" src="en-us_image_0179639495.png" title="Click to enlarge" class="imgResize"></span></p>
|
||||||
|
<p id="cts_02_0005__en-us_topic_0000001285438117_en-us_topic_0179639644_p1396369135019">For details about key fields in the trace structure, see <a href="cts_03_0010.html">Trace Structure</a> and <a href="cts_03_0011.html">Example Traces</a>.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_03_01436.html">Trace Management</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
||||||
36
docs/cts/umn/cts_02_0006.html
Normal file
36
docs/cts/umn/cts_02_0006.html
Normal file
@ -0,0 +1,36 @@
|
|||||||
|
<a name="cts_02_0006"></a><a name="cts_02_0006"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Querying Archived Traces</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_section1534311495828"><h4 class="sectiontitle">Scenarios</h4><p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p1901988917341">CTS periodically sends trace files to OBS buckets. A trace file is a collection of traces. CTS generates trace files based on services and transfer cycle, and adjusts the number of traces contained in each trace file as needed.</p>
|
||||||
|
<p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p2525842395828">This section describes how to obtain historical operation records from trace files downloaded from the OBS bucket.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_section18621912172323"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p19610739172324">You have configured a tracker. For details, see <a href="cts_03_0002.html">Configuring a Tracker</a>.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_section4763421295828"><h4 class="sectiontitle">Procedure</h4><ol id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_ol2707562395828"><li id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li618917495828">Log in to the management console.</li><li id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li5346313795828">Click <span><img id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_image1045015451188" src="en-us_image_0000001232728979.png"></span> in the upper left corner and choose <strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b1743814131578">Management & Deployment</strong> > <strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b144506459814">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li3441308995828">Choose <strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b1186114313014">Tracker List</strong> in the navigation pane on the left.</li><li id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li1617149695828">Click a bucket in the <strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b1785205217818">OBS Bucket</strong> column.<div class="fignone" id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_fig971717479509"><span class="figcap"><b>Figure 1 </b>Selecting an OBS bucket</span><br><span><img id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_image9718204715502" src="en-us_image_0000001467612717.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li><li id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li5554945111133">In the OBS bucket, select the trace to be viewed based on the trace file storage path, and download the file to the default download path of the browser. If you need to save the event file to a custom path, click <strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b91151243155415">Download As</strong> on the right.<ul id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_ul148190001162"><li id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li279919171162">The trace file storage path is as follows:<p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p47428456155727"><a name="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li279919171162"></a><a name="en-us_topic_0000001285318397_en-us_topic_0179639508_li279919171162"></a><strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b1121122891210"><em id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_i1039932631211">OBS bucket name > CloudTraces > Region > Year > Month > Day > Tracker name > Service directory</em></strong></p>
|
||||||
|
<p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p4663776495828">An example is <strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b126921336121310"><em id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_i18364736121319">User-defined name > CloudTraces > region > 2016 > 5 > 19 > system > ECS</em></strong>.</p>
|
||||||
|
</li></ul>
|
||||||
|
<ul id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_ul342885641165"><li id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li529846131165">The trace file naming format is as follows:<p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p1621688895828"><a name="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li529846131165"></a><a name="en-us_topic_0000001285318397_en-us_topic_0179639508_li529846131165"></a><strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b3493124141517"><em id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_i12115114113152">Trace file prefix_CloudTrace_Region/Region-project_Time when the trace file was uploaded to OBS: Year-Month-DayTHour-Minute-SecondZ_Random characters.json.gz</em></strong></p>
|
||||||
|
<p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p577818395828">An example is <em id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_i449391271613"><strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b9493612131610">File Prefix</strong></em><strong id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_b849381216160">_CloudTrace_region-project_2016-05-30T16-20-56Z_21d36ced8c8af71e.json.gz</strong>.</p>
|
||||||
|
</li></ul>
|
||||||
|
<div class="note" id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_note4679381511655"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p564014491176">The OBS bucket name and trace file prefix are user-defined, and other parameters are automatically generated.</p>
|
||||||
|
</div></div>
|
||||||
|
<p id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_p1590129142913">For details about key fields in the CTS trace structure, see <a href="cts_03_0010.html">Trace Structure</a> and <a href="cts_03_0011.html">Example Traces</a>.</p>
|
||||||
|
<div class="fignone" id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_fig67924624816"><span class="figcap"><b>Figure 2 </b>Viewing trace file content</span><br><span><img id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_image579194654810" src="en-us_image_0000001410476944.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li><li id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_li60299728173928">Decompress the downloaded package to obtain a JSON file with the same name as the package. Open the JSON file using a text file editor to view traces.<div class="fignone" id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_fig17496885104024"><span class="figcap"><b>Figure 3 </b>JSON file</span><br><span><img id="cts_02_0006__en-us_topic_0000001285318397_en-us_topic_0179639508_image7961553104024" src="en-us_image_0296237505.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_03_01436.html">Trace Management</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
||||||
17
docs/cts/umn/cts_031_001.html
Normal file
17
docs/cts/umn/cts_031_001.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<a name="cts_031_001"></a><a name="cts_031_001"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Permissions Management</h1>
|
||||||
|
<div id="body0000001475134230"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_031_002.html">Creating a User and Granting Permissions</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_031_003.html">Custom Policies</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030628003.html">User Guide</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
21
docs/cts/umn/cts_031_002.html
Normal file
21
docs/cts/umn/cts_031_002.html
Normal file
@ -0,0 +1,21 @@
|
|||||||
|
<a name="cts_031_002"></a><a name="cts_031_002"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Creating a User and Granting Permissions</h1>
|
||||||
|
<div id="body0000001474974246"><p id="cts_031_002__en-us_topic_0207902851_p188381303204">For fine-grained management of CTS permissions, you can use <a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0026.html" target="_blank" rel="noopener noreferrer">Identity and Access Management (IAM)</a>. With IAM, you can:</p>
|
||||||
|
<ul id="cts_031_002__en-us_topic_0207902851_ul583810010208"><li id="cts_031_002__en-us_topic_0207902851_li58386082011">Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing CTS resources.</li><li id="cts_031_002__en-us_topic_0207902851_li6838110132018">Manage permissions on a principle of least permissions (PoLP) basis.</li><li id="cts_031_002__en-us_topic_0207902851_li483815013208">Entrust an account or cloud service to perform efficient O&M on your CTS resources.</li></ul>
|
||||||
|
<p id="cts_031_002__en-us_topic_0207902851_p118381405208">If your account does not require individual IAM users, skip this section.</p>
|
||||||
|
<div class="section" id="cts_031_002__en-us_topic_0207902851_section16528787219"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_031_002__en-us_topic_0207902851_p99333127215">Learn about the permissions (see <a href="https://docs.otc.t-systems.com/permissions/index.html" target="_blank" rel="noopener noreferrer">Permissions</a>) supported by CTS and choose policies or roles according to your requirements.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_031_002__en-us_topic_0207902851_section17188122816365"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="cts_031_002__en-us_topic_0207902851_fig33331434153117"><span class="figcap"><b>Figure 1 </b>Process of granting CTS permissions</span><br><span><img class="eddx" id="cts_031_002__en-us_topic_0207902851_image133373410315" src="en-us_image_0000001525454037.png"></span></div>
|
||||||
|
<ol id="cts_031_002__en-us_topic_0207902851_ol896174893315"><li id="cts_031_002__en-us_topic_0207902851_li10961848173315"><a name="cts_031_002__en-us_topic_0207902851_li10961848173315"></a><a name="en-us_topic_0207902851_li10961848173315"></a><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0030.html" target="_blank" rel="noopener noreferrer">Create a user group and assign permissions</a>.<p id="cts_031_002__en-us_topic_0207902851_p8961154813332">Create a user group on the IAM console, and attach the <strong id="cts_031_002__b86996350032942">CTS Administrator</strong> policy to the group.</p>
|
||||||
|
</li><li id="cts_031_002__en-us_topic_0207902851_li6961134814332"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0031.html" target="_blank" rel="noopener noreferrer">Create a user and add the user to the user group</a>.<p id="cts_031_002__en-us_topic_0207902851_p896144817336">Create a user on the IAM console and add the user to the user group created in <a href="#cts_031_002__en-us_topic_0207902851_li10961848173315">1</a>.</p>
|
||||||
|
</li><li id="cts_031_002__en-us_topic_0207902851_li1996111483331"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0032.html" target="_blank" rel="noopener noreferrer">Log in as the created user</a> and verify permissions.<p id="cts_031_002__en-us_topic_0207902851_p119612048193317">Log in to the console by using the created user and verify permissions in the authorized region.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_031_001.html">Permissions Management</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
57
docs/cts/umn/cts_031_003.html
Normal file
57
docs/cts/umn/cts_031_003.html
Normal file
@ -0,0 +1,57 @@
|
|||||||
|
<a name="cts_031_003"></a><a name="cts_031_003"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Custom Policies</h1>
|
||||||
|
<div id="body0000001525294081"><p id="cts_031_003__p1363833161415">Custom policies can be created to supplement the system-defined policies of CTS. For the actions supported for custom policies, see "Permissions Policies and Supported Actions" in the <em id="cts_031_003__i82886478411">API Reference</em>.</p>
|
||||||
|
<p id="cts_031_003__p1391019913815">You can create custom policies in either of the following ways:</p>
|
||||||
|
<ul id="cts_031_003__ul1146431393818"><li id="cts_031_003__li5764181518386">Visual editor: Select cloud services, actions, resources, and request conditions. You do not need to have knowledge of the policy syntax.</li><li id="cts_031_003__li546410135389">JSON: Edit policies from scratch or based on an existing policy in JSON format.</li></ul>
|
||||||
|
<p id="cts_031_003__p82911030103912">For details about how to create custom policies, see <a href="https://docs.otc.t-systems.com/usermanual/iam/en-us_topic_0274187246.html" target="_blank" rel="noopener noreferrer">Creating a Custom Policy</a>. The following section contains examples of common CTS custom policies.</p>
|
||||||
|
<div class="section" id="cts_031_003__section7529733164812"><h4 class="sectiontitle">Example Custom Policies</h4><ul id="cts_031_003__ul2504185715494"><li id="cts_031_003__li5504357164912">Example 1: Authorize a user to view the event list.<pre class="screen" id="cts_031_003__screen48273211535">{
|
||||||
|
"Version": "1.1",
|
||||||
|
"Statement": [
|
||||||
|
{
|
||||||
|
"Effect": "Allow",
|
||||||
|
"Action": [
|
||||||
|
"cts:trace:list"
|
||||||
|
]
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}</pre>
|
||||||
|
</li><li id="cts_031_003__li3652938178">Example 2: Deny modification and delete the tracker.<p id="cts_031_003__p1892813119464"><a name="cts_031_003__li3652938178"></a><a name="li3652938178"></a>A policy with only "Deny" permissions must be used in conjunction with other policies. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.</p>
|
||||||
|
<p id="cts_031_003__p17928101124619">The following method can be used if you need to assign permissions of the <strong id="cts_031_003__b18659928184820">CTS FullAccess</strong> policy to a user but also forbid the user from modifying or deleting trackers. Create a custom policy to disallow tracker deletion or modifying and assign both policies to the group the user belongs to. Then the user can perform all operations on CTS except deleting or modifying trackers. The following is an example of a deny policy:</p>
|
||||||
|
<pre class="screen" id="cts_031_003__screen39281011144617">{
|
||||||
|
"Version": "1.1",
|
||||||
|
"Statement": [
|
||||||
|
{
|
||||||
|
"Effect": "Deny",
|
||||||
|
"Action": [
|
||||||
|
"cts:tracker:delete",
|
||||||
|
"cts:tracker:update"
|
||||||
|
]
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}</pre>
|
||||||
|
</li><li id="cts_031_003__li8475316125413">Example 3: Define actions for multiple services in a policy<p id="cts_031_003__p466319313484"><a name="cts_031_003__li8475316125413"></a><a name="li8475316125413"></a>A custom policy can contain the actions of multiple services that are of the same type: global or project-level. The following is a policy with multiple statements:</p>
|
||||||
|
<pre class="screen" id="cts_031_003__screen46646311485">{{
|
||||||
|
"Version": "1.1",
|
||||||
|
"Statement": [
|
||||||
|
{
|
||||||
|
"Effect": "Allow",
|
||||||
|
"Action": [
|
||||||
|
"cts:tracker:list",
|
||||||
|
"cts:trace:list",
|
||||||
|
"lts:groups:get",
|
||||||
|
"lts:logs:list",
|
||||||
|
"lts:logstreams:list"
|
||||||
|
]
|
||||||
|
}
|
||||||
|
]
|
||||||
|
}</pre>
|
||||||
|
</li></ul>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_031_001.html">Permissions Management</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
17
docs/cts/umn/cts_03_0000.html
Normal file
17
docs/cts/umn/cts_03_0000.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<a name="cts_03_0000"></a><a name="cts_03_0000"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Tracker Management</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_03_0002.html">Configuring a Tracker</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_03_0003.html">Disabling or Enabling a Tracker</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030628003.html">User Guide</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
71
docs/cts/umn/cts_03_0002.html
Normal file
71
docs/cts/umn/cts_03_0002.html
Normal file
@ -0,0 +1,71 @@
|
|||||||
|
<a name="cts_03_0002"></a><a name="cts_03_0002"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Configuring a Tracker</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_03_0002__en-us_topic_0170932828_section44745431173049"><h4 class="sectiontitle">Scenario</h4><p id="cts_03_0002__en-us_topic_0170932828_ae0731f4d0fbb4d4fa9375617d2732bd7">You can configure the file prefix of trackers on the CTS console no matter whether the trackers are enabled or not. For enabled trackers, you can also configure OBS buckets for trace transfer and LTS dumps.</p>
|
||||||
|
<ul id="cts_03_0002__en-us_topic_0170932828_ul197861137025"><li id="cts_03_0002__en-us_topic_0170932828_li3343910095343">You can select an existing OBS bucket for trace transfer. CTS will automatically attach a required policy to the OBS bucket.</li><li id="cts_03_0002__en-us_topic_0170932828_li078793710213">If you modify the trace file prefix of a tracker, the OBS bucket policy will not be affected.</li></ul>
|
||||||
|
<div class="note" id="cts_03_0002__en-us_topic_0170932828_note1944845171413"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cts_03_0002__en-us_topic_0170932828_p1394494541411">There are three storage classes of OBS buckets, Standard, Infrequent Access, and Archive. You must use Standard OBS buckets for trace transfer because CTS needs to frequently access the OBS buckets.</p>
|
||||||
|
</div></div>
|
||||||
|
<p id="cts_03_0002__en-us_topic_0170932828_p33867259112732">The configuration will take effect immediately after it is complete.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0002__en-us_topic_0170932828_section13948718173426"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_03_0002__en-us_topic_0170932828_p47704382173428">You have enabled CTS.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0002__en-us_topic_0170932828_section3571284110915"><h4 class="sectiontitle">Procedure</h4><ol id="cts_03_0002__en-us_topic_0170932828_ol5994761510915"><li id="cts_03_0002__en-us_topic_0170932828_li2952081710915">Log in to the management console.</li><li id="cts_03_0002__en-us_topic_0170932828_li913677210915">Click <span><img id="cts_03_0002__en-us_topic_0170932828_image8849822132811" src="en-us_image_0000001187949118.png"></span> in the upper left corner and choose <strong id="cts_03_0002__en-us_topic_0170932828_b068516527285">Management & Deployment</strong> > <strong id="cts_03_0002__en-us_topic_0170932828_b4849172214285">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_03_0002__en-us_topic_0170932828_li5130618410915">Choose <strong id="cts_03_0002__en-us_topic_0170932828_b598117737">Tracker List</strong> in the navigation pane on the left.</li><li id="cts_03_0002__en-us_topic_0170932828_li590643495529">On the right of the tracker information, click <strong id="cts_03_0002__en-us_topic_0170932828_b1763794182016">Configure</strong>.</li><li id="cts_03_0002__en-us_topic_0170932828_li9235823153311">Configure a transfer.
|
||||||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cts_03_0002__en-us_topic_0170932828_table1810015091011" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters for configuring a transfer</caption><thead align="left"><tr id="cts_03_0002__en-us_topic_0170932828_row171006071017"><th align="left" class="cellrowborder" valign="top" width="20.46%" id="mcps1.3.3.2.5.1.2.3.1.1"><p id="cts_03_0002__en-us_topic_0170932828_p710015012109">Parameter</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="79.54%" id="mcps1.3.3.2.5.1.2.3.1.2"><p id="cts_03_0002__en-us_topic_0170932828_p1510040131019">Description</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="cts_03_0002__en-us_topic_0170932828_row141003081019"><td class="cellrowborder" valign="top" width="20.46%" headers="mcps1.3.3.2.5.1.2.3.1.1 "><p id="cts_03_0002__en-us_topic_0170932828_p71001706106">Transfer to OBS</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="79.54%" headers="mcps1.3.3.2.5.1.2.3.1.2 "><p id="cts_03_0002__en-us_topic_0170932828_p171001407104">If you select <strong id="cts_03_0002__en-us_topic_0170932828_b34218171817">Yes</strong>, select an existing OBS bucket and set <strong id="cts_03_0002__en-us_topic_0170932828_b0423181710810">File Prefix</strong>.</p>
|
||||||
|
<p id="cts_03_0002__en-us_topic_0170932828_p510014019100">When <strong id="cts_03_0002__en-us_topic_0170932828_b11747149172111">Transfer to OBS</strong> is disabled, no operation is required.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="cts_03_0002__en-us_topic_0170932828_row610080161014"><td class="cellrowborder" valign="top" width="20.46%" headers="mcps1.3.3.2.5.1.2.3.1.1 "><p id="cts_03_0002__en-us_topic_0170932828_p61001207106">OBS Bucket</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="79.54%" headers="mcps1.3.3.2.5.1.2.3.1.2 "><p id="cts_03_0002__en-us_topic_0170932828_p310010161012"><strong id="cts_03_0002__en-us_topic_0170932828_b181040181011">New</strong>: If this function is enabled, an OBS bucket will be created automatically with the name you enter.</p>
|
||||||
|
<p id="cts_03_0002__en-us_topic_0170932828_p141001201107">Select <strong id="cts_03_0002__en-us_topic_0170932828_b188601648191713">Existing</strong>: Select an existing OBS bucket.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="cts_03_0002__en-us_topic_0170932828_row15100106102"><td class="cellrowborder" valign="top" width="20.46%" headers="mcps1.3.3.2.5.1.2.3.1.1 "><p id="cts_03_0002__en-us_topic_0170932828_p610012014108">Select Bucket</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="79.54%" headers="mcps1.3.3.2.5.1.2.3.1.2 "><p id="cts_03_0002__en-us_topic_0170932828_p31001061012">When you select <strong id="cts_03_0002__en-us_topic_0170932828_b4625175782016">New</strong>, enter an OBS bucket name. The OBS bucket name cannot be empty. It can contain 3 to 63 characters, including only lowercase letters, digits, hyphens (-), and periods (.). It cannot contain two consecutive periods (..). For example, <strong id="cts_03_0002__en-us_topic_0170932828_b01671207236">my..bucket</strong> is not allowed.</p>
|
||||||
|
<p id="cts_03_0002__en-us_topic_0170932828_p210010111012">When you select <strong id="cts_03_0002__en-us_topic_0170932828_b92201628142511">Existing</strong>, select an existing OBS bucket.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="cts_03_0002__en-us_topic_0170932828_row510019016103"><td class="cellrowborder" valign="top" width="20.46%" headers="mcps1.3.3.2.5.1.2.3.1.1 "><p id="cts_03_0002__en-us_topic_0170932828_p1110090111014">Retention Period</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="79.54%" headers="mcps1.3.3.2.5.1.2.3.1.2 "><p id="cts_03_0002__en-us_topic_0170932828_p71001403108">The duration for storing traces in the OBS bucket. This configuration will apply to the selected bucket and all files in it. Different compliance standards require different trace retention periods. You are advised to set the retention period to at least 180 days.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="cts_03_0002__en-us_topic_0170932828_row10100100201017"><td class="cellrowborder" valign="top" width="20.46%" headers="mcps1.3.3.2.5.1.2.3.1.1 "><p id="cts_03_0002__en-us_topic_0170932828_p41018017109">File Prefix</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="79.54%" headers="mcps1.3.3.2.5.1.2.3.1.2 "><p id="cts_03_0002__en-us_topic_0170932828_p14101130151020">A prefix is used to mark a transferred trace file. Your specified prefix will be automatically added to the beginning of the name of a transferred file, helping you quickly filter files. Enter 0 to 64 characters. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="cts_03_0002__en-us_topic_0170932828_row167008581753"><td class="cellrowborder" valign="top" width="20.46%" headers="mcps1.3.3.2.5.1.2.3.1.1 "><p id="cts_03_0002__en-us_topic_0170932828_p169941638613">Transfer to LTS</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="79.54%" headers="mcps1.3.3.2.5.1.2.3.1.2 "><p id="cts_03_0002__en-us_topic_0170932828_p69941231761">When <strong id="cts_03_0002__en-us_topic_0170932828_b994115815417">Transfer to LTS</strong> is enabled, traces are transferred to the log stream.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="cts_03_0002__en-us_topic_0170932828_row11889858558"><td class="cellrowborder" valign="top" width="20.46%" headers="mcps1.3.3.2.5.1.2.3.1.1 "><p id="cts_03_0002__en-us_topic_0170932828_p1499483960">Log group name</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="79.54%" headers="mcps1.3.3.2.5.1.2.3.1.2 "><p id="cts_03_0002__en-us_topic_0170932828_p49941336616">When <strong id="cts_03_0002__en-us_topic_0170932828_b28495297511">Transfer to LTS</strong> is enabled, the default log group name is <strong id="cts_03_0002__en-us_topic_0170932828_b113401545356">CTS</strong>. When <strong id="cts_03_0002__en-us_topic_0170932828_b5208203716279">Transfer to LTS</strong> is disabled, no operation is required.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</li><li id="cts_03_0002__en-us_topic_0170932828_li36839883314">Click <strong id="cts_03_0002__en-us_topic_0170932828_b544912752919">OK</strong> to complete the configuration.<p id="cts_03_0002__en-us_topic_0170932828_p3261874810915">You can then view the tracker details on the <strong id="cts_03_0002__en-us_topic_0170932828_b842352706152452">Tracker List</strong> page.</p>
|
||||||
|
<div class="note" id="cts_03_0002__en-us_topic_0170932828_note5225481917328"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cts_03_0002__en-us_topic_0170932828_p1187630417331">Traces recorded by CTS are delivered periodically to the OBS bucket for storage. If you configure an OBS bucket for a tracker, traces generated during the current cycle (usually several minutes) will be delivered to the configured OBS bucket. For example, if the current cycle is from 12:00:00 to 12:05:00 and you configure an OBS bucket for a tracker at 12:02:00, traces received from 12:00:00 to 12:02:00 will also be delivered to the configured OBS bucket for storage at 12:05:00.</p>
|
||||||
|
</div></div>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_03_0000.html">Tracker Management</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
17
docs/cts/umn/cts_03_0003.html
Normal file
17
docs/cts/umn/cts_03_0003.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<a name="cts_03_0003"></a><a name="cts_03_0003"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Disabling or Enabling a Tracker</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_03_0003__en-us_topic_0170932838_section344954110552"><h4 class="sectiontitle">Scenario</h4><p id="cts_03_0003__en-us_topic_0170932838_p60695182185319">You can disable a tracker on the CTS console. After a tracker is disabled, it will stop recording operations, but you can still view operation records that have been collected.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0003__en-us_topic_0170932838_section2610789710552"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_03_0003__en-us_topic_0170932838_p4242985510552">You have created a tracker on the CTS console.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0003__en-us_topic_0170932838_section3447669010552"><h4 class="sectiontitle">Procedure</h4><ol id="cts_03_0003__en-us_topic_0170932838_ol4553303910552"><li id="cts_03_0003__en-us_topic_0170932838_li3285461910552">Log in to the management console.</li><li id="cts_03_0003__en-us_topic_0170932838_li1282117610552">Click <span><img id="cts_03_0003__en-us_topic_0170932838_image596724583118" src="en-us_image_0000001187789198.png"></span> in the upper left corner and choose <strong id="cts_03_0003__en-us_topic_0170932838_b14967134593113">Management & Deployment</strong> > <strong id="cts_03_0003__en-us_topic_0170932838_b1696814510318">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_03_0003__en-us_topic_0170932838_li1534345110552">Choose <strong id="cts_03_0003__en-us_topic_0170932838_b15584203510414">Tracker List</strong> in the navigation pane on the left.</li><li id="cts_03_0003__en-us_topic_0170932838_li2176469810552">Click <strong id="cts_03_0003__en-us_topic_0170932838_b13521835171515">Disable</strong> in the <strong id="cts_03_0003__en-us_topic_0170932838_b1454373721518">Operation</strong> column in the row of the target tracker.</li><li id="cts_03_0003__en-us_topic_0170932838_li2146126110552">Click <strong id="cts_03_0003__en-us_topic_0170932838_b1292691019323">OK</strong>.<p id="cts_03_0003__en-us_topic_0170932838_p6232125214919">After the tracker is disabled, the <strong id="cts_03_0003__en-us_topic_0170932838_b1391223261">Disable</strong> button changes to <strong id="cts_03_0003__en-us_topic_0170932838_b13916231966">Enable</strong>. To enable the tracker, click <strong id="cts_03_0003__en-us_topic_0170932838_b66861553341">Enable</strong> and then click <strong id="cts_03_0003__en-us_topic_0170932838_b106861052341">Yes</strong>. The tracker will start recording operations again.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_03_0000.html">Tracker Management</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
19
docs/cts/umn/cts_03_0005.html
Normal file
19
docs/cts/umn/cts_03_0005.html
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
<a name="cts_03_0005"></a><a name="cts_03_0005"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Application Examples</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_03_0006.html">Security Auditing</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_03_0007.html">Fault Locating</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_03_0008.html">Resource Tracking</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030628003.html">User Guide</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
19
docs/cts/umn/cts_03_0006.html
Normal file
19
docs/cts/umn/cts_03_0006.html
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
<a name="cts_03_0006"></a><a name="cts_03_0006"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Security Auditing</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_03_0006__en-us_topic_0170932679_section29070389181456"><h4 class="sectiontitle">Scenario</h4><p id="cts_03_0006__en-us_topic_0170932679_p19353273181544">You can query operation records matching specified conditions and check whether operations have been performed by authorized users for security analysis.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0006__en-us_topic_0170932679_section15151415181756"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_03_0006__en-us_topic_0170932679_p1184131015427">You have enabled CTS and trackers are running properly.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0006__en-us_topic_0170932679_section48879286181857"><h4 class="sectiontitle">Procedure</h4><p id="cts_03_0006__en-us_topic_0170932679_p39460202181942">The following takes the records of EVS disk creation and deletion in the last two weeks as an example.</p>
|
||||||
|
<ol id="cts_03_0006__en-us_topic_0170932679_ol22040361181932"><li id="cts_03_0006__en-us_topic_0170932679_li49796966181949">Log in to the management console as a CTS administrator.</li><li id="cts_03_0006__en-us_topic_0170932679_li1394586618202">Click <span><img id="cts_03_0006__en-us_topic_0170932679_image1359174784119" src="en-us_image_0000001187470664.png"></span> in the upper left corner and choose <strong id="cts_03_0006__en-us_topic_0170932679_b17592104714418">Management & Deployment</strong> > <strong id="cts_03_0006__en-us_topic_0170932679_b11592347154118">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_03_0006__en-us_topic_0170932679_li5286401318204">Choose <strong id="cts_03_0006__en-us_topic_0170932679_b5498459217">Trace List</strong> in the navigation pane on the left.</li><li id="cts_03_0006__en-us_topic_0170932679_li8526497437"><a name="cts_03_0006__en-us_topic_0170932679_li8526497437"></a><a name="en-us_topic_0170932679_li8526497437"></a>Set filters in sequence and click <strong id="cts_03_0006__en-us_topic_0170932679_b8139101062317">Query</strong>.<div class="note" id="cts_03_0006__en-us_topic_0170932679_note144491850556"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cts_03_0006__en-us_topic_0170932679_p1925811411518">Select <strong id="cts_03_0006__en-us_topic_0170932679_b13119734111916">Management</strong> for <strong id="cts_03_0006__en-us_topic_0170932679_b12119934141914">Trace Type</strong>, <strong id="cts_03_0006__en-us_topic_0170932679_b108571942141911">EVS</strong> for <strong id="cts_03_0006__en-us_topic_0170932679_b19120634101913">Trace Source</strong>, <strong id="cts_03_0006__en-us_topic_0170932679_b3120153419193">evs</strong> for <strong id="cts_03_0006__en-us_topic_0170932679_b11120123411915">Resource Type</strong>, <strong id="cts_03_0006__en-us_topic_0170932679_b13120173420198">Trace name</strong> for <strong id="cts_03_0006__en-us_topic_0170932679_b1012053411914">Search By</strong>, select <strong id="cts_03_0006__en-us_topic_0170932679_b412023416199">createVolume</strong> or <strong id="cts_03_0006__en-us_topic_0170932679_b01201934161913">deleteVolume</strong>, and click <strong id="cts_03_0006__en-us_topic_0170932679_b81202342193">Query</strong>. By default, all EVS disk creation or deletion operations in the last hour are queried. You can also set the time range to query all EVS creation or deletion operations performed in the last 7 days at most.</p>
|
||||||
|
</div></div>
|
||||||
|
</li><li id="cts_03_0006__en-us_topic_0170932679_li64792700182010">Choose <strong id="cts_03_0006__en-us_topic_0170932679_b1647827584165843">Tracker List</strong> in the navigation pane on the left.</li><li id="cts_03_0006__en-us_topic_0170932679_li26706607152621">Download traces older than seven days or all traces by following the instructions in <a href="cts_02_0006.html#cts_02_0006">Querying Archived Traces</a>.</li><li id="cts_03_0006__en-us_topic_0170932679_li38255771182015"><a name="cts_03_0006__en-us_topic_0170932679_li38255771182015"></a><a name="en-us_topic_0170932679_li38255771182015"></a>In the trace files, search traces using keywords <strong id="cts_03_0006__en-us_topic_0170932679_b842352706173133">createVolume</strong> or <strong id="cts_03_0006__en-us_topic_0170932679_b842352706173136">deleteVolume</strong>.</li><li id="cts_03_0006__en-us_topic_0170932679_li22997390182020">Check the traces obtained from steps <a href="#cts_03_0006__en-us_topic_0170932679_li8526497437">5</a> and <a href="#cts_03_0006__en-us_topic_0170932679_li38255771182015">7</a> to see whether there are any unauthorized operations or operations that do not conform to security rules.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_03_0005.html">Application Examples</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
21
docs/cts/umn/cts_03_0007.html
Normal file
21
docs/cts/umn/cts_03_0007.html
Normal file
@ -0,0 +1,21 @@
|
|||||||
|
<a name="cts_03_0007"></a><a name="cts_03_0007"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Fault Locating</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_03_0007__en-us_topic_0170932760_section6291060118322"><h4 class="sectiontitle">Scenario</h4><p id="cts_03_0007__en-us_topic_0170932760_p41652022183211">If a resource or an action encounters an exception, you can query operation records of the resource or action in a specified time period and view the requests and responses to facilitate fault locating.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0007__en-us_topic_0170932760_section2947819183220"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_03_0007__en-us_topic_0170932760_p1184131015427">You have enabled CTS and trackers are running properly. </p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0007__en-us_topic_0170932760_section64841869191343"><h4 class="sectiontitle">Procedure</h4><p id="cts_03_0007__en-us_topic_0170932760_p25971326191548"><strong id="cts_03_0007__en-us_topic_0170932760_b835810453304">The following shows how to locate an ECS fault which occurred in a morning.</strong></p>
|
||||||
|
<ol id="cts_03_0007__en-us_topic_0170932760_ol5387276719305"><li id="cts_03_0007__en-us_topic_0170932760_li5674193619305">Log in to the management console as a CTS administrator.</li><li id="cts_03_0007__en-us_topic_0170932760_li597108019307">Click <span><img id="cts_03_0007__en-us_topic_0170932760_image18230310103219" src="en-us_image_0000001232870297.png"></span> in the upper left corner and choose <strong id="cts_03_0007__en-us_topic_0170932760_b19488550151417">Management & Deployment</strong> > <strong id="cts_03_0007__en-us_topic_0170932760_b20488650101412">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_03_0007__en-us_topic_0170932760_li10568277193011">Choose <strong id="cts_03_0007__en-us_topic_0170932760_b42162954165740">Trace List</strong> in the navigation pane on the left.</li><li id="cts_03_0007__en-us_topic_0170932760_li3297220111729">Set filters in sequence and click <strong id="cts_03_0007__en-us_topic_0170932760_b1383152315247">Query</strong>.<div class="note" id="cts_03_0007__en-us_topic_0170932760_note693371411743"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cts_03_0007__en-us_topic_0170932760_p6240342811743">Select <strong id="cts_03_0007__en-us_topic_0170932760_b81351332112512">Management</strong> for <strong id="cts_03_0007__en-us_topic_0170932760_b14136193212518">Trace Type</strong>, <strong id="cts_03_0007__en-us_topic_0170932760_b121371732122512">ecs</strong> for <strong id="cts_03_0007__en-us_topic_0170932760_b16137123212510">Trace Source</strong>, <strong id="cts_03_0007__en-us_topic_0170932760_b1813893242516">ecs</strong> for <strong id="cts_03_0007__en-us_topic_0170932760_b19138133211257">Resource Type</strong>, <strong id="cts_03_0007__en-us_topic_0170932760_b171381632152511">Resource ID</strong> for <strong id="cts_03_0007__en-us_topic_0170932760_b14139143214256">Search By</strong>, and enter the ID of the faulty virtual machine (VM). In the upper right corner, select a time range from 06:00:00 to 12:00:00 on the day when the fault occurred. Then, click <strong id="cts_03_0007__en-us_topic_0170932760_b413916323259">Query</strong> to view the result.</p>
|
||||||
|
</div></div>
|
||||||
|
</li><li id="cts_03_0007__en-us_topic_0170932760_li62204713193022">Check the returned traces, especially the request type and response of each trace. Pay attention to traces whose status is <strong id="cts_03_0007__en-us_topic_0170932760_b84235270610656">warning</strong> or <strong id="cts_03_0007__en-us_topic_0170932760_b8423527061072">incident</strong>, and traces whose response indicates a failure.</li></ol>
|
||||||
|
<div class="p" id="cts_03_0007__en-us_topic_0170932760_p28269376192959"><strong id="cts_03_0007__en-us_topic_0170932760_b88761421782">The following shows how to locate a fault after an ECS server failed to be created.</strong><ol id="cts_03_0007__en-us_topic_0170932760_ol60752627193028"><li id="cts_03_0007__en-us_topic_0170932760_li63924094193028">Log in to the management console as a CTS administrator.</li><li id="cts_03_0007__en-us_topic_0170932760_li35398716193055">Click <span><img id="cts_03_0007__en-us_topic_0170932760_image93071119169" src="en-us_image_0000001232950241.png"></span> in the upper left corner and choose <strong id="cts_03_0007__en-us_topic_0170932760_b820614419357">Management & Deployment</strong> > <strong id="cts_03_0007__en-us_topic_0170932760_b152060415359">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_03_0007__en-us_topic_0170932760_li11485349193058">Choose <strong id="cts_03_0007__en-us_topic_0170932760_b14567174113415">Trace List</strong> in the navigation pane on the left.</li><li id="cts_03_0007__en-us_topic_0170932760_li51616363141150">Select <strong id="cts_03_0007__en-us_topic_0170932760_b17152174123315">Management</strong> for <strong id="cts_03_0007__en-us_topic_0170932760_b131537443317">Trace Type</strong>, <strong id="cts_03_0007__en-us_topic_0170932760_b18154347339">ecs</strong> for <strong id="cts_03_0007__en-us_topic_0170932760_b715444113311">Trace Source</strong>, <strong id="cts_03_0007__en-us_topic_0170932760_b14155448338">ecs</strong> for <strong id="cts_03_0007__en-us_topic_0170932760_b1815517443311">Resource Type</strong>, and <strong id="cts_03_0007__en-us_topic_0170932760_b715614433317">Warning</strong> for <strong id="cts_03_0007__en-us_topic_0170932760_b1515617423318">Trace Status</strong>. In the returned traces, locate the trace named <strong id="cts_03_0007__en-us_topic_0170932760_b51564483312">createServer</strong>.</li><li id="cts_03_0007__en-us_topic_0170932760_li424729119312">Check the trace details and locate the fault based on the error code or error message.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_03_0005.html">Application Examples</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
19
docs/cts/umn/cts_03_0008.html
Normal file
19
docs/cts/umn/cts_03_0008.html
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
<a name="cts_03_0008"></a><a name="cts_03_0008"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Resource Tracking</h1>
|
||||||
|
<div id="body8662426"><div class="section" id="cts_03_0008__en-us_topic_0170932730_section28509637193319"><h4 class="sectiontitle">Scenario</h4><p id="cts_03_0008__en-us_topic_0170932730_p18352529193330">You can view operation records of a cloud resource throughout its lifecycle.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0008__en-us_topic_0170932730_section13625028193339"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_03_0008__en-us_topic_0170932730_p1184131015427">You have enabled CTS and trackers are running properly. </p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_03_0008__en-us_topic_0170932730_section727451193431"><h4 class="sectiontitle">Procedure</h4><p id="cts_03_0008__en-us_topic_0170932730_p3294395193523">The following takes the records of all operations on an ECS server as an example.</p>
|
||||||
|
<ol id="cts_03_0008__en-us_topic_0170932730_ol45058899193540"><li id="cts_03_0008__en-us_topic_0170932730_li46788270193540">Log in to the management console as a CTS administrator.</li><li id="cts_03_0008__en-us_topic_0170932730_li32288751193543">Click <span><img id="cts_03_0008__en-us_topic_0170932730_image18230310103219" src="en-us_image_0000001187630634.png"></span> in the upper left corner and choose <strong id="cts_03_0008__en-us_topic_0170932730_b544450173718">Management & Deployment</strong> > <strong id="cts_03_0008__en-us_topic_0170932730_b19441507376">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cts_03_0008__en-us_topic_0170932730_li42427023193548">Choose <strong id="cts_03_0008__en-us_topic_0170932730_b299872515417">Trace List</strong> in the navigation pane on the left.</li><li id="cts_03_0008__en-us_topic_0170932730_li36410601182"><a name="cts_03_0008__en-us_topic_0170932730_li36410601182"></a><a name="en-us_topic_0170932730_li36410601182"></a>Set filters in sequence and click <strong id="cts_03_0008__en-us_topic_0170932730_b4598183212414">Query</strong>.<div class="note" id="cts_03_0008__en-us_topic_0170932730_note4381420811811"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cts_03_0008__en-us_topic_0170932730_p5878355811811">Select <strong id="cts_03_0008__en-us_topic_0170932730_b1186817933412">Management</strong> for <strong id="cts_03_0008__en-us_topic_0170932730_b16870169133411">Trace Type</strong>, <strong id="cts_03_0008__en-us_topic_0170932730_b187049123413">ecs</strong> for <strong id="cts_03_0008__en-us_topic_0170932730_b1987049103419">Trace Source</strong>, <strong id="cts_03_0008__en-us_topic_0170932730_b9871199133420">ecs</strong> for <strong id="cts_03_0008__en-us_topic_0170932730_b128711919346">Resource Type</strong>, <strong id="cts_03_0008__en-us_topic_0170932730_b1387112953412">Resource ID</strong> for <strong id="cts_03_0008__en-us_topic_0170932730_b11871159103412">Search By</strong>, enter the ID of the faulty VM, and click <strong id="cts_03_0008__en-us_topic_0170932730_b5871149203418">Query</strong>. By default, the matching traces generated in the last hour are returned. You can also set the time range to view the matching traces in the last 7 days at most.</p>
|
||||||
|
</div></div>
|
||||||
|
</li><li id="cts_03_0008__en-us_topic_0170932730_li62831252193553">Choose <strong id="cts_03_0008__en-us_topic_0170932730_b147738463467">Tracker List</strong> in the navigation pane on the left.</li><li id="cts_03_0008__en-us_topic_0170932730_li14173783182013"><a name="cts_03_0008__en-us_topic_0170932730_li14173783182013"></a><a name="en-us_topic_0170932730_li14173783182013"></a>Download traces older than seven days or all traces by following the instructions in <a href="cts_02_0006.html#cts_02_0006">Querying Archived Traces</a>.</li><li id="cts_03_0008__en-us_topic_0170932730_li2566137193558">Check all the traces obtained in <a href="#cts_03_0008__en-us_topic_0170932730_li36410601182">4</a> and <a href="#cts_03_0008__en-us_topic_0170932730_li14173783182013">6</a>.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cts_03_0005.html">Application Examples</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
17
docs/cts/umn/cts_03_0009.html
Normal file
17
docs/cts/umn/cts_03_0009.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<a name="cts_03_0009"></a><a name="cts_03_0009"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Trace References</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_03_0010.html">Trace Structure</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_03_0011.html">Example Traces</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030628003.html">User Guide</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
180
docs/cts/umn/cts_03_0010.html
Normal file
180
docs/cts/umn/cts_03_0010.html
Normal file
File diff suppressed because it is too large
Load Diff
114
docs/cts/umn/cts_03_0011.html
Normal file
114
docs/cts/umn/cts_03_0011.html
Normal file
File diff suppressed because it is too large
Load Diff
108
docs/cts/umn/cts_03_0021_01.html
Normal file
108
docs/cts/umn/cts_03_0021_01.html
Normal file
File diff suppressed because it is too large
Load Diff
17
docs/cts/umn/cts_03_01436.html
Normal file
17
docs/cts/umn/cts_03_01436.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<a name="cts_03_01436"></a><a name="cts_03_01436"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Trace Management</h1>
|
||||||
|
<div id="body8662426"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_02_0005.html">Querying Real-Time Traces</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="cts_02_0006.html">Querying Archived Traces</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030628003.html">User Guide</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
236
docs/cts/umn/cts_03_0300.html
Normal file
236
docs/cts/umn/cts_03_0300.html
Normal file
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,11 +1,12 @@
|
|||||||
<a name="cts_faq_001"></a><a name="cts_faq_001"></a>
|
<a name="cts_faq_001"></a><a name="cts_faq_001"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Can I Create Multiple Trackers?</h1>
|
<h1 class="topictitle1">What Are the Recommended Users of CTS?</h1>
|
||||||
<div id="body1464057168910"><p id="cts_faq_001__p11827335103441">Currently, only one tracker can be created for each tenant.</p>
|
<div id="body1481802609181"><p id="cts_faq_001__p55207703174135">It is highly recommended that cloud users should enable CTS.</p>
|
||||||
|
<ul id="cts_faq_001__ul3687642917429"><li id="cts_faq_001__li6345240817429">CTS is core to information security audit. It is an essential part of security risk control for information systems in enterprises and public sectors, and is also necessary for compliance with many industry standards and audit specifications.</li><li id="cts_faq_001__li55443176174213">CTS helps accelerate troubleshooting and reduces manpower costs when exceptions occur on cloud resources. With CTS, you can track all operations involved when a fault happens, which helps narrow the possibilities.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|||||||
@ -1,11 +0,0 @@
|
|||||||
<a name="cts_faq_002"></a><a name="cts_faq_002"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Which Type of Information Is Displayed on the Trace List?</h1>
|
|
||||||
<div id="body1464057168910"><p id="cts_faq_002__p8060118">The trace list displays details about operations, such as creation, configuration, and deletion of cloud service resources, in your account. The trace list does not record information about query operations.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
||||||
@ -1,11 +0,0 @@
|
|||||||
<a name="cts_faq_003"></a><a name="cts_faq_003"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Can I Delete Traces from the Trace List?</h1>
|
|
||||||
<div id="body1464057168911"><p id="cts_faq_003__p49114214153458">No. Audit logs must be objective, complete, and accurate. Therefore, they cannot be deleted or modified.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
||||||
12
docs/cts/umn/cts_faq_004.html
Normal file
12
docs/cts/umn/cts_faq_004.html
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
<a name="cts_faq_004"></a><a name="cts_faq_004"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">How Will CTS Be Affected If My Account Is in Arrears?</h1>
|
||||||
|
<div id="body1473389361207"><p id="cts_faq_004__p35094504111634">If your account is in arrears, CTS can still receive operation records from supported services, but the records can only be retained for 7 days. In most cases, records can be merged into trace files and transferred to OBS buckets for long term storage. Trace file storage in OBS buckets generates fees and this function cannot work when your account is in arrears.</p>
|
||||||
|
<p id="cts_faq_004__p363239151186">In addition, the only action you can perform on trackers is to delete them.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
11
docs/cts/umn/cts_faq_0040.html
Normal file
11
docs/cts/umn/cts_faq_0040.html
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
<a name="cts_faq_0040"></a><a name="cts_faq_0040"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Must I Use an IAM User (Sub Account) to Configure Transfer on CTS and Perform Operations on an OBS Bucket?</h1>
|
||||||
|
<div id="body1574651623170"><p id="cts_faq_0040__p8060118">No. You only need to ensure that you have the permissions for OBS buckets.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
@ -1,12 +1,12 @@
|
|||||||
<a name="cts_faq_005"></a><a name="cts_faq_005"></a>
|
<a name="cts_faq_005"></a><a name="cts_faq_005"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">What Are the Recommended Users of CTS?</h1>
|
<h1 class="topictitle1">Why Are user and source_ip Null for Some Traces with trace_type as SystemAction?</h1>
|
||||||
<div id="body1481802609181"><p id="cts_faq_005__p55207703174135">It is highly recommended that cloud users enable CTS.</p>
|
<div id="body1518070250569"><p id="cts_faq_005__p33589534141239">The <strong id="cts_faq_005__b842352706104545">trace_type</strong> field indicates the request source. This field can be <strong id="cts_faq_005__b842352706104658">ConsoleAction</strong>, <strong id="cts_faq_005__b84235270610471">ApiCall</strong>, and <strong id="cts_faq_005__b84235270610475">SystemAction</strong>.</p>
|
||||||
<ul id="cts_faq_005__ul3687642917429"><li id="cts_faq_005__li6345240817429">CTS is core to information security audit. It is an essential part of security risk control for information systems in enterprises and public sectors, and is also necessary for compliance of many industry standards and audit specifications.</li><li id="cts_faq_005__li55443176174213">CTS helps accelerate troubleshooting and reduces manpower costs when exceptions occur on cloud resources. With CTS, you can track all operations involved when an exception happens, which helps narrow the possibilities.</li></ul>
|
<p id="cts_faq_005__p8060118"><strong id="cts_faq_005__b1768110039104714">SystemAction</strong> indicates operations that are not triggered by users, such as alarms, elastic scaling, regular backup, or secondary invocations by systems to complete a user's request. In this case, <strong id="cts_faq_005__b1594489848105933">user</strong> and <strong id="cts_faq_005__b1881962885105933">source_ip</strong> are both null.</p>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|||||||
@ -1,11 +0,0 @@
|
|||||||
<a name="cts_faq_006"></a><a name="cts_faq_006"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">How Long Can Trace Files Be Retained?</h1>
|
|
||||||
<div id="body1481802609181"><p id="cts_faq_006__p62577924195744">By default, trace files of the last seven days can be retained on the management console. Archived trace files stored in the OBS bucket can be permanently retained.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
||||||
@ -1,12 +1,12 @@
|
|||||||
<a name="cts_faq_007"></a><a name="cts_faq_007"></a>
|
<a name="cts_faq_007"></a><a name="cts_faq_007"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">What Will Happen If I Have Enabled CTS But Have Not Configured a Correct Policy for the OBS Bucket?</h1>
|
<h1 class="topictitle1">What Will Happen If I Have Enabled Trace Transfer But Have Not Configured an Appropriate Policy for an OBS Bucket?</h1>
|
||||||
<div id="body1481802609181"><p id="cts_faq_007__p3378434720958">CTS will deliver trace files based on the existing OBS bucket policy. If the policy is incorrectly configured, CTS may not deliver trace files to the OBS bucket.</p>
|
<div id="body1481802609181"><p id="cts_faq_007__p3378434720958">CTS delivers trace files based on the OBS bucket policy. If the policy is configured incorrectly, trace files cannot be delivered.</p>
|
||||||
<p id="cts_faq_007__p2441688220227">If an OBS bucket has been deleted or encounters an exception, an error message will be displayed on the management console. In this case, you can choose to create an OBS bucket or reconfigure the access permissions of the OBS bucket. For detailed operations, see the "Bucket Management" section in the <em id="cts_faq_007__i842352697151554">Object Storage Service User Guide</em>.</p>
|
<p id="cts_faq_007__p2441688220227">If an OBS bucket has been deleted or encounters an exception, an error message will be displayed on the management console. </p>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|||||||
11
docs/cts/umn/cts_faq_008.html
Normal file
11
docs/cts/umn/cts_faq_008.html
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
<a name="cts_faq_008"></a><a name="cts_faq_008"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Does CTS Support Integrity Verification of Trace Files?</h1>
|
||||||
|
<div id="body1481802609182"><p id="cts_faq_008__p8060118">Yes. The following fields must be included in trace files: <strong id="cts_faq_008__b842352706151053">time</strong>, <strong id="cts_faq_008__b842352706151057">service_type</strong>, <strong id="cts_faq_008__b84235270615118">resource_type</strong>, <strong id="cts_faq_008__b842352706151115">trace_name</strong>, <strong id="cts_faq_008__b842352706151120">trace_rating</strong>, and <strong id="cts_faq_008__b842352706151124">trace_type</strong>. Other fields can be added by the services from which traces are collected.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
@ -1,11 +0,0 @@
|
|||||||
<a name="cts_faq_009"></a><a name="cts_faq_009"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Will Performance of Other Cloud Service Resources Be Affected If I Enable CTS?</h1>
|
|
||||||
<div id="body1481802609182"><p id="cts_faq_009__p8060118">No. Enabling CTS does not affect the performance of other cloud resources.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
||||||
@ -1,12 +1,12 @@
|
|||||||
<a name="cts_faq_010"></a><a name="cts_faq_010"></a>
|
<a name="cts_faq_010"></a><a name="cts_faq_010"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Why Are Fields of Some Traces Displayed as Null on the View Trace Page?</h1>
|
<h1 class="topictitle1">Why Are There Some Null Fields on the View Trace Page?</h1>
|
||||||
<div id="body1484125680311"><p id="cts_faq_010__p1123882619517">Fields <strong id="cts_faq_010__b1736554410133">resource_IP</strong>, <strong id="cts_faq_010__b7377144411137">code</strong>, <strong id="cts_faq_010__b173781447134">request</strong>, <strong id="cts_faq_010__b13791644191319">response</strong>, and <strong id="cts_faq_010__b1637910441133">message</strong> can be null. These fields are not mandatory for CTS.</p>
|
<div id="body1484125680311"><p id="cts_faq_010__p1123882619517">Fields <strong id="cts_faq_010__b889513489393">source_ip</strong>, <strong id="cts_faq_010__b689764817394">code</strong>, <strong id="cts_faq_010__b198992482391">request</strong>, <strong id="cts_faq_010__b69001148183913">response</strong>, and <strong id="cts_faq_010__b139021448173918">message</strong> can be null. These fields are not mandatory for CTS.</p>
|
||||||
<ul id="cts_faq_010__ul13442867174245"><li id="cts_faq_010__li53876940174245"><strong id="cts_faq_010__b2708125281713">resource_IP</strong>: If the value of <strong id="cts_faq_010__b916194232411">trace_type</strong> is <strong id="cts_faq_010__b842352706155737">SystemAction</strong>, the operation is triggered by the system. It is normal that the <strong id="cts_faq_010__b842352706164856">resource_IP</strong> field is empty.</li><li id="cts_faq_010__li15130414174245"><strong id="cts_faq_010__b842352706163540">request</strong>, <strong id="cts_faq_010__b842352706163543">response</strong>, and <strong id="cts_faq_010__b842352706163546">code</strong>: These three fields indicate the request content, request result, and HTTP return code of an operation. In some cases, these fields are empty or have no service meaning. Therefore, they are left blank based on actual situations.</li><li id="cts_faq_010__li1956002174245"><strong id="cts_faq_010__b84235270616398">message</strong>: This is a reserved field. Additional information of other cloud services will be added in this field when necessary. It is normal that it is left blank.</li></ul>
|
<ul id="cts_faq_010__ul13442867174245"><li id="cts_faq_010__li53876940174245"><strong id="cts_faq_010__b2708125281713">source_ip</strong>: If the value of <strong id="cts_faq_010__b916194232411">trace_type</strong> is <strong id="cts_faq_010__b842352706155737">SystemAction</strong>, the operation was triggered by the system. In this case, <strong id="cts_faq_010__b842352706164856">source_ip</strong> is null.</li><li id="cts_faq_010__li15130414174245"><strong id="cts_faq_010__b842352706163540">request</strong>, <strong id="cts_faq_010__b842352706163543">response</strong>, and <strong id="cts_faq_010__b842352706163546">code</strong>: These three fields indicate the request content, request result, and HTTP return code of an operation. In some cases, these fields are null or have no service meaning. Therefore, they are left blank based on actual situations.</li><li id="cts_faq_010__li1956002174245"><strong id="cts_faq_010__b84235270616398">message</strong>: This is a reserved field. Information of other cloud services will be added to this field when necessary. It is normal that the field is null.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|||||||
@ -1,11 +0,0 @@
|
|||||||
<a name="cts_faq_011"></a><a name="cts_faq_011"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Why Are the Resource IDs of Some Traces in the Trace List Hyperlinks?</h1>
|
|
||||||
<div id="body1484128559417"><p id="cts_faq_011__p18858355165249">For ECS, EVS, VBS, IMS, AS, Cloud Eye, and VPC, you can click <strong id="cts_faq_011__b842352706145421">Resource ID</strong> of some traces to go to the resource details page. The resource ID of such a trace is a hyperlink. More traces will be supported in future.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
||||||
@ -1,13 +1,13 @@
|
|||||||
<a name="cts_faq_012"></a><a name="cts_faq_012"></a>
|
<a name="cts_faq_012"></a><a name="cts_faq_012"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Why Is an Operation Recorded Twice in the Trace List?</h1>
|
<h1 class="topictitle1">Why Is an Operation Recorded Twice in the Trace List?</h1>
|
||||||
<div id="body1486112893055"><p id="cts_faq_012__p3215496317835">For an asynchronously invoked trace, two records with the same trace name, resource type, and resource name will be generated. The two records may seem to be the same. However, they are generated at different times and document different details.</p>
|
<div id="body1486112893055"><p id="cts_faq_012__p3215496317835">For an asynchronously invoked trace, such as <strong id="cts_faq_012__b842352706102256">deleteDesktop</strong> trace of Workspace, two records with the same trace name, resource type, and resource name will be generated. The two records may seem to be the same. However, they are generated at different times and document different details.</p>
|
||||||
<ul id="cts_faq_012__ul2739855617957"><li id="cts_faq_012__li5102020017957">The first record documents the request initiated by a user.</li><li id="cts_faq_012__li6383658017957">The second record documents the response to the request and the operation result, and is usually several minutes later than the first record.</li></ul>
|
<ul id="cts_faq_012__ul2739855617957"><li id="cts_faq_012__li5102020017957">The first record documents the request initiated by a user.</li><li id="cts_faq_012__li6383658017957">The second record documents the response to the request and the operation result, and is usually several minutes later than the first record.</li></ul>
|
||||||
<p id="cts_faq_012__p552462917835">The two records together give a full view of the operation.</p>
|
<p id="cts_faq_012__p552462917835">The two records together give a full view of the operation.</p>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|||||||
@ -1,11 +0,0 @@
|
|||||||
<a name="cts_faq_013"></a><a name="cts_faq_013"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Why Are <strong id="b25462020114511">user_name</strong> and <strong id="b1547162034517">op_service</strong> Displayed When I Filter Traces by User?</h1>
|
|
||||||
<div id="body1497584695839"><p id="cts_faq_013__p26404530114543">If you submit a request that calls operations requiring high permissions or calling of other services, you may not have the required permissions. In this case, your permissions will be elevated temporarily on condition that security requirements are met. Your permissions will be resumed after the request is processed, but the permissions elevation will be recorded in CTS logs and the operation user is recorded as <strong id="cts_faq_013__b116082544517">user_name</strong> or <strong id="cts_faq_013__b6617256454">op_service</strong>.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
||||||
@ -1,12 +1,11 @@
|
|||||||
<a name="cts_faq_015"></a><a name="cts_faq_015"></a>
|
<a name="cts_faq_015"></a><a name="cts_faq_015"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">What Services Are Supported for Key Event Notification?</h1>
|
<h1 class="topictitle1">What Services Are Supported by Key Event Notifications?</h1>
|
||||||
<div id="body1503307226953"><p id="cts_faq_015__p48272697172133">Currently, CTS only sends notifications for some key operations on ECS, EVS, VPC, KMS, IAM, and native OpenStack. This feature currently supports creation, deletion, login, and native OpenStack API operations. This function is still being improved and will support more services and operation types in the future. For details, see <a href="en-us_topic_0059288681.html">Configuring a Tracker</a>.</p>
|
<div id="body1503307226953"><p id="cts_faq_015__p48272697172133">CTS sends notifications of all key operations on services including ECS, EVS, VPC, DEW, native OpenStack, and IAM. These operations include creation, deletion, login, and native OpenStack API calls. </p>
|
||||||
<p id="cts_faq_015__p61937348145311"></p>
|
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|||||||
@ -1,11 +1,11 @@
|
|||||||
<a name="cts_faq_017"></a><a name="cts_faq_017"></a>
|
<a name="cts_faq_017"></a><a name="cts_faq_017"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Which Type of OBS Buckets Is Suitable for CTS to Store Traces?</h1>
|
<h1 class="topictitle1">How Can I Store Trace Files for a Long Time?</h1>
|
||||||
<div id="body1514000583255"><p id="cts_faq_017__p20831725114510">OBS provides three storage classes of buckets for storage, respectively standard access, infrequent access, or archive. You must select a standard OBS bucket because CTS needs to frequently access the OBS bucket that stores traces.</p>
|
<div id="body1514000583255"><p id="cts_faq_017__p378910299711">CTS only retains traces for seven days. To store traces for a long time, configure your tracker to transfer traces to OBS buckets. For details, see <a href="cts_03_0002.html">Configuring a Tracker</a>.</p>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|||||||
@ -1,12 +0,0 @@
|
|||||||
<a name="cts_faq_019"></a><a name="cts_faq_019"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Why Are <strong id="b842352706105319">user</strong> and <strong id="b842352706105322">source_ip</strong> Empty for Some Traces with <strong id="b842352706105446">trace_type</strong> as <strong id="b842352706105450">systemAction</strong>?</h1>
|
|
||||||
<div id="body1518070250569"><p id="cts_faq_019__p33589534141239">The <strong id="cts_faq_019__b842352706104545">trace_type</strong> field indicates the request resource. This field can be <strong id="cts_faq_019__b842352706104658">ConsoleAction</strong>, <strong id="cts_faq_019__b84235270610471">ApiCall</strong>, and <strong id="cts_faq_019__b84235270610475">SystemAction</strong>.</p>
|
|
||||||
<p id="cts_faq_019__p8060118"><strong id="cts_faq_019__b1768110039104714">SystemAction</strong> indicates that the operations are not triggered by users, such as automatic alarms, elastic scaling, scheduled backup tasks, and secondary invocations generated within the system to respond to the user's request. In this case, no user or device that triggers an operation exists. Therefore, <strong id="cts_faq_019__b1594489848105933">user</strong> and <strong id="cts_faq_019__b1881962885105933">source_ip</strong> are both empty.</p>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
||||||
@ -1,12 +0,0 @@
|
|||||||
<a name="cts_faq_020"></a><a name="cts_faq_020"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">What Are the Meanings of the Three Trace Statuses?</h1>
|
|
||||||
<div id="body1526265334999"><div class="p" id="cts_faq_020__p101512744619">The trace status is defined based on <strong id="cts_faq_020__b8423527061559">trace_status</strong> information recorded in a trace. Different fields have different meanings as follows:<ul id="cts_faq_020__ul41976214489"><li id="cts_faq_020__li18197132114819"><strong id="cts_faq_020__b842352706145929">normal</strong>: indicates that this operation succeeded.</li><li id="cts_faq_020__li719719216481"><strong id="cts_faq_020__b8423527061508">warning</strong>: indicates that this operation failed.</li><li id="cts_faq_020__li7197122154814"><strong id="cts_faq_020__b84235270615025">incident</strong>: indicates that this operation causes a more serious consequence than a failure, for example, causing a node failure or service interruption.</li></ul>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
<div>
|
|
||||||
<div class="familylinks">
|
|
||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0030932518.html">FAQs</a></div>
|
|
||||||
</div>
|
|
||||||
</div>
|
|
||||||
|
|
||||||
18
docs/cts/umn/cts_faq_0912.html
Normal file
18
docs/cts/umn/cts_faq_0912.html
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
<a name="cts_faq_0912"></a><a name="cts_faq_0912"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">How Can I Find Out Who Created a Specific ECS?</h1>
|
||||||
|
<div id="body1568253564558"><div class="section" id="cts_faq_0912__section119831758913"><h4 class="sectiontitle">Solution</h4><p id="cts_faq_0912__p1625612519214">To identify the user who created a specific ECS, you can view traces recorded by CTS.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_faq_0912__section25561015626"><h4 class="sectiontitle">Prerequisites</h4><ul id="cts_faq_0912__ul376317333810"><li id="cts_faq_0912__li57635331187">You have enabled CTS.</li><li id="cts_faq_0912__li1476311331582">You have obtained the resource ID of the ECS.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_faq_0912__section3626714416"><h4 class="sectiontitle">Procedure</h4><p id="cts_faq_0912__p789833519816">Log in to the CTS console, choose <strong id="cts_faq_0912__b1221211152413">Trace List</strong>, and select <strong id="cts_faq_0912__b11591314114714">ECS</strong> for <strong id="cts_faq_0912__b097022313251">Trace Source</strong>. In the displayed traces, look for the <strong id="cts_faq_0912__b164781348172613">createServer</strong> trace with the obtained resource ID, and expand the trace details.</p>
|
||||||
|
<p id="cts_faq_0912__p12551033117">The <strong id="cts_faq_0912__b391111507279">user</strong> field shows details of the IAM user who created the ECS. The format is <strong id="cts_faq_0912__b1432612535291">{"name": "</strong><em id="cts_faq_0912__i145093177290">Account name</em><strong id="cts_faq_0912__b7233105820291">", "id": "</strong><em id="cts_faq_0912__i420010315291">Account ID</em><strong id="cts_faq_0912__b19974183019">", "domain"{"name": "</strong><em id="cts_faq_0912__i12482154462914">IAM user name</em><strong id="cts_faq_0912__b886324153012">", "id": "</strong><em id="cts_faq_0912__i18219184910294">IAM user ID</em><strong id="cts_faq_0912__b11661128103010">"}}</strong>. If the ECS was created by an account, the IAM user name and the account name are the same.</p>
|
||||||
|
<p id="cts_faq_0912__p16267123814718"></p>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
18
docs/cts/umn/cts_faq_0913.html
Normal file
18
docs/cts/umn/cts_faq_0913.html
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
<a name="cts_faq_0913"></a><a name="cts_faq_0913"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">How Can I Find Out the Login IP Address of an IAM User?</h1>
|
||||||
|
<div id="body1594258048036"><div class="section" id="cts_faq_0913__section119831758913"><h4 class="sectiontitle">Solution</h4><p id="cts_faq_0913__p1625612519214">If you want to check if there are security risks in your account by examining the login IP addresses and login time of IAM users, you can view traces recorded by CTS.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_faq_0913__section128637710303"><h4 class="sectiontitle">Prerequisites</h4><p id="cts_faq_0913__p719851133010">You have enabled CTS.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="cts_faq_0913__section189791343183014"><h4 class="sectiontitle">Procedure</h4><ol id="cts_faq_0913__ol317734253118"><li id="cts_faq_0913__li201771542113112"><span>Log in to the CTS console, select <strong id="cts_faq_0913__b95016673011">IAM</strong> for <strong id="cts_faq_0913__b821815373017">Trace Source</strong>, select a time range, and click <strong id="cts_faq_0913__b2521158112910">Query</strong>.</span><p><p id="cts_faq_0913__p6472037163212"></p>
|
||||||
|
</p></li><li id="cts_faq_0913__li99991939163217"><span>Click <strong id="cts_faq_0913__b22051752155816">View Trace</strong> in the <strong id="cts_faq_0913__b2078115516587">Operation</strong> column of a trace to view its details. <strong id="cts_faq_0913__b94451042193211">source_ip</strong> indicates the login IP address, and <strong id="cts_faq_0913__b11382151153214">record_time</strong> indicates the login time.</span><p><p id="cts_faq_0913__p1189835017349"></p>
|
||||||
|
</p></li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
11
docs/cts/umn/cts_faq_0915.html
Normal file
11
docs/cts/umn/cts_faq_0915.html
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
<a name="cts_faq_0915"></a><a name="cts_faq_0915"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Why Are Two deleteMetadata Traces Generated When I Buy an ECS?</h1>
|
||||||
|
<div id="body1602818357520"><p id="cts_faq_0915__p7214516858">During ECS creation, metadata is used to store temporary information. When the creation is finished, the information is automatically deleted. Thus, two traces named <strong id="cts_faq_0915__b1786175912155">deleteMetadata</strong> are generated.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0000001410799284.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user