diff --git a/umn/source/_static/images/en-us_image_0000001127059132.png b/umn/source/_static/images/en-us_image_0000001127059132.png deleted file mode 100644 index 81ed5b0..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001127059132.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001127298856.png b/umn/source/_static/images/en-us_image_0000001127298856.png deleted file mode 100644 index e4636cd..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001127298856.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001173095271.png b/umn/source/_static/images/en-us_image_0000001173095271.png deleted file mode 100644 index e173b39..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001173095271.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001173357101.png b/umn/source/_static/images/en-us_image_0000001173357101.png deleted file mode 100644 index 36d0bd6..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001173357101.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001293796118.png b/umn/source/_static/images/en-us_image_0000001293796118.png deleted file mode 100644 index 143baa3..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001293796118.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001880657541.png b/umn/source/_static/images/en-us_image_0000001880657541.png deleted file mode 100644 index d40c7d8..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001880657541.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001570429773.png b/umn/source/_static/images/en-us_image_0000002230396592.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001570429773.png rename to umn/source/_static/images/en-us_image_0000002230396592.png diff --git a/umn/source/adding_risky_operations.rst b/umn/source/adding_risky_operations.rst index f8c79e6..1a250cd 100644 --- a/umn/source/adding_risky_operations.rst +++ b/umn/source/adding_risky_operations.rst @@ -70,12 +70,6 @@ Procedure #. Set the operation type, operation object, and execution result. For details about related parameters, see :ref:`Table 2 `. - - .. figure:: /_static/images/en-us_image_0000001127298856.png - :alt: **Figure 2** Setting the operation type, operation object, and execution result - - **Figure 2** Setting the operation type, operation object, and execution result - .. _dbss_01_0192__table1588718356449: .. table:: **Table 2** Parameters diff --git a/umn/source/best_practices/auditing_an_rds_db_instance_without_agents.rst b/umn/source/best_practices/auditing_an_rds_db_instance_without_agents.rst index 698e599..b523828 100644 --- a/umn/source/best_practices/auditing_an_rds_db_instance_without_agents.rst +++ b/umn/source/best_practices/auditing_an_rds_db_instance_without_agents.rst @@ -25,7 +25,7 @@ This section describes how to audit the security of a relational database instan Solution Architecture --------------------- -The DBSS instance receives the logs sent from databases, such as certain GaussDB(for MySQL) or RDS for MySQL versions, and saves the logs to its log library for security analysis, aggregation statistics, and compliance analysis. +The DBSS instance receives the logs sent from databases, such as certain TaurusDB or RDS for MySQL versions, and saves the logs to its log library for security analysis, aggregation statistics, and compliance analysis. .. figure:: /_static/images/en-us_image_0000001438417909.png @@ -33,19 +33,19 @@ The DBSS instance receives the logs sent from databases, such as certain GaussDB **Figure 1** Auditing an RDS DB instance (without agents) -Take the :ref:`GaussDB(for MySQL) ` database as an example. Assume you need to locate and track internal violations and improper operations in the database to meet compliance requirements. This section describes how to enable the database audit function and check audit results. +Take the TaurusDB database as an example. For details, see :ref:`Table 2 `. Assume you need to locate and track internal violations and improper operations in the database to meet compliance requirements. This section describes how to enable the database audit function and check audit results. .. _dbss_06_0020__en-us_topic_0000001438668561_table79614220126: .. table:: **Table 1** Database example - ============= ================== + ============= ============= Database Type RDS database - Database Type GaussDB(for MySQL) + Database Type TaurusDB Version MySQL 8.0 IP Address 192.168.0.237 Database Port 3306 - ============= ================== + ============= ============= Limitations and Constraints --------------------------- @@ -107,13 +107,12 @@ You can check audit results on the dashboard page, or generate, preview, or down e. Click **OK**. - The **Reports** page will be displayed. You can view the report status on this page. After a report is generated, you can click **Preview** or choose **More** > **Download**. See :ref:`Figure 2 `. + The **Reports** page will be displayed. You can view the report status on this page. After a report is generated, you can click **Preview** or choose **More** > **Download**. .. important:: To preview a report online, use Google Chrome or Mozilla FireFox. - .. _dbss_06_0020__en-us_topic_0000001438668561_en-us_topic_0252967583_fig17206172612245: .. figure:: /_static/images/en-us_image_0000001560437302.png :alt: **Figure 2** Previewing or downloading an audit report diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index b353709..3d9fd62 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -5,40 +5,49 @@ Change History ============== -+-----------------------------------+----------------------------------------------------------------------------------------------------------------+ -| Released On | Description | -+===================================+================================================================================================================+ -| 2025-04-03 | This is the fourth official release. | -| | | -| | Optimized: | -| | | -| | - Changed the database name to MySQL. | -| | - Added the description of the source IP address and source port in :ref:`Adding Audit Scope `. | -| | - Modified the string: Audit Rules. | -| | - Modified the string: Apply for DBSS. | -+-----------------------------------+----------------------------------------------------------------------------------------------------------------+ -| 2024-10-30 | This is the third official release. | -| | | -| | - Modified :ref:`Table 1 `. | -| | - Supported :ref:`Adding an SQL Whitelist `. | -| | - Supported :ref:`Managing an SQL Whitelist `. | -| | | -| | Supported the following database versions: | -| | | -| | - RDS for MySQL 5.6 (5.6.51.1 or later) | -| | - RDS for MySQL 5.7 (5.7.29.2 or later) | -| | - RDS for MySQL 8.0 (8.0.20.3 or later) | -| | - PostgreSQL 14 (14.4 or later) | -| | - PostgreSQL 13 (13.6 or later) | -| | - PostgreSQL 12 (12.10 or later) | -| | - PostgreSQL 11 (11.15 or later) | -| | - PostgreSQL 9.6 (9.6.24 or later) | -| | - PostgreSQL 9.5 (9.5.25 or later) | -| | - SQLServer supports all editions by default. | -+-----------------------------------+----------------------------------------------------------------------------------------------------------------+ -| 2023-05-31 | This is the second official release. | -| | | -| | Added "Best Practices." | -+-----------------------------------+----------------------------------------------------------------------------------------------------------------+ -| 2022-07-30 | This is the first official release. | -+-----------------------------------+----------------------------------------------------------------------------------------------------------------+ ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------+ +| Released On | Description | ++===================================+====================================================================================================================================+ +| 2025-11-18 | This is the sixth official release. | +| | | +| | - Updated :ref:`Viewing Session Distribution `. | +| | - Updated :ref:`Viewing Audit Reports `. | +| | - GaussDB(for MySQL) is renamed TaurusDB. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------+ +| 2025-06-27 | This is the fifth official release. | +| | | +| | - Added the **Exception Client IP Address/IP Address Segment** parameter to :ref:`Adding Risky Operations `. | +| | - Added the description that more than 100 risk detection types are supported in :ref:`Managing Risky Operations `. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------+ +| 2025-04-03 | This is the fourth official release. | +| | | +| | Optimized: | +| | | +| | - Changed the database name to MySQL. | +| | - Added the description of the source IP address and source port in :ref:`Adding Audit Scope `. | +| | - Modified the string: Audit Rules. | +| | - Modified the string: Apply for DBSS. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------+ +| 2024-10-30 | This is the third official release. | +| | | +| | Modified :ref:`Table 1 `. | +| | | +| | Supported the following database versions: | +| | | +| | - RDS for MySQL 5.6 (5.6.51.1 or later) | +| | - RDS for MySQL 5.7 (5.7.29.2 or later) | +| | - RDS for MySQL 8.0 (8.0.20.3 or later) | +| | - PostgreSQL 14 (14.4 or later) | +| | - PostgreSQL 13 (13.6 or later) | +| | - PostgreSQL 12 (12.10 or later) | +| | - PostgreSQL 11 (11.15 or later) | +| | - PostgreSQL 9.6 (9.6.24 or later) | +| | - PostgreSQL 9.5 (9.5.25 or later) | +| | - SQLServer supports all editions by default. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-05-31 | This is the second official release. | +| | | +| | Added "Best Practices." | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------+ +| 2022-07-30 | This is the first official release. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/configuring_alarm_notifications.rst b/umn/source/configuring_alarm_notifications.rst index 6bde599..36adf98 100644 --- a/umn/source/configuring_alarm_notifications.rst +++ b/umn/source/configuring_alarm_notifications.rst @@ -29,12 +29,6 @@ Procedure #. Set alarm notifications. For details about related parameters, see :ref:`Table 1 `. - - .. figure:: /_static/images/en-us_image_0000001173357101.png - :alt: **Figure 1** Configuring alarm notifications - - **Figure 1** Configuring alarm notifications - .. _dbss_01_0239__table29461252153613: .. table:: **Table 1** Alarm notification parameters @@ -42,7 +36,9 @@ Procedure +----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Parameter | Description | Example Value | +============================+=========================================================================================================================================================================================+=======================+ - | Message Notifications | Enables or disables notifications. | |image1| | + | Alarm Notifications | Status of the alarm notification function By default, **Alarm Notifications** is enabled for database audit. You will receive an email when a configured alarm is triggered. | ``-`` | + +----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Alarm Mode | Email notifications are supported currently. | Email Notifications | +----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | SMN Topic | Select an existing topic from the drop-down list or click **View Topic** and create an SMN topic on the displayed page for configuring the terminals for receiving alarm notifications. | ``-`` | | | | | @@ -75,5 +71,3 @@ Procedure +----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ #. Click **Apply**. - -.. |image1| image:: /_static/images/en-us_image_0000001880657541.png diff --git a/umn/source/index.rst b/umn/source/index.rst index a30be43..d808273 100644 --- a/umn/source/index.rst +++ b/umn/source/index.rst @@ -13,7 +13,6 @@ Database Security Service - User Guide enabling_or_disabling_sql_injection_detection adding_risky_operations configuring_privacy_data_protection_rules - sql_whitelist/index viewing_sql_statement_details viewing_session_distribution viewing_the_audit_dashboard diff --git a/umn/source/overview/constraints.rst b/umn/source/overview/constraints.rst index 7f1635c..f3d90d8 100644 --- a/umn/source/overview/constraints.rst +++ b/umn/source/overview/constraints.rst @@ -10,7 +10,7 @@ Database audit is subject to certain constraints. Supported Database Types ------------------------ -The following types of databases on the management console can be audited in out-of-path mode: +Database audit provides the audit function in out-of-path mode for the following databases on the management console: - Relational Database Service (RDS) - Databases built on ECS @@ -26,7 +26,7 @@ The following database versions can be audited. +-----------------------------------+----------------------------------------+ | Database Type | Edition | +===================================+========================================+ - | GaussDB(for MySQL) | MySQL 8.0 | + | TaurusDB | MySQL 8.0 | +-----------------------------------+----------------------------------------+ | RDS for MySQL | - 5.6 (5.6.51.1 or later) | | | - 5.7 (5.7.29.2 or later) | diff --git a/umn/source/overview/dbss.rst b/umn/source/overview/dbss.rst index 474437c..02cb8a7 100644 --- a/umn/source/overview/dbss.rst +++ b/umn/source/overview/dbss.rst @@ -16,7 +16,7 @@ Database audit provides the audit function in out-of-path mode for the following - Databases built on ECS - Databases built on BMS -Database audit supports the following database types and versions. +Database audit supports the following database types and versions, as shown in :ref:`Table 1 `. .. _dbss_01_0001__table1221454114112: @@ -25,7 +25,7 @@ Database audit supports the following database types and versions. +-----------------------------------+----------------------------------------+ | Database Type | Edition | +===================================+========================================+ - | GaussDB(for MySQL) | MySQL 8.0 | + | TaurusDB | MySQL 8.0 | +-----------------------------------+----------------------------------------+ | RDS for MySQL | - 5.6 (5.6.51.1 or later) | | | - 5.7 (5.7.29.2 or later) | diff --git a/umn/source/overview/functions.rst b/umn/source/overview/functions.rst index 689d400..59521eb 100644 --- a/umn/source/overview/functions.rst +++ b/umn/source/overview/functions.rst @@ -20,7 +20,7 @@ Database audit delivers functions such as user behavior detection and audit, mul - Session analysis - Conducts analysis based on time, user, IP address, and client. + Conducts analysis based on time, database user, and client. - Statement analysis diff --git a/umn/source/sql_whitelist/adding_an_sql_whitelist.rst b/umn/source/sql_whitelist/adding_an_sql_whitelist.rst deleted file mode 100644 index b09b317..0000000 --- a/umn/source/sql_whitelist/adding_an_sql_whitelist.rst +++ /dev/null @@ -1,48 +0,0 @@ -:original_name: dbss_01_0046.html - -.. _dbss_01_0046: - -Adding an SQL Whitelist -======================= - -You can add risky SQL statements to the whitelist. The SQL statements in the whitelist will be ignored during the audit. - -Constraints and Limitations ---------------------------- - -The risky SQL statements can be added to the whitelist in data reports. - -Adding Scanned SQL Statements ------------------------------ - -#. Log in to the management console. -#. Select a region, click |image1|, and choose **Security** > **Database Security Service**. The **Dashboard** page is displayed. -#. In the navigation tree on the left, choose **Data Reports**. The **Data Reports** page is displayed. -#. In the **Instance** drop-down list, select the instance whose session information you want to view. -#. Click the **Statements** tab to view risky SQL statements. -#. Add SQL statements to the whitelist. - - - Add a single SQL statement. - - a. Click **Add to Whitelist** in the **Operation** column of the target SQL statement. - b. In the displayed dialog box, select the database and description of the target SQL statement. - c. Click **OK**. - - - Add SQL statements in batches. - - a. Select the target SQL statement and click **One-Click Whitelisting**. - b. In the displayed dialog box, select the database and description of the target SQL statement. - c. Click **OK**. - -Add a customized SQL statement. -------------------------------- - -#. Log in to the management console. -#. Select a region, click |image2|, and choose **Security** > **Database Security Service**. The **Dashboard** page is displayed. -#. In the navigation tree on the left, choose **Audit Rules**. -#. In the **Instance** drop-down list, select the instance whose session information you want to view. -#. Click the **SQL Whitelist** tab and click **Add an SQL whitelist**. -#. In the dialog box that is displayed, enter the **SQL Statement**, **Applied to the Database**, and **Description**. Confirm the settings and click **OK**. - -.. |image1| image:: /_static/images/en-us_image_0000001074398929.png -.. |image2| image:: /_static/images/en-us_image_0000001074398929.png diff --git a/umn/source/sql_whitelist/index.rst b/umn/source/sql_whitelist/index.rst deleted file mode 100644 index ef6f3c7..0000000 --- a/umn/source/sql_whitelist/index.rst +++ /dev/null @@ -1,16 +0,0 @@ -:original_name: dbss_01_0045.html - -.. _dbss_01_0045: - -SQL whitelist -============= - -- :ref:`Adding an SQL Whitelist ` -- :ref:`Managing an SQL Whitelist ` - -.. toctree:: - :maxdepth: 1 - :hidden: - - adding_an_sql_whitelist - managing_an_sql_whitelist diff --git a/umn/source/sql_whitelist/managing_an_sql_whitelist.rst b/umn/source/sql_whitelist/managing_an_sql_whitelist.rst deleted file mode 100644 index 1f82a97..0000000 --- a/umn/source/sql_whitelist/managing_an_sql_whitelist.rst +++ /dev/null @@ -1,41 +0,0 @@ -:original_name: dbss_01_0047.html - -.. _dbss_01_0047: - -Managing an SQL Whitelist -========================= - -You can edit, disable, and delete the added SQL statement whitelist. - -Prerequisites -------------- - -The SQL statement to be associated has been added to the whitelist. - -Procedure ---------- - -#. Log in to the management console. -#. Select a region, click |image1|, and choose **Security** > **Database Security Service**. The **Dashboard** page is displayed. -#. In the navigation tree on the left, choose **Audit Rules**. -#. In the **Instance** drop-down list, select the instance whose session information you want to view. -#. Click the **SQL Whitelist** tab to view all SQL statement whitelists. -#. Manage the whitelist. - - - Click **Edit** in the **Operation** column of the target SQL statement to modify the description and applied database. - - - Click **Disable** in the **Operation** column of the target SQL statement. The disabled statement does not execute the rule in the audit. - - .. note:: - - After the SQL statement is disabled, there is a delay of about 1 minute. - - - Click **Delete** in the **Operation** column of the target SQL statement. The deleted SQL statement cannot be restored. You can only add the SQL statement to the whitelist again. The SQL statement will be scanned again. - - To delete multiple SQL statements from the whitelist, select the SQL statements to be deleted, click **Delete All** and confirm the deletion. - - .. note:: - - After the SQL whitelist is modified, the modification does not take effect on the audited data. - -.. |image1| image:: /_static/images/en-us_image_0000001074398929.png diff --git a/umn/source/step_1_add_a_database.rst b/umn/source/step_1_add_a_database.rst index bd802be..7132759 100644 --- a/umn/source/step_1_add_a_database.rst +++ b/umn/source/step_1_add_a_database.rst @@ -35,15 +35,15 @@ Adding a Database .. table:: **Table 1** Parameters - +-----------------------+-------------------------------------------------------------+-----------------------+ - | Parameter | Description | Example Value | - +=======================+=============================================================+=======================+ - | Database Type | Supported database type. You can select RDS. | RDS database | - +-----------------------+-------------------------------------------------------------+-----------------------+ - | Type | Supported database type. You can select GaussDB(for MySQL). | GaussDB(for MySQL) | - | | | | - | | You do not need to install an agent on the database. | | - +-----------------------+-------------------------------------------------------------+-----------------------+ + +-----------------------+------------------------------------------------------+-----------------------+ + | Parameter | Description | Example Value | + +=======================+======================================================+=======================+ + | Database Type | Supported database type. You can select RDS. | RDS database | + +-----------------------+------------------------------------------------------+-----------------------+ + | Type | Supported database type. You can select TaurusDB. | TaurusDB | + | | | | + | | You do not need to install an agent on the database. | | + +-----------------------+------------------------------------------------------+-----------------------+ #. Click **OK**. A database whose **Audit Status** is **Disabled** is added to the database list. You do not need to manually install the agent. diff --git a/umn/source/viewing_audit_reports.rst b/umn/source/viewing_audit_reports.rst index 5c067d3..19afffc 100644 --- a/umn/source/viewing_audit_reports.rst +++ b/umn/source/viewing_audit_reports.rst @@ -53,6 +53,8 @@ You can generate reports immediately or periodically. You can also customize the #. Select a region, click |image1|, and choose **Security** > **Database Security Service**. The **Dashboard** page is displayed. +#. In the navigation tree on the left, choose **Reports**. + #. In the **Instance** drop-down list, select the instance whose instance report you want to generate. #. Click the **Report Management** tab. @@ -85,18 +87,18 @@ You can generate reports immediately or periodically. You can also customize the #. In the **Instance** drop-down list, select the instance for which you want to set a report task. -#. Locate the target template and click **Schedule Task** in the **Operation** column, as shown in :ref:`Figure 3 `. +#. Click the **Report Management** tab. + +#. Locate the target template and click **Schedule Task** in the **Operation** column. - .. _dbss_01_0248__fig17220135462: .. figure:: /_static/images/en-us_image_0000001530872056.png :alt: **Figure 3** Setting a task **Figure 3** Setting a task -#. In the displayed dialog box, set the parameters of the scheduled task, as shown in :ref:`Figure 4 `. For details about related parameters, see :ref:`Table 2 `. +#. In the displayed dialog box, set the parameters of the scheduled task. For details about related parameters, see :ref:`Table 2 `. - .. _dbss_01_0248__fig11222737469: .. figure:: /_static/images/en-us_image_0000001531037008.png :alt: **Figure 4** Setting a scheduled task @@ -162,9 +164,8 @@ Before previewing or downloading an audit report, ensure that its **Status** is #. In the **Instance** drop-down list, select the instance whose report you want to preview or download. -#. Locate the target template, and click **Preview** or **More** > **Download** in the **Operation** column to preview or download the report. See :ref:`Figure 5 `.. +#. Locate the target template, and click **Preview** or **More** > **Download** in the **Operation** column to preview or download the report. - .. _dbss_01_0248__fig161171357132716: .. figure:: /_static/images/en-us_image_0000001581439873.png :alt: **Figure 5** Previewing or downloading an audit report diff --git a/umn/source/viewing_session_distribution.rst b/umn/source/viewing_session_distribution.rst index 976f066..a6922d8 100644 --- a/umn/source/viewing_session_distribution.rst +++ b/umn/source/viewing_session_distribution.rst @@ -18,6 +18,7 @@ Procedure #. Log in to the management console. #. Select a region, click |image1|, and choose **Security** > **Database Security Service**. The **Dashboard** page is displayed. +#. In the navigation tree on the left, choose **Data Reports**. The **Data Reports** page is displayed. #. In the **Instance** drop-down list, select the instance whose session information you want to view. #. Click the **Sessions** tab. #. View the session distribution chart. diff --git a/umn/source/viewing_the_audit_dashboard.rst b/umn/source/viewing_the_audit_dashboard.rst index 458c56a..f294f95 100644 --- a/umn/source/viewing_the_audit_dashboard.rst +++ b/umn/source/viewing_the_audit_dashboard.rst @@ -17,33 +17,14 @@ Procedure --------- #. Log in to the management console. - #. Select a region, click |image1|, and choose **Security** > **Database Security Service**. The **Dashboard** page is displayed. - +#. In the navigation tree on the left, choose **Data Reports**. The **Data Reports** page is displayed. +#. Click the **Trends** tab. The trend analysis page is displayed. #. In the **Instance** drop-down list, select the instance whose audit information you want to view. - #. View the overall audit statistics, risk distribution, session statistics, and SQL distribution. - Select **All databases** or a specified database from the **Database** drop-down list to view the statistics about all databases in the instance or a specified database. - Select **Last 30 minutes**, **1 hour**, **Today**, **7 days**, or **30 days**, or click |image2| to customize start time and end time to view the statistics of the specified time range. - - .. figure:: /_static/images/en-us_image_0000001293796118.png - :alt: **Figure 1** Viewing the audit statistics - - **Figure 1** Viewing the audit statistics - - - .. figure:: /_static/images/en-us_image_0000001173095271.png - :alt: **Figure 2** Risk distribution - - **Figure 2** Risk distribution - - - .. figure:: /_static/images/en-us_image_0000001127059132.png - :alt: **Figure 3** Session statistics - - **Figure 3** Session statistics - .. |image1| image:: /_static/images/en-us_image_0000001074398929.png .. |image2| image:: /_static/images/en-us_image_0000001148018506.png diff --git a/umn/source/viewing_the_system_monitoring.rst b/umn/source/viewing_the_system_monitoring.rst index b76726e..1a9fd68 100644 --- a/umn/source/viewing_the_system_monitoring.rst +++ b/umn/source/viewing_the_system_monitoring.rst @@ -24,7 +24,7 @@ Procedure #. View the system monitoring information. - Select **Last 30 minutes**, **1 hour**, **24 hours**, **7 days**, or **30 days**, or click |image1| to customize start time and end time to view the system monitoring information of the specified time range. + Select **Last 30 minutes**, **1 hour**, **7 days**, or **30 days**, or click |image1| to customize start time and end time to view the system monitoring information of the specified time range. .. figure:: /_static/images/en-us_image_0000001127160302.png diff --git a/umn/source/viewing_tracing_logs.rst b/umn/source/viewing_tracing_logs.rst index d3da0c9..d039443 100644 --- a/umn/source/viewing_tracing_logs.rst +++ b/umn/source/viewing_tracing_logs.rst @@ -12,7 +12,7 @@ Viewing a DBSS Trace on the CTS Console #. Log in to the management console. -#. In the navigation pane on the left, click |image1| and choose **Management & Governance** > **Cloud Trace Service**. +#. Click |image1| in the upper left corner and choose **Mgmt & Deployment** > **Cloud Trace Service**. #. Choose **Trace List** in the navigation pane. @@ -50,5 +50,5 @@ Viewing a DBSS Trace on the CTS Console **Figure 2** Viewing a trace -.. |image1| image:: /_static/images/en-us_image_0000001570429773.png +.. |image1| image:: /_static/images/en-us_image_0000002230396592.png .. |image2| image:: /_static/images/en-us_image_0210925109.png