Skip to main content
Version: dev

Monitoring:MySQL database monitoring

Collect and monitor the general performance Metrics of MySQL database. Support MYSQL5+.

Driver selection

HertzBeat now supports two MySQL query paths:

  • If mysql-connector-j is present in ext-lib, the JVM collector or built-in server collector automatically prefers JDBC.
  • If mysql-connector-j is absent, HertzBeat automatically uses the built-in MySQL query engine. No extra JAR is required.
  • Restart HertzBeat or the standalone JVM collector after adding or removing a JAR in ext-lib.
  • The automatic decision only checks ext-lib. If you want to force one path, set hertzbeat.collector.mysql.query-engine=jdbc, r2dbc, or auto.
Collector package selection

MySQL monitoring supports both JVM and native deployment now.

  • Built-in server collector or JVM collector package: automatically prefers JDBC when mysql-connector-j exists in ext-lib
  • Native collector package: supported when you do not rely on ext-lib and want the built-in MySQL query engine
  • If you explicitly need runtime ext-lib JDBC loading, choose the JVM collector package

Configuration parameter

Parameter nameParameter help description
Monitoring HostMonitored IPV4, IPV6 or domain name. Note⚠️Without protocol header (eg: https://, http://)
Monitoring nameIdentify the name of this monitoring. The name needs to be unique
PortPort provided by the database. The default is 3306
Query timeoutSet the timeout time when SQL query does not respond to data, unit: ms, default: 3000ms
Database nameDatabase instance name, optional
UsernameDatabase connection user name, optional
PasswordDatabase connection password, optional
URLDatabase connection URL,optional,If configured, the database name, user name, password and other parameters in the URL will overwrite the above configured parameters
Collection intervalInterval time of monitor periodic data collection, unit: second, and the minimum interval that can be set is 30 seconds
Whether to detectWhether to detect and check the availability of monitoring before adding monitoring. Adding and modifying operations will continue only after the detection is successful
Description remarksFor more information about identifying and describing this monitoring, users can note information here

Collection Metric

Metric set:basic

Metric nameMetric unitMetric help description
versionnoneDatabase version
portnoneDatabase exposure service port
datadirnoneDatabase storage data disk address
max_connectionsnoneDatabase maximum connections

Metric set:status

Metric nameMetric unitMetric help description
threads_creatednoneMySql created total connections
threads_connectednoneMySql connected connections
threads_cachednoneMySql current cached connections
threads_runningnoneMySql current active connections

Metric set:innodb

Metric nameMetric unitMetric help description
innodb_data_readsnoneinnodb average number of reads from files per second
innodb_data_writesnoneinnodb average number of writes from file per second
innodb_data_readKBinnodb average amount of data read per second
innodb_data_writtenKBinnodb average amount of data written per second