<divid="body8662426"><pid="aom_04_0000__en-us_topic_0175303967_p7933938392">Public cloud APIs comply with the RESTful API design principles. REST-based web services are organized into resources. Each resource is identified by one or more Uniform Resource Identifiers (URIs). An application accesses a resource based on the resource's Unified Resource Locator (URL). A URL is usually in the following format: https://<emid="aom_04_0000__en-us_topic_0175303967_i193313381196">Endpoint/uri</em>. In the URL, <emid="aom_04_0000__en-us_topic_0175303967_i193311389910">uri</em> indicates the resource path, that is, the API access path.</p>
<pid="aom_04_0000__en-us_topic_0175303967_p39330381094">Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted using JSON messages, with the media type represented by <strongid="aom_04_0000__en-us_topic_0175303967_b49339387910">Application/json</strong>.</p>
<pid="aom_04_0000__en-us_topic_0175303967_p139331638999">For details about how to use APIs, see <ahref="https://docs.otc.t-systems.com/en-us/api/apiug/apig-en-api-180328001.html"target="_blank"rel="noopener noreferrer">API Usage Guidelines</a>.</p>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.3.1.2.5.1.3 "><pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p59371788102942">Yes for token-based authentication</p>
<pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p32709868141244">which is <strongid="aom_04_0008__en-us_topic_0096010422_b84235270695515">application/json;charset=utf-8</strong>.</p>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.3.1.2.5.1.2 "><pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p51618533141920">Time to send a request,</p>
<pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p61913619141920">which is in the format of YYYYMMDD'T'HHMMSS'Z'. GMT time is used.</p>
</td>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.3.1.2.5.1.3 "><pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p37871689141920">Yes for Access Key ID/Secret Access Key (AK/SK)-based authentication</p>
<pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p61808088141920">which is obtained from the result of request signing.</p>
</td>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.3.1.2.5.1.3 "><pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p51113090141920">Yes for AK/SK-based authentication</p>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.3.1.2.5.1.2 "><pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p39431107141920">Request server information, which is obtained from the URL of a service API. The value is <strongid="aom_04_0008__en-us_topic_0096010422_b84235270612057">hostname[:port]</strong>. If no port is specified, the default port will be used. For HTTPS, port 443 is used by default.</p>
</td>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.3.1.2.5.1.3 "><pid="aom_04_0008__en-us_topic_0096010422_en-us_topic_0095259731_en-us_topic_0073180055_p22683417141920">Yes for AK/SK-based authentication</p>
<divid="body8662426"><pid="aom_04_0009__en-us_topic_0096010423_en-us_topic_0095259732_en-us_topic_0073180020_p5023366916959">A response usually contains the following headers:</p>
<tdclass="cellrowborder"valign="top"width="33.33333333333333%"headers="mcps1.3.2.2.4.1.2 "><pid="aom_04_0009__en-us_topic_0096010423_en-us_topic_0095259732_en-us_topic_0073180020_p4057779095935">(Standard HTTP header) Time when a message is sent. This field complies with RFC822 definitions.</p>
</td>
<tdclass="cellrowborder"valign="top"width="33.33333333333333%"headers="mcps1.3.2.2.4.1.3 "><pid="aom_04_0009__en-us_topic_0096010423_en-us_topic_0095259732_en-us_topic_0073180020_p3667485695935">Mon, 12 Nov 2007 15:55:01 GMT</p>
<tdclass="cellrowborder"valign="top"width="33.33333333333333%"headers="mcps1.3.2.2.4.1.2 "><pid="aom_04_0009__en-us_topic_0096010423_en-us_topic_0095259732_en-us_topic_0073180020_p6297619295935">(Standard HTTP header) Software that a server uses to process the request.</p>
<tdclass="cellrowborder"valign="top"width="33.33333333333333%"headers="mcps1.3.2.2.4.1.2 "><pid="aom_04_0009__en-us_topic_0096010423_en-us_topic_0095259732_en-us_topic_0073180020_p4460423795935">(Standard HTTP header) Length of the response body, which is represented by a decimal number and stored in bytes.</p>
<tdclass="cellrowborder"valign="top"width="33.33333333333333%"headers="mcps1.3.2.2.4.1.2 "><pid="aom_04_0009__en-us_topic_0096010423_en-us_topic_0095259732_en-us_topic_0073180020_p1726003895935">(Standard HTTP header) Media type of the response body sent to the recipient.</p>
<tdclass="cellrowborder"valign="top"width="80%"headers="mcps1.3.1.2.3.1.2 "><ulid="aom_04_0020__ul36282371325"><liid="aom_04_0020__li664333912217">Deleted the description of auto scaling APIs.</li><liid="aom_04_0020__li2628143717213">Optimized the solution description for error codes.</li></ul>
<tdclass="cellrowborder"valign="top"width="80%"headers="mcps1.3.1.2.3.1.2 "><pid="aom_04_0020__p639719231788">This issue is the first official release.</p>
<divid="body1534921092041"><pid="aom_02_0004__p812411178144">Alarms are the information reported when AOM or an external service such as Cloud Container Engine (CCE) is abnormal or may cause exceptions. Take measures to resolve faults. Otherwise, service exceptions may occur.</p>
<divclass="section"id="aom_02_0004__section1926111381416"><h4class="sectiontitle">Viewing Alarms</h4><olid="aom_02_0004__ol8214652112313"><liid="aom_02_0004__li637913444571"><span>Log in to the management console.</span></li><liid="aom_02_0004__li975084955716"><span>Under <strongid="aom_02_0004__b168042619214921">Application</strong>, click <strongid="aom_02_0004__b147816196914921">Application Operations Management</strong>.</span></li><liid="aom_02_0004__li14229814184718"><span>In the navigation pane, choose <strongid="aom_02_0004__b5435670814921">Alarm Center</strong>><strongid="aom_02_0004__b115521198214921">Alarms</strong>.</span><p><divclass="note"id="aom_02_0004__note1918716335019"><imgsrc="public_sys-resources/note_3.0-en-us.png"><spanclass="notetitle"></span><divclass="notebody"><ulid="aom_02_0004__ul318715325011"><liid="aom_02_0004__li1918793135016">Alarms are displayed by time. The alarm generated at the latest time is displayed at the topmost of the alarm list.</li><liid="aom_02_0004__li21871632508">You can also click <span><imgid="aom_02_0004__image205362166314921"src="en-us_image_0297078492.png"></span> on the right of the page to view the latest three alarms.</li></ul>
</div></div>
</p></li><liid="aom_02_0004__li13952173133419"><aname="aom_02_0004__li13952173133419"></a><aname="li13952173133419"></a><span>Set the time range or filter criteria.</span><p><oltype="a"id="aom_02_0004__ol1745611179813"><liid="aom_02_0004__li145613171989">Set the time range.<pid="aom_02_0004__p14059147395"><aname="aom_02_0004__li145613171989"></a><aname="li145613171989"></a>View the alarms generated within the time range. There are two methods to set a time range:</p>
<pid="aom_02_0004__p142140527235">Method 1: Use the predefined time label, such as <strongid="aom_02_0004__b47385016514921">Last 1 hour</strong>, <strongid="aom_02_0004__b112242967314921">Last 6 hours</strong>, or <strongid="aom_02_0004__b34703569014921">Last 1 day</strong>. You can select a time range as required.</p>
<pid="aom_02_0004__p32141252202310">Method 2: Specify the start time and end time to customize a time range. You can specify 30 days at most.</p>
</li><liid="aom_02_0004__li104561817187">Set filter criteria.<pid="aom_02_0004__p183764329490"><aname="aom_02_0004__li104561817187"></a><aname="li104561817187"></a>Enter an alarm status, name, or source, and click <strongid="aom_02_0004__b2658367414921">Search</strong>.</p>
<divclass="note"id="aom_02_0004__note16139143764920"><imgsrc="public_sys-resources/note_3.0-en-us.png"><spanclass="notetitle"></span><divclass="notebody"><ulid="aom_02_0004__ul830912446499"><liid="aom_02_0004__li1130913448491">You can click <strongid="aom_02_0004__b152003289114921">Reset</strong> to reset filter criteria.</li><liid="aom_02_0004__li11598517415">You can enter multiple alarm sources and separate them by using commas (,) to filter alarms.</li><liid="aom_02_0004__li930964411491">Alarm names and sources are case-sensitive.</li></ul>
</div></div>
</li></ol>
</p></li><liid="aom_02_0004__li18949175018919"><span>View the search result.</span><p><ulid="aom_02_0004__ul83192527105"><liid="aom_02_0004__li125233875018">In the bar graph, view the statistics of alarms that meet the filter criterion within the time range specified in <ahref="#aom_02_0004__li13952173133419">4</a>.<divclass="fignone"id="aom_02_0004__fig49873214199"><spanclass="figcap"><b>Figure 1 </b>Alarm statistics</span><br><span><imgid="aom_02_0004__image79881323191"src="en-us_image_0297078493.png"height="95.69416500000001"width="497.42"title="Click to enlarge"class="imgResize"></span></div>
</li><liid="aom_02_0004__li7187198195119">In the alarm list, view the information about alarms that meet the filter criterion within the time range specified in <ahref="#aom_02_0004__li13952173133419">4</a>.<pid="aom_02_0004__p1218714825114">Click <strongid="aom_02_0004__b36050371914921">View Details</strong> in the <strongid="aom_02_0004__b185806114921">Operation</strong> column to view alarm details.</p>
<divclass="fignone"id="aom_02_0004__fig269717184186"><spanclass="figcap"><b>Figure 2 </b>Alarm list</span><br><span><imgid="aom_02_0004__image5697201821813"src="en-us_image_0297078494.png"height="144.962419"width="497.42"title="Click to enlarge"class="imgResize"></span></div>
</li></ul>
</p></li><liid="aom_02_0004__li06081945172013"><span>Clear alarms.</span><p><pid="aom_02_0004__p10134166345">In the <strongid="aom_02_0004__b185820980414921">Operation</strong> column of the target alarm, click <strongid="aom_02_0004__b11820451514921">Clear</strong>.</p>
<pid="aom_02_0004__p1114175282011">In addition, AOM supports automatic clearance of alarms triggered by threshold rules. For example, you create a threshold rule. That is, if the CPU usage exceeds 85%, a threshold alarm will be generated. If the CPU usage is lower than 85%, the alarm will be cleared. In this case, you do not need to manually clear the alarm. When the CPU usage returns to normal, the threshold alarm will be automatically cleared. In addition, when the threshold rule is deleted, the threshold alarm will also be automatically cleared.</p>
<divid="body1534930763573"><pid="aom_02_0008__en-us_topic_0201820731_p1119664285317">AOM monitors the resource usage and health status of hosts, common system devices such as disks and file systems of hosts, and service processes or instances running on hosts.</p>
<divclass="note"id="aom_02_0008__note1254015148448"><imgsrc="public_sys-resources/note_3.0-en-us.png"><spanclass="notetitle"></span><divclass="notebody"><pid="aom_02_0008__p127962154520">The ICAgent reports resource information every ten minutes. The resource status changes are described as follows:</p>
<ulid="aom_02_0008__ul145201634184519"><liid="aom_02_0008__li352019342459">If the ICAgent on a host does not report resource information <strongid="aom_02_0008__b1662263481615">for three consecutive times</strong>, the system determines that the resource has been deleted. Therefore, the host status is displayed as <strongid="aom_02_0008__b362713345167">Deleted</strong> within 30 minutes after the host is stopped or the ICAgent is uninstalled.</li><liid="aom_02_0008__li1180938164613">When the ICAgent on a host reports resource information <strongid="aom_02_0008__b4187103114147">for one time</strong>, the system determines that the resource is restored. The host status is displayed as <strongid="aom_02_0008__b141871031121417">Normal</strong> ten minutes after the host is started or the ICAgent is reinstalled.</li></ul>
</div></div>
<divclass="section"id="aom_02_0008__section36211948143011"><h4class="sectiontitle">Precautions</h4><ulid="aom_02_0008__ul18462456143015"><liid="aom_02_0008__li11424185817307">A maximum of five tags can be added to a host, and each tag must be unique.</li><liid="aom_02_0008__li169874438385">The same tag can be added to different hosts.</li><liid="aom_02_0008__li16931451411">For hosts created on the CCE or ServiceStage console, you cannot select clusters or create aliases for them.</li><liid="aom_02_0008__li4971161713200">The host status can be <strongid="aom_02_0008__b02581657142413">Normal</strong>, <strongid="aom_02_0008__b0258155722412">Abnormal</strong>, <strongid="aom_02_0008__b1125925717249">Warning</strong>, <strongid="aom_02_0008__b52596579245">Silent</strong>, or <strongid="aom_02_0008__b2034917306253">Deleted</strong>. The running status of a host is displayed as <strongid="aom_02_0008__b76997332019735">Abnormal</strong> when the host is faulty due to network failures, and power off or shut down of the host, or when the host generates a threshold alarm. If resources are not running properly, follow the instructions in <ahref="aom_02_1012.html">What Can I Do If Resources Are Not Running Properly?</a>.</li></ul>
</div>
<divclass="section"id="aom_02_0008__section4984135633115"><h4class="sectiontitle">Procedure</h4><olid="aom_02_0008__ol8452632743"><liid="aom_02_0008__li2396186125916"><span>Log in to the management console.</span></li><liid="aom_02_0008__li81851115911"><span>Under <strongid="aom_02_0008__b0727114451510">Application</strong>, click <strongid="aom_02_0008__b14727044131514">Application Operations Management</strong>.</span></li><liid="aom_02_0008__li65335398"><span>In the navigation pane, choose <strongid="aom_02_0008__b11409184514159">Host Monitoring</strong> and perform the following operations as required:</span><p><ulid="aom_02_0008__ul174529321747"><liid="aom_02_0008__li20452232348"><strongid="aom_02_0008__b1011114621510">Adding an alias</strong><pid="aom_02_0008__p84521232441">If a host name is too complex to identify, you can add an alias, which makes it easy to identify a host as required.</p>
<pid="aom_02_0008__p15452203212410">In the host list, choose <strongid="aom_02_0008__b6936193161">More</strong>><strongid="aom_02_0008__b159363915162">Add Alias</strong> in the <strongid="aom_02_0008__b10936293160">Operation</strong> column of a desired host.</p>
</li><liid="aom_02_0008__li44521232743"><strongid="aom_02_0008__b69081123169">Adding a tag</strong><pid="aom_02_0008__p12452133210419">Tags are identifiers of hosts. You can manage hosts using tags. After a tag is added, you can quickly identify and select a host.</p>
<pid="aom_02_0008__p16453153212414">In the host list, click <strongid="aom_02_0008__b469091471616">Add tags</strong> in the <strongid="aom_02_0008__b769015147164">Operation</strong> column of the row that contains the target host. In the displayed dialog box, click <span><imgid="aom_02_0008__image23601514151613"src="en-us_image_0297092397.png"></span>, enter a tag, and click <span><imgid="aom_02_0008__image510915563175"src="en-us_image_0297092398.png"></span> and <strongid="aom_02_0008__b86911314131618">OK</strong>. After a tag is added, you can enter a tag keyword in the search box in the upper right corner of the page to search for a host. The <strongid="aom_02_0008__b16548131891616">Tags</strong> column of the host list is hidden by default. You can click <span><imgid="aom_02_0008__image1979915168144"src="en-us_image_0297092399.png"></span> in the upper right corner and select or deselect <strongid="aom_02_0008__b1549141816163">Show tag</strong>.</p>
</li></ul>
</p></li><liid="aom_02_0008__li44538323415"><span>Set filter criteria to search for the host to be monitored and monitor resource usage and health status of the host.</span><p><divclass="fignone"id="aom_02_0008__fig8803427141720"><spanclass="figcap"><b>Figure 1 </b>Monitoring the resource usage and health status of the desired host</span><br><span><imgid="aom_02_0008__image2803827181714"src="en-us_image_0297092400.png"height="33.915"width="523.6875"title="Click to enlarge"class="imgResize"></span></div>
</p></li><liid="aom_02_0008__li445310321418"><span>Click the host name to enter the <strongid="aom_02_0008__b113911920171614">Host Details</strong> page. In the instance list, monitor the resource usage and health status of the instances running on the host. Click the <strongid="aom_02_0008__b139118206166">View Monitor Graphs</strong> tab to monitor all the metrics of the host.</span><p><ulid="aom_02_0008__ul1177717441999"><liid="aom_02_0008__li6535321514"><strongid="aom_02_0008__b2407132131620">Creating a view template</strong><pid="aom_02_0008__p19535921019">AOM provides the default view template (<strongid="aom_02_0008__b467310223163">Host Template</strong>) that you can modify. You can also click the plus sign (+) in <span><imgid="aom_02_0008__image109641941131213"src="en-us_image_0297092401.png"></span> to add you own template.</p>
</li><liid="aom_02_0008__li7535821216"><strongid="aom_02_0008__b9839182481613">Adding a metric graph</strong><pid="aom_02_0008__p145353213114">You can click <span><imgid="aom_02_0008__image115351321915"src="en-us_image_0297092402.png"></span> to add a line graph or <span><imgid="aom_02_0008__image1953582118"src="en-us_image_0297092403.png"></span> to add a digit graph to the view template. You can also delete, move, and copy metric graphs in the view template according to <ahref="aom_02_0003.html">Dashboard</a>.</p>
</li><liid="aom_02_0008__li1535162010"><strongid="aom_02_0008__b116429992">Adding a view template to a dashboard</strong><pid="aom_02_0008__p1753510219112">On the host details page, choose <strongid="aom_02_0008__b833192026">More</strong>><strongid="aom_02_0008__b1525855500">Add To Dashboard</strong> in the upper right corner to add the view template to a dashboard for monitoring.</p>
</li></ul>
</p></li><liid="aom_02_0008__li174539321340"><span>Monitor common system devices such as GPUs and NICs of the host.</span><p><ulid="aom_02_0008__ul945317328414"><liid="aom_02_0008__li14453123217411">Click the <strongid="aom_02_0008__b638138038">GPUs</strong> tab to view the basic information about the GPUs of the host. Click a GPU to monitor its metrics on the <strongid="aom_02_0008__b372677727">View Monitor Graphs</strong> page.</li><liid="aom_02_0008__li7454132642">Click the <strongid="aom_02_0008__b2048510289">NIC</strong> tab to view the basic information about the NICs of the host. Click a NIC to monitor its metrics on the <strongid="aom_02_0008__b948075976">View Monitor Graphs</strong> page.</li><liid="aom_02_0008__li74541632842">Click the <strongid="aom_02_0008__b1736571023">Disks</strong> tab to view the basic information about the disks of the host. Click a disk to monitor its metrics on the <strongid="aom_02_0008__b1760416721">View Monitor Graphs</strong> page.</li><liid="aom_02_0008__li104542321047">Click the <strongid="aom_02_0008__b1578552913166">File System</strong> tab to view the basic information about the file system of the host. Click a disk file partition to monitor its metrics on the <strongid="aom_02_0008__b0790529101617">View Monitor Graphs</strong> page.</li></ul>
<divid="body1534921645538"><pid="aom_02_0009__p63443418">AOM enables you to quickly query logs, and use log source information and context to locate faults.</p>
<olid="aom_02_0009__ol9143273"><liid="aom_02_0009__li72081113014"><span>Log in to the management console.</span></li><liid="aom_02_0009__li17547135207"><span>Under <strongid="aom_02_0009__b1112018163012">Application</strong>, click <strongid="aom_02_0009__b71211416506">Application Operations Management</strong>.</span></li><liid="aom_02_0009__li1714210407316"><span>In the navigation pane, choose <strongid="aom_02_0009__b486841710019">Log</strong><strongid="aom_02_0009__b13782121118250">Management</strong>><strongid="aom_02_0009__b128681817109">Log Search</strong>.</span></li><liid="aom_02_0009__li21668983"><span>On the <strongid="aom_02_0009__b1222918323193">Log Search</strong> page, set filter criteria as prompted.</span><p><divclass="note"id="aom_02_0009__note2045618441585"><imgsrc="public_sys-resources/note_3.0-en-us.png"><spanclass="notetitle"></span><divclass="notebody"><oltype="a"id="aom_02_0009__ol788611114593"><liid="aom_02_0009__li178861411145920">You can search for logs by service, system, or host.<ulid="aom_02_0009__ul2634419013"><liid="aom_02_0009__li617802472717">For service logs, you can set filter criteria such as <strongid="aom_02_0009__b1078114914578">Cluster</strong>, <strongid="aom_02_0009__b9787164910575">Namespace</strong>, and <strongid="aom_02_0009__b20787249175714">Service</strong>. You can also click <strongid="aom_02_0009__b278719491570">Advanced Search</strong> and set filter criteria such as <strongid="aom_02_0009__b1178844917572">Instance</strong>, <strongid="aom_02_0009__b12788114935710">Host</strong>, and <strongid="aom_02_0009__b10788249195718">File Name</strong>, and choose whether to enable <strongid="aom_02_0009__b1278844985717">Hide System Service</strong>.</li><liid="aom_02_0009__li119186147">For system logs, you can set filter criteria such as <strongid="aom_02_0009__b122461026208">Cluster</strong> and <strongid="aom_02_0009__b52472026501">Host</strong>.</li><liid="aom_02_0009__li19841945540">For host logs, you can set filter criteria such as <strongid="aom_02_0009__b1966913271403">Cluster</strong> and <strongid="aom_02_0009__b64021613175714">IP Address</strong>.</li></ul>
</li><liid="aom_02_0009__li111841514115915">Enter a keyword in the search box. Rules are as follows:<ulid="aom_02_0009__ul1645684417588"><liid="aom_02_0009__li174561044175813">Enter a case-sensitive keyword.</li><liid="aom_02_0009__li1245624465814">Enter a keyword for exact search. A keyword refers to a word between two adjacent delimiters.</li><liid="aom_02_0009__li1245634417580">Enter a keyword containing an asterisk (*) or a question mark (?) for fuzzy search. For example, enter <strongid="aom_02_0009__b171891936907">ER?OR</strong>, <strongid="aom_02_0009__b819016367010">*ROR</strong>, or <strongid="aom_02_0009__b1019033610016">ER*R</strong>.</li><liid="aom_02_0009__li545674410585">Enter a phrase for exact search. For example, enter <strongid="aom_02_0009__b741518318017">Start to refresh</strong> or <strongid="aom_02_0009__b542018312004">Start-to-refresh</strong>. Note that hyphens (-) are <ahref="aom_02_0082.html">delimiters</a>.</li><liid="aom_02_0009__li44560440587">Enter a keyword containing AND (&&) or OR (||) for search. For example, enter <strongid="aom_02_0009__b12248143414014">query logs&&error*</strong> or <strongid="aom_02_0009__b10248834704">query logs||error</strong>.</li><liid="aom_02_0009__li131754480910">If no log is found, you are advised to narrow down the search scope and add an asterisk (*) before and after the keyword for fuzzy match.</li></ul>
</li></ol>
</div></div>
</p></li><liid="aom_02_0009__li34212241"><aname="aom_02_0009__li34212241"></a><aname="li34212241"></a><span>View the search results of logs.</span><p><pid="aom_02_0009__p1777141917420">The search results are sorted based on the log collection time. The keywords in the search results are highlighted. </p>
<pid="aom_02_0009__p6815132484415">By default, the descending order is used. You can click <span><imgid="aom_02_0009__image14198155613451"src="en-us_image_0297092404.png"></span> in the <strongid="aom_02_0009__b5302185911457">Time</strong> column to change the order. <span><imgid="aom_02_0009__image201441423194619"src="en-us_image_0297092725.png"></span> indicates the ascending order by time (that is, the latest log is displayed at the end). <span><imgid="aom_02_0009__image8732105174613"src="en-us_image_0297092726.png"></span> indicates the descending order by time (that is, the latest log is displayed at the top).</p>
<oltype="a"id="aom_02_0009__ol19728122"><liid="aom_02_0009__li43335374">Click <span><imgid="aom_02_0009__image44761611173911"src="en-us_image_0227418531.png"></span> on the left of the log list to view details such as host IP address and source.</li><liid="aom_02_0009__li823995655615">AOM allows you to view the surrounding logs of a specified log by clicking <strongid="aom_02_0009__b756531192115">View Context</strong> in the <strongid="aom_02_0009__b957193117213">Operation</strong> column, facilitating fault locating. Therefore, you do not need to search for logs in raw files.<ulid="aom_02_0009__ul50321738"><liid="aom_02_0009__li50242460">In the <strongid="aom_02_0009__b24191230154415">Display Rows</strong> drop-down list, set the number of rows that display raw context data of the log.<divclass="note"id="aom_02_0009__note49528960"><imgsrc="public_sys-resources/note_3.0-en-us.png"><spanclass="notetitle"></span><divclass="notebody"><pclass="text"id="aom_02_0009__p43107464">For example, select <strongid="aom_02_0009__b457322519454">200</strong> from the <strongid="aom_02_0009__b357312517452">Display Rows</strong> drop-down list.</p>
<ulid="aom_02_0009__ul52422860"><liid="aom_02_0009__li2043692">If there are more than or equal to 100 logs printed prior to a log and more than or equal to 99 logs printed following the log, the preceding 100 logs and following 99 logs are displayed as the context.</li><liid="aom_02_0009__li18393235">If there are fewer than 100 logs (for example, 90) printed prior to a log and fewer than 99 logs (for example, 80) printed following the log, the preceding 90 logs and following 80 logs are displayed as the context.</li></ul>
</div></div>
</li><liclass="subitemlist"id="aom_02_0009__li38551552422">Click <strongid="aom_02_0009__b842352706164356">Export Current Page</strong> to export displayed raw context data of the log to a local PC.</li></ul>
</li></ol>
<divclass="note"id="aom_02_0009__note54004927"><imgsrc="public_sys-resources/note_3.0-en-us.png"><spanclass="notetitle"></span><divclass="notebody"><pclass="text"id="aom_02_0009__p16282296">To ensure that tenant hosts and services run properly, some components (for example, kube-dns) provided by the system will run on the tenant hosts. The logs of these components are also queried during tenant log query.</p>
</div></div>
</p></li><liid="aom_02_0009__li10229194714111"><span>(Optional) Click <span><imgid="aom_02_0009__image179806362010"src="en-us_image_0297092727.png"></span> on the right of the <strongid="aom_02_0009__b44171351224">Log Search</strong> page, select an export format, and export the search result to a local PC.</span><p><pid="aom_02_0009__p13742134820119">Logs are sorted according to the order set in <ahref="#aom_02_0009__li34212241">5</a> and a maximum of 5000 logs can be exported. For example, when 6000 logs in the search result are sorted in the descending order, only the first 5000 logs can be exported.</p>
<pid="aom_02_0009__p3430230111313">Logs can be exported in CSV or TXT format. You can select a format as required. If you select the CSV format, detailed information (such as the log content, host IP address, and source) can be exported, as shown in <ahref="#aom_02_0009__fig1785710409496">Figure 1</a>. Only log content will be exported when you select the TXT format (as shown in <ahref="#aom_02_0009__fig9558111333018">Figure 2</a>). Each line indicates a log.</p>
<divclass="fignone"id="aom_02_0009__fig1785710409496"><aname="aom_02_0009__fig1785710409496"></a><aname="fig1785710409496"></a><spanclass="figcap"><b>Figure 1 </b>Exporting logs in CSV format</span><br><span><imgid="aom_02_0009__image17858540134914"src="en-us_image_0297092728.png"height="74.8125"width="523.6875"title="Click to enlarge"class="imgResize"></span></div>
<divclass="fignone"id="aom_02_0009__fig9558111333018"><aname="aom_02_0009__fig9558111333018"></a><aname="fig9558111333018"></a><spanclass="figcap"><b>Figure 2 </b>Exporting logs in TXT format</span><br><span><imgid="aom_02_0009__image7558413193019"src="en-us_image_0297092729.png"height="79.80000000000001"width="523.6875"title="Click to enlarge"class="imgResize"></span></div>
<h1class="topictitle1">Configuring VM Log Collection Paths</h1>
<divid="body8662426"><pid="aom_02_0039__en-us_topic_0169698346_p9451651359">AOM can collect and display VM logs. VM refers to an Elastic Cloud Server (ECS) running Linux. Before collecting logs, configure a log collection path according to the following procedure.</p>
<divclass="section"id="aom_02_0039__en-us_topic_0169698346_section188528174444"><h4class="sectiontitle">Prerequisites</h4><pid="aom_02_0039__en-us_topic_0169698346_p1740907555">You have installed the ICAgent on a VM according to <ahref="aom_02_2012.html">Installing the ICAgent</a>. </p>
</div>
<divclass="section"id="aom_02_0039__en-us_topic_0169698346_section0650147205514"><h4class="sectiontitle">Precautions</h4><ulid="aom_02_0039__en-us_topic_0169698346_ul127115695413"><liid="aom_02_0039__en-us_topic_0169698346_li1434612187534">The ICAgent collects <strongid="aom_02_0039__en-us_topic_0169698346_b47261142131612">*.log</strong>, <strongid="aom_02_0039__en-us_topic_0169698346_b75811046181615">*.trace</strong>, and <strongid="aom_02_0039__en-us_topic_0169698346_b17465453191615">*.out</strong> log files only. For example, <strongid="aom_02_0039__en-us_topic_0169698346_b1062672020410">/opt/yilu/work/xig/debug_cpu.log</strong>.</li><liid="aom_02_0039__en-us_topic_0169698346_li24741354175011">Ensure that an absolute path of the log directory or file is configured and the path exists. For example, <strongid="aom_02_0039__en-us_topic_0169698346_b108911222302">/opt/yilu/work/xig</strong> or <strongid="aom_02_0039__en-us_topic_0169698346_b1461816914303">/opt/yilu/work/xig/debug_cpu.log</strong>.</li><liid="aom_02_0039__en-us_topic_0169698346_li8476854155018">The ICAgent does not collect log files from subdirectories. For example, the ICAgent does not collect log files from the <strongid="aom_02_0039__en-us_topic_0169698346_b373923710379">/opt/yilu/work/xig/debug</strong> subdirectory of <strongid="aom_02_0039__en-us_topic_0169698346_b1773953753714">/opt/yilu/work/xig</strong>.</li><liid="aom_02_0039__en-us_topic_0169698346_li166817595">A maximum of 20 log collection paths can be configured for a VM.</li><liid="aom_02_0039__li3336184010111">For ECSs in the same resource set, only the latest log collection configuration in the system will be used. AOM and LTS log collection configurations cannot take effect at the same time. For example, if you configure log collection paths in AOM for ECSs, the previous LTS collection configurations of all ECSs under the resource set become invalid.</li></ul>
</div>
<divclass="section"id="aom_02_0039__en-us_topic_0169698346_section18187161014116"><h4class="sectiontitle">Procedure</h4><olid="aom_02_0039__en-us_topic_0169698346_ol18682144114402"><liid="aom_02_0039__li177555413590"><span>Log in to the management console.</span></li><liid="aom_02_0039__li113591446145915"><span>Under <strongid="aom_02_0039__b9287666603453">Application</strong>, click <strongid="aom_02_0039__b15099776253453">Application Operations Management</strong>.</span></li><liid="aom_02_0039__li9899115915349"><span>In the navigation pane, choose <strongid="aom_02_0039__b20080378173453">Log Management</strong>><strongid="aom_02_0039__b17803103173453">Path Configuration</strong>.</span></li><liid="aom_02_0039__en-us_topic_0169698346_li191014817485"><span>In the VM list, click <strongid="aom_02_0039__en-us_topic_0169698346_b11893103115376">Configure</strong> in the <strongid="aom_02_0039__en-us_topic_0169698346_b18894123113715">Operation</strong> column to configure one or more log collection paths for a VM.</span><p><divclass="p"id="aom_02_0039__en-us_topic_0169698346_p6748151101613">You can use the paths automatically identified by the ICAgent or manually configure paths.<ulid="aom_02_0039__en-us_topic_0169698346_ul6557828164212"><liid="aom_02_0039__en-us_topic_0169698346_li1617516410478"><strongid="aom_02_0039__en-us_topic_0169698346_b594112620198">Using the paths automatically identified by the ICAgent</strong><pid="aom_02_0039__en-us_topic_0169698346_p141641868472">The ICAgent automatically scans the log files of your VM, and displays all the log files that have file handles and are suffixed with <strongid="aom_02_0039__en-us_topic_0169698346_b14828476182">.log</strong>, <strongid="aom_02_0039__en-us_topic_0169698346_b3642451181813">.trace</strong>, or <strongid="aom_02_0039__en-us_topic_0169698346_b47275514188">.out</strong> on the page.</p>
<pid="aom_02_0039__en-us_topic_0169698346_p31061914182013">You can click <span><imgid="aom_02_0039__en-us_topic_0169698346_image862314124916"src="en-us_image_0227418562.png"></span> in the <strongid="aom_02_0039__b12773175422214">Operation</strong> column to add a path automatically identified by the ICAgent to the log collection path list. To configure multiple paths, repeat this operation.</p>
<divclass="fignone"id="aom_02_0039__en-us_topic_0169698346_fig17711201993711"><spanclass="figcap"><b>Figure 1 </b>Using the paths automatically identified by the ICAgent</span><br><span><imgid="aom_02_0039__image1578271218109"src="en-us_image_0297092742.png"width="492.1"height="239.09529700000002"title="Click to enlarge"class="imgResize"></span></div>
</li><liid="aom_02_0039__en-us_topic_0169698346_li13686152014313"><strongid="aom_02_0039__en-us_topic_0169698346_b321481144016">Manually configuring log collection paths</strong><pid="aom_02_0039__en-us_topic_0169698346_p470410123613">If the paths automatically identified by the ICAgent cannot meet your requirements, enter a log directory or file (for example, <strongid="aom_02_0039__b14971036183417">/opt/yilu/work/xig/debug_cpu.log</strong>) in the <strongid="aom_02_0039__b1866121944916">Log Collection Path</strong> text box, and then click <span><imgid="aom_02_0039__en-us_topic_0169698346_image11989123315500"src="en-us_image_0227418562.png"></span> to add the path to the log collection path list. To configure multiple paths, repeat this operation.</p>
<divclass="fignone"id="aom_02_0039__en-us_topic_0169698346_fig729151074218"><spanclass="figcap"><b>Figure 2 </b>Manually configuring log collection paths</span><br><span><imgid="aom_02_0039__image17469115831016"src="en-us_image_0297092743.png"width="492.1"height="259.197715"title="Click to enlarge"class="imgResize"></span></div>
</li></ul>
</div>
</p></li><liid="aom_02_0039__li63355523816"><span>Click <strongid="aom_02_0039__b7433937443453">OK</strong>.</span><p><pid="aom_02_0039__p153335520384">After a log collection path is configured, the ICAgent collects log files from the configured path. The collection takes about 1 minute. After log files are collected, choose <strongid="aom_02_0039__b11147490883453">Log Management</strong>><strongid="aom_02_0039__b12725021383453">Log Files</strong> in the navigation pane and then click the <strongid="aom_02_0039__b11212954863453">Host</strong> tab to view the collected log files.</p>
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.