This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Overview

1: Server Types
2: Monitoring Metrics
3: ServiceWatch Metrics

Service Overview

MariaDB (DBaaS) is an open-source relational database (RDBMS) with high compatibility with MySQL. Samsung Cloud Platform provides an environment that can automate MariaDB installation and perform management functions for operation through a web-based Console.

MariaDB (DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, it provides an automatic backup feature at user-specified times to prepare for issues with the DB server or data, enabling recovery of data at the desired point in time.

Provided Features

MariaDB (DBaaS) provides the following features.

Auto Provisioning (Auto Provisioning): Allows installation and configuration of Database(DB) via UI, and provides an Active-standby redundancy configuration based on storage replication. * When the active server fails, it automatically fails over to standby.
Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, you can restart if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, the user can manually perform node switching between Active and Standby via a switch‑over.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time windows and storage locations can be set by the user, and additional fees are incurred based on the backup size. * It also provides a recovery function for backed‑up data, so when the user performs a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup save point or a user‑specified point). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour earlier, based on the stored backup and archive files.
Version Management: Provides a version upgrade (Minor) feature based on some functionality improvements and security patches. * Whether to perform a backup for a version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, after which the DB engine is updated.
Replica configuration: Up to five Read Replicas can be configured in the same or different regions for read load balancing and disaster recovery (DR).
Audit configuration: Provides an Audit configuration feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
Parameter management: Performance improvements and security-related DB configuration parameters can be modified.
Service Status Query: Retrieves the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
DB User Management: Query and manage the DB account (user) information registered in the DB.
DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
Archive Management: You can set the Archive file retention period (1 to 35 days) on the DB server and configure the Archive mode (On/Off).
DB Log Export: Through Audit settings, you can export stored logs to the user’s Object Storage.
Migration: Synchronize data in real time with the operational database and support migration using replication without service interruption.
OS Kernel Upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.

Component

MariaDB(DBaaS) provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use it based on the scale of the service they wish to configure.

Engine version

The engine versions supported by MariaDB (DBaaS) are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.

Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.

MariaDB (Community): https://mariadb.org/about/#maintenance-policy

service	Provided version	EOS Date (Samsung Cloud Platform new creation stop date)	EoTS Date (Community technical support end date)
MariaDB (Community)	10.6.5	2026-03-19	2026-07-06
	10.6.9	2026-03-19	2026-07-06
	10.6.10	2026-03-19	2026-07-06
	10.6.12	2026-03-19	2026-07-06
	10.6.14	2026-03-19	2026-07-06
	10.6.15	2026-03-19	2026-07-06
	10.6.16	2026-03-19	2026-07-06
	10.6.17	2026-03-19	2026-07-06
	10.6.19	2026-03-19	2026-07-06
	10.6.22	2026-03-19	2026-07-06
	10.11.8	2027-09 (planned)	2028-02-16
	10.11.9	2027-09 (planned)	2028-02-16
	10.11.13	2027-09 (planned)	2028-02-16
	11.4.7	2028-12 (planned)	2029-05-29

Table. Engine versions offered for MariaDB (DBaaS)

information

The next version of MariaDB is scheduled to be available after July 2026. The actual service delivery schedule is subject to change.

MariaDB 10.11.15
MariaDB 11.4.10

Server type

The server types supported by MariaDB (DBaaS) are as follows.

For detailed information about the server types offered by MariaDB (DBaaS), refer to MariaDB(DBaaS) Server Types.

Standard db1v2m4

Category	Example	Detailed description
Server type	Standard	Provided server types Standard: Standard configuration (vCPU, Memory) commonly used High Capacity: Large server specifications of 24 vCores or more
Server specifications	db1	Provided server specifications db1: Standard specifications (vCPU, Memory) commonly used dbh2: Large-scale server specifications Provides servers with 24 vCores or more
Server specifications	v2	vCore count v2: 2 virtual cores
Server specifications	m4	Memory capacity m4: 4GB Memory

Table. MariaDB (DBaaS) server type components

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

Service Category	service	Detailed description
Networking	VPC	A service that provides an isolated virtual network in a cloud environment

Table. MariaDB (DBaaS) Pre-service

1 - Server Types

MariaDB(DBaaS) server type

MariaDB(DBaaS) provides server types composed of various combinations of CPU, memory, and network bandwidth. When creating a MariaDB(DBaaS), the Database Engine is installed according to the server type selected for the intended use.

The server types supported by MariaDB (DBaaS) are as follows.

Standard db1v2m4

Category	example	Detailed description
Server type	Standard	Provided server type classifications Standard: Configured with commonly used standard specifications (vCPU, Memory) High Capacity: Large-capacity server specifications exceeding Standard
Server specifications	db1	Provided server type classification and generation db1: indicates a standard specification, and 1 denotes the generation dbh2: h indicates a high-capacity server specification, and 2 denotes the generation
Server specifications	v2	Number of vCores v2: 2 virtual cores
Server specifications	m4	Memory capacity m4: 4GB Memory

Table. MariaDB (DBaaS) server type format

db1 server type

The db1 server type of MariaDB(DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
Standard	db1v1m2	1 vCore	2 GB	Up to 10 Gbps
Standard	db1v2m4	2 vCore	4 GB	Up to 10 Gbps
Standard	db1v2m8	2 vCore	8 GB	Up to 10 Gbps
Standard	db1v2m16	2 vCore	16 GB	Up to 10 Gbps
Standard	db1v2m24	2 vCore	24 GB	Up to 10 Gbps
Standard	db1v2m32	2 vCore	32 GB	Up to 10 Gbps
Standard	db1v4m8	4 vCore	8 GB	Up to 10 Gbps
Standard	db1v4m16	4 vCore	16 GB	Up to 10 Gbps
Standard	db1v4m32	4 vCore	32 GB	Up to 10 Gbps
Standard	db1v4m48	4 vCore	48 GB	Up to 10 Gbps
Standard	db1v4m64	4 vCore	64 GB	Up to 10 Gbps
Standard	db1v6m12	6 vCore	12 GB	Up to 10 Gbps
Standard	db1v6m24	6 vCore	24 GB	Up to 10 Gbps
Standard	db1v6m48	6 vCore	48 GB	Up to 10 Gbps
Standard	db1v6m72	6 vCore	72 GB	Up to 10 Gbps
Standard	db1v6m96	6 vCore	96 GB	Up to 10 Gbps
Standard	db1v8m16	8 vCore	16 GB	Up to 10 Gbps
Standard	db1v8m32	8 vCore	32 GB	Up to 10 Gbps
Standard	db1v8m64	8 vCore	64 GB	Up to 10 Gbps
Standard	db1v8m96	8 vCore	96 GB	Up to 10 Gbps
Standard	db1v8m128	8 vCore	128 GB	Up to 10 Gbps
Standard	db1v10m20	10 vCore	20 GB	Up to 10 Gbps
Standard	db1v10m40	10 vCore	40 GB	Up to 10 Gbps
Standard	db1v10m80	10 vCore	80 GB	Up to 10 Gbps
Standard	db1v10m120	10 vCore	120 GB	Up to 10 Gbps
Standard	db1v10m160	10 vCore	160 GB	Up to 10 Gbps
Standard	db1v12m24	12 vCore	24 GB	Up to 12.5 Gbps
Standard	db1v12m48	12 vCore	48 GB	Up to 12.5 Gbps
Standard	db1v12m96	12 vCore	96 GB	Up to 12.5 Gbps
Standard	db1v12m144	12 vCore	144 GB	Up to 12.5 Gbps
Standard	db1v12m192	12 vCore	192 GB	Up to 12.5 Gbps
Standard	db1v14m28	14 vCore	28 GB	Up to 12.5 Gbps
Standard	db1v14m56	14 vCore	56 GB	Up to 12.5 Gbps
Standard	db1v14m112	14 vCore	112 GB	Up to 12.5 Gbps
Standard	db1v14m168	14 vCore	168 GB	Up to 12.5 Gbps
Standard	db1v14m224	14 vCore	224 GB	Up to 12.5 Gbps
Standard	db1v16m32	16 vCore	32 GB	Up to 12.5 Gbps
Standard	db1v16m64	16 vCore	64 GB	Up to 12.5 Gbps
Standard	db1v16m128	16 vCore	128 GB	Up to 12.5 Gbps
Standard	db1v16m192	16 vCore	192 GB	Up to 12.5 Gbps
Standard	db1v16m256	16 vCore	256 GB	Up to 12.5 Gbps

Table. MariaDB (DBaaS) server type specifications - db1 server type

db2 server type

The db2 server type of MariaDB (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
Standard	db2v1m2	1 vCore	2 GB	Up to 10 Gbps
Standard	db2v2m4	2 vCore	4 GB	Up to 10 Gbps
Standard	db2v2m8	2 vCore	8 GB	Up to 10 Gbps
Standard	db2v2m16	2 vCore	16 GB	Up to 10 Gbps
Standard	db2v2m24	2 vCore	24 GB	Up to 10 Gbps
Standard	db2v2m32	2 vCore	32 GB	Up to 10 Gbps
Standard	db2v4m8	4 vCore	8 GB	Up to 10 Gbps
Standard	db2v4m16	4 vCore	16 GB	Up to 10 Gbps
Standard	db2v4m32	4 vCore	32 GB	Up to 10 Gbps
Standard	db2v4m48	4 vCore	48 GB	Up to 10 Gbps
Standard	db2v4m64	4 vCore	64 GB	Up to 10 Gbps
Standard	db2v6m12	6 vCore	12 GB	Up to 10 Gbps
Standard	db2v6m24	6 vCore	24 GB	Up to 10 Gbps
Standard	db2v6m48	6 vCore	48 GB	Up to 10 Gbps
Standard	db2v6m72	6 vCore	72 GB	Up to 10 Gbps
Standard	db2v6m96	6 vCore	96 GB	Up to 10 Gbps
Standard	db2v8m16	8 vCore	16 GB	Up to 10 Gbps
Standard	db2v8m32	8 vCore	32 GB	Up to 10 Gbps
Standard	db2v8m64	8 vCore	64 GB	Up to 10 Gbps
Standard	db2v8m96	8 vCore	96 GB	Up to 10 Gbps
Standard	db2v8m128	8 vCore	128 GB	Up to 10 Gbps
Standard	db2v10m20	10 vCore	20 GB	Up to 10 Gbps
Standard	db2v10m40	10 vCore	40 GB	Up to 10 Gbps
Standard	db2v10m80	10 vCore	80 GB	Up to 10 Gbps
Standard	db2v10m120	10 vCore	120 GB	Up to 10 Gbps
Standard	db2v10m160	10 vCore	160 GB	Up to 10 Gbps
Standard	db2v12m24	12 vCore	24 GB	Up to 12.5 Gbps
Standard	db2v12m48	12 vCore	48 GB	Up to 12.5 Gbps
Standard	db2v12m96	12 vCore	96 GB	Up to 12.5 Gbps
Standard	db2v12m144	12 vCore	144 GB	Up to 12.5 Gbps
Standard	db2v12m192	12 vCore	192 GB	Up to 12.5 Gbps
Standard	db2v14m28	14 vCore	28 GB	Up to 12.5 Gbps
Standard	db2v14m56	14 vCore	56 GB	Up to 12.5 Gbps
Standard	db2v14m112	14 vCore	112 GB	Up to 12.5 Gbps
Standard	db2v14m168	14 vCore	168 GB	Up to 12.5 Gbps
Standard	db2v14m224	14 vCore	224 GB	Up to 12.5 Gbps
Standard	db2v16m32	16 vCore	32 GB	Up to 12.5 Gbps
Standard	db2v16m64	16 vCore	64 GB	Up to 12.5 Gbps
Standard	db2v16m128	16 vCore	128 GB	Up to 12.5 Gbps
Standard	db2v16m192	16 vCore	192 GB	Up to 12.5 Gbps
Standard	db2v16m256	16 vCore	256 GB	Up to 12.5 Gbps

Table. MariaDB (DBaaS) server type specifications - db2 server type

dbh2 server type

The dbh2 server type of MariaDB (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.

Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Networking speed up to 25 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
High Capacity	dbh2v24m48	24 vCore	48 GB	Maximum 25 Gbps
High Capacity	dbh2v24m96	24 vCore	96 GB	Maximum 25 Gbps
High Capacity	dbh2v24m192	24 vCore	192 GB	Maximum 25 Gbps
High Capacity	dbh2v24m288	24 vCore	288 GB	Maximum 25 Gbps
High Capacity	dbh2v32m64	32 vCore	64 GB	Up to 25 Gbps
High Capacity	dbh2v32m128	32 vCore	128 GB	Maximum 25 Gbps
High Capacity	dbh2v32m256	32 vCore	256 GB	Maximum 25 Gbps
High Capacity	dbh2v32m384	32 vCore	384 GB	Maximum 25 Gbps
High Capacity	dbh2v48m192	48 vCore	192 GB	Maximum 25 Gbps
High Capacity	dbh2v48m576	48 vCore	576 GB	Maximum 25 Gbps
High Capacity	dbh2v64m256	64 vCore	256 GB	Up to 25 Gbps
High Capacity	dbh2v64m768	64 vCore	768 GB	Up to 25 Gbps
High Capacity	dbh2v72m288	72 vCore	288 GB	Up to 25 Gbps
High Capacity	dbh2v72m864	72 vCore	864 GB	Maximum 25 Gbps
High Capacity	dbh2v96m384	96 vCore	384 GB	Up to 25 Gbps
High Capacity	dbh2v96m1152	96 vCore	1152 GB	Up to 25 Gbps
High Capacity	dbh2v128m512	128 vCore	512 GB	Maximum 25 Gbps
High Capacity	dbh2v128m1536	128 vCore	1536 GB	Maximum 25 Gbps

Table. MariaDB (DBaaS) server type specifications - dbh2 server type

2 - Monitoring Metrics

Cloud Monitoring service termination notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

Guide to Applying Monitoring Service by Resource
- New Resources: Resources created after the service improvement work in March 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
  Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (ex. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for the Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
  - You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.

Offering	Region	Cloud Monitoring console URL
Enterprise	kr-west1	https://console.kr-west1.e.samsungsdscloud.com/console/monitoring
Enterprise	kr-east1	https://console.kr-east1.e.samsungsdscloud.com/console/monitoring
Samsung	kr-west1	https://console.kr-west1.s.samsungsdscloud.com/console/monitoring
Samsung	kr-east1	https://console.kr-east1.s.samsungsdscloud.com/console/monitoring
Sovereign	kr-south1	https://console.kr-south1.g.samsungsdscloud.com/console/monitoring
Sovereign	kr-south2	https://console.kr-south2.g.samsungsdscloud.com/console/monitoring
Sovereign	kr-south3	https://console.kr-south3.g.samsungsdscloud.com/console/monitoring

Table. Cloud Monitoring console URL by region

* Service termination (November 2026 service improvement work)
  * All services of Cloud Monitoring, including the API, will be permanently discontinued.
	  * **After the service ends in November, Cloud Monitoring data cannot be accessed.**     	  * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch can be found in the ServiceWatch Overview.

MariaDB(DBaaS) Monitoring Metrics

The table below shows the performance monitoring metrics for MariaDB (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

The server monitoring metrics for MariaDB (DBaaS) can be found in the Virtual Server Monitoring Metrics guide.

Performance items	Detailed description	unit
Active Locks	Number of Active Locks	cnt
Active Sessions	Number of Active Sessions	cnt
Connection Usage [Total]	DB connection session usage rate	%
Connections	Number of connections	cnt
Connections [MAX]	max connected threads count	cnt
Binary Log Used [MB]	binary log usage	MB
Data Directory Used [MB]	data directory usage	MB
Open Files	Number of open DB files	cnt
Open Files [MAX]	Number of DB files that can be opened	cnt
Open Files Usage	DB file maximum count usage rate	%
Relay Log Used [MB]	relay log usage	MB
Instance Status [PID]	mariadbd process	pid
Safe PID	mariadbd_safe process	pid
Slave Behind Master seconds	Data time difference between Master and Slave (run only on slave)	sec
Tablespace Used	Tablespace usage	MB
Tablespace Used [Total]	Total tablespace usage	MB
Running Threads	running thread count	cnt
Slowqueries	Number of SQL queries running for a long time (over 5 minutes) (by DB)	cnt
Slowqueries [Total]	Number of long-running (5 minutes or more) SQL queries (total)	cnt
Transaction Time [Long]	Maximum transaction execution time	sec
Wait Locks	Number of sessions blocked for more than 60 seconds by lock	cnt

Table. MariaDB(DBaaS) Monitoring Metrics

3 - ServiceWatch Metrics

MariaDB sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.

Reference

For how to view metrics in ServiceWatch, refer to the ServiceWatch guide.

Basic Metrics

The following are the basic metrics for the namespace MariaDB(DBaaS).

The indicators whose names are shown in bold below are the key indicators selected among the basic metrics provided by MariaDB(DBaaS). The key metrics are used to configure the service dashboards that are automatically built for each service in ServiceWatch.

Each metric guides users, through the user guide, on which statistical values are meaningful when querying that metric, and among the meaningful statistics, the values displayed in bold are the primary statistics. In the service dashboard, you can view key metrics using these primary statistical values.

OS Basic Metrics

Category	Performance items	unit	Detailed description	meaningful statistics
CPU	CPU Usage	Percent	CPU usage	Maximum
Disk	Disk Usage	Percent	Disk usage	Maximum
Disk	Disk Write Bytes	Bytes/Second	Write bandwidth (bytes/second) on block device	average maximum minimum
Disk	Disk Read Bytes	Bytes/Second	Read throughput from block device (bytes/second)	average maximum minimum
Disk	Disk Write Requests	Count/Second	Number of write requests on block device (requests per second)	average maximum minimum
Disk	Disk Read Requests	Count/Second	Number of read requests on block device (requests per second)	average maximum minimum
Disk	Average Disk I/O Queue Size	None	Average queue length of requests issued to the block device	average maximum minimum
Disk	Disk I/O Utilization	Percent	The proportion of time the block device actually spent handling I/O operations	average maximum minimum
Memory	Memory Usage	Percent	Memory usage	Maximum
Network	Network In Bytes	Bytes/Second	Received data rate (bytes/second) on the network interface	average maximum minimum
Network	Network Out Bytes	Bytes/Second	Transmitted capacity (bytes/second) on the network interface	average maximum minimum
Network	TCP Connections	Count/Second	Current total number of successfully established TCP connections	average maximum minimum
Network	Network In Packets	Count	Number of packets received on the network interface	average maximum minimum
Network	Network Out Packets	Count	Number of packets transmitted on the network interface	average maximum minimum
Network	Network In Dropped	Count	Number of packet drops received on the network interface	average maximum minimum
Network	Network Out Dropped	Count	Number of packet drops transmitted from the network interface	average maximum minimum
Network	Network In Errors	Count	Number of packet errors received on the network interface	average maximum minimum
Network	Network Out Errors	Count	Number of packet errors transmitted on the network interface	average maximum minimum

Table. OS basic metrics

MariaDB basic metrics

Category	Performance items	unit	Detailed description	meaningful statistics
Activelock	Active locks	Count	Number of transactions in the InnoDB storage engine that have been in lock wait state for 1 minute (60 seconds) or longer.	Total Average Maximum Minimum
Activesession	Active sessions	Count	Number of active sessions	Total Average Maximum Minimum
Activesession	Connection usage	Percent	DB connection session usage rate	Total Average Maximum Minimum
Activesession	Connections	Count	DB connection session	Total Average Maximum Minimum
Activesession	Aborted Connections	Count/Minute	Number of abnormal terminated connections	Total Average Maximum Minimum
Datafile	Current open files	Count	Number of file descriptors opened by the DB	Total Average Maximum Minimum
Datafile	Max open files	Count	Maximum number of file descriptors the DB can open	Total Average Maximum Minimum
Datafile	Open files usage	Percent	DB file maximum count utilization	Total Average Maximum Minimum
InnoDB	InnoDB buffer pool hit ratio	Percent	The ratio of data read directly from memory without accessing the disk	Total Average Maximum Minimum
InnoDB	Innodb row lock wait transactions	Count	Current number of InnoDB transactions waiting for a row lock	Total Average Maximum Minimum
InnoDB	InnoDB row lock time	Milliseconds	Total time waited due to InnoDB row locks (in milliseconds)	Total Average Maximum Minimum
InnoDB	InnoDB deadlocks	Count/Minute	Number of transactions rolled back due to deadlock	Total Average Maximum Minimum
InnoDB	Table lock waits	Count/Minute	Number of waits that occurred to acquire a table lock	Total Average Maximum Minimum
InnoDB	Temp disk tables	Count/Minute	Number of Temp Tables created on disk	Total Average Maximum Minimum
InnoDB	Innodb log waits	Count	Number of times waited to write the redo log to disk	Total Average Maximum Minimum
State	Instance state	None	Check Scalable DB up/down status 1 - Up 0 - Down	-
State	Slave behind master seconds	Seconds	Replica latency (unit: seconds)	Total Average Maximum Minimum
State	Slave io thread running (Replica Only)	None	I/O Thread status 1 - Running 0 - Down	-
State	Slave SQL thread running (Replica Only)	None	SQL Thread status 1 - Running 0 - Down	-
Tablespace	Tablespace used	Megabytes	Tablespace usage	Total Average Maximum Minimum
Tablespace	Tablespace used(TOTAL)	Megabytes	Tablespace usage (total)	Total Average Maximum Minimum
Transactions	Slow queries	Count	Number of queries running longer than 10 seconds	Total Average Maximum Minimum
Transactions	Long transaction time	Seconds	Long Transaction time	Total Average Maximum Minimum
Transactions	Wait locks	Count	Number of sessions waiting for lock	Total Average Maximum Minimum
Transactions	SQL Queries/Minute	Count/Minute	Queries executed per minute	Total Average Maximum Minimum

Table. MariaDB basic metrics