This topic describes the Flagship Edition instance workbench overview: fields in Basic Information, Capacity Resources usage and View Capacity Trend, per-tenant QPS, TPS, and average SQL processing time in Key Metrics Monitoring and how to open full monitoring, and replica–node–tenant relationships in the Topology diagram, including switching topology/list views and using Change Configuration.
View basic instance information
After you click a cluster instance name on the instance list page, you enter the instance workbench. The Basic Information section displays the current instance's identity, deployment, specifications, and O&M-related fields in a grid layout (the exact fields shown depend on the console).
Note
Some fields appear only after you enable the corresponding capability or use the related feature. Unconfigured items (such as JVM-dependent services) may show as "Not configured". You can click the edit entry next to them to configure them.
Parameter |
Description |
|---|---|
| ID | The unique identifier of the cluster instance in the console. |
| Type | The instance type, such as Cluster instance (Flagship Edition) for Flagship Edition clusters. |
| Cloud Vendor | The cloud service provider of the instance. |
| Region | The region of the instance. |
| Deployment Mode | The deployment mode of the instance, such as dual-IDC, single-IDC (two replicas), or multi-IDC. |
| Full-featured Replica Nodes | The number of full-featured replica nodes. The console may show the total count and distribution across zones (for example, total count with per-zone distribution). |
| Read-only Replicas | The number of read-only replicas. |
| Zone | The zones involved in the instance, for example multiple zones listed as "Zone I, Zone J". |
| Storage Architecture | The storage architecture of the instance, such as Shared Nothing or Shared Storage. |
| Compute | The compute specification per replica, such as vCPUs and memory (for example, 8 vCPUs and 16 GiB). |
| Storage Disk Type | The data disk storage type or tier shown in the console (for example, ESSD PL1).
|
| IOPS | The IOPS upper limit or reference value related to the storage configuration. Click the information icon next to it for details.
NoteIn the current version, only instances from some cloud vendors, such as Alibaba Cloud, Huawei Cloud, and AWS, support viewing IOPS in the console. |
| Created At (UTC+8) | The time when the instance was created, displayed in the UTC+8 time zone. |
| Database Version | The OceanBase Database version (for example, 4.4.2). |
| Major Compaction (UTC+8) | Daily major compaction settings or entry, displayed in the UTC+8 time zone. Click Actions to initiate major compaction or change the compaction time. For more information, see Major compactions. |
| Tenant Resource Isolation | Whether resource isolation between tenants is enabled. When enabled, you can usually click to view or manage it. |
| Maintenance Window (UTC+8) | The maintenance time window (for example, 3:00–4:00 daily), displayed in the UTC+8 time zone. You can adjust it using the edit icon. |
| JVM-dependent Services | The configuration status of JVM-dependent services (for example, Not configured or Configured). If not configured, click the edit entry to configure them.
NoteThis feature is currently available only to allowlist users. Contact Technical Support if you want to use it. |
| Tag | The number of tags bound to the current instance. Click to manage tags. For more information, see Manage tags. |
View capacity resources
On the instance workbench overview page, the Capacity Resources section shows real-time usage and upper limits of cluster CPU, memory, and storage:
- Each item is shown as "used / total" with a usage percentage and a progress bar (CPU and memory are usually blue; storage may be green; the exact style depends on the console).
- A trend icon may appear next to storage usage to help you quickly see storage changes.
- View Capacity Trend in the section header opens a trend chart or details page for capacity over time.
View key metrics monitoring
The Key Metrics Monitoring section displays recent performance curves for each tenant in the cluster side by side. Common metrics include QPS, TPS, and Average SQL Statement Processing Time:
Monitoring item |
Metric |
Unit |
Description |
|---|---|---|---|
| QPS | sql_all_count | time/s | The number of SQL statements processed per second. |
| TPS | transaction_count | time/s | The number of transactions processed per second. |
| Average SQL Statement Processing Time | sql_all_rt | ms | The average SQL statement processing time. |
View the topology
The Topology on the instance workbench shows the deployment and resource relationships from zone replicas, compute nodes, to tenants in a top-down three-layer structure.
- Click the Tenant drop-down list in the upper-right corner to filter or focus the topology by tenant.
- Click the icon to switch between Topology and List views.
- Click Change Configuration to start reconfiguration on the current page. For more information, see Change instance configuration (pay-as-you-go). For storage capacity, see also Set storage auto-scaling.
Replicas
- Shows replica types that match your deployment mode and labels the zone (for example, Hangzhou Zone I, Hangzhou Zone J).
- Shows node count, node specifications (such as total CPU cores and memory, and allocated CPU/memory), storage total and allocated usage, and other summary information.
Nodes
- Shows each node under a replica (such as node ID or host identifier) and node specifications.
- Progress bars for CPU, memory, and storage show resource usage relative to the node specification.
Tenants
- Shows tenants on the cluster. A tenant row may include running status, resource specifications and used storage, compatibility mode (such as MySQL, Oracle, HBase API, or Table API compatibility mode), parameter template, or workload type (such as OLTP simple transactions or NoSQL).
- Shows tenant replica distribution across zones: primary replica (for example, primary replica I-1 (readable and writable)) and standby replicas (for example, standby replica J-1 (read-only)) and their allocated compute and storage resources, to help you understand cross-zone primary/standby and read/write relationships.