MariaDB Metrics and Insights

The metrics panel combines resource usage with a native-metrics snapshot for each MariaDB instance. Compare connections, activity, and storage to understand workload changes without treating one field as a definitive diagnosis.

Accessing metrics

In the sidebar, click Projects.
Open the desired MariaDB database.
Go to the project's metrics area.
If the project has more than one instance or replica, select the one you want to inspect.

Native metric groups

Group	What it shows	How to interpret it
Health	sample status and current uptime	Uptime describes the current instance; it is not an SLA or availability history.
Connections and threads	current connections, limit, utilization, aborted connections, connected threads, and running threads	Connected threads represent open sessions. Running threads are doing work at that moment and do not equal total connections.
Activity	total queries and client operations, queries per second, bytes received/sent per second, and slow queries	Totals are cumulative counters; per-second fields are rates between samples. None includes query text or parameters.
Read cache	buffer-pool size, data, free space, dirty pages, physical/logical reads, and hit ratio	Measures MariaDB's internal cache. It does not measure the operating system cache. The ratio exists only when enough data is available.
Redo and I/O	log writes, log waits, synchronization operations, and I/O rate, when available	Availability varies by instance capability; missing values remain `null`.
Locks	current waits, total and duration of row-lock waits, and deadlocks	A sustained increase may indicate contention. The snapshot does not identify sessions, users, or queries.
Latency	aggregate average latency, when available	It does not include query text, groupings, or identifiers and does not provide percentiles that were not collected.
Storage	aggregate database size and project storage usage/capacity	Database size may be unavailable without affecting resource metrics. There is no per-table breakdown.
Replication	status, available and expected replicas, and lag in seconds	Fields appear only when the configuration provides the information.

Connected and running threads

These fields answer different questions:

threads_connected: how many sessions are connected, including sessions waiting for work;
threads_running: how many threads are executing work at sample time.

Many connected threads with few running threads may be normal for applications that keep connections open. Review utilization, limit, and activity as well before making a decision.

Current values, counters, and rates

Current value: represents the state of a sample, such as running threads or connection utilization.
Counter: accumulates events since the last restart or reset and ends in _total, such as queries_total.
Rate: represents change between two valid samples and ends in _per_second, such as bytes_sent_per_second.
Ratio: is a fraction from 0 to 1; the Console may display it as a percentage.

After a restart or counter reset, the related rate is Unavailable until two valid samples exist. Zenifra does not display a negative rate or replace a missing value with zero.

Units

Suffix or field	Unit
`_bytes` and `_bytes_total`	integer bytes
`_per_second`	units per second; `_bytes_per_second` fields use bytes per second
`_ms` and `_ms_total`	milliseconds
`_seconds`	seconds
`_ratio`	fraction from `0` to `1`
CPU	CPU cores
Memory	bytes

Last collection and availability

Each snapshot reports two timestamps:

observed_at: when values were observed on the instance;
collected_at: when the snapshot became available for retrieval.

The Console uses Last collection to show the age of the data. The availability state explains snapshot quality:

State	Meaning
Available (`available`)	the sample completed and the expected groups were evaluated; conditional fields may still be `null`.
Partial (`partial`)	only some groups or fields could be obtained.
Stale (`stale`)	a previous valid sample is displayed with its original timestamp; it does not represent current state.
Unavailable (`unavailable`)	no valid sample can be presented at this time.

A null field means the value is unsupported, was not observed, or could not be calculated. Do not interpret null as zero.

Snapshot, not history

Native metrics represent the latest reading for each instance. The current capability returns history: null: it does not provide time-series retention or historical charts. Counters may represent activity accumulated by the instance itself, but that does not turn Zenifra snapshots into queryable history.

For integrations, check the metrics capabilities and contract first. The public endpoints remain:

GET /v1/project/{id}/metrics/capabilities
GET /v1/project/{id}/metrics?instance={instance}