Databases · MySQL / MariaDB
Deep operational coverage across the MySQL family, including Galera and InnoDB Cluster.
SchemaPulse applies the same operational model to MySQL / MariaDB as to every other engine — one console, one policy language for backup and retention, one incident and recommendation pipeline.
MySQL is the engine SchemaPulse covers most deeply. Beyond metrics and slow queries, SchemaPulse understands MySQL topology — Galera and InnoDB Cluster included — and records elections and term changes as reviewable events.
MariaDB is covered as part of the MySQL engine family, sharing the same topology model, incident pipeline and policy language. Where the engines diverge, SchemaPulse follows the engine: backup runs through mariabackup on MariaDB and Percona XtraBackup on MySQL and Percona XtraDB Cluster, with mysqldump available as a logical and fallback path.
Point-in-time recovery works from a base or full backup plus archived binary log segments, replayed forward to the second you select.
Support
Versions and deployment
Supported versions
- MySQL 8.0
- MySQL 8.4 LTS
- MariaDB 10.11
- MariaDB 11.4
Storage targets
- local
- NFS
- S3
- GCS
Topologies
How SchemaPulse sees MySQL / MariaDB
- Standalone
- Replication Cluster
- Galera Cluster
- InnoDB Cluster
Election events and term snapshots are recorded as first-class history, so a failover can be reviewed after the fact rather than reconstructed from logs. MySQL Router reachability is probed on port 6446.
Capabilities
What is covered on MySQL / MariaDB
- Monitoring
- Database and system metrics from a signed agent on each host
- Query Analytics
- Slow queries, query timeline, index reports, background export
- Backup
- Percona XtraBackup — supported MySQL and PXC versions · mariabackup — MariaDB · mysqldump — logical and fallback backup
- Point-in-time recovery
- Base or full backup plus archived binary-log segments, replayed to the selected recovery point.
- Storage targets
- local · NFS · S3 · GCS
- Provisioning
- Terraform and Ansible, with the agent installed as part of the build
- Integrations
- Jira · PagerDuty · Email
Intelligence
What SchemaPulse recommends on for MySQL / MariaDB
- Inefficient or unused indexes
- Slow-query regressions and plan degradation
- Replication lag and replication errors
- Unstable cluster elections
- Backup policies without a successful verification
- Resource saturation trends