Help Center/ TaurusDB/ User Guide/ RegionlessDB Clusters/ Viewing the Replication Latency and Traffic of a RegionlessDB Cluster
Updated on 2024-11-06 GMT+08:00

Viewing the Replication Latency and Traffic of a RegionlessDB Cluster

After a RegionlessDB cluster is created, you can monitor the database status and performance based on related metrics.

Method 1: Viewing Metrics on the Console

  1. Log in to the management console.
  2. Click in the upper left corner and select the region and project of the primary instance.
  3. Click and select Cloud Eye under Management & Governance.
  4. In the navigation pane, choose Cloud Service Monitoring > GaussDB(for MySQL).
  5. Click in the front of a RegionlessDB cluster. Locate a standby instance and click View Metric in the Operation column.

    • Cloud Eye can monitor performance metrics in the last 1 hour, last 3 hours, last 12 hours, last 24 hours or last 7 days.
      Figure 1 Viewing RegionlessDB metrics
    • For details about metrics supported by RegionlessDB clusters, see Table 1.
      Table 1 RegionlessDB cluster metrics

      Metric ID

      Metric Name

      Description

      Value Range

      Monitored Object

      Monitoring Interval (Raw Data)

      gdb_replication_latency

      GDB Replication Delay

      Data replication latency of the measured object

      ≥0 ms

      RegionlessDB standby instances

      1 minute

      gdb_replication_capacity

      GDB Replication Traffic

      Data replication traffic of the measured object

      ≥0 bytes/s

      RegionlessDB standby instances

      1 minute

      For details about the metrics of primary and standby instances, see section 4.17.3

Method 2: Viewing Metrics Using SQL Commands

Use a MySQL client tool to connect to the GaussDB(for MySQL) instance and run the following command to query the RegionlessDB status:

mysql> select * from information_schema.global_db_status;
Figure 2 Querying the RegionlessDB status

In the command output, each row indicates an instance in the RegionlessDB cluster (the first row indicates the primary instance and other rows indicate the standby instances). For details about the parameters contained in each row, see Table 2.

Table 2 Parameter description

Parameter

Description

HW_REGION

Region code of the standby instance. The first row in the table is the primary instance, and the region code of the primary instance is an empty string.

IS_PRIMARY

Whether the instance is the primary instance. true: it is the primary instance. false: It is the standby instance.

MAX_PERSIST_LSN

Maximum LSN of the current redo logs of the instance that have been persisted to the shared storage.

REPLICATION_LAG_IN_MILLISECONDS

Latency from the time when data is written to the primary instance to the time when data can be read from the standby instance, in ms. The replication latency of the primary instance is 0.

REPLICATION_CAPACITY_IN_MB

Throughput of data replication from the primary instance to a standby instance, in MB/s. The replication throughput of the primary instance is 0.