From 1062ce3297679f4b92482bf6aeece6b023296a77 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9Cjiayuying=E2=80=9D?= <“jiayuying1@huawei.com”> Date: Thu, 29 Sep 2022 16:36:59 +0800 Subject: [PATCH] AOM UMN 0929 --- docs/aom/umn/.placeholder | 0 docs/aom/umn/ALL_META.TXT.json | 452 +++++++++++++ docs/aom/umn/CLASS.TXT.json | 407 ++++++++++++ docs/aom/umn/PARAMETERS.txt | 3 + docs/aom/umn/aom_02_0001.html | 17 + docs/aom/umn/aom_02_0003.html | 121 ++++ docs/aom/umn/aom_02_0004.html | 35 ++ docs/aom/umn/aom_02_0008.html | 36 ++ docs/aom/umn/aom_02_0009.html | 36 ++ docs/aom/umn/aom_02_0010.html | 138 ++++ docs/aom/umn/aom_02_0039.html | 32 + docs/aom/umn/aom_02_0044.html | 19 + docs/aom/umn/aom_02_0045.html | 31 + docs/aom/umn/aom_02_0048.html | 19 + docs/aom/umn/aom_02_0054.html | 23 + docs/aom/umn/aom_02_0068.html | 17 + docs/aom/umn/aom_02_0079.html | 52 ++ docs/aom/umn/aom_02_0082.html | 593 ++++++++++++++++++ docs/aom/umn/aom_02_0083.html | 32 + docs/aom/umn/aom_02_0087.html | 15 + docs/aom/umn/aom_02_1002.html | 50 ++ docs/aom/umn/aom_02_1007.html | 7 + docs/aom/umn/aom_02_1010.html | 20 + docs/aom/umn/aom_02_1011.html | 26 + docs/aom/umn/aom_02_1012.html | 81 +++ docs/aom/umn/aom_02_1014.html | 33 + docs/aom/umn/aom_02_1015.html | 47 ++ docs/aom/umn/aom_02_1016.html | 142 +++++ docs/aom/umn/aom_02_1017.html | 82 +++ docs/aom/umn/aom_02_1018.html | 111 ++++ docs/aom/umn/aom_02_1019.html | 329 ++++++++++ docs/aom/umn/aom_02_1020.html | 184 ++++++ docs/aom/umn/aom_02_1021.html | 275 ++++++++ docs/aom/umn/aom_02_1022.html | 160 +++++ docs/aom/umn/aom_02_1023.html | 12 + docs/aom/umn/aom_02_1024.html | 11 + docs/aom/umn/aom_02_1030.html | 37 ++ docs/aom/umn/aom_02_1035.html | 82 +++ docs/aom/umn/aom_02_1041.html | 85 +++ docs/aom/umn/aom_02_1100.html | 17 + docs/aom/umn/aom_02_1101.html | 15 + docs/aom/umn/aom_02_1117.html | 95 +++ docs/aom/umn/aom_02_2007.html | 33 + docs/aom/umn/aom_02_2011.html | 19 + docs/aom/umn/aom_02_2012.html | 23 + docs/aom/umn/aom_02_2013.html | 14 + docs/aom/umn/aom_02_2014.html | 14 + docs/aom/umn/aom_06_6001.html | 31 + docs/aom/umn/en-us_image_0000001315765116.png | Bin 0 -> 16286 bytes docs/aom/umn/en-us_image_0000001320760778.png | Bin 0 -> 10099 bytes docs/aom/umn/en-us_image_0000001366881660.png | Bin 0 -> 79501 bytes docs/aom/umn/en-us_image_0000001367106940.png | Bin 0 -> 80002 bytes docs/aom/umn/en-us_image_0000001367745042.png | Bin 0 -> 76538 bytes docs/aom/umn/en-us_image_0000001368935324.png | Bin 0 -> 104819 bytes docs/aom/umn/en-us_image_0000001415472973.png | Bin 0 -> 46345 bytes docs/aom/umn/en-us_image_0000001417721645.png | Bin 0 -> 1124 bytes docs/aom/umn/en-us_image_0000001417801529.png | Bin 0 -> 129672 bytes docs/aom/umn/en-us_image_0169698516.png | Bin 0 -> 543 bytes docs/aom/umn/en-us_image_0201820725.png | Bin 0 -> 1448 bytes docs/aom/umn/en-us_image_0201820771.png | Bin 0 -> 190 bytes docs/aom/umn/en-us_image_0201820799.png | Bin 0 -> 1493 bytes docs/aom/umn/en-us_image_0227418531.png | Bin 0 -> 278 bytes docs/aom/umn/en-us_image_0227418562.png | Bin 0 -> 333 bytes docs/aom/umn/en-us_image_0296834237.png | Bin 0 -> 11920 bytes docs/aom/umn/en-us_image_0296834240.png | Bin 0 -> 12842 bytes docs/aom/umn/en-us_image_0296834241.png | Bin 0 -> 8391 bytes docs/aom/umn/en-us_image_0296835591.png | Bin 0 -> 658 bytes docs/aom/umn/en-us_image_0296835776.png | Bin 0 -> 164 bytes docs/aom/umn/en-us_image_0297078492.png | Bin 0 -> 16285 bytes docs/aom/umn/en-us_image_0297078493.png | Bin 0 -> 18099 bytes docs/aom/umn/en-us_image_0297078494.png | Bin 0 -> 86438 bytes docs/aom/umn/en-us_image_0297078495.png | Bin 0 -> 14011 bytes docs/aom/umn/en-us_image_0297078496.png | Bin 0 -> 58797 bytes docs/aom/umn/en-us_image_0297092397.png | Bin 0 -> 197 bytes docs/aom/umn/en-us_image_0297092398.png | Bin 0 -> 294 bytes docs/aom/umn/en-us_image_0297092399.png | Bin 0 -> 190 bytes docs/aom/umn/en-us_image_0297092400.png | Bin 0 -> 8770 bytes docs/aom/umn/en-us_image_0297092401.png | Bin 0 -> 1124 bytes docs/aom/umn/en-us_image_0297092402.png | Bin 0 -> 1493 bytes docs/aom/umn/en-us_image_0297092403.png | Bin 0 -> 1448 bytes docs/aom/umn/en-us_image_0297092404.png | Bin 0 -> 260 bytes docs/aom/umn/en-us_image_0297092725.png | Bin 0 -> 187 bytes docs/aom/umn/en-us_image_0297092726.png | Bin 0 -> 171 bytes docs/aom/umn/en-us_image_0297092727.png | Bin 0 -> 619 bytes docs/aom/umn/en-us_image_0297092728.png | Bin 0 -> 52948 bytes docs/aom/umn/en-us_image_0297092729.png | Bin 0 -> 15917 bytes docs/aom/umn/en-us_image_0297092730.png | Bin 0 -> 490 bytes docs/aom/umn/en-us_image_0297092731.png | Bin 0 -> 1287 bytes docs/aom/umn/en-us_image_0297092732.png | Bin 0 -> 84673 bytes docs/aom/umn/en-us_image_0297092733.png | Bin 0 -> 232 bytes docs/aom/umn/en-us_image_0297092734.png | Bin 0 -> 232 bytes docs/aom/umn/en-us_image_0297092735.png | Bin 0 -> 43457 bytes docs/aom/umn/en-us_image_0297092736.png | Bin 0 -> 490 bytes docs/aom/umn/en-us_image_0297092737.png | Bin 0 -> 1287 bytes docs/aom/umn/en-us_image_0297092738.png | Bin 0 -> 84673 bytes docs/aom/umn/en-us_image_0297092739.png | Bin 0 -> 232 bytes docs/aom/umn/en-us_image_0297092740.png | Bin 0 -> 232 bytes docs/aom/umn/en-us_image_0297092742.png | Bin 0 -> 53487 bytes docs/aom/umn/en-us_image_0297092743.png | Bin 0 -> 57383 bytes docs/aom/umn/en-us_image_0297106347.png | Bin 0 -> 26989 bytes docs/aom/umn/en-us_image_0297180622.png | Bin 0 -> 37053 bytes docs/aom/umn/en-us_image_0297180623.png | Bin 0 -> 22833 bytes docs/aom/umn/en-us_image_0297180624.png | Bin 0 -> 23925 bytes docs/aom/umn/en-us_image_0297180645.png | Bin 0 -> 1036 bytes docs/aom/umn/en-us_image_0297180646.png | Bin 0 -> 23220 bytes docs/aom/umn/en-us_image_0297180648.png | Bin 0 -> 24274 bytes docs/aom/umn/en-us_image_0297180649.png | Bin 0 -> 30005 bytes docs/aom/umn/en-us_image_0297180650.png | Bin 0 -> 21454 bytes docs/aom/umn/en-us_image_0297180651.png | Bin 0 -> 4544 bytes docs/aom/umn/en-us_image_0297180661.png | Bin 0 -> 16750 bytes docs/aom/umn/en-us_image_0297180662.png | Bin 0 -> 533 bytes docs/aom/umn/en-us_image_0297180663.png | Bin 0 -> 376 bytes docs/aom/umn/en-us_image_0297180664.png | Bin 0 -> 30082 bytes docs/aom/umn/en-us_image_0297183034.png | Bin 0 -> 20962 bytes docs/aom/umn/en-us_image_0297183036.png | Bin 0 -> 8074 bytes docs/aom/umn/en-us_image_0297183037.png | Bin 0 -> 490 bytes docs/aom/umn/en-us_image_0297183038.png | Bin 0 -> 317 bytes docs/aom/umn/en-us_image_0297183045.png | Bin 0 -> 44243 bytes docs/aom/umn/en-us_image_0297183060.png | Bin 0 -> 47431 bytes docs/aom/umn/en-us_image_0297183061.png | Bin 0 -> 50343 bytes docs/aom/umn/en-us_image_0297183062.png | Bin 0 -> 50291 bytes docs/aom/umn/en-us_image_0297183813.png | Bin 0 -> 433 bytes docs/aom/umn/en-us_image_0297183816.png | Bin 0 -> 374 bytes docs/aom/umn/en-us_image_0297183817.png | Bin 0 -> 374 bytes docs/aom/umn/en-us_image_0297183818.png | Bin 0 -> 7619 bytes docs/aom/umn/en-us_image_0297194004.png | Bin 0 -> 1036 bytes docs/aom/umn/en-us_image_0297531017.png | Bin 0 -> 5962 bytes docs/aom/umn/en-us_image_0297531019.png | Bin 0 -> 197 bytes docs/aom/umn/en-us_image_0297531020.png | Bin 0 -> 374 bytes docs/aom/umn/en-us_image_0297531022.png | Bin 0 -> 490 bytes docs/aom/umn/en-us_image_0297531023.png | Bin 0 -> 210 bytes docs/aom/umn/en-us_image_0297610957.png | Bin 0 -> 36351 bytes docs/aom/umn/en-us_image_0297616583.png | Bin 0 -> 13653 bytes docs/aom/umn/en-us_image_0297616584.png | Bin 0 -> 671 bytes docs/aom/umn/en-us_image_0297616606.png | Bin 0 -> 44687 bytes docs/aom/umn/en-us_image_0297616607.png | Bin 0 -> 283 bytes docs/aom/umn/en-us_image_0297616608.png | Bin 0 -> 260 bytes docs/aom/umn/en-us_image_0297616609.png | Bin 0 -> 187 bytes docs/aom/umn/en-us_image_0297616611.png | Bin 0 -> 171 bytes docs/aom/umn/en-us_image_0297616613.png | Bin 0 -> 21680 bytes docs/aom/umn/en-us_topic_0296826282.html | 24 + .../public_sys-resources/ExpandCollapse.js | 1 + .../caution_3.0-en-us.png | Bin 0 -> 2752 bytes .../umn/public_sys-resources/commonltr.css | 1 + .../public_sys-resources/commonltr_print.css | 1 + .../umn/public_sys-resources/commonrtl.css | 2 + .../public_sys-resources/danger_3.0-en-us.png | Bin 0 -> 2771 bytes docs/aom/umn/public_sys-resources/delta.gif | Bin 0 -> 836 bytes .../aom/umn/public_sys-resources/deltaend.gif | Bin 0 -> 834 bytes .../umn/public_sys-resources/icon-arrowdn.gif | Bin 0 -> 68 bytes .../umn/public_sys-resources/icon-arrowrt.gif | Bin 0 -> 70 bytes .../umn/public_sys-resources/icon-caution.gif | Bin 0 -> 1086 bytes .../umn/public_sys-resources/icon-danger.gif | Bin 0 -> 1086 bytes .../umn/public_sys-resources/icon-huawei.gif | Bin 0 -> 2767 bytes .../umn/public_sys-resources/icon-note.gif | Bin 0 -> 983 bytes .../umn/public_sys-resources/icon-notice.gif | Bin 0 -> 962 bytes .../aom/umn/public_sys-resources/icon-tip.gif | Bin 0 -> 879 bytes .../umn/public_sys-resources/icon-warning.gif | Bin 0 -> 1086 bytes .../umn/public_sys-resources/imageResize.js | 18 + .../umn/public_sys-resources/imageclose.gif | Bin 0 -> 1238 bytes .../public_sys-resources/imageclosehover.gif | Bin 0 -> 1172 bytes .../aom/umn/public_sys-resources/imagemax.gif | Bin 0 -> 1267 bytes .../public_sys-resources/imagemaxhover.gif | Bin 0 -> 1199 bytes .../jquery-migrate-1.2.1.min.js | 2 + .../umn/public_sys-resources/jquery-ui.min.js | 6 + .../umn/public_sys-resources/jquery.min.js | 2 + .../jquery.mousewheel.min.js | 7 + .../umn/public_sys-resources/macFFBgHack.png | Bin 0 -> 1014 bytes .../public_sys-resources/note_3.0-en-us.png | Bin 0 -> 1080 bytes .../public_sys-resources/notice_3.0-en-us.png | Bin 0 -> 1672 bytes docs/aom/umn/public_sys-resources/popup.js | 1 + .../aom/umn/public_sys-resources/thickbox.css | 1 + docs/aom/umn/public_sys-resources/thickbox.js | 8 + .../warning_3.0-en-us.png | Bin 0 -> 3164 bytes 174 files changed, 4187 insertions(+) delete mode 100644 docs/aom/umn/.placeholder create mode 100644 docs/aom/umn/ALL_META.TXT.json create mode 100644 docs/aom/umn/CLASS.TXT.json create mode 100644 docs/aom/umn/PARAMETERS.txt create mode 100644 docs/aom/umn/aom_02_0001.html create mode 100644 docs/aom/umn/aom_02_0003.html create mode 100644 docs/aom/umn/aom_02_0004.html create mode 100644 docs/aom/umn/aom_02_0008.html create mode 100644 docs/aom/umn/aom_02_0009.html create mode 100644 docs/aom/umn/aom_02_0010.html create mode 100644 docs/aom/umn/aom_02_0039.html create mode 100644 docs/aom/umn/aom_02_0044.html create mode 100644 docs/aom/umn/aom_02_0045.html create mode 100644 docs/aom/umn/aom_02_0048.html create mode 100644 docs/aom/umn/aom_02_0054.html create mode 100644 docs/aom/umn/aom_02_0068.html create mode 100644 docs/aom/umn/aom_02_0079.html create mode 100644 docs/aom/umn/aom_02_0082.html create mode 100644 docs/aom/umn/aom_02_0083.html create mode 100644 docs/aom/umn/aom_02_0087.html create mode 100644 docs/aom/umn/aom_02_1002.html create mode 100644 docs/aom/umn/aom_02_1007.html create mode 100644 docs/aom/umn/aom_02_1010.html create mode 100644 docs/aom/umn/aom_02_1011.html create mode 100644 docs/aom/umn/aom_02_1012.html create mode 100644 docs/aom/umn/aom_02_1014.html create mode 100644 docs/aom/umn/aom_02_1015.html create mode 100644 docs/aom/umn/aom_02_1016.html create mode 100644 docs/aom/umn/aom_02_1017.html create mode 100644 docs/aom/umn/aom_02_1018.html create mode 100644 docs/aom/umn/aom_02_1019.html create mode 100644 docs/aom/umn/aom_02_1020.html create mode 100644 docs/aom/umn/aom_02_1021.html create mode 100644 docs/aom/umn/aom_02_1022.html create mode 100644 docs/aom/umn/aom_02_1023.html create mode 100644 docs/aom/umn/aom_02_1024.html create mode 100644 docs/aom/umn/aom_02_1030.html create mode 100644 docs/aom/umn/aom_02_1035.html create mode 100644 docs/aom/umn/aom_02_1041.html create mode 100644 docs/aom/umn/aom_02_1100.html create mode 100644 docs/aom/umn/aom_02_1101.html create mode 100644 docs/aom/umn/aom_02_1117.html create mode 100644 docs/aom/umn/aom_02_2007.html create mode 100644 docs/aom/umn/aom_02_2011.html create mode 100644 docs/aom/umn/aom_02_2012.html create mode 100644 docs/aom/umn/aom_02_2013.html create mode 100644 docs/aom/umn/aom_02_2014.html create mode 100644 docs/aom/umn/aom_06_6001.html create mode 100644 docs/aom/umn/en-us_image_0000001315765116.png create mode 100644 docs/aom/umn/en-us_image_0000001320760778.png create mode 100644 docs/aom/umn/en-us_image_0000001366881660.png create mode 100644 docs/aom/umn/en-us_image_0000001367106940.png create mode 100644 docs/aom/umn/en-us_image_0000001367745042.png create mode 100644 docs/aom/umn/en-us_image_0000001368935324.png create mode 100644 docs/aom/umn/en-us_image_0000001415472973.png create mode 100644 docs/aom/umn/en-us_image_0000001417721645.png create mode 100644 docs/aom/umn/en-us_image_0000001417801529.png create mode 100644 docs/aom/umn/en-us_image_0169698516.png create mode 100644 docs/aom/umn/en-us_image_0201820725.png create mode 100644 docs/aom/umn/en-us_image_0201820771.png create mode 100644 docs/aom/umn/en-us_image_0201820799.png create mode 100644 docs/aom/umn/en-us_image_0227418531.png create mode 100644 docs/aom/umn/en-us_image_0227418562.png create mode 100644 docs/aom/umn/en-us_image_0296834237.png create mode 100644 docs/aom/umn/en-us_image_0296834240.png create mode 100644 docs/aom/umn/en-us_image_0296834241.png create mode 100644 docs/aom/umn/en-us_image_0296835591.png create mode 100644 docs/aom/umn/en-us_image_0296835776.png create mode 100644 docs/aom/umn/en-us_image_0297078492.png create mode 100644 docs/aom/umn/en-us_image_0297078493.png create mode 100644 docs/aom/umn/en-us_image_0297078494.png create mode 100644 docs/aom/umn/en-us_image_0297078495.png create mode 100644 docs/aom/umn/en-us_image_0297078496.png create mode 100644 docs/aom/umn/en-us_image_0297092397.png create mode 100644 docs/aom/umn/en-us_image_0297092398.png create mode 100644 docs/aom/umn/en-us_image_0297092399.png create mode 100644 docs/aom/umn/en-us_image_0297092400.png create mode 100644 docs/aom/umn/en-us_image_0297092401.png create mode 100644 docs/aom/umn/en-us_image_0297092402.png create mode 100644 docs/aom/umn/en-us_image_0297092403.png create mode 100644 docs/aom/umn/en-us_image_0297092404.png create mode 100644 docs/aom/umn/en-us_image_0297092725.png create mode 100644 docs/aom/umn/en-us_image_0297092726.png create mode 100644 docs/aom/umn/en-us_image_0297092727.png create mode 100644 docs/aom/umn/en-us_image_0297092728.png create mode 100644 docs/aom/umn/en-us_image_0297092729.png create mode 100644 docs/aom/umn/en-us_image_0297092730.png create mode 100644 docs/aom/umn/en-us_image_0297092731.png create mode 100644 docs/aom/umn/en-us_image_0297092732.png create mode 100644 docs/aom/umn/en-us_image_0297092733.png create mode 100644 docs/aom/umn/en-us_image_0297092734.png create mode 100644 docs/aom/umn/en-us_image_0297092735.png create mode 100644 docs/aom/umn/en-us_image_0297092736.png create mode 100644 docs/aom/umn/en-us_image_0297092737.png create mode 100644 docs/aom/umn/en-us_image_0297092738.png create mode 100644 docs/aom/umn/en-us_image_0297092739.png create mode 100644 docs/aom/umn/en-us_image_0297092740.png create mode 100644 docs/aom/umn/en-us_image_0297092742.png create mode 100644 docs/aom/umn/en-us_image_0297092743.png create mode 100644 docs/aom/umn/en-us_image_0297106347.png create mode 100644 docs/aom/umn/en-us_image_0297180622.png create mode 100644 docs/aom/umn/en-us_image_0297180623.png create mode 100644 docs/aom/umn/en-us_image_0297180624.png create mode 100644 docs/aom/umn/en-us_image_0297180645.png create mode 100644 docs/aom/umn/en-us_image_0297180646.png create mode 100644 docs/aom/umn/en-us_image_0297180648.png create mode 100644 docs/aom/umn/en-us_image_0297180649.png create mode 100644 docs/aom/umn/en-us_image_0297180650.png create mode 100644 docs/aom/umn/en-us_image_0297180651.png create mode 100644 docs/aom/umn/en-us_image_0297180661.png create mode 100644 docs/aom/umn/en-us_image_0297180662.png create mode 100644 docs/aom/umn/en-us_image_0297180663.png create mode 100644 docs/aom/umn/en-us_image_0297180664.png create mode 100644 docs/aom/umn/en-us_image_0297183034.png create mode 100644 docs/aom/umn/en-us_image_0297183036.png create mode 100644 docs/aom/umn/en-us_image_0297183037.png create mode 100644 docs/aom/umn/en-us_image_0297183038.png create mode 100644 docs/aom/umn/en-us_image_0297183045.png create mode 100644 docs/aom/umn/en-us_image_0297183060.png create mode 100644 docs/aom/umn/en-us_image_0297183061.png create mode 100644 docs/aom/umn/en-us_image_0297183062.png create mode 100644 docs/aom/umn/en-us_image_0297183813.png create mode 100644 docs/aom/umn/en-us_image_0297183816.png create mode 100644 docs/aom/umn/en-us_image_0297183817.png create mode 100644 docs/aom/umn/en-us_image_0297183818.png create mode 100644 docs/aom/umn/en-us_image_0297194004.png create mode 100644 docs/aom/umn/en-us_image_0297531017.png create mode 100644 docs/aom/umn/en-us_image_0297531019.png create mode 100644 docs/aom/umn/en-us_image_0297531020.png create mode 100644 docs/aom/umn/en-us_image_0297531022.png create mode 100644 docs/aom/umn/en-us_image_0297531023.png create mode 100644 docs/aom/umn/en-us_image_0297610957.png create mode 100644 docs/aom/umn/en-us_image_0297616583.png create mode 100644 docs/aom/umn/en-us_image_0297616584.png create mode 100644 docs/aom/umn/en-us_image_0297616606.png create mode 100644 docs/aom/umn/en-us_image_0297616607.png create mode 100644 docs/aom/umn/en-us_image_0297616608.png create mode 100644 docs/aom/umn/en-us_image_0297616609.png create mode 100644 docs/aom/umn/en-us_image_0297616611.png create mode 100644 docs/aom/umn/en-us_image_0297616613.png create mode 100644 docs/aom/umn/en-us_topic_0296826282.html create mode 100644 docs/aom/umn/public_sys-resources/ExpandCollapse.js create mode 100644 docs/aom/umn/public_sys-resources/caution_3.0-en-us.png create mode 100644 docs/aom/umn/public_sys-resources/commonltr.css create mode 100644 docs/aom/umn/public_sys-resources/commonltr_print.css create mode 100644 docs/aom/umn/public_sys-resources/commonrtl.css create mode 100644 docs/aom/umn/public_sys-resources/danger_3.0-en-us.png create mode 100644 docs/aom/umn/public_sys-resources/delta.gif create mode 100644 docs/aom/umn/public_sys-resources/deltaend.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-arrowdn.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-arrowrt.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-caution.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-danger.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-huawei.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-note.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-notice.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-tip.gif create mode 100644 docs/aom/umn/public_sys-resources/icon-warning.gif create mode 100644 docs/aom/umn/public_sys-resources/imageResize.js create mode 100644 docs/aom/umn/public_sys-resources/imageclose.gif create mode 100644 docs/aom/umn/public_sys-resources/imageclosehover.gif create mode 100644 docs/aom/umn/public_sys-resources/imagemax.gif create mode 100644 docs/aom/umn/public_sys-resources/imagemaxhover.gif create mode 100644 docs/aom/umn/public_sys-resources/jquery-migrate-1.2.1.min.js create mode 100644 docs/aom/umn/public_sys-resources/jquery-ui.min.js create mode 100644 docs/aom/umn/public_sys-resources/jquery.min.js create mode 100644 docs/aom/umn/public_sys-resources/jquery.mousewheel.min.js create mode 100644 docs/aom/umn/public_sys-resources/macFFBgHack.png create mode 100644 docs/aom/umn/public_sys-resources/note_3.0-en-us.png create mode 100644 docs/aom/umn/public_sys-resources/notice_3.0-en-us.png create mode 100644 docs/aom/umn/public_sys-resources/popup.js create mode 100644 docs/aom/umn/public_sys-resources/thickbox.css create mode 100644 docs/aom/umn/public_sys-resources/thickbox.js create mode 100644 docs/aom/umn/public_sys-resources/warning_3.0-en-us.png diff --git a/docs/aom/umn/.placeholder b/docs/aom/umn/.placeholder deleted file mode 100644 index e69de29bb..000000000 diff --git a/docs/aom/umn/ALL_META.TXT.json b/docs/aom/umn/ALL_META.TXT.json new file mode 100644 index 000000000..8b0794a48 --- /dev/null +++ b/docs/aom/umn/ALL_META.TXT.json @@ -0,0 +1,452 @@ +[ + { + "uri":"aom_02_1007.html", + "product_code":"aom", + "code":"1", + "des":"Application Operations Management (AOM) is a one-stop, multi-dimensional O&M management platform for cloud applications. It monitors applications and related cloud resour", + "doc_type":"usermanual", + "kw":"Introduction,User Guide", + "title":"Introduction", + "githuburl":"" + }, + { + "uri":"aom_06_6001.html", + "product_code":"aom", + "code":"2", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"User Guide", + "title":"User Guide", + "githuburl":"" + }, + { + "uri":"en-us_topic_0296826282.html", + "product_code":"aom", + "code":"3", + "des":"Process of Using AOM shows the process of using AOM.(Mandatory) Register an account.(Mandatory) Create a cloud host.(Mandatory) Install the ICAgent.ICAgent is the data co", + "doc_type":"usermanual", + "kw":"Process of Using AOM,User Guide,User Guide", + "title":"Process of Using AOM", + "githuburl":"" + }, + { + "uri":"aom_02_1041.html", + "product_code":"aom", + "code":"4", + "des":"The Overview page provides full-link, multi-layer, and one-stop O&M for applications and resources. The following types of graphs are supported: infrastructure monitoring", + "doc_type":"usermanual", + "kw":"Overview,User Guide,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"aom_02_0001.html", + "product_code":"aom", + "code":"5", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"View Management", + "title":"View Management", + "githuburl":"" + }, + { + "uri":"aom_02_0003.html", + "product_code":"aom", + "code":"6", + "des":"With a dashboard, different graphs can be displayed on the same screen. Different graphs, such as line graphs and digit graphs can be used to display resource data, so th", + "doc_type":"usermanual", + "kw":"Dashboard,View Management,User Guide", + "title":"Dashboard", + "githuburl":"" + }, + { + "uri":"aom_02_1117.html", + "product_code":"aom", + "code":"7", + "des":"AOM displays metric data of each resource on the Metric Monitoring page. You can monitor metric values and trends in real time, add metrics to dashboards, create threshol", + "doc_type":"usermanual", + "kw":"Monitoring Metrics,View Management,User Guide", + "title":"Monitoring Metrics", + "githuburl":"" + }, + { + "uri":"aom_02_0044.html", + "product_code":"aom", + "code":"8", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Alarm Management", + "title":"Alarm Management", + "githuburl":"" + }, + { + "uri":"aom_02_0004.html", + "product_code":"aom", + "code":"9", + "des":"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 fau", + "doc_type":"usermanual", + "kw":"Viewing Alarms,Alarm Management,User Guide", + "title":"Viewing Alarms", + "githuburl":"" + }, + { + "uri":"aom_02_0045.html", + "product_code":"aom", + "code":"10", + "des":"Generally, events carry important information, informing you of the changes of AOM itself or an external service such as Cloud Container Engine (CCE). Such changes do not", + "doc_type":"usermanual", + "kw":"Viewing Events,Alarm Management,User Guide", + "title":"Viewing Events", + "githuburl":"" + }, + { + "uri":"aom_02_1035.html", + "product_code":"aom", + "code":"11", + "des":"To use threshold rules, customize threshold conditions first. If a metric value meets a threshold condition, AOM generates a threshold alarm. If no metric data is reporte", + "doc_type":"usermanual", + "kw":"Creating Threshold Rules,Alarm Management,User Guide", + "title":"Creating Threshold Rules", + "githuburl":"" + }, + { + "uri":"aom_02_0048.html", + "product_code":"aom", + "code":"12", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Resource Monitoring", + "title":"Resource Monitoring", + "githuburl":"" + }, + { + "uri":"aom_02_0008.html", + "product_code":"aom", + "code":"13", + "des":"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 h", + "doc_type":"usermanual", + "kw":"Host Monitoring,Resource Monitoring,User Guide", + "title":"Host Monitoring", + "githuburl":"" + }, + { + "uri":"aom_02_2007.html", + "product_code":"aom", + "code":"14", + "des":"AOM enables you to monitor workloads deployed on Cloud Container Engine (CCE).The workload status can be Normal, Abnormal, Warning, Silent, or Deleted. If a workload gene", + "doc_type":"usermanual", + "kw":"Monitoring Workloads,Resource Monitoring,User Guide", + "title":"Monitoring Workloads", + "githuburl":"" + }, + { + "uri":"aom_02_1030.html", + "product_code":"aom", + "code":"15", + "des":"Services refer to containers and common processes you deploy. For example, a workload on Cloud Container Engine (CCE) is a service, and the Tomcat running on a VM is also", + "doc_type":"usermanual", + "kw":"Monitoring Services,Resource Monitoring,User Guide", + "title":"Monitoring Services", + "githuburl":"" + }, + { + "uri":"aom_02_0054.html", + "product_code":"aom", + "code":"16", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Log Management", + "title":"Log Management", + "githuburl":"" + }, + { + "uri":"aom_02_0009.html", + "product_code":"aom", + "code":"17", + "des":"AOM enables you to quickly query logs, and use log source information and context to locate faults.You can search for logs by service, system, or host.For service logs, y", + "doc_type":"usermanual", + "kw":"Searching for Logs,Log Management,User Guide", + "title":"Searching for Logs", + "githuburl":"" + }, + { + "uri":"aom_02_0010.html", + "product_code":"aom", + "code":"18", + "des":"You can quickly view log files of service instances or hosts to locate faults.The time information contained in a log file, if any, is automatically displayed, as shown i", + "doc_type":"usermanual", + "kw":"Viewing Log Files,Log Management,User Guide", + "title":"Viewing Log Files", + "githuburl":"" + }, + { + "uri":"aom_02_0039.html", + "product_code":"aom", + "code":"19", + "des":"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 fo", + "doc_type":"usermanual", + "kw":"Configuring VM Log Collection Paths,Log Management,User Guide", + "title":"Configuring VM Log Collection Paths", + "githuburl":"" + }, + { + "uri":"aom_02_0079.html", + "product_code":"aom", + "code":"20", + "des":"A log bucket is a logical group of log files. Ensure that a log bucket has been created before you view bucket logs.A maximum of 500 log files can be added to each log bu", + "doc_type":"usermanual", + "kw":"Adding a Log Bucket,Log Management,User Guide", + "title":"Adding a Log Bucket", + "githuburl":"" + }, + { + "uri":"aom_02_0083.html", + "product_code":"aom", + "code":"21", + "des":"AOM supports fine-grained log query. It enables you to view logs by bucket to obtain key service data and quickly locate problems.Ensure that you have added at least one ", + "doc_type":"usermanual", + "kw":"Viewing Bucket Logs,Log Management,User Guide", + "title":"Viewing Bucket Logs", + "githuburl":"" + }, + { + "uri":"aom_02_0068.html", + "product_code":"aom", + "code":"22", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Configuration Management", + "title":"Configuration Management", + "githuburl":"" + }, + { + "uri":"aom_02_2011.html", + "product_code":"aom", + "code":"23", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"ICAgent Management", + "title":"ICAgent Management", + "githuburl":"" + }, + { + "uri":"aom_02_2012.html", + "product_code":"aom", + "code":"24", + "des":"ICAgent is the collector of AOM. It runs on each host to collect metrics and logs in real time. Before using AOM, install the ICAgent. Otherwise, AOM cannot be used.Prere", + "doc_type":"usermanual", + "kw":"Installing the ICAgent,ICAgent Management,User Guide", + "title":"Installing the ICAgent", + "githuburl":"" + }, + { + "uri":"aom_02_2013.html", + "product_code":"aom", + "code":"25", + "des":"To ensure better collection experience, AOM will continuously upgrade ICAgent versions. When the system displays a message indicating that a new ICAgent version is availa", + "doc_type":"usermanual", + "kw":"Upgrading the ICAgent,ICAgent Management,User Guide", + "title":"Upgrading the ICAgent", + "githuburl":"" + }, + { + "uri":"aom_02_2014.html", + "product_code":"aom", + "code":"26", + "des":"After the ICAgent is uninstalled from a host, metric and log data is unavailable. Exercise caution when performing this operation.Select Cluster: xxx (xxx indicates the n", + "doc_type":"usermanual", + "kw":"Uninstalling the ICAgent,ICAgent Management,User Guide", + "title":"Uninstalling the ICAgent", + "githuburl":"" + }, + { + "uri":"aom_02_0087.html", + "product_code":"aom", + "code":"27", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Log Configuration", + "title":"Log Configuration", + "githuburl":"" + }, + { + "uri":"aom_02_0082.html", + "product_code":"aom", + "code":"28", + "des":"AOM enables you to divide the log content into multiple words for search by configuring delimiters. By default, AOM provides the following delimiters:If default delimiter", + "doc_type":"usermanual", + "kw":"Configuring Delimiters,Log Configuration,User Guide", + "title":"Configuring Delimiters", + "githuburl":"" + }, + { + "uri":"aom_02_1014.html", + "product_code":"aom", + "code":"29", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Metric Description", + "title":"Metric Description", + "githuburl":"" + }, + { + "uri":"aom_02_1015.html", + "product_code":"aom", + "code":"30", + "des":"Metrics reflect resource performance data or status. A metric consists of the namespace, dimension, name, and unit. Metrics are classified into system metrics and custom ", + "doc_type":"usermanual", + "kw":"Introduction,Metric Description,User Guide", + "title":"Introduction", + "githuburl":"" + }, + { + "uri":"aom_02_1016.html", + "product_code":"aom", + "code":"31", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Network Metrics and Dimensions,Metric Description,User Guide", + "title":"Network Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1017.html", + "product_code":"aom", + "code":"32", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Disk Metrics and Dimensions,Metric Description,User Guide", + "title":"Disk Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1018.html", + "product_code":"aom", + "code":"33", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"File System Metrics and Dimensions,Metric Description,User Guide", + "title":"File System Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1019.html", + "product_code":"aom", + "code":"34", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Host Metrics and Dimensions,Metric Description,User Guide", + "title":"Host Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1020.html", + "product_code":"aom", + "code":"35", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cluster Metrics and Dimensions,Metric Description,User Guide", + "title":"Cluster Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1021.html", + "product_code":"aom", + "code":"36", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Container Metrics and Dimensions,Metric Description,User Guide", + "title":"Container Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1022.html", + "product_code":"aom", + "code":"37", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Process Metrics and Dimensions,Metric Description,User Guide", + "title":"Process Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1023.html", + "product_code":"aom", + "code":"38", + "des":"Instance metrics consist of container or process metrics. The dimensions of instance metrics are the same as those of container or process metrics. For details, see Conta", + "doc_type":"usermanual", + "kw":"Instance Metrics and Dimensions,Metric Description,User Guide", + "title":"Instance Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1024.html", + "product_code":"aom", + "code":"39", + "des":"Service metrics consist of instance metrics. The dimensions of service metrics are the same as those of instance metrics. For details, see Instance Metrics and Dimensions", + "doc_type":"usermanual", + "kw":"Service Metrics and Dimensions,Metric Description,User Guide", + "title":"Service Metrics and Dimensions", + "githuburl":"" + }, + { + "uri":"aom_02_1010.html", + "product_code":"aom", + "code":"40", + "des":"AOM supports services such as Simple Message Notification (SMN), Cloud Trace Service (CTS), and Cloud Container Engine (CCE). You can use them after subscription. For exa", + "doc_type":"usermanual", + "kw":"Related Services,User Guide,User Guide", + "title":"Related Services", + "githuburl":"" + }, + { + "uri":"aom_02_1101.html", + "product_code":"aom", + "code":"41", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"FAQs", + "title":"FAQs", + "githuburl":"" + }, + { + "uri":"aom_02_1100.html", + "product_code":"aom", + "code":"42", + "des":"Each user can create a maximum of two AK/SK pairs. Once they are generated, they are permanently valid.AK: unique ID associated with the SK. It is used together with the ", + "doc_type":"usermanual", + "kw":"Obtaining an AK/SK,FAQs,User Guide", + "title":"Obtaining an AK/SK", + "githuburl":"" + }, + { + "uri":"aom_02_1002.html", + "product_code":"aom", + "code":"43", + "des":"In AOM, a maximum of 1440 data points can be returned for a single metric query. The relationship between the time range and statistical cycle is as follows:Maximum time ", + "doc_type":"usermanual", + "kw":"What Is the Relationship Between the Time Range and Statistical Cycle?,FAQs,User Guide", + "title":"What Is the Relationship Between the Time Range and Statistical Cycle?", + "githuburl":"" + }, + { + "uri":"aom_02_1012.html", + "product_code":"aom", + "code":"44", + "des":"Resource statuses include Normal, Warning, Abnormal, Deleted, and Silent. Warning, Abnormal, and Silent indicate improper resource running. Analyze and rectify faults acc", + "doc_type":"usermanual", + "kw":"What Can I Do If Resources Are Not Running Properly?,FAQs,User Guide", + "title":"What Can I Do If Resources Are Not Running Properly?", + "githuburl":"" + }, + { + "uri":"aom_02_1011.html", + "product_code":"aom", + "code":"45", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Change History,User Guide", + "title":"Change History", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/aom/umn/CLASS.TXT.json b/docs/aom/umn/CLASS.TXT.json new file mode 100644 index 000000000..a87af5126 --- /dev/null +++ b/docs/aom/umn/CLASS.TXT.json @@ -0,0 +1,407 @@ +[ + { + "desc":"Application Operations Management (AOM) is a one-stop, multi-dimensional O&M management platform for cloud applications. It monitors applications and related cloud resour", + "product_code":"aom", + "title":"Introduction", + "uri":"aom_02_1007.html", + "doc_type":"usermanual", + "p_code":"", + "code":"1" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"User Guide", + "uri":"aom_06_6001.html", + "doc_type":"usermanual", + "p_code":"", + "code":"2" + }, + { + "desc":"Process of Using AOM shows the process of using AOM.(Mandatory) Register an account.(Mandatory) Create a cloud host.(Mandatory) Install the ICAgent.ICAgent is the data co", + "product_code":"aom", + "title":"Process of Using AOM", + "uri":"en-us_topic_0296826282.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"3" + }, + { + "desc":"The Overview page provides full-link, multi-layer, and one-stop O&M for applications and resources. The following types of graphs are supported: infrastructure monitoring", + "product_code":"aom", + "title":"Overview", + "uri":"aom_02_1041.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"4" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"View Management", + "uri":"aom_02_0001.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"5" + }, + { + "desc":"With a dashboard, different graphs can be displayed on the same screen. Different graphs, such as line graphs and digit graphs can be used to display resource data, so th", + "product_code":"aom", + "title":"Dashboard", + "uri":"aom_02_0003.html", + "doc_type":"usermanual", + "p_code":"5", + "code":"6" + }, + { + "desc":"AOM displays metric data of each resource on the Metric Monitoring page. You can monitor metric values and trends in real time, add metrics to dashboards, create threshol", + "product_code":"aom", + "title":"Monitoring Metrics", + "uri":"aom_02_1117.html", + "doc_type":"usermanual", + "p_code":"5", + "code":"7" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Alarm Management", + "uri":"aom_02_0044.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"8" + }, + { + "desc":"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 fau", + "product_code":"aom", + "title":"Viewing Alarms", + "uri":"aom_02_0004.html", + "doc_type":"usermanual", + "p_code":"8", + "code":"9" + }, + { + "desc":"Generally, events carry important information, informing you of the changes of AOM itself or an external service such as Cloud Container Engine (CCE). Such changes do not", + "product_code":"aom", + "title":"Viewing Events", + "uri":"aom_02_0045.html", + "doc_type":"usermanual", + "p_code":"8", + "code":"10" + }, + { + "desc":"To use threshold rules, customize threshold conditions first. If a metric value meets a threshold condition, AOM generates a threshold alarm. If no metric data is reporte", + "product_code":"aom", + "title":"Creating Threshold Rules", + "uri":"aom_02_1035.html", + "doc_type":"usermanual", + "p_code":"8", + "code":"11" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Resource Monitoring", + "uri":"aom_02_0048.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"12" + }, + { + "desc":"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 h", + "product_code":"aom", + "title":"Host Monitoring", + "uri":"aom_02_0008.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"13" + }, + { + "desc":"AOM enables you to monitor workloads deployed on Cloud Container Engine (CCE).The workload status can be Normal, Abnormal, Warning, Silent, or Deleted. If a workload gene", + "product_code":"aom", + "title":"Monitoring Workloads", + "uri":"aom_02_2007.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"14" + }, + { + "desc":"Services refer to containers and common processes you deploy. For example, a workload on Cloud Container Engine (CCE) is a service, and the Tomcat running on a VM is also", + "product_code":"aom", + "title":"Monitoring Services", + "uri":"aom_02_1030.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"15" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Log Management", + "uri":"aom_02_0054.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"16" + }, + { + "desc":"AOM enables you to quickly query logs, and use log source information and context to locate faults.You can search for logs by service, system, or host.For service logs, y", + "product_code":"aom", + "title":"Searching for Logs", + "uri":"aom_02_0009.html", + "doc_type":"usermanual", + "p_code":"16", + "code":"17" + }, + { + "desc":"You can quickly view log files of service instances or hosts to locate faults.The time information contained in a log file, if any, is automatically displayed, as shown i", + "product_code":"aom", + "title":"Viewing Log Files", + "uri":"aom_02_0010.html", + "doc_type":"usermanual", + "p_code":"16", + "code":"18" + }, + { + "desc":"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 fo", + "product_code":"aom", + "title":"Configuring VM Log Collection Paths", + "uri":"aom_02_0039.html", + "doc_type":"usermanual", + "p_code":"16", + "code":"19" + }, + { + "desc":"A log bucket is a logical group of log files. Ensure that a log bucket has been created before you view bucket logs.A maximum of 500 log files can be added to each log bu", + "product_code":"aom", + "title":"Adding a Log Bucket", + "uri":"aom_02_0079.html", + "doc_type":"usermanual", + "p_code":"16", + "code":"20" + }, + { + "desc":"AOM supports fine-grained log query. It enables you to view logs by bucket to obtain key service data and quickly locate problems.Ensure that you have added at least one ", + "product_code":"aom", + "title":"Viewing Bucket Logs", + "uri":"aom_02_0083.html", + "doc_type":"usermanual", + "p_code":"16", + "code":"21" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Configuration Management", + "uri":"aom_02_0068.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"22" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"ICAgent Management", + "uri":"aom_02_2011.html", + "doc_type":"usermanual", + "p_code":"22", + "code":"23" + }, + { + "desc":"ICAgent is the collector of AOM. It runs on each host to collect metrics and logs in real time. Before using AOM, install the ICAgent. Otherwise, AOM cannot be used.Prere", + "product_code":"aom", + "title":"Installing the ICAgent", + "uri":"aom_02_2012.html", + "doc_type":"usermanual", + "p_code":"23", + "code":"24" + }, + { + "desc":"To ensure better collection experience, AOM will continuously upgrade ICAgent versions. When the system displays a message indicating that a new ICAgent version is availa", + "product_code":"aom", + "title":"Upgrading the ICAgent", + "uri":"aom_02_2013.html", + "doc_type":"usermanual", + "p_code":"23", + "code":"25" + }, + { + "desc":"After the ICAgent is uninstalled from a host, metric and log data is unavailable. Exercise caution when performing this operation.Select Cluster: xxx (xxx indicates the n", + "product_code":"aom", + "title":"Uninstalling the ICAgent", + "uri":"aom_02_2014.html", + "doc_type":"usermanual", + "p_code":"23", + "code":"26" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Log Configuration", + "uri":"aom_02_0087.html", + "doc_type":"usermanual", + "p_code":"22", + "code":"27" + }, + { + "desc":"AOM enables you to divide the log content into multiple words for search by configuring delimiters. By default, AOM provides the following delimiters:If default delimiter", + "product_code":"aom", + "title":"Configuring Delimiters", + "uri":"aom_02_0082.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"28" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Metric Description", + "uri":"aom_02_1014.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"29" + }, + { + "desc":"Metrics reflect resource performance data or status. A metric consists of the namespace, dimension, name, and unit. Metrics are classified into system metrics and custom ", + "product_code":"aom", + "title":"Introduction", + "uri":"aom_02_1015.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"30" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Network Metrics and Dimensions", + "uri":"aom_02_1016.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"31" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Disk Metrics and Dimensions", + "uri":"aom_02_1017.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"32" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"File System Metrics and Dimensions", + "uri":"aom_02_1018.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"33" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Host Metrics and Dimensions", + "uri":"aom_02_1019.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"34" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Cluster Metrics and Dimensions", + "uri":"aom_02_1020.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"35" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Container Metrics and Dimensions", + "uri":"aom_02_1021.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"36" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Process Metrics and Dimensions", + "uri":"aom_02_1022.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"37" + }, + { + "desc":"Instance metrics consist of container or process metrics. The dimensions of instance metrics are the same as those of container or process metrics. For details, see Conta", + "product_code":"aom", + "title":"Instance Metrics and Dimensions", + "uri":"aom_02_1023.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"38" + }, + { + "desc":"Service metrics consist of instance metrics. The dimensions of service metrics are the same as those of instance metrics. For details, see Instance Metrics and Dimensions", + "product_code":"aom", + "title":"Service Metrics and Dimensions", + "uri":"aom_02_1024.html", + "doc_type":"usermanual", + "p_code":"29", + "code":"39" + }, + { + "desc":"AOM supports services such as Simple Message Notification (SMN), Cloud Trace Service (CTS), and Cloud Container Engine (CCE). You can use them after subscription. For exa", + "product_code":"aom", + "title":"Related Services", + "uri":"aom_02_1010.html", + "doc_type":"usermanual", + "p_code":"2", + "code":"40" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"FAQs", + "uri":"aom_02_1101.html", + "doc_type":"usermanual", + "p_code":"", + "code":"41" + }, + { + "desc":"Each user can create a maximum of two AK/SK pairs. Once they are generated, they are permanently valid.AK: unique ID associated with the SK. It is used together with the ", + "product_code":"aom", + "title":"Obtaining an AK/SK", + "uri":"aom_02_1100.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"42" + }, + { + "desc":"In AOM, a maximum of 1440 data points can be returned for a single metric query. The relationship between the time range and statistical cycle is as follows:Maximum time ", + "product_code":"aom", + "title":"What Is the Relationship Between the Time Range and Statistical Cycle?", + "uri":"aom_02_1002.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"43" + }, + { + "desc":"Resource statuses include Normal, Warning, Abnormal, Deleted, and Silent. Warning, Abnormal, and Silent indicate improper resource running. Analyze and rectify faults acc", + "product_code":"aom", + "title":"What Can I Do If Resources Are Not Running Properly?", + "uri":"aom_02_1012.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"44" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"aom", + "title":"Change History", + "uri":"aom_02_1011.html", + "doc_type":"usermanual", + "p_code":"", + "code":"45" + } +] \ No newline at end of file diff --git a/docs/aom/umn/PARAMETERS.txt b/docs/aom/umn/PARAMETERS.txt new file mode 100644 index 000000000..6da8d5f07 --- /dev/null +++ b/docs/aom/umn/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/aom/umn/aom_02_0001.html b/docs/aom/umn/aom_02_0001.html new file mode 100644 index 000000000..0ad4edc97 --- /dev/null +++ b/docs/aom/umn/aom_02_0001.html @@ -0,0 +1,17 @@ + + +
With a dashboard, different graphs can be displayed on the same screen. Different graphs, such as line graphs and digit graphs can be used to display resource data, so that you can view monitoring data comprehensively.
+You can add key resource metrics to a dashboard and monitor them in real time. You can also compare the same metric of different resources on one screen. In addition, by adding routine O&M metrics to a dashboard, you can perform routine checks without re-selecting metrics when you open AOM again.
+Before creating a dashboard, learn the types of graphs that can be added to a dashboard for accurate resource monitoring. The following graphs can be added to a dashboard:
+You can use a line graph to compare the same metric of different resources. The following figure shows the CPU usage of different hosts.
+
The following figure shows the latest CPU usage.
+
The statuses of thresholds, hosts, and components can be displayed. The statuses of one or more threshold rules, hosts, or components can be added in one graph for monitoring. Titles of health status graphs can be customized.
+
Before adding a threshold-crossing status graph, create a threshold rule. Otherwise, the threshold-crossing status graph cannot be added.
+

Before adding a threshold-crossing status graph, create a threshold rule. Otherwise, the graph cannot be added.
+The following shows how to add a line graph to a dashboard:
+After creating a dashboard, you can also perform the operations described in Table 1.
+ +Operation Object + |
+Operation + |
+Description + |
+
|---|---|---|
Dashboard + |
+Set an interpolation mode + |
+For details, see Table 2. + |
+
Save as + |
+Click More in the upper right corner of the Dashboard page, and choose Save As, Rename, or Delete from the drop-down list. + |
+|
Rename + |
+||
Delete + |
+||
Export a monitoring report + |
+Click Export Monitoring Report to export only line graphs in the dashboard as CSV files to a local PC. + |
+|
Metric graph + |
+Add + |
+Click Add Metric Graph to add a line graph, digit graph, threshold-crossing status graph, host status graph, or service status graph to the dashboard. + |
+
Modify + |
+Choose Modify Copy, Delete, or View Larger (support only for line graphs) from the Operation drop-down list. +Figure 6 Metric graph
+![]() NOTE:
+In a dashboard, when resources such as hosts and services are deleted, metric graphs created for these resources are not automatically deleted. To improve system performance, manually delete unnecessary graphs. + |
+|
Copy + |
+||
Delete + |
+||
Zoom in + |
+||
Refresh + |
+||
Resize + |
+Hover over the lower right corner of a metric graph. When the cursor changes to |
+|
Reposition + |
+Hover over the blank area in the upper or lower part of a graph, and drag and drop it to the desired position. + |
+
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.
+
on the right of the page to view the latest three alarms.View the alarms generated within the time range. There are two methods to set a time range:
+Method 1: Use the predefined time label, such as Last 1 hour, Last 6 hours, or Last 1 day. You can select a time range as required.
+Method 2: Specify the start time and end time to customize a time range. You can specify 30 days at most.
+Enter an alarm status, name, or source, and click Search.
+

Click View Details in the Operation column to view alarm details.
+
In the Operation column of the target alarm, click Clear.
+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.
+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.
+
The ICAgent reports resource information every ten minutes. The resource status changes are described as follows:
+If a host name is too complex to identify, you can add an alias, which makes it easy to identify a host as required.
+In the host list, choose More > Add Alias in the Operation column of a desired host.
+Tags are identifiers of hosts. You can manage hosts using tags. After a tag is added, you can quickly identify and select a host.
+In the host list, click Add tags in the Operation column of the row that contains the target host. In the displayed dialog box, click
, enter a tag, and click
and OK. 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 Tags column of the host list is hidden by default. You can click
in the upper right corner and select or deselect Show tag.

AOM provides the default view template (Host Template) that you can modify. You can also click the plus sign (+) in
to add you own template.
You can click
to add a line graph or
to add a digit graph to the view template. You can also delete, move, and copy metric graphs in the view template according to Dashboard.
On the host details page, choose More > Add To Dashboard in the upper right corner to add the view template to a dashboard for monitoring.
+AOM enables you to quickly query logs, and use log source information and context to locate faults.
+
The search results are sorted based on the log collection time. The keywords in the search results are highlighted.
+By default, the descending order is used. You can click
in the Time column to change the order.
indicates the ascending order by time (that is, the latest log is displayed at the end).
indicates the descending order by time (that is, the latest log is displayed at the top).
on the left of the log list to view details such as host IP address and source.
For example, select 200 from the Display Rows drop-down list.
+
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.
+
on the right of the Log Search page, select an export format, and export the search result to a local PC.Logs are sorted according to the order set in 5 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.
+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 Figure 1. Only log content will be exported when you select the TXT format (as shown in Figure 2). Each line indicates a log.
+ + +You can quickly view log files of service instances or hosts to locate faults.
+The time information contained in a log file, if any, is automatically displayed, as shown in the red box in Figure 1. This time information is irrelevant to the time range that you set.
+ + +You can quickly view log files of service instances to locate faults.
+
to search services.+
Operation + |
+Setup + |
+Description + |
+
|---|---|---|
Entering a keyword + |
+None + |
+Enter a keyword in the search box in the upper right corner. Rules are as follows:
+
|
+
Setting a time range + |
+Date and time + |
+Click |
+
Time range + |
+Select a specific time range on the time axis to view logs. You can select only one range (5 minutes) each time. +Scroll the mouse to increase or decrease the time granularity. + |
+|
Viewing log files + |
+Clear + |
+Click Clear to clear the logs displayed on the screen. This operation clears only the logs displayed on the screen but does not delete them. + |
+
Viewing real-time logs + |
+The function of real-time monitoring is disabled by default. To enable it, click Enable Real-Time Viewing. After this function is enabled, the latest written logs can be viewed. +The exception in the log records the exceptions that occur during code running. When using logs to locate faults, pay attention to the exception. For real-time log viewing, AOM automatically highlights exception keywords in logs, facilitating fault locating. Such keywords are case-sensitive. For example, exception and Exception are highlighted, but keywords such as EXCEPTION, exCeption, and EXception are not highlighted, as shown in the following figure. +Figure 2 Viewing real-time logs
+![]() NOTE:
+After the function of viewing logs in real time is enabled, AOM automatically highlights exception keywords in logs. In that case, you cannot enter keywords to search for logs. + |
+|
Maximized display + |
+Click |
+
AOM enables you to quickly view log files of hosts, facilitating fault locating.
+
to search.+
Operation + |
+Setup + |
+Description + |
+
|---|---|---|
Entering a keyword + |
+None + |
+Enter a keyword in the search box in the upper right corner. Rules are as follows:
+
|
+
Setting a time range + |
+Date and time + |
+Click |
+
Time range + |
+Select a specific time range on the time axis to view logs. You can select only one range (5 minutes) each time. +Scroll the mouse to increase or decrease the time granularity. + |
+|
Viewing log files + |
+Clear + |
+Click Clear to clear the logs displayed on the screen. This operation clears only the logs displayed on the screen but does not delete them. + |
+
Viewing real-time logs + |
+The function of real-time monitoring is disabled by default. To enable it, click Enable Real-Time Viewing. After this function is enabled, the latest written logs can be viewed. +The exception in the log records the exceptions that occur during code running. When using logs to locate faults, pay attention to the exception. For real-time log viewing, AOM automatically highlights exception keywords in logs, facilitating fault locating. Such keywords are case-sensitive. For example, exception and Exception are highlighted, but keywords such as EXCEPTION, exCeption, and EXception are not highlighted, as shown in the following figure. +Figure 4 Viewing real-time logs
+![]() NOTE:
+After the function of viewing logs in real time is enabled, AOM automatically highlights exception keywords in logs. In that case, you cannot enter keywords to search for logs. + |
+|
Maximized display + |
+Click |
+
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.
+You have installed the ICAgent on a VM according to Installing the ICAgent.
+The ICAgent automatically scans the log files of your VM, and displays all the log files that have file handles and are suffixed with .log, .trace, or .out on the page.
+You can click
in the Operation column to add a path automatically identified by the ICAgent to the log collection path list. To configure multiple paths, repeat this operation.

If the paths automatically identified by the ICAgent cannot meet your requirements, enter a log directory or file (for example, /opt/yilu/work/xig/debug_cpu.log) in the Log Collection Path text box, and then click
to add the path to the log collection path list. To configure multiple paths, repeat this operation.

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 Log Management > Log Files in the navigation pane and then click the Host tab to view the collected log files.
+Generally, events carry important information, informing you of the changes of AOM itself or an external service such as Cloud Container Engine (CCE). Such changes do not necessarily cause exceptions. Events do not need to be handled.
+Events are displayed by time. The latest event is displayed at the topmost of the event list.
+View the events generated within the time range. There are two methods to set a time range:
+Method 1: Use the predefined time label, such as Last 1 hour, Last 6 hours, or Last 1 day. You can select a time range as required.
+Method 2: Specify the start time and end time to customize a time range. You can specify 30 days at most.
+Enter an event name and source, and click Search.
+
A log bucket is a logical group of log files. Ensure that a log bucket has been created before you view bucket logs.
+
After adding a log bucket, you can also perform the operations described in Table 1.
+ +Operation + |
+Description + |
+
|---|---|
View bucket logs + |
+Click a log bucket to view logs. + |
+
Modify a log bucket + |
+Click Modify in the Operation column. + |
+
Delete a log bucket + |
+Click Delete in the Operation column. +Deleting a log bucket will not delete log files in it. + |
+
AOM enables you to divide the log content into multiple words for search by configuring delimiters. By default, AOM provides the following delimiters:
+, '";=()[]{}@&<>/:\n\t\r
+If default delimiters cannot meet requirements, customize delimiters according to the following procedure.
+Delimiters are applicable only to the logs generated after the delimiters are configured. Earlier logs are processed based on earlier delimiters.
+
, enter a delimiter in the text box, and click
.
The asterisk (*) and question mark (?) are wildcards and cannot serve as delimiters.
+
.Enter the log content to preview in the text box and click Preview.
+
Click Reset to restore the default configuration. Default delimiters are as follows:
+, '";=()[]{}@&<>/:\n\t\r
+ASCII Value + |
+Control Character + |
+ASCII Value + |
+Control Character + |
+ASCII Value + |
+Control Character + |
+ASCII Value + |
+Control Character + |
+
|---|---|---|---|---|---|---|---|
0 + |
+NUL (Null) + |
+32 + |
+Space + |
+64 + |
+@ + |
+96 + |
+` + |
+
1 + |
+SOH (Start of heading) + |
+33 + |
+! + |
+65 + |
+A + |
+97 + |
+a + |
+
2 + |
+STX (Start of text) + |
+34 + |
+" + |
+66 + |
+B + |
+98 + |
+b + |
+
3 + |
+ETX (End of text) + |
+35 + |
+# + |
+67 + |
+C + |
+99 + |
+c + |
+
4 + |
+EOT (End of transmission) + |
+36 + |
+$ + |
+68 + |
+D + |
+100 + |
+d + |
+
5 + |
+ENQ (Enquiry) + |
+37 + |
+% + |
+69 + |
+E + |
+101 + |
+e + |
+
6 + |
+ACK (Acknowledge) + |
+38 + |
+& + |
+70 + |
+F + |
+102 + |
+f + |
+
7 + |
+BEL (Bell) + |
+39 + |
+' + |
+71 + |
+G + |
+103 + |
+g + |
+
8 + |
+BS (Backspace) + |
+40 + |
+( + |
+72 + |
+H + |
+104 + |
+h + |
+
9 + |
+HT (Horizontal tab) + |
+41 + |
+) + |
+73 + |
+I + |
+105 + |
+i + |
+
10 + |
+LF (Line feed) + |
+42 + |
+* + |
+74 + |
+J + |
+106 + |
+j + |
+
11 + |
+VT (Vertical tab) + |
+43 + |
++ + |
+75 + |
+K + |
+107 + |
+k + |
+
12 + |
+FF (Form feed) + |
+44 + |
+, + |
+76 + |
+L + |
+108 + |
+l + |
+
13 + |
+CR (Carriage return) + |
+45 + |
+- + |
+77 + |
+M + |
+109 + |
+m + |
+
14 + |
+SO (Shift out) + |
+46 + |
+. + |
+78 + |
+N + |
+110 + |
+n + |
+
15 + |
+SI (Shift in) + |
+47 + |
+/ + |
+79 + |
+O + |
+111 + |
+o + |
+
16 + |
+DLE (Data link escape) + |
+48 + |
+0 + |
+80 + |
+P + |
+112 + |
+p + |
+
17 + |
+DC1 (Device control 1) + |
+49 + |
+1 + |
+81 + |
+Q + |
+113 + |
+q + |
+
18 + |
+DC2 (Device control 2) + |
+50 + |
+2 + |
+82 + |
+R + |
+114 + |
+r + |
+
19 + |
+DC3 (Device control 3) + |
+51 + |
+3 + |
+83 + |
+S + |
+115 + |
+s + |
+
20 + |
+DC4 (Device control 4) + |
+52 + |
+4 + |
+84 + |
+T + |
+116 + |
+t + |
+
21 + |
+NAK (Negative acknowledge) + |
+53 + |
+5 + |
+85 + |
+U + |
+117 + |
+u + |
+
22 + |
+SYN (Synchronous suspension) + |
+54 + |
+6 + |
+86 + |
+V + |
+118 + |
+v + |
+
23 + |
+ETB (End of transmission block) + |
+55 + |
+7 + |
+87 + |
+W + |
+119 + |
+w + |
+
24 + |
+CAN (Cancel) + |
+56 + |
+8 + |
+88 + |
+X + |
+120 + |
+x + |
+
25 + |
+EM (End of medium) + |
+57 + |
+9 + |
+89 + |
+Y + |
+121 + |
+y + |
+
26 + |
+SUB (Substitute) + |
+58 + |
+: + |
+90 + |
+Z + |
+122 + |
+z + |
+
27 + |
+ESC (Escape) + |
+59 + |
+; + |
+91 + |
+[ + |
+123 + |
+{ + |
+
28 + |
+FS (File separator) + |
+60 + |
+< + |
+92 + |
+/ + |
+124 + |
+| + |
+
29 + |
+GS (Group separator) + |
+61 + |
+= + |
+93 + |
+] + |
+125 + |
+} + |
+
30 + |
+RS (Record separator) + |
+62 + |
+> + |
+94 + |
+^ + |
+126 + |
+~ + |
+
31 + |
+US (Unit separator) + |
+63 + |
+? + |
+95 + |
+_ + |
+127 + |
+DEL (Delete) + |
+
AOM supports fine-grained log query. It enables you to view logs by bucket to obtain key service data and quickly locate problems.
+The bar chart shows the number of logs that meet the filter criteria set in step 4 at different time points. The horizontal axis represents the time and is divided into 30 identical rectangular blocks. The time of each rectangle block is calculated by dividing the selected time range by 30. For example, if the time range is 30 minutes, the time of each rectangle block is 1 minute. If the time range is 60 minutes, the time of each rectangle block is 2 minutes. The vertical axis represents the number of logs that meet filter criteria.
+
When you hover the mouse pointer over a rectangle block, the time range (including the start time and end time) and the number of logs that meet filter criteria are displayed. When you click a rectangle block, the logs of the rectangle block are displayed in the log list. To deselect the block, click
next to the search box.
The log list displays the details of the logs that meet the filter criteria set in 4.
+
to view the details such as the host IP address and source of a specified log.
in the Collection Time column to change the order. When you click the black triangle icon
to sort logs by time in ascending order, the latest log is displayed at the end. When you click the black triangle icon
to sort logs by time in descending order, the latest log is displayed at the top.
In AOM, a maximum of 1440 data points can be returned for a single metric query. The relationship between the time range and statistical cycle is as follows:
+Maximum time range = Statistical cycle x 1440
+If you select a time range shorter than or equal to the maximum time range, all the statistical cycles that meet the preceding formula can be selected. For example, if you want to query metrics in the last hour, the available statistical cycles are 1 minute and 5 minutes.
+For a dashboard, the relationship between the time range and statistical cycle is shown in the following table.
+ +Time Range + |
+Statistical Cycle + |
+
|---|---|
Last 1 hour + |
+1 minute or 5 minutes + |
+
Last 6 hours + |
+1 minute, 5 minutes, or 1 hour + |
+
Last 1 day + |
+|
Last 1 week + |
+1 hour + |
+
Last 15 days + |
+1 hour + |
+
Last 30 days + |
+
Application Operations Management (AOM) is a one-stop, multi-dimensional O&M management platform for cloud applications. It monitors applications and related cloud resources in real time, collects and associates resource metrics, logs, and events to analyze application health status, and provides flexible alarm reporting and data visualization, helping you detect faults in a timely manner and monitor the running status of applications, resources, and services in real time.
+Specifically, AOM comprehensively monitors and uniformly manages cloud servers, storage devices, networks, web containers, and applications hosted in Docker and Kubernetes, effectively preventing problems, facilitating fault locating, and reducing O&M costs. In addition, AOM provides unified APIs for interconnecting self-developed monitoring or reporting systems. Unlike traditional monitoring systems, AOM monitors services by applications, meeting your requirements for high efficiency and fast iteration. It provides effective IT support for your services, and protects and optimizes your IT assets, enabling you to achieve strategic goals.
+AOM supports services such as Simple Message Notification (SMN), Cloud Trace Service (CTS), and Cloud Container Engine (CCE). You can use them after subscription. For example, after you subscribe to SMN, threshold rule status changes of AOM can be sent to related personnel by email or Short Message Service (SMS) message.
+SMN can push notifications based on your requirements, and end users can receive notifications by SMS message, email, or application. You can also integrate application functions through SMN to reduce system complexity.
+AOM uses the message transmission mechanism provided by SMN. When it is inconvenient for you to query threshold rule status changes in time through AOM, SMN can send the changes to you by email or SMS message in a timely manner. In this way, you can obtain information such as resource running status in real time and take necessary measures to avoid service loss.
+CTS records operations on cloud resources in your account. You can perform security analysis, track resource changes, conduct compliance audits, and locate faults based on operation records. To store operation records for a longer time, you can subscribe to Object Storage Service (OBS) and synchronize operation records to OBS in real time.
+With CTS, you can record operations associated with AOM for later querying, auditing, and backtracking.
+CCE provides high-performance and scalable container service, enabling you to build reliable container clusters based on cloud servers. It integrates network and storage capabilities, and is compatible with Kubernetes and Docker container ecosystems. CCE enables you to create and manage diverse container workloads easily. It also provides efficient O&M capabilities, such as self-healing of container faults, collection of monitoring logs, and auto scaling.
+You can use AOM to monitor applications deployed on CCE.
+Date + |
+Description + |
+
|---|---|
2022-09-29 + |
+Updated the document based on UAT comments: +
|
+
2020-12-31 + |
+This issue is the first official release. + |
+
Resource statuses include Normal, Warning, Abnormal, Deleted, and Silent. Warning, Abnormal, and Silent indicate improper resource running. Analyze and rectify faults according to the following instructions.
+If a minor alarm or warning exists, the resource status is Warning.
+Suggestion: Handle the alarm based on alarm details.
+If a critical or major alarm exists, the resource status is Abnormal.
+Suggestion: Handle the alarm based on alarm details.
+If the ICAgent fails to collect resource metrics, the resource status is Silent. The causes include but are not limited to:
+Suggestion: In the navigation pane, choose Agent Management. On the page that is displayed, check the ICAgent status, as shown in Figure 1. If the status is not Running, the ICAgent has been uninstalled or is abnormal. For details on how to solve the problem, see Table 1.
+ +Status + |
+Suggestion + |
+
|---|---|
Uninstalled + |
+Install the ICAgent by referring to Installing the ICAgent. + |
+
Installing + |
+Wait for about 1 minute to complete the ICAgent installation. + |
+
Installation failed + |
+If the ICAgent fails to be installed, reinstall it. + |
+
Upgrading + |
+Wait for about 1 minute to complete the ICAgent upgrade. + |
+
Upgrade failed + |
+If the ICAgent fails to be upgraded, reinstall it. + |
+
Offline + |
+Check for network faults and rectify such faults. + |
+
Faulty + |
+Contact technical support. + |
+
Suggestion: Check whether your resources can be monitored by AOM. AOM can monitor hosts, Kubernetes containers, and user processes, but does not monitor system processes.
+
NTP Sync Status: indicates whether the local time of the host is synchronized with the NTP server time. The value can be 0 or 1. 0 indicates the synchronized status while 1 indicates the asynchronized status.
+Suggestion: Choose View Management > Metric Monitoring and check the NTP Sync Status metric of the host. If the value of NTP Sync Status is 1, the local time of the host is not synchronized with that of the NTP server. To solve the problem, perform synchronization.
+Suggestions:
+Metrics reflect resource performance data or status. A metric consists of the namespace, dimension, name, and unit. Metrics are classified into system metrics and custom metrics.
+Metric namespaces indicate containers for storing metrics. Metrics in different namespaces are independent of each other so that metrics of different applications will not be aggregated to the same statistics information.
+Metric dimensions indicate the categories of metrics. Each metric has certain features, and a dimension may be considered as a category of relevant features.
+
The dimensions listed in Network Metrics and Dimensions to Service Metrics and Dimensions are the dimensions of metrics collected and reported by the AOM backend. You can select these dimensions when calling APIs. Resources are filtered and displayed by dimensions on the AOM frontend.
+Metric + |
+Description + |
+Value Range + |
+Unit + |
+
|---|---|---|---|
Downlink rate (recvBytesRate) + |
+Inbound network traffic rate of a measured object + |
+≥ 0 + |
+Byte per Second (BPS) + |
+
Downlink rate (recvPackRate) + |
+Number of data packets received by the NIC per second + |
+≥ 0 + |
+Packet per Second (PPS) + |
+
Downlink error rate (recvErrPackRate) + |
+Number of error packets received by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Uplink rate (sendBytesRate) + |
+Outbound network traffic rate of a measured object + |
+≥ 0 + |
+BPS + |
+
Uplink error rate (sendErrPackRate) + |
+Number of error packets sent by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Uplink rate (sendPackRate) + |
+Number of data packets sent by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Total rate (totalBytesRate) + |
+Total inbound and outbound network traffic rate of a measured object + |
+≥ 0 + |
+BPS + |
+
Dimension + |
+Description + |
+
|---|---|
clusterId + |
+Cluster ID + |
+
clustername + |
+Cluster name + |
+
NIC + |
+Network interface card (NIC) + |
+
hostID + |
+Host ID + |
+
hostIP + |
+Host IP address + |
+
nameSpace + |
+Cluster namespace + |
+
netDevice + |
+NIC name + |
+
nodeIP + |
+Host IP address + |
+
nodeName + |
+Host name + |
+
Metric + |
+Description + |
+Value Range + |
+Unit + |
+
|---|---|---|---|
Disk read rate (diskReadRate) + |
+Volume of data read from a disk per second + |
+≥ 0 + |
+KB/s + |
+
Disk write rate (diskWriteRate) + |
+Volume of data written into a disk per second + |
+≥ 0 + |
+KB/s + |
+
Dimension + |
+Description + |
+
|---|---|
clusterId + |
+Cluster ID + |
+
diskDevice + |
+Disk name + |
+
hostID + |
+Host ID + |
+
nameSpace + |
+Cluster namespace + |
+
nodeIP + |
+Host IP address + |
+
nodeName + |
+Host name + |
+
Metric + |
+Description + |
+Value Range + |
+Unit + |
+
|---|---|---|---|
Available disk space (diskAvailableCapacity) + |
+Disk space that has not been used + |
+≥ 0 + |
+MB + |
+
Total disk space (diskCapacity) + |
+Total disk space + |
+≥ 0 + |
+MB + |
+
Disk read/write status (diskRWStatus) + |
+Read/write status of a disk + |
+0 or 1 +
|
+None + |
+
Disk usage (diskUsedRate) + |
+Percentage of the used disk space to the total disk space + |
+≥ 0 + |
+% + |
+
Dimension + |
+Description + |
+
|---|---|
clusterId + |
+Cluster ID + |
+
clusterName + |
+Cluster name + |
+
fileSystem + |
+File system + |
+
hostID + |
+Host ID + |
+
mountPoint + |
+Mount point + |
+
nameSpace + |
+Cluster namespace + |
+
nodeIP + |
+Host IP address + |
+
nodeName + |
+Host name + |
+
Metric + |
+Description + |
+Value Range + |
+Unit + |
+
|---|---|---|---|
Total CPU cores (cpuCoreLimit) + |
+Total number of CPU cores that have been applied for a measured object + |
+≥ 1 + |
+Cores + |
+
Used CPU cores (cpuCoreUsed) + |
+Number of CPU cores used by a measured object + |
+≥ 0 + |
+Cores + |
+
CPU usage (cpuUsage) + |
+CPU usage of a measured object + |
+0%–100% + |
+% + |
+
Available disk space (diskAvailableCapacity) + |
+Disk space that has not been used + |
+≥ 0 + |
+MB + |
+
Total disk space (diskCapacity) + |
+Total disk space + |
+≥ 0 + |
+MB + |
+
Disk read rate (diskReadRate) + |
+Volume of data read from a disk per second + |
+≥ 0 + |
+KB/s + |
+
Disk read/write status (diskRWStatus) + |
+Read/write status of a disk + |
+0 or 1 +
|
+None + |
+
Disk usage (diskUsedRate) + |
+Percentage of the used disk space to the total disk space + |
+≥ 0 + |
+% + |
+
Disk write rate (diskWriteRate) + |
+Volume of data written into a disk per second + |
+≥ 0 + |
+KB/s + |
+
Available physical memory (freeMem) + |
+Available physical memory of a measured object + |
+≥ 0 + |
+MB + |
+
Available virtual memory (freeVirMem) + |
+Available virtual memory of a measured object + |
+≥ 0 + |
+MB + |
+
Physical memory usage (memUsedRate) + |
+Percentage of the used physical memory to the total physical memory + |
+0%–100% + |
+% + |
+
Host status (nodeStatus) + |
+Host status + |
+
|
+None + |
+
NTP offset (ntpOffset) + |
+Offset between the local time of the host and the NTP server time. When the NTP offset is closer to 0, the local time of the host is closer to the time of the NTP server. + |
+None + |
+ms + |
+
NTP server status (ntpServerStatus) + |
+Whether the host is connected to the NTP server + |
+0 or 1 +
|
+None + |
+
NTP sync status (ntpStatus) + |
+Whether the local time of the host is synchronous with the NTP server time + |
+0 or 1 +
|
+None + |
+
Processes (processNum) + |
+Number of processes on a measured object + |
+≥ 0 + |
+None + |
+
Downlink rate (recvBytesRate) + |
+Inbound network traffic rate of a measured object + |
+≥ 0 + |
+Byte per Second (BPS) + |
+
Downlink rate (recvPackRate) + |
+Number of data packets received by the NIC per second + |
+≥ 0 + |
+Packet per Second (PPS) + |
+
Downlink error rate (recvErrPackRate) + |
+Number of error packets received by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Uplink rate (sendBytesRate) + |
+Outbound network traffic rate of a measured object + |
+≥ 0 + |
+BPS + |
+
Uplink error rate (sendErrPackRate) + |
+Number of error packets sent by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Uplink rate (sendPackRate) + |
+Number of data packets sent by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Total rate (totalBytesRate) + |
+Total inbound and outbound network traffic rate of a measured object + |
+≥ 0 + |
+BPS + |
+
Total physical memory (totalMem) + |
+Total physical memory that has been applied for a measured object + |
+≥ 0 + |
+MB + |
+
Total virtual memory (totalVirMem) + |
+Total virtual memory of a measured object + |
+≥ 0 + |
+MB + |
+
Virtual memory usage (virMemUsedRate) + |
+Percentage of the used virtual memory to the total virtual memory + |
+0%–100% + |
+% + |
+
GPU usage (gpuUtil) + |
+GPU usage of a measured object + |
+0%–100% + |
+% + |
+
Dimension + |
+Description + |
+
|---|---|
clusterId + |
+Cluster ID + |
+
clusterName + |
+Cluster name + |
+
gpuName + |
+GPU name + |
+
gpuID + |
+GPU ID + |
+
hostID + |
+Host ID + |
+
nameSpace + |
+Cluster namespace + |
+
nodeIP + |
+Host IP address + |
+
nodeName + |
+Host name + |
+
Metric + |
+Description + |
+Value Range + |
+Unit + |
+
|---|---|---|---|
Total CPU cores (cpuCoreLimit) + |
+Total number of CPU cores that have been applied for a measured object + |
+≥ 1 + |
+Cores + |
+
Used CPU cores (cpuCoreUsed) + |
+Number of CPU cores used by a measured object + |
+≥ 0 + |
+Cores + |
+
CPU usage (cpuUsage) + |
+CPU usage of a measured object + |
+0%–100% + |
+% + |
+
Available disk space (diskAvailableCapacity) + |
+Disk space that has not been used + |
+≥ 0 + |
+MB + |
+
Total disk space (diskCapacity) + |
+Total disk space + |
+≥ 0 + |
+MB + |
+
Disk usage (diskUsedRate) + |
+Percentage of the used disk space to the total disk space + |
+≥ 0 + |
+% + |
+
Available physical memory (freeMem) + |
+Available physical memory of a measured object + |
+≥ 0 + |
+MB + |
+
Available virtual memory (freeVirMem) + |
+Available virtual memory of a measured object + |
+≥ 0 + |
+MB + |
+
Physical memory usage (memUsedRate) + |
+Percentage of the used physical memory to the total physical memory + |
+0%–100% + |
+% + |
+
Downlink rate (recvBytesRate) + |
+Inbound network traffic rate of a measured object + |
+≥ 0 + |
+Byte per Second (BPS) + |
+
Uplink rate (sendBytesRate) + |
+Outbound network traffic rate of a measured object + |
+≥ 0 + |
+BPS + |
+
Total physical memory (totalMem) + |
+Total physical memory that has been applied for a measured object + |
+≥ 0 + |
+MB + |
+
Total virtual memory (totalVirMem) + |
+Total virtual memory of a measured object + |
+≥ 0 + |
+MB + |
+
Virtual memory usage (virMemUsedRate) + |
+Percentage of the used virtual memory to the total virtual memory + |
+0%–100% + |
+% + |
+
GPU usage (gpuUtil) + |
+GPU usage of a measured object + |
+0%–100% + |
+% + |
+
Dimension + |
+Description + |
+
|---|---|
clusterId + |
+Cluster ID + |
+
clusterName + |
+Cluster name + |
+
projectId + |
+Project ID + |
+
Metric + |
+Description + |
+Value Range + |
+Unit + |
+
|---|---|---|---|
Total CPU cores (cpuCoreLimit) + |
+Total number of CPU cores that have been applied for a measured object + |
+≥ 1 + |
+Cores + |
+
Used CPU cores (cpuCoreUsed) + |
+Number of CPU cores used by a measured object + |
+≥ 0 + |
+Cores + |
+
CPU usage (cpuUsage) + |
+Percentage of the used CPU cores to the total CPU cores + |
+0%–100% + |
+% + |
+
Disk read rate (diskReadRate) + |
+Volume of data read from a disk per second + |
+≥ 0 + |
+KB/s + |
+
Disk write rate (diskWriteRate) + |
+Volume of data written into a disk per second + |
+≥ 0 + |
+KB/s + |
+
Available file system (filesystemAvailable) + |
+Available file system capacity of a measured object + |
+≥ 0 + |
+MB + |
+
Total file system (filesystemCapacity) + |
+Total file system capacity of a measured object + |
+≥ 0 + |
+MB + |
+
File system usage (filesystemUsage) + |
+File system usage of a measured object Percentage of the used file system to the total file system This metric is supported only for the containers using the device mapper in the Kubernetes cluster of version 1.11 or later. + |
+0%–100% + |
+% + |
+
Total physical memory (memCapacity) + |
+Total physical memory that has been applied for a measured object + |
+≥ 0 + |
+MB + |
+
Physical memory usage (memUsage) + |
+Percentage of the used physical memory to the total physical memory + |
+0%–100% + |
+% + |
+
Used physical memory (memUsed) + |
+Used physical memory of a measured object + |
+≥ 0 + |
+MB + |
+
Downlink rate (recvBytesRate) + |
+Inbound network traffic rate of a measured object + |
+≥ 0 + |
+Byte per Second (BPS) + |
+
Downlink rate (recvPackRate) + |
+Number of data packets received by the NIC per second + |
+≥ 0 + |
+Packet per Second (PPS) + |
+
Downlink error rate (recvErrPackRate) + |
+Number of error packets received by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Error packets (rxPackErrors) + |
+Number of error packets received by a measured object + |
+≥ 0 + |
+Packets + |
+
Uplink rate (sendBytesRate) + |
+Outbound network traffic rate of a measured object + |
+≥ 0 + |
+BPS + |
+
Uplink error rate (sendErrPackRate) + |
+Number of error packets sent by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Uplink rate (sendPackRate) + |
+Number of data packets sent by the NIC per second + |
+≥ 0 + |
+PPS + |
+
Status (status) + |
+Docker container status + |
+0 or 1 +
|
+None + |
+
GPU usage (gpuUtil) + |
+GPU usage of a measured object + |
+0%–100% + |
+% + |
+
Dimension + |
+Description + |
+
|---|---|
appID + |
+Service ID + |
+
appName + |
+Service name + |
+
clusterId + |
+Cluster ID + |
+
clusterName + |
+Cluster name + |
+
containerID + |
+Container ID + |
+
containerName + |
+Container name + |
+
deploymentName + |
+Kubernetes deployment name + |
+
kind + |
+Application type + |
+
nameSpace + |
+Cluster namespace + |
+
podID + |
+Pod ID + |
+
podName + |
+Pod name + |
+
serviceID + |
+Inventory ID + |
+
Metric + |
+Description + |
+Value Range + |
+Unit + |
+
|---|---|---|---|
Total CPU cores (cpuCoreLimit) + |
+Total number of CPU cores that have been applied for a measured object + |
+≥ 1 + |
+Cores + |
+
Used CPU cores (cpuCoreUsed) + |
+Number of CPU cores used by a measured object + |
+≥ 0 + |
+Cores + |
+
CPU usage (cpuUsage) + |
+Percentage of the used CPU cores to the total CPU cores + |
+0%–100% + |
+% + |
+
Handles (handleCount) + |
+Number of handles used by a measured object + |
+≥ 0 + |
+None + |
+
Total physical memory (memCapacity) + |
+Total physical memory that has been applied for a measured object + |
+≥ 0 + |
+MB + |
+
Physical memory usage (memUsage) + |
+Percentage of the used physical memory to the total physical memory + |
+0%–100% + |
+% + |
+
Used physical memory (memUsed) + |
+Used physical memory of a measured object + |
+≥ 0 + |
+MB + |
+
Status (status) + |
+Process status + |
+0 or 1 +
|
+None + |
+
Threads (threadsCount) + |
+Number of threads used by a measured object + |
+≥ 0 + |
+None + |
+
Total virtual memory (virMemCapacity) + |
+Total virtual memory that has been applied for a measured object + |
+≥ 0 + |
+MB + |
+
Dimension + |
+Description + |
+
|---|---|
appName + |
+Service name + |
+
clusterId + |
+Cluster ID + |
+
clusterName + |
+Cluster name + |
+
nameSpace + |
+Cluster namespace + |
+
processID + |
+Process ID + |
+
processName + |
+Process name + |
+
serviceID + |
+Inventory ID + |
+
Instance metrics consist of container or process metrics. The dimensions of instance metrics are the same as those of container or process metrics. For details, see Container Metrics and Dimensions and Process Metrics and Dimensions.
+For workloads deployed on Cloud Container Engine (CCE), AOM supports drill-down from services to service instances, containers, and processes. For services that directly run on VMs, AOM supports drill-down from services to service instances and processes. In this way, you can implement multi-dimensional monitoring.
+Service metrics consist of instance metrics. The dimensions of service metrics are the same as those of instance metrics. For details, see Instance Metrics and Dimensions.
+Services refer to containers and common processes you deploy. For example, a workload on Cloud Container Engine (CCE) is a service, and the Tomcat running on a VM is also a service.
+The service list displays the type, CPU usage, memory usage, and alarm status of each service, helping you learn services. You can click a service name to learn more information. AOM supports drill-down from a service to a service instance, a container, and then to a process. In this way, you can implement multi-dimensional monitoring.
+If a service name is complex and difficult to identify, add an alias for the service.
+Choose More > Add alias in the Operation column, and specify an alias.
+
Tags are used to identify services. You can distinguish system and non-system services using tags. By default, AOM adds the System Service tag to system services, including icagent, css-defender, nvidia-driver-installer, nvidia-gpu-device-plugin, kube-dns, org.tanukisoftware.wrapper.WrapperSimpleApp, evs-driver, obs-driver, sfs-driver, icwatchdog, and sh. You can click
in the upper right corner to select or deselect Hide system services. You can also customize tags to facilitate service management.
In the service list, choose More > Modify Tag in the Operation column of the service. On the displayed page, click
to enter a tag, and click
and OK. After the tag is added, enter a tag keyword in the search box in the upper right corner of the page to search for services.
in the upper right corner and select or deselect Tag to show or hide them. In the Tags column, use double quotation marks ("") to separate tags. Enter the content in double quotation marks when using tags to search for services.
to switch to the card view or click
to switch to the list.You can select a cluster from the drop-down list above the service list to filter services, or directly enter a service name in the search box to search for a service.
+
To use threshold rules, customize threshold conditions first. If a metric value meets a threshold condition, AOM generates a threshold alarm. If no metric data is reported, AOM generates an insufficient data event.
+AOM is interconnected with Simple Message Notification (SMN). After you set a notification policy on the SMN console, notifications are sent by email or Short Message Service (SMS) message if the threshold rule status (Exceeded, OK, or Insufficient) changes. In this way, you can identify and handle exceptions at the earliest time.
+Select apm for Services that can publish messages to this topic. Otherwise, notifications cannot be sent.
+
For example, enter Monitor_Host_cpuUsage in the Threshold Name text box and select the aom-1 host and then the aom-2 host from the resource tree. In this way, threshold rules Monitor_Host_cpuUsage0 and Monitor_Host_cpuUsage1 will be generated. The former monitors the aom-1 host while the latter monitors the aom-2 host.
+
You can select multiple trigger conditions for a threshold rule. For example, to receive notifications if the threshold status changes to Exceeded, select Threshold crossing. To receive notifications upon any threshold status change, select all trigger conditions.
+
If the CPU usage of a host exceeds 85%, a threshold alarm is generated on the alarm page. You can choose Alarm Center > Alarms in the navigation pane to view the alarm. If the host meets the preset notification policy, an email or SMS message will be sent to the specified recipient.
+
After creating a threshold rule, you can also perform the operations described in Table 1.
+ +Operation + |
+Description + |
+
|---|---|
Modify a threshold rule + |
+Click Modify in the Operation column. + |
+
Delete a threshold rule + |
+
|
+
Search for a threshold rule + |
+Enter a keyword of the threshold rule name in the search box in the upper right corner and click |
+
View a threshold rule + |
+Click |
+
View an alarm + |
+If the metric value of a resource meets a threshold condition in the specified number of consecutive periods, a threshold alarm will be sent. +In the navigation pane, choose Alarm Center > Alarms to view the alarm. + |
+
View an event + |
+During the configured consecutive periods, if no metric data of a resource is reported, an insufficient data event will be sent. +In the navigation pane, choose Alarm Center > Events to view the event. + |
+
The Overview page provides full-link, multi-layer, and one-stop O&M for applications and resources. The following types of graphs are supported: infrastructure monitoring, host monitoring (CPU and memory), service monitoring (CPU and memory), instance monitoring (CPU and memory), host monitoring (disk), host monitoring (network), cluster monitoring (CPU and memory), and cluster monitoring (disk).
+
This area displays infrastructure metrics. You can select one or all clusters to view monitoring information. In the preceding figure, all clusters are selected. The information includes:
+
The information includes:
+
When the value of a metric exceeds a threshold, a red line is displayed in the trend graph, alerting you that such a value needs attention.
+
The information includes:
+
, which can be selected to hide system services.
The information includes:
+
, which can be selected to hide system instances.
The information includes:
+
The information includes:
+
The information includes:
+

The information includes:
+You can also perform the operations described in Table 1.
+ +Operation + |
+Description + |
+
|---|---|
Favorites + |
+Click Add to Favorites in the upper right corner of each monitoring area to move a graph to the Favorites. +Click |
+
Enlarging a metric graph + |
+Click |
+
Drilling down blue texts + |
+Click blue texts, for example, a host name, to drill down to the details page, as shown in the following figure. +
|
+
Each user can create a maximum of two AK/SK pairs. Once they are generated, they are permanently valid.
+
Keep the AK/SK secure.
+AOM displays metric data of each resource on the Metric Monitoring page. You can monitor metric values and trends in real time, add metrics to dashboards, create threshold rules, and export reports for real-time monitoring and correlation analysis.
++
Parameter + |
+Description + |
+
|---|---|
Time Range + |
+Time period when metrics are monitored. + |
+
Statistical Period + |
+Interval at which metric data is collected. + |
+
Statistic + |
+Method used to measure metrics. + NOTE:
+
|
+
You can also perform the operations described in Table 2.
+ +Operation + |
+Description + |
+
|---|---|
Add a metric graph to a dashboard + |
+Click Add to Dashboard to add a metric graph to a dashboard. + |
+
Add a threshold rule for a metric + |
+Click Add to Threshold Rule, set threshold rule parameters, and click Submit to add a threshold rule. + |
+
Export a monitoring report + |
+Click Export Report to export a metric graph as a CSV file to a local PC. + |
+
Set an interpolation mode + |
+By default, AOM uses Null to represent breakpoints in a metric graph, as shown in Figure 1. However, a metric graph with breakpoints is not suitable for reports or presentation. To solve the problem, set the value of Interpolation Mode to 0 or Average to interpolate values. In this way, you can replace the missing metric data and avoid breakpoints. +The value of Interpolation Mode can be Null, 0, or Average. +
|
+
AOM enables you to monitor workloads deployed on Cloud Container Engine (CCE).
+The workload status can be Normal, Abnormal, Warning, Silent, or Deleted. If a workload generates a threshold alarm or is abnormal due to a network exception, host power-off, or shutdown, the workload status becomes Abnormal. For more information, see What Can I Do If Resources Are Not Running Properly?.
+The workload list displays the status, CPU usage, and memory usage of each workload, helping you learn the running status of each workload.
+
Click an instance to monitor information such as resource usage and health status.
+
AOM provides a default view template (Service Template) that can be modified. You can also click the plus sign (+) in
to customize view templates.
You can click
to add a line graph or
to add a digit graph to the view template. You can also delete, move, and copy metric graphs in the view template according to Dashboard.
On the workload details page, choose More > Add To Dashboard in the upper right corner to add the view template to a dashboard for monitoring.
+ICAgent is the collector of AOM. It runs on each host to collect metrics and logs in real time. Before using AOM, install the ICAgent. Otherwise, AOM cannot be used.
+Prerequisite
+Procedure
+
After a cluster is created on the Cloud Container Engine (CCE) console, the system automatically installs the ICAgent on all hosts in the cluster. After the ICAgent is uninstalled, install it again according to the following procedure:
+The ICAgent begins to be installed. Please wait. When the ICAgent status changes from Installing to Running, the ICAgent is successfully installed.
+To ensure better collection experience, AOM will continuously upgrade ICAgent versions. When the system displays a message indicating that a new ICAgent version is available, perform the following operations:
+The ICAgent begins to be upgraded. Please wait. When the ICAgent status changes from Upgrading to Running, the ICAgent is successfully upgraded.
+After the ICAgent is uninstalled from a host, metric and log data is unavailable. Exercise caution when performing this operation.
+The ICAgent begins to be uninstalled. Please wait. When the ICAgent status changes from Uninstalling to Uninstalled, the ICAgent is successfully uninstalled.
+v>^pjAVbs%YYppfWMZpMVP
zN7-GvJe1@PvK*
zUA_>8^#H|$Kfm1jQ=-7If~80N*TSHm{C