Back
Database Management

Reliable database management for modern, high-performance systems.

Back
Data Modernisation

Reliable database management for modern, high-performance systems.

Back
Data Engineering

Reliable database management for modern, high-performance systems.

Back
Analytics & Intelligence

Reliable database management for modern, high-performance systems.

Back
Data Strategy Consulting

Reliable database management for modern, high-performance systems.

MySQL 26.10 Health Monitor in Community Edition: A DBA Walkthrough

Ajay S
Published on
November 20, 2026

MySQL 26.10 brings a built-in MySQL Health Monitor to Community Edition. Until now, the feature was only available on MySQL HeatWave. It watches disk, memory and host resources from inside the server and records what it sees in Performance Schema tables. The same release also adds a four-part version identifier, so you can check the exact build and update level from SQL. We tested both on a Linux host.

At a glance

The October 2026 MySQL releases include 26.10 Innovation, 9.7.4 LTS and 8.4.13 LTS. This post covers two features from the 26.10 line.

FeatureWhat it doesWhere it applies
Health MonitorRecords disk, memory and host measurements in Performance Schema tables, with disk space forecasting.Community Edition. Full metric set on Linux.
VERSION_WITH_UPDATE()Returns the full four-part version, MAJOR.MINOR.PATCH.UPDATE.All platforms. VERSION() keeps its three-part format.

MySQL 26.10 features covered in this post

  • Health Monitor: resource monitoring for disk, memory and host, with disk space forecasting, in Community Edition.
  • VERSION_WITH_UPDATE(): the full MAJOR.MINOR.PATCH.UPDATE version identity.

Checking the exact version

MySQL already had VERSION(), which returns a three-part version such as 26.10.0. VERSION_WITH_UPDATE() returns the full four-part identity. On a build with no update component, the last part shows as 0.

Run the three statements below to compare them.

mysqlMySQL 26.10 test host
mysql> SELECT VERSION();
+------------+
| VERSION()  |
+------------+
| 26.10.0    |
+------------+
1 row in set (0.002 sec)

mysql> SELECT VERSION_WITH_UPDATE();
+-----------------------+
| VERSION_WITH_UPDATE() |
+-----------------------+
| 26.10.0.0             |
+-----------------------+
1 row in set (0.002 sec)

mysql> SELECT @@version_with_update;
+-----------------------+
| @@version_with_update |
+-----------------------+
| 26.10.0.0             |
+-----------------------+
1 row in set (0.000 sec)

The three version checks on the test host: VERSION() returns the three-part value, while VERSION_WITH_UPDATE() and @@version_with_update return the four-part value.

The existing VERSION() and @@version outputs keep their three-part format, so scripts that parse them do not change. A separate query confirms the edition and license. On our test host it returned MySQL Community Server - GPL.

Terminal output of SELECT @@version, @@version_comment and @@license on MySQL 26.10, showing version 26.10.0, MySQL Community Server - GPL and license GPL
Edition and license check on the test host

Turning on Health Monitor

The component is installed like any other MySQL component. After it loads, it appears in mysql.component with the URN file://component_health_monitor.

mysql.component table showing the component_health_monitor row with URN file://component_health_monitor
The Health Monitor component row in mysql.component

Its settings are global variables that start with health_monitor. Run SHOW GLOBAL VARIABLES LIKE 'health_monitor.%'; to list them. On the test host, the disk fallback setting was OFF by default and automatic disk recovery was ON. Check the 26.10 reference manual before you change any of these in production.

SHOW GLOBAL VARIABLES output for health_monitor settings, including disk_fallback_enable OFF and disk_recovery_enable ON
Health Monitor settings on the test host

A short checklist for the whole check is below.

  1. Check the versionRun VERSION_WITH_UPDATE() to get the four-part identity.
  2. Confirm the componentLook for file://component_health_monitor in mysql.component.
  3. Review the settingsList health_monitor.% global variables.
  4. Read device samplesQuery health_block_device for capacity and percent used.
  5. Check the disk metricQuery disk_metric for volume size and used space in MB.
  6. Review the forecastRead the forecast summary once enough samples exist.

A checklist for Health Monitor on a MySQL 26.10 server

Resource and disk monitoring

Health Monitor stores its measurements in Performance Schema tables. The health_block_device table holds one row per device sample, with the device name, timestamp, total bytes, available bytes, percent used and mount point.

mysqlperformance_schema
mysql> SELECT *
    -> FROM performance_schema.health_block_device
    -> ORDER BY TIMESTAMP DESC
    -> LIMIT 5;
| DEVICE    | TIMESTAMP           | TOTAL_BYTES | AVAILABLE_BYTES | USE_PERCENT | MOUNT_POINT    |
| /dev/root | 2026-11-16 10:03:35 | 11263152128 |      4514238464 |       59.92 | /var/lib/mysql |
| /dev/root | 2026-11-16 10:02:34 | 11263152128 |      4514238464 |       59.92 | /var/lib/mysql |
| /dev/root | 2026-11-16 10:01:35 | 11263152128 |      4514238464 |       59.92 | /var/lib/mysql |
| /dev/root | 2026-11-16 10:00:35 | 11263152128 |      4514242560 |       59.92 | /var/lib/mysql |
| /dev/root | 2026-11-16 09:59:35 | 11263152128 |      4514246656 |       59.92 | /var/lib/mysql |
5 rows in set (0.013 sec)

Five device samples from health_block_device on the test host, taken within about four minutes

The Linux root filesystem mounted at /var/lib/mysql showed 59.92% used across five samples taken within about four minutes.

The health_process_memory and health_system_memory tables cover memory. The disk_metric table records the raw volume size and used space in megabytes. On the test host the volume was 10741 MB, with 6436 MB used at the same sample times.

performance_schema.disk_metric output showing volume size 10741 MB and used space 6436 MB at five timestamps
Disk measurements in disk_metric

Disk forecasting builds on those samples. The forecast and summary tables show projected usage and an estimated time to exhaustion. Forecasting needs enough samples before its estimate is useful, so a new server will not show a reliable forecast straight away. For a wider view of recovery planning, see our MySQL backup and recovery webinar.

Limits to know

Health Monitor is fully supported on Linux and partly supported on macOS. It is not supported on Windows in this release. Metrics that are not available on a platform show as NULL in their Performance Schema columns.

PlatformWhat it meansWhat to do instead
LinuxThe full metric set is available, including disk forecasting.Use this platform for the disk and memory checks in this post.
macOSBasic filesystem, memory and CPU measurements only. The vendor reference is not consistent on disk forecasting here.Confirm the metric you need with the reference manual before you rely on it.
WindowsNot supported in this release.Use Linux for Health Monitor checks, or keep your current monitoring tool.

Health Monitor support by platform in MySQL 26.10

Where it fits in a DBA's day

Health Monitor is useful as an early warning, not a replacement for your existing alerting. We would use the disk summary in a daily check, and watch the used-space trend on any volume that holds the data directory or binary logs. For teams that already run DBA managed services, these checks are a good addition to the daily routine. The version function is handy in change tickets and upgrade checks, because it records the exact update level, not just the minor version.

In our view, 26.10 suits teams that want to test new capabilities before production adoption. 9.7 LTS suits teams planning a move to the newer LTS generation after compatibility testing. 8.4 LTS suits teams already standardised on MySQL 8.4 that want maintenance updates without changing release track. Teams that also need replicas for failover can look at our high availability and disaster recovery services.

Wrapping up

Health Monitor and the four-part version identifier are small additions, but they make routine checks in MySQL easier to script. If you want help setting up disk and resource monitoring across your MySQL estate, or a review of how your upgrade path fits your release plan, talk to the Geopits team. You can also book a free database audit to see where your MySQL environment stands today.

For more on tuning MySQL workloads, read how we handled Aurora MySQL query optimization for a client, or see our MySQL performance and security audit on AWS RDS. More posts are on the Geopits blog.

FAQ

  1. Is Health Monitor available in MySQL Community Edition?
    Yes. The 26.10.0 release notes say it is now available in Community Edition, where it was previously only in MySQL HeatWave.
  2. Which platforms does Health Monitor support?
    Linux has the full metric set. macOS has basic measurements. Windows is not supported in this release.
  3. What is the difference between VERSION() and VERSION_WITH_UPDATE()?
    VERSION() returns the three-part compatibility version. VERSION_WITH_UPDATE() returns the four-part MAJOR.MINOR.PATCH.UPDATE identity.
  4. Does disk forecasting need time to produce a result?
    Yes. The forecast uses sampled history, so a new server needs enough samples before its estimate is useful.
  5. Will the version change break scripts that parse VERSION()?
    No. VERSION() and @@version keep their three-part format for compatibility.

Related reading

Sources

MySQL 26.10.0 Release Notes (dev.mysql.com/doc/relnotes/mysql/26.10/en/news-26-10-0.html); MySQL 26.10 Reference Manual, Health Monitor Component (dev.mysql.com/doc/refman/26.10/en/health-monitor-component.html).

Ajay S

Ajay S is a Senior DBA at Geopits and an Oracle Certified MySQL DBA. He works on high-availability database platforms across MySQL, PostgreSQL and MongoDB, including AWS RDS, Amazon Aurora and Azure MySQL, with a focus on upgrades, migrations and production operations.

Our Latest Blogs

From monitoring to modernization, GeoPITS provides expert database management services that enhance performance, strengthen security, and reduce operational costs.

Ready to Transform Your Data?

Geopits works alongside your team as a strategic partner, starting with stabilizing your current databases, then modernizing your data infrastructure, and ultimately helping you unlock the full potential of AI.

170

Happy Clients so far

2100+

Databases Managed

142+

Successful Migrations

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.